Agency record
A location disclosed by a government agency in a camera inventory, deployment list, map, or other primary record. Coordinates may be derived from an agency-supplied address and are labeled when they are.
Washington surveillance transparency
Know what is watching the road.
Flock Blocking brings public records, open mapping, utility-locate evidence, and field observations into one evidence-tagged map of automated surveillance infrastructure.
No plate lookup. No first-party analytics or behavioral tracking. No claim is stronger than its evidence.
—estimated installation sites
—mapped evidence records
—corroborated sites
—Flock-tagged records
—agency-record locations
—WA AGO ALPR registrations
Live research map
Documented surveillance-location evidence
Loading current dataset…
Default view: estimated installation sites. This is not a count of individual cameras. Switch to evidence-record view to inspect the underlying source records.
Methodology
Evidence first, certainty second.
Field confirmed
A location corroborated by direct observation or a geotagged field photograph. This supports physical presence at the observation date, not perpetual operation.
811 installation candidate
A public utility-locate record associated with Flock installation work. It is evidence of planned or performed work, not proof that a camera is currently installed or active.
Crowd mapped
A camera mapped in the OpenStreetMap/DeFlock ecosystem. Useful and often precise, but community-maintained rather than an agency confirmation.
Record derived
A candidate extracted from a released public record that still needs stronger corroboration before being treated as primary-location evidence.
Other
Useful evidence that does not yet fit a stronger category. These records remain visible rather than being silently upgraded or discarded.
Site reconciliation: the default map conservatively groups strong cross-source matches into estimated installation sites while preserving every underlying evidence record. Nearby records from the same source are not merged merely because they are close. An installation site can contain multiple cameras, so site counts are not device counts.
Important: Flock Blocking documents surveillance infrastructure. The project does not provide instructions for damaging, disabling, evading, or interfering with equipment.
Public records campaign
Follow the paper trail.
— requests tracked
— with updates
| Jurisdiction | Status | Latest response | Estimate |
|---|---|---|---|
| Loading… | |||
Why this exists
Public infrastructure should be publicly understandable.
Automated license-plate readers and related camera systems can be difficult to inventory because evidence is scattered across contracts, maps, utility-locate tickets, agency portals, open-data projects, and physical installations. Flock Blocking collects those sources while preserving how each fact was established.
The goal is a useful research record: what was documented, where, by whom, when, and with what level of confidence.
Flock Blocking is an independent research project and is not affiliated with, sponsored by, or endorsed by Flock Safety or any other camera-system vendor.
Source health
Loading…
Automated source checks can fail temporarily. A failed poll does not erase previously collected evidence.
Privacy by design
The public dataset contains surveillance-location research data only. Flock Blocking does not publish Purple's credentials, Gmail contents, private administration data, or license-plate histories, and it does not run first-party analytics or behavioral tracking. Search and filtering happen in your browser. The site is delivered through Cloudflare, and map tiles are requested from OpenStreetMap's tile service; those providers receive ordinary connection metadata needed to deliver their services.