How Many Flock Cameras Watch You in South Jersey? It’s More Than You Think.

By Tom Ritter
Data and AI strategist, producer of the New Jersey Criminal Podcast

Drive from Bridgeton to Vineland, Millville, or Deptford on any given day and you’ll pass them without noticing: small, dark boxes strapped to poles at intersections, shopping center entrances, and neighborhood gateways. These are Flock Safety cameras – a mix of license plate readers and live‑view video – and they are spreading across South Jersey far faster than most people realize.

Flock markets its system as a way to “solve and deter crime.” Their cameras scan plates, log vehicles, and send alerts when a car matches a hotlist. On paper, that sounds simple: stolen cars, warrants, AMBER alerts. In practice, the data from these devices feeds a nationwide, privately run surveillance network that can track where you drive, who you travel with, and what sensitive locations you visit – all without you ever knowing it happened.

I work with data and AI models every day. I’m not guessing about how this infrastructure works – I’ve read the technical documentation, I’ve looked at internal logs from a real‑world deployment in Dunwoody, Georgia, and I’ve spent years helping legal professionals and businesses understand how data systems behave at scale. What I see in the Flock ecosystem should concern anyone who lives, drives, works, or raises children in South Jersey.

This post is written for Bridgeton and the wider South Jersey community, in plain language, to explain:

• >What Flock cameras are actually doing when you drive past them. >What we’ve learned from verified internal logs in Dunwoody, GA. >Why that matters for towns from Bridgeton to Monroe Township. >What citizens, journalists, and local officials should be doing right now.

What Flock Safety Really Is (It’s Not Just “Plate Readers”)

Flock calls itself a “public safety technology ecosystem.” That language is important: it hints at something much bigger than a few cameras on poles.

ALPRs and “vehicle fingerprints”

The devices most people notice are the automatic license plate readers (ALPRs). They:

• >Capture a high‑resolution image of every vehicle that passes. >Read the plate number, timestamp it, and pin it to GPS coordinates. >Tag vehicle attributes: make, model, color, body style, visible damage, roof racks, bumper stickers.

Flock uses this to build what it calls a “vehicle fingerprint.” That means an officer (or any authorized user) can search for:

• >“Blue Honda sedan, roof rack, front‑left damage” – even if they never saw the plate. >“White pickup with ladder rack and black rims seen near a specific address on three different days.”

Technically, this is straightforward computer vision. From a civil‑liberties standpoint, it’s a massive step beyond “we saw this one car once.”

Live‑view cameras on parks, schools, and parking lots

Flock also sells live‑view video cameras. These are often pitched to HOAs, school districts, religious institutions, and businesses as “trespass” or “illegal dumping” solutions. They can be pointed at:

• >Parks and playgrounds. >Shopping center lots. >Church or JCC parking lots. >School driveways and drop‑off areas.

In some towns, so‑called “plate readers” have quietly been upgraded to full live‑view video without any fresh public debate. That’s not hypothetical; we’ve seen exactly that happen in Dunwoody, Georgia, where “LPRs” became full video cameras that could be watched live.

FlockOS: the real power is in the platform

All of this data – plate scans, vehicle fingerprints, live video – flows into Flock’s cloud software, called FlockOS. From a data/AI perspective, think of it as a centralized search engine and analytics layer:

• >Users can query by plate, partial plate, or vehicle fingerprint. >They can see maps of every time and place a vehicle was seen. >They can identify vehicles that frequently appear together (“convoy analysis”). >If live‑view is enabled, they can click into real‑time video streams.

Crucially, Flock encourages agencies – and even private camera owners – to share their networks with each other. So a camera outside a Bridgeton shopping center doesn’t just feed Bridgeton PD. Depending on configuration, it can feed state police, neighboring towns, task forces, and even agencies in other states.

What Dunwoody, GA Taught Us About Flock (With Actual Logs)

One of the strongest examples we have of how Flock behaves in the wild comes from Dunwoody, Georgia. Thanks to a persistent resident using open‑records law, we now have:

