BC + AI

The municipal record

The issues

Artificial intelligence reached Vancouver municipal politics as a set of specific, dated decisions: a system the City already runs, three buildings, one Council vote, and a procurement rule that changes in October. This page is the public record of those decisions, with the source for each one. It says nothing about any candidate.
Checked 2026-09-03

Navigate the record

Jump directly to the policy area you need. Each finding states both what the source establishes and what it does not.

What the City already runs

Municipal AI in Vancouver is not a future question. Three systems are already in public use, and the public record describes them unevenly.

COV-AI-001

01 / 04

The City launched an AI chatbot on vancouver.ca in March 2025 to answer questions when staff are unavailable, with an operating window of 4:30 pm to 8:30 am daily, a feedback survey, and oversight described as sitting with a City AI Advisory Committee.

What this establishes
That the City deployed a public-facing AI system, when, and what it said about oversight.
What it does not establish
The vendor, the underlying model, what happens to what residents type into it, or whether the advisory committee reviewed it before launch.

SourcesCOV-AI-001

COV-AI-002

02 / 04

Council agendas from July and August 2026 carry AI-assisted live transcription. The public link resolves to a vendor-hosted endpoint.

What this establishes
That a visible third-party provider endpoint is in use for Council proceedings.
What it does not establish
The terms of the City agreement, every component in the pipeline, or where the audio and transcripts are stored.

SourcesCOV-AI-002

COV-AI-003

03 / 04

The City Open Data Portal offers an "Explore data with AI" interface over published datasets.

What this establishes
That the interface is publicly available.
What it does not establish
The model behind it or how queries are logged and retained.

SourcesCOV-AI-003

COV-PROC-001

04 / 04

On July 15, 2026 Council approved procurement changes effective October 1, 2026 that eliminate the Bid Committee, raise the permitted sole-source threshold from ten thousand to twenty-five thousand dollars, and move Council from approving individual contract awards within approved budgets to setting strategic direction.

What this establishes
That the approval route for a mid-sized City software purchase changes shortly before the new Council takes office.
What it does not establish
That any particular AI system will be bought this way.

SourcesVAN-PRIV-012

The pattern across all four is the same. The City has said what it deployed. It has said much less about who built it, what it does with resident data, and who reviewed it first.

What has been proposed, and what Council did

Three Vancouver sites appear in the public record in connection with large-scale data-centre development, and one Council motion tested how the City would handle them.

VAN-INFRA-001

01 / 02

A rezoning application at 111 East 5th Avenue and 2060 Quebec Street would allow a bulk data storage use in an existing commercial building. It was received on September 4, 2025. The public question period closed on February 10, 2026. Council referred it toward a public hearing on July 14, 2026. The hearing planned for July 23 did not proceed, because Council referred the matter back to staff on July 21 for additional public consultation, which the City said would not begin until after the election. No rezoning approval is recorded.

What this establishes
The application, its dates, and that it remains undecided and deferred past the election.
What it does not establish
That the site is the same project as any separately announced facility. The July 15 Council motion described the proposal as a TELUS data centre, and TELUS separately announced a Mount Pleasant facility, but no official source reviewed establishes that the two are the same. See conflict CIVIC-CNF-001.

SourcesVAN-INFRA-006VAN-INFRA-007

VAN-INFRA-MOTION

02 / 02

Councillor Lucy Maloney moved Motion 5, "Addressing the Risks of Digital Infrastructure," seconded by Councillor Sean Orr, on July 15, 2026. It proposed seven staff directions on data-centre risk. The official minutes record that the Committee heard twenty-one speakers, all in support. The motion was lost as Vote No. 11790. Councillors Dominato, Kirby-Yung, Klassen, Meiszner, Montague, Zhou, and Mayor Sim were opposed. Councillor Fry was absent for the vote.

What this establishes
The motion text, the speakers heard, the result, and how each member present voted.
What it does not establish
A general position on data centres or on artificial intelligence held by any member. An absence is not a vote for or against. See conflict CIVIC-CNF-004.

SourcesVAN-INFRA-004VAN-INFRA-005

This is the clearest municipal test on record of how a Vancouver Council handles AI infrastructure, which is why the guide returns to it. It is a record of one vote on one motion, and it is treated that way.

What a resident can do today

When a municipal system makes or shapes a decision about you, provincial law sets the floor. The floor is lower than most people assume.

PRIV-NOTICE

01 / 04

The Freedom of Information and Protection of Privacy Act requires a public body to tell you why it is collecting your personal information, under section 27(2), and to make a reasonable effort to keep it accurate, under section 28. You can ask for a correction under section 29, and if the body declines, it must annotate the record.

