What is a Flock network audit, and what does a row prove?

Identify what was exported before counting searches

Begin with the report name, exporting organization, date range, filters and column definitions. An organization-focused report and a broader network report may cover different activity. Do not assume the same scope because both files contain agency names and timestamps.

Flock's transparency explanation describes public audit fields including case number, purpose, offense type, anonymized user and searched camera/network counts. It does not establish a universal schema for every export or say that a search count equals the number of returned local images.

Retain the source file and explanatory correspondence when permitted. Record whether the export is complete, filtered, redacted or a screenshot. A precise description such as 'rows in this released export' is easier to support than a claim about all system activity.

Vendor explanation of public audit fields

Los Altos explains why network rows need local context

In its March 9, 2026 message, Los Altos' police chief said a network report produced rows for a period before the city's cameras were installed, and distinguished those rows from searches returning local data. The message also described earlier organization-only reviews. This is the chief's interpretation, not our independent inspection of the underlying audit files.

The research lesson is to check whether local cameras existed during the query period and what the report says about included devices and results. Do not assume another city's export uses the same fields or filters. Ask its custodian to explain the actual file rather than importing an interpretation from this example.

Los Altos: chief's explanation of network and organization audits

Separate the search, its scope and its results

Use this checklist when preparing a spreadsheet or reporting a finding. These are questions to investigate, not a claim that every export contains each field. If a field is unavailable, keep that gap in the conclusion.

A zero, blank and redacted value have different meanings. Obtain the field definition before interpreting any of them. Repeated rows may also need explanation: establish whether they represent distinct requests, separate devices or duplicated records before summing them.

Scroll horizontally to compare all columns.

Use conclusions that match the records

Separate a policy question from an access finding. A broad query could merit review even when the available export does not establish a returned local image. Conversely, a narrow organization report may be insufficient to resolve outside-agency access. State the question the evidence can actually answer.

For a follow-up, name the specific rows and ask what confirms their local scope or result. Avoid publishing plate numbers or unnecessary identifying details merely to show that a file exists. FlockDetour does not hold these audit exports or provide a captured-plate search service; our directory links help identify operators to research.

Please identify the report type, exporting organization, date range, filters, timezone and field definitions for [file/rows]. Please explain which fields establish local-device inclusion and returned local records, and distinguish unavailable values from zero, redacted or not-applicable values.

Request the underlying audit records · Research cross-agency sharing

Related guides

Can other agencies search your city's Flock camera data? · How to request your city's Flock audit logs · How long does Flock keep license plate data? · All guides · Live camera map · Get the app