• >Flock organization and network audit logs (who searched what and when). >Shared‑network lists (which agencies could see Dunwoody’s data and cameras). >An internal IT security assessment from the city’s own tech department.

Thousands of outside organizations searching one suburb

According to the March 2026 Dunwoody data update on Have I Been Flocked, in one year:

• >About

• ran queries involving Dunwoody’s Flock network. >There were over

• network‑audit records – external entities searching Dunwoody data.

Some of those are neighboring agencies. But the logs also show internal Flock orgs like “Flock Safety – Admins” and “Flock Intelligence” performing hundreds of searches against Dunwoody’s cameras and data.

“Do Not Share” cameras that were shared anyway

The Marcus Jewish Community Center (MJCC) in Dunwoody appears in Flock’s configuration as a private camera network labeled “Do Not Share.” Despite that, the logs and local reporting show:

• >MJCC cameras were shared with outside agencies. >Those agencies had permissions to view live streams, recorded video, and download footage.

A Yahoo News piece describes how Flock “inadvertently shared live footage from the Marcus Jewish Community Center … despite settings meant to prevent sharing,” and notes that this contributed to Dunwoody delaying contract renewals.

Flock employees using Dunwoody as a live testbed

The analysis “The Platform: Flock Safety Is Running on Promises, Not Policy” shows that Flock employees and an internal org called “Flock Intelligence” used Dunwoody’s live‑view network as a sandbox:

• >Running free‑form AI searches like “chicken truck,” “cattle truck,” and “lawnmower.” >Accessing live and recorded cameras across the city, including sensitive locations.

Combined with local reporting from Rough Draft Atlanta and Atl Press Collective, we see a clear pattern:

• >Flock and its internal teams had broad, real‑time access to Dunwoody’s cameras. >Private “Do Not Share” networks like MJCC were not actually protected in practice. >Dunwoody’s council eventually delayed Flock contracts after public backlash.

Dunwoody’s own IT memo, which you can read here, explicitly warns that Flock’s “standing/self‑service sharing model” is intrinsically high‑risk and that misuse controls and audit logging are not as strong as they should be.

Why This Matters in Bridgeton, Millville, Vineland, and Across South Jersey

If you live in Bridgeton or anywhere in Cumberland, Gloucester, or Salem Counties, you might be thinking: “That’s Georgia. We’re different.” But the vendor, the architecture, and the sales pitch are the same.

South Jersey towns are already waking up to the scale of this roll‑out. A South Jersey–focused Instagram reel and Facebook post titled “How many cameras are watching you as you drive?” pointed out that towns here are rapidly installing Flock ALPR cameras “often without any public discussion,” and that these systems feed into a nationwide network, not just the local police server.
(Examples: Instagram, Facebook)

On Reddit, people in r/SouthJersey are asking which towns have the most Flock cameras, and pointing to tools like DeFlock.org and Banish Big Brother’s Flock map to see where these devices already stand.

What we’re seeing here is not “just” Bridgeton PD choosing a camera vendor. It’s:

• >Local plate and video data being plugged into a much larger Flock network. >Potential sharing with neighboring towns, state police, and out‑of‑state agencies. >A vendor that, in at least one city, has used customer networks as a live AI training and testing environment.

As someone who understands how data and AI models exploit whatever input they can get, this is the core issue: once the infrastructure is in place, it will be used for far more than the narrow scenarios sold at the council meeting.

From a Data & AI Perspective: The Real Risks

When you give a vendor like Flock continuous streams of:

• >Where cars go and when. >What vehicles look like and who they travel with. >Live video of public and semi‑private spaces.

you are not just buying “crime‑fighting tools.” You are training and feeding a surveillance platform. A few key risks:

1. Mission creep

Today, the pitch is stolen cars and AMBER alerts. Tomorrow, the same data can be used to:

• >Map who attends protests or political meetings. >Track visits to clinics, recovery centers, or religious institutions. >Build “patterns of life” on entire neighborhoods.