What this establishes
A right to notice of collection, and a right to correct a record or have your disagreement attached to it.
What it does not establish
A right to an explanation of how an automated system reached a result, or a right to appeal the decision itself.

SourcesVAN-PRIV-001

PRIV-PIA

02 / 04

A public body must complete a privacy impact assessment under section 69(5) before a new system that handles personal information.

What this establishes
That an internal assessment is required.
What it does not establish
That the assessment is published, or that anyone outside the organization sees it. A completed assessment is not a public disclosure. See conflict CIVIC-CNF-002.

SourcesVAN-PRIV-005VAN-PRIV-001

PRIV-RESIDENCY

03 / 04

Amendments in 2021 removed the former broad rule that a public body had to store and access personal information only in Canada. What applies now is a risk-assessment approach for sensitive personal information disclosed for storage outside Canada.

What this establishes
The current statutory position on data residency.
What it does not establish
That a system described as compliant keeps municipal data in Canada. A promise of Canadian residency may exceed what the law requires. See conflict CIVIC-CNF-003.

SourcesVAN-PRIV-007

PRIV-REVIEW

04 / 04

The Office of the Information and Privacy Commissioner can review an access decision.

What this establishes
An independent route to challenge an access refusal.
What it does not establish
A route to challenge the underlying service decision an automated system produced.

SourcesVAN-PRIV-009

A privacy impact assessment is not public disclosure. A correction right is not an appeal. A data-residency statement is not proof of data control. A human somewhere in the workflow is not necessarily meaningful human review. Each of those gaps is something a mayor could choose to close, or choose to leave.

Five tests for large compute

BC + AI has published five questions for any major compute project. They are the questions the guide uses to test what candidates propose, and they are the reason the questionnaire asks what it asks.

  1. 01

    Who owns it?

    Beneficial ownership, the operator, the financier, and who holds the authority to allocate what the facility produces.

    A rezoning names an applicant. It does not necessarily name who ends up controlling the asset.

  2. 02

    What does it consume?

    Electricity, water withdrawal and water consumption as separate figures, cooling, land, and the emissions of building it as well as running it.

    Requested, allocated, contracted, connected, and actually used power are five different numbers. Heat that exists is not heat delivered. Unknown is not zero.

  3. 03

    Who pays for the load?

    Grid, water, sewer, road, emergency, monitoring, and decommissioning costs, identified early, assigned clearly, and secured where necessary.

    The load should pay for the load. Where exactly that assignment lands is a tariff, agreement, and authority question, not a slogan.

  4. 04

    What remains in British Columbia?

    Jobs, procurement, skills, research access, public-interest compute, heat reuse, and tax contribution, each with a baseline, a milestone, reporting, and a remedy when it does not arrive.

    A benefit without a definition, a date, and a consequence is a press release.

  5. 05

    Who has power over the decision?

    Which decisions belong to the City, which to the province, the utility, or a federal regulator, and which require government-to-government work with First Nations.

    A mayor who promises an outcome held by another order of government is promising something they cannot deliver alone.

Published position, from BC + AI public-compute work. Recorded as BCAI-POL-005 and BCAI-POL-006 in the project research.

BC + AI supports serious compute infrastructure in British Columbia and wants researchers, companies, public institutions, and communities here to have access to it. That support is conditional on ownership, consumption, costs, authority, and durable public value being visible. Being pro-building and asking for a signed bill are not in conflict.

First Nations governments and rights holders

The guide keeps municipal engagement, Crown duties, Nation authority, consent, benefits, and information governance distinct.

The Musqueam, Squamish, and Tsleil-Waututh Nations are governments and rights holders, not a stakeholder category. Negotiated benefits do not substitute for rights, title, consultation, accommodation, consent, or a Nation decision. This guide records what candidates say about government-to-government work. It does not determine rights, affected Nations, consultation adequacy, or consent, and it does not carry Nation-controlled information.

What the public record does not settle

A missing public record stays visible as a gap. It is not silently converted into reassurance.

  1. 01

    Which vendor and model sit behind the City chatbot, and what happens to what residents type into it.

  2. 02

    Whether a privacy impact assessment was completed for any of the three systems already in use, and what it found.

  3. 03

    The text of City Privacy By-law 11451, which has not yet been retrieved for this project.

  4. 04

    Whether the East 5th Avenue rezoning and the separately announced Mount Pleasant facility are one project or two.

  5. 05

    How the October 1 procurement changes will apply to software that makes or shapes decisions about residents.