Proton's Flock map preserves a snapshot, not a live camera inventory

Proton is hosting a public Flock surveillance map, giving residents and reporters another way to examine the company's infrastructure. The most consequential qualification is in Proton's own FAQ: the data is a December 2025 snapshot, so devices installed or removed afterwards are not reflected.

CNET's report, published on October 22, 2026 in UTC, says the hosting arrangement was announced on October 21. The new development is preservation of public access. It should not be mistaken for a fresh survey of every camera.

Read status labels as part of a dated record

Proton attributes the locations to security researcher Joshua Michael and describes the map as a mirror of an inventory obtained from Flock's systems. That provenance differs from a map built from volunteer sightings, but neither origin nor a polished interface establishes that each entry is current.

The original project's interface distinguishes active, planned and decommissioned devices. For a reader checking a neighbourhood, those categories describe the record being displayed. An active label in an old snapshot is not independent confirmation that a camera is operating there today. Conversely, a blank area does not prove an absence of surveillance.

Counts also need consistent definitions. An inventory can include cameras alongside other kinds of infrastructure. Comparing an all-device total with a camera-only total without matching dates and categories can create an apparent discrepancy that the comparison itself has not established. This is an editorial caution about interpreting the map, rather than an independent audit of its entries.

CNET reports that a Proton spokesperson said the map would be updated if reliable new data became available. That describes a condition for updates, not a published refresh schedule. The current FAQ's snapshot date remains the useful limit to carry into a local investigation.

Turn a location into a question for the operator

A map entry is a starting point for checking current public records: which agency operates the installation, whether its contract is active, what it collects, and which retention and sharing rules apply. A location alone does not show who searched a vehicle record or whether a particular search was justified.

Our earlier report on Flock's retention and audit changes covers that separate policy layer. It provides background for asking about controls; it does not certify the present configuration of a local agency.

For a wider view, the Atlas of Surveillance documents law-enforcement technology through public records, reporting and other open sources. Its scope includes technologies beyond plate readers, and its own About page displays a data-update date. It can supply context for an agency's purchases, while still requiring attention to when each record was collected.

Proton's hosting makes information easier to keep in public view. Its practical value is strongest when readers retain the date and provenance, then verify the local claim they want to make. The map's continued availability and the current state of a street are questions answered by different evidence.

Sources

• CNET: hosting report and Proton response

• Proton: map provenance and snapshot limitations

• Flock Surveillance Map: original project interface

• Atlas of Surveillance: scope and methodology