Privacy transparency

Flock & ALPR cameras, mapped.

Find cameras for free. Avoid them with BanditKin. Type a city below to see every mapped ALPR camera near you — and which way each one faces.

Public data · OpenStreetMap + EFF Atlas · Community-verified
⛶ Fullscreen
Follow @banditkinapp

Message us cameras to add, corrections, or requests.

From the BanditKin app

Don't just see the cameras. Route around them.

BanditKin's private navigation is built on this same camera data. Plan a drive and it can steer you around the ALPR cameras it knows about — turn by turn, entirely on your device.

BanditKin routing around Flock ALPR cameras with Avoid Flock cameras on — the route detours past cameras facing the path

Avoidance, built into navigation

Switch on Avoid Flock and BanditKin steers your route around the ALPR cameras it knows about — using each camera's field of view, so it only detours when your path would actually cross a camera's view, not when you'd pass behind it. A strength slider sets how wide a berth to give, and if no camera-free route exists it falls back to the normal one. The avoidance is computed on your phone; your route isn't sent to the camera service. It's a privacy choice — avoid being logged by a commercial surveillance network, using public camera data.

See how private navigation works →

It only detours when you'd actually be seen

The route preview says it plainly: "avoids 5 · 6 not facing your path." Cameras aimed away from your route don't trigger a detour — only ones whose approximate field of view your path would cross.

BanditKin field-of-view-aware avoidance: route preview showing avoids 5, 6 not facing your path — only cameras whose view crosses the route trigger a detour
BanditKin recalculating to avoid cameras — drawing a new route around mapped ALPR camera locations

Recalculates around cameras as you drive

Miss a turn and BanditKin recalculates to avoid cameras on the new path — computed on your phone, with your route never sent to the camera service.

Honest when one can't be avoided

"Avoids 8, 1 unavoidable." When there's no camera-free way through, BanditKin says so and takes the best route anyway — it never pretends, and it never strands you.

BanditKin route preview reporting honestly: avoids 8 cameras, 1 unavoidable — with Avoid Flock cameras turned on
BanditKin Maximum camera avoidance dialog: the route may use parking lots or service roads, and the driver must confirm the maneuvers are legal before routing

Maximum avoidance asks first

At the top of the Aggressive Routing slider, a route may use parking lots or service roads. Before it does, you confirm those maneuvers are legal where you are — BanditKin doesn't determine legality; the driver is responsible.

Matte-graphite BanditKin Sentinel roadside-awareness receiver with a wide dark front sensor panel, four small optical receiver windows, windshield cradle, and USB-C cable. Product render.
COMING FROM BANDITKIN

Beyond the plate: meet Sentinel.

Roadside sensing is moving past the license plate. BanditKin Sentinel is a receive-only USB-C accessory — in development and in-house testing — designed to flag supported roadside sensor activity and help you document it. It doesn't jam or identify a specific vendor from a signal.

Background

What are Flock and ALPR cameras?

An automated license-plate reader (ALPR) is a camera paired with software that photographs passing vehicles and reads their license plates. Each read is typically logged with the plate number, a timestamp, the camera's location, and often a photo of the vehicle. Flock Safety is the most widely deployed vendor in the United States; other vendors include Motorola Solutions (Vigilant) and Genetec.

Read the full explainer — what every read captures, who can search it, and SignalTrace, the industry's next step from tracking cars to tracking people →

What they capture

Plate number, date and time, and location of each passing vehicle. Many systems also record a “vehicle fingerprint” — make, type, color, and distinguishing features — even when a plate isn't readable.

How they're deployed

As fixed units on poles and at intersections, or as mobile units mounted on vehicles. Reads are stored in searchable databases, and some vendors let agencies share data across a wider network.

What they're used for

Locating stolen or wanted vehicles, supporting criminal investigations and AMBER or Silver alerts, neighborhood and HOA security, and access, toll, or parking enforcement.

Who operates them

Law enforcement agencies, homeowner associations and neighborhoods, and private businesses. Retention periods for stored reads vary by operator and jurisdiction.

How to read the map

What you're looking at

Each pin is a camera location with a confidence score. Here's how to use it.

Hundreds of Flock and other ALPR camera locations across Cincinnati on the BanditKin map, built from public data
Color = confidence

Green pins are verified or confirmed, amber are listed or corroborated, and red are newly reported and least certain.

Viewing cones

Zoom in and each camera shows its approximate capture zone — the direction it faces, drawn as a translucent wedge, with 360° cameras shown as a circle (about a 75-foot read range). See at a glance which side of the road a camera reads.

Filter by vendor

Toggle Flock, Motorola / Vigilant, Genetec, other, or untagged cameras from the menu to focus the view.

Click for detail

Tap any camera to see its vendor, operator, the agencies that run ALPR in that area (via the EFF Atlas), and the source record on OpenStreetMap.

Report & confirm

Spotted a camera? Add it. Confirm or dispute existing ones with “still here / gone.” Reports are reviewed before they go public.

BanditKin map close-up: a directional ALPR camera's approximate viewing cone drawn as a translucent wedge, and a 360° camera shown as a coverage circle
Sources

