clm-94cc76fe19438872
quantitative
San Francisco's 2019 ordinance did two separate things
Permanent project revision
Revision 2026-08-20-claim-baseline · effective 2026-07-26
Superseded. A later revision exists: 2026-08-21-source-dates →
Created the first structured Evidence Passport with 13 claims and 15 source dossiers.
sha256:b2fefe2599c3b9c32645dc77728c23c5c65944ecf670364856ae7b96973493f5
add /evidencePassport — Added claim-level evidence mapping and source dossiers.add /revisionHistory — Established a permanent, hash-addressed baseline revision.The text below is copied verbatim from the published record. Each claim names the source dossiers that carry it; caveats stay attached to the claim they qualify.
clm-94cc76fe19438872
quantitative
San Francisco's 2019 ordinance did two separate things
clm-a42ca98b7a256bed
descriptive
it barred city departments from using facial recognition
clm-bc3d5da2632f60d6
descriptive
the first US city to do so
clm-dc663d3f6d842a54
descriptive
it required Board of Supervisors approval, with a published impact report and use policy, before any department acquires surveillance technology
clm-18eff2e00ccbc759
quantitative
Proposition E loosened the approval step for police in 2024
clm-0354ba2435c955e6
descriptive
the ban itself stands
clm-6524e69bedc3b0fa
descriptive
The register the law created is real and maintained
clm-e553797fb408c13c
quantitative
the city's own inventory listed 93 surveillance technologies on 1 March 2026
clm-2c5ea063b9293614
quantitative
66% of technologies in use or being procured have a Board-approved policy and 7% a draft reviewed by COIT's Privacy and Surveillance Advisory Board
clm-8f64fc52eed375b1
quantitative
A 2024 lawsuit by the non-profit Secure Justice counted 42 technologies then in use without one
clm-d465f3d7abf3fcfa
descriptive
its police department admitted six breaches of the facial-recognition ban
clm-85e874b2d076708d
descriptive
won a court case because the ordinance grandfathered technology it already had
clm-ef96c3000881e960
descriptive
persuaded voters to grant a year's grace before policies are due
This layer records what is known about each source, what is still missing, and the exact snapshot this page is rendering. A missing date, archive or hash stays visible as missing.
Awaiting operator and domain-expert review; publication of this revision implies neither.
sha256:b2fefe2599c3b9c32645dc77728c23c5c65944ecf670364856ae7b96973493f5
src-ed1c80ba1ea895ffThe authoritative record of passage: 'Ordinance amending the Administrative Code to require that City departments acquiring surveillance technology... submit a Board of Supervisors approved Surveillance Technology Policy'. Sponsors Aaron Peskin, Norman Yee, Shamann Walton, Hillary Ronen, Matt Haney, Ahsha Safai; introduced 29 January 2019; final passage 21 May 2019; the Mayor returned it unsigned on 31 May 2019, which is the enactment date the city records.
src-26841c3bc1a13f76The two mechanisms, in the law's own words. The ban, 19B.2(d): 'it shall be unlawful for any Department to obtain, retain, access, or use: 1) any Face Recognition Technology on City-issued software or a City-issued product or device; or 2) any information obtained from Face Recognition Technology...'. The carve-out, which applies to the ban only: 'For purposes of subsection 19B.2(d) only, City Department and Department shall not include federally-regulated facilities at the Airport or Port.' The rest of 19B.2 carries the separate approval requirement. Caution for a future check: this publisher returned 403 to our fetch, so the provisions are quoted through the search index of the same page rather than read on it.
src-0bf632fc485987d9The first-reading vote: 8-1, with District 2 Supervisor Catherine Stefani dissenting, and the point that the ban reaches city departments only — not personal, business or federal use. Note the limit of the 'first' claim: San Francisco was first to ban government facial recognition, but the acquisition-approval half follows the CCOPS model that Santa Clara County adopted in 2016, so no first is claimed for that mechanism.
src-87955f70d67fad4eThe public artefact the ordinance was supposed to produce, and the reason this entry is publishable: a live, department-by-department register of surveillance technologies with their impact reports and approved policies.
src-f7abebbabd21d41cCarries the entry's figures: 'As of March 1, 2026, 66% of surveillance technologies in use or in the process of being procured have a surveillance technology policy approved by the Board of Supervisors, 7% have a draft policy that has been reviewed by the COIT Privacy and Surveillance Advisory Board.' The same report lists 93 technologies and 58 surveillance technology policies. Two cautions: the 93/58 counts and the 66% share use different denominators and should not be arithmetically reconciled; and the PDF did not yield machine-readable text to this desk, so both figures are cited through the search index of the document. Chapter 19B was amended on 19 January 2025 to require this report twice a year, replacing annual reporting.
src-07caacc4f9685b0cThe one-year mechanism in plain terms: Prop E lets police 'acquire and use new surveillance technology on the public without approval from the Board of Supervisors as long as the department submitted a set of policies governing its use within one year'. Also the money: Chris Larsen $250,000; Daniel Lurie $635,000 including $250,000 from his brother; the police union $50,000; the ACLU $200,000 opposed.
src-d8a7a2184b8196a5Advocacy, cited for two things it states precisely. The grace period: 'the SFPD can use any technology they want for a full year without publishing an official policy about how they'd use the technology or allowing community members to voice their concerns.' And the disputed facial-recognition reading: EFF reports the City Attorney determined Prop E 'would even enable the SFPD to outfit surveillance tools such as drones and surveillance cameras with face recognition technology', while EFF's own position is that the 2019 ban is clear and survives. The entry states only what is checkable in 2026: 19B.2(d) is still in the code and still being litigated as live law.
src-6a2e32bffedf1aebThe second, stronger mechanism, distinct from the one-year grace: Prop E would 'exempt new police drones and surveillance cameras from the city's technology ordinance altogether, meaning those technologies would not require a policy approved by the Board of Supervisors'. Also the campaign total, 'more than $1.4 million', and Chris Larsen as 'one of the measure's chief financiers'.
src-c9a9bf5154912d3bThe result: 'Proposition E was winning with 54.6% of the vote with roughly 37,500 votes still left to count.' The entry says 'more than 54%' rather than a precise certified share, which we did not obtain from the Department of Elections.
src-94bf21a34a0e75ceThe correction that keeps this entry honest. Three activists sued in October 2020 over SFPD's live access to the Union Square Business Improvement District camera network during the George Floyd protests. On 9 February 2022 Judge Richard Ulmer granted the city summary judgment: the ordinance let departments keep using surveillance technology they had used before it passed, and the same cameras had been used at 2019 Pride. Notice of appeal filed 25 March 2022; no final appellate decision was found in this review. So the camera episode is documented, but it did not produce a judicial finding that the ordinance was breached.
src-dcf89f165d829c21The public-records work that surfaced the episode: SFPD 'received a real-time remote link to more than 400 surveillance cameras' operated by the Union Square Business Improvement District, a non-city entity, between 31 May and 7 June 2020.
src-e37b0b3ee391682fThe admitted breaches and the suit. Police 'copped to circumventing the ban six times, blaming two officers for most of the violations'; the non-profit Secure Justice alleges at least six more officers did so 'at least seven other times by asking neighboring agencies to use the technology for them'. The breaches were left out of SFPD's 2023 annual surveillance report, itself a breach of the 2019 ordinance. The suit also identifies 42 technologies deployed without the required disclosures and seven with no annual report. No final judgment was found as of July 2026.
src-725c98dc14f8eb96The live threat to the ordinance as of this review: Supervisor Matt Dorsey introduced legislation to strip the private right of action that lets residents and organisations sue over violations, calling the law 'an onerous mess' that invites 'baseless but costly lawsuits'. The proposal does not touch the facial-recognition ban. Introduced only, not voted, at publication.
src-3ffffa5cfd36a241Currency. What the city is running two years after Prop E: 'Last month, the SFPD recorded a record 700 drone flights — an average of 25 per day', across 98 devices, and 400 privately funded Flock automated plate readers, with Chris Larsen again the main funder.
src-ad4b458fcd853f9eIncluded as context and as a boundary marker, not as an ordinance outcome. SFPD's own audit found the Northern California Regional Intelligence Center and the West States Information Network searched the city's plate-reader data hundreds of times since May 2025, and access was disabled. The rule broken is California's 2015 state law on sharing plate data with federal and out-of-state agencies — not Chapter 19B — so it is deliberately kept out of the entry's impact.