2. Cross‑jurisdictional sharing without real consent

Dunwoody’s logs show thousands of outside entities querying one city’s data. In California, a class action alleges that Flock allowed out‑of‑state and federal agencies to search California drivers’ ALPR data millions of times, potentially violating state law. Once Bridgeton or Millville’s data sits in Flock’s cloud, the real question becomes: who else will be able to access it, today or in five years?

3. Vendor employees in the loop

As Dunwoody demonstrates, it’s not just sworn officers running searches. Flock employees, internal orgs like “Flock Intelligence,” and even engineering and marketing teams have accessed real city networks. That’s not how a truly locked‑down, law‑enforcement‑only system behaves.

4. Security vulnerabilities and live‑feed exposure

WABE recently profiled a Cobb County YouTuber who documented Flock camera vulnerabilities, including accessing a live Flock camera in Brookhaven to record himself – undermining Flock’s public assurances that such access was impossible.
https://www.wabe.org/cobb-county-youtuber-documents-flock-camera-vulnerabilities/

When live feeds of parks, school access roads, or church parking lots can be exposed or mishandled, the risk isn’t theoretical – it’s personal.

What South Jersey Residents Can Do Right Now

If you’re reading this on Bridgeton Beacon, you’re already ahead of the curve. Awareness is the first step. The next steps are concrete and local.

1. Find out where Flock cameras are

• >Use community tools like

• and

• to see where cameras are already deployed. >Pay attention to social posts showing Flock boxes in South Jersey (several reels and posts have already flagged installations along major routes and in certain town centers).

2. Ask your town five specific questions

At the next council meeting, or via email/OPRA, ask:

• >Exactly how long do we retain Flock data (plates and video)? >Which agencies – local, state, out‑of‑state, federal – can:
• >Search our Flock data? >View our live‑view cameras (if any)?
• >Are any private networks (schools, HOAs, churches, JCCs) feeding cameras into the Flock system? >Under what conditions can Flock employees access our data or live feeds? >Can you provide an independent audit of actual usage (who accessed what, when, and under what case number)?

3. Talk to private facilities that use Flock

Many Flock cameras in South Jersey aren’t on municipal poles – they’re on:

• >HOA entrances. >Apartment complexes. >School and camp properties. >Church or synagogue parking lots.

If you sit on a board, attend services, or send your kids to these places, ask:

• >Are our cameras on Flock? >Is our network shared with law enforcement or other entities? >Do we have a written policy on how long data is kept and who can see it?

4. Support local journalists and organizers

The only reason we know what’s happening in Dunwoody is because a resident did the work to pull the logs, and local outlets and projects like Have I Been Flocked? and Rough Draft Atlanta took the time to dig through them. South Jersey needs the same:

• >Encourage Bridgeton Beacon and other local outlets to file OPRA requests for Flock contracts, policies, and logs. >Share episodes like the New Jersey Criminal Podcast’s Flock deep‑dive with neighbors and local officials. >Show up when Flock contracts come up at council meetings – especially when they are framed as “routine upgrades.”

Conclusion: Staying Ahead of a Data Infrastructure We Didn’t Vote On

Flock Safety didn’t arrive in South Jersey as a referendum. It arrived as a budget line, a sales pitch, and a handful of well‑chosen success stories. The deeper you look at how this platform actually works – and at what has already happened in places like Dunwoody – the clearer it becomes that communities like Bridgeton must stay ahead of it.

As someone who works with data and AI every day, my view is simple: if a private company is building a pervasive, searchable history of where we drive and what our public spaces look like, we owe it to ourselves to understand it, question it, and, where necessary, say no.

This isn’t about being anti‑police or anti‑technology. It’s about insisting on transparency, limits, and proof. Until South Jersey towns can show, in writing, exactly who can see our Flock data, how long it’s kept, and how misuse is prevented and punished, skepticism is not paranoia – it’s responsible citizenship.