Where the data comes from

Locations come from public records and verified community reports. Nothing here is private data.

OpenStreetMap

The location source of truth — roughly 336,000 mapped ALPR cameras, openly licensed and editable by anyone.

EFF Atlas of Surveillance

Cross-references which agencies operate ALPR and which vendor they use, for jurisdiction-level coverage context.

Community reports

New and updated pins, validated by independent confirmations and drive-by corroboration before they appear.

BanditKin settings for the Flock camera overlay, approach alerts, and offline map downloads
FAQ

Questions about the camera map

What is an ALPR or Flock camera?

An automated license-plate reader (ALPR) photographs every passing vehicle's plate, along with the time and location. Flock Safety is the most common vendor in the US; others include Motorola / Vigilant and Genetec.

How accurate are the camera locations?

Pins come from OpenStreetMap — the openly maintained location source of truth — plus community reports that are confirmed by multiple independent users before they appear. Each pin carries a confidence score.

Is this affiliated with Flock Safety or law enforcement?

No. BanditKin is not affiliated with Flock Safety, any camera vendor, or any agency. It is a privacy-transparency tool that documents public infrastructure using public data.

Does using this map share my location?

No. Browsing the map sends nothing identifying. “Near me” uses your device location only to center the map, and any camera report you submit is anonymous — tagged with a random ID, never your identity.

Can I add a camera I've seen?

Yes. Tap the map to report one. New reports stay hidden until they're corroborated by other users or approved, so the public map stays accurate.

Which direction does a Flock camera face?

Zoom into any camera and the map draws its approximate viewing cone — the direction it faces and its capture zone, shown as a translucent wedge (360° cameras show a circle). The direction comes from public map data; the field of view is an approximate, best-case illustration, not an exact measurement.

How far can an ALPR camera read a license plate?

Roughly 75 feet for a typical fixed camera — that's what the viewing cones on the map illustrate. It's an approximate range that varies with the camera, lens, angle, and conditions, so treat the cone as a guide rather than a precise boundary.

Can I route around Flock cameras?

In the BanditKin app, yes. Turn on Avoid Flock and it plans a route around the ALPR cameras it knows about, using each camera's field of view so it only detours when your path would actually cross a camera's view. A slider sets how wide a berth to give, and if no camera-free route exists it falls back to the normal one — computed on your device, as a privacy preference to avoid being logged by a commercial surveillance network.

Want this map in your pocket?

BanditKin puts this same camera map — plus optional Avoid Flock routing — in a private, end-to-end-encrypted app. Use it on your own for navigation, and add your circle when you want. Available now for Android on Google Play.

Get it on Google Play

iPhone: in final testing, App Store release next.

On iPhone? Leave your email and we'll let you know when BanditKin is ready on the App Store. No spam, no sharing.

Thanks — we'll email you when BanditKin for iPhone is ready.

Oops! Something went wrong while submitting the form.

Data: © OpenStreetMap contributors (ODbL) · coverage © EFF Atlas of Surveillance (CC-BY) · plus community-contributed reports. BanditKin is not affiliated with Flock Safety, any vendor, or any agency.

BY STATE

Flock & ALPR cameras by state

Every state has its own page: 145,191 mapped ALPR cameras across all 50 states as of 1 November 2026, each counted inside the state boundary rather than by metro box. Open a state for its largest operators, vendor mix, direction coverage and city-by-city counts.

Alabama

2,981 cameras

Alaska

53 cameras

Arizona

3,106 cameras

Arkansas

1,094 cameras

California

21,105 cameras

Colorado

2,844 cameras

Connecticut

1,034 cameras

Delaware

488 cameras

Florida

9,374 cameras

Georgia

10,326 cameras

Hawaii

66 cameras

Idaho

516 cameras

Illinois

7,585 cameras

Indiana

3,744 cameras

Iowa

1,038 cameras

Kansas

2,045 cameras

Kentucky

1,944 cameras

Louisiana

2,207 cameras

Maine

100 cameras

Maryland

1,002 cameras

Massachusetts

1,180 cameras

Michigan

3,774 cameras

Minnesota

2,048 cameras

Mississippi

1,140 cameras

Missouri

3,432 cameras

Montana

74 cameras

Nebraska

609 cameras

Nevada

978 cameras

New Hampshire

81 cameras

New Jersey

2,416 cameras

New Mexico

1,020 cameras

New York

4,558 cameras

North Carolina

3,879 cameras

North Dakota

604 cameras

Ohio

6,897 cameras

Oklahoma

1,525 cameras

Oregon

544 cameras

Pennsylvania

3,915 cameras

Rhode Island

309 cameras

South Carolina

2,218 cameras

South Dakota

291 cameras

Tennessee

3,656 cameras

Texas

17,328 cameras

Utah

1,227 cameras

Vermont

31 cameras

Virginia

3,417 cameras

Washington

2,487 cameras

West Virginia

248 cameras

Wisconsin

2,193 cameras

Wyoming

460 cameras

State totals are polygon counts and can be compared with each other; city figures on the pages above are bounding-box reads and cannot. Every number is a floor — cameras appear on the map as people map them.