Why "was I near one" is the wrong question
People assume a plate reader works like a radar trap covering everything around it. It does not. It is a fixed camera aimed down one approach of one road, and it captures vehicles moving through that cone.
So there are two very different situations that a normal camera map cannot tell apart:
| Situation | Distance | Captured? |
|---|---|---|
| You drove straight into the lens | 250 m | Very likely |
| You passed the pole travelling away from the lens | 15 m | Unlikely |
| You were on the far carriageway of a divided road | 30 m | Often not |
| You turned off before entering the cone | 90 m | No |
The second row is the one that surprises people. You can pass within a car's length of a plate reader and not be recorded by it, because you were behind it.
The three things that decide it
- Bearing. Which compass direction the lens faces. Recorded for about 95% of mapped US cameras — 136,653 of 143,415.
- Your heading. Whether you drove into that cone or out of it.
- Range. Whether you were close enough for a legible plate. Useful range is typically tens of metres, not hundreds, though it varies with the unit, the lighting and the angle.
Work those three out for a single camera and you have your answer. Doing it by hand for every camera on a commute is impractical, which is the whole reason the app exists.
How the app answers it automatically
Flock Camera runs that calculation continuously while alerts are armed, and writes the result to your History.
- Arm alerts in the Alerts tab and pick a warning distance from 200 m to 1.5 km.
- Drive normally. The app works in the background with the phone in your pocket.
- You get one alert as you come inside your radius — "Camera ahead" — and a second, separate alert if you actually enter the camera's field of view.
- Open History. Every camera you passed is logged with the street, the town, the time, the distance and a "likely captured" marker that is only set when you were both close enough and in front of the lens.
The History tab shows two running totals: how many readers you passed, and how many likely captured you. Those are usually very different numbers, and the gap is the point.
Can you request the actual records?
Sometimes. Because the operating agency is usually a public body, a public-records request can work, though outcomes vary a lot by state and department. Requests are commonly refused under investigative-technique exemptions, and some states specifically shield ALPR data.
A few practical notes:
- Address the request to the agency, not to Flock Safety. The agency is the data controller and the records custodian.
- Cite the specific plate and a narrow date range. Broad requests get refused faster.
- Ask for the audit log of searches involving your plate as well as the reads themselves. Several states require agencies to keep one, and it shows who looked you up and why.
- Move quickly. Retention windows are often short — see how long the data is kept. A request filed after the window has closed returns nothing.
Knowing which cameras you passed, and which of them were facing you, is what makes such a request specific enough to be worth filing.
Know before you pass one.
Flock Camera draws a view cone on every camera with a recorded bearing and warns you before you pass one. Free, with no account.

Last reviewed 2026-08-15. Camera data © OpenStreetMap contributors (ODbL). Flock Camera is an independent project and is not affiliated with or endorsed by Flock Safety, Inc.