There are cameras everywhere.
Stores have security cameras. Homes have doorbell cameras. Police wear body cameras. Cities use traffic cameras. Businesses monitor parking lots. Schools have video systems.
Those technologies can raise very different questions.
DeFlock Metro Detroit is not trying to become the organization responsible for solving every surveillance, privacy and technology issue in Michigan.
Our focus is deliberately narrower.
We are working to end systems that routinely create searchable records of ordinary people’s vehicle movements for government use.
Our primary focus is networked ALPR surveillance.
That includes automated license plate reader systems operated by, purchased for, or made meaningfully available to government agencies.
Examples include systems provided by companies such as Flock Safety, Motorola Solutions/Vigilant, Genetec, Rekor and other vendors offering materially similar capabilities.
The company name is not what determines our position.
The surveillance model does.
What makes these systems different?
Our concern becomes much stronger when technology routinely does several things together:
Records ordinary vehicles - People do not need to be suspected of a crime before their vehicles enter the system.
Attaches location and time - The observation becomes a record of where a vehicle was seen and when.
Stores the observation - The information remains available after the vehicle has left.
Makes it searchable - Authorized users can look backward through prior observations.
Connects many cameras - A single observation can become part of a much larger movement history.
Shares information - Records may become available outside the agency or municipality where the camera is physically located.
Analyzes patterns - Newer software can make it easier to identify repeated locations, vehicle relationships, matching descriptions and other patterns.
Put those capabilities together and the result is no longer simply:
A camera saw a car.
It becomes:
A system remembers where vehicles have been and makes those observations useful for later investigation.
That is the practice we oppose.
Government access matters.
A camera does not necessarily have to be physically owned by a police department to become relevant to this campaign.
Suppose a private organization operates ALPR cameras.
If those cameras function only as a private security system, that raises one set of questions.
If the resulting vehicle-location information is routinely shared into a law-enforcement network or directly searchable by government users, the public/private distinction becomes less meaningful.
Our interest is therefore not limited to:
Who owns the pole?
We also ask:
Who can search the information?
Private camera networks can raise serious privacy questions too.
Doorbell cameras and other private security systems have generated legitimate controversies involving law-enforcement access, third-party data handling, cloud storage, warrants, user consent, neighborhood surveillance and corporate control over recorded information.
Those are real privacy issues.
They are simply not the central campaign DeFlock Metro Detroit is organizing around.
We do not need to declare every other camera system harmless in order to maintain a focused mission.
We are not campaigning to remove every security camera.
An ordinary security camera watching a store entrance, bank lobby, private building, parking lot or another limited location is not automatically the same thing as a regional ALPR network.
That does not mean every use is good.
It means the privacy analysis is different.
A camera monitoring one specific property for security purposes is structurally different from a system designed to create searchable observations of vehicles moving throughout a community.
We are not campaigning against ordinary home cameras.
People use cameras around their homes for package theft, property damage, personal security and seeing who is at the door.
Those systems can still create privacy concerns, especially when footage or data becomes accessible beyond the homeowner.
But DeFlock Metro Detroit is not a campaign to take people’s doorbell cameras away.
Keeping that distinction clear helps us stay focused on something residents can realistically change through local government action.
Body cameras are outside our primary scope.
Police body-worn cameras raise important issues involving accountability, privacy, public records, retention, access and other technology policy.
Those debates deserve serious attention.
They are not the same issue as building a searchable database of where vehicles move throughout a region.
Traffic cameras are not automatically ALPR surveillance.
A city may operate cameras for traffic flow, signal management, road conditions, crash monitoring or other transportation purposes.
A camera facing traffic does not automatically mean it is storing searchable vehicle-location records.
Before calling something ALPR:
Verify what it actually does.
The technology can change the answer.
A system may begin as ordinary video.
Then software changes. A new integration appears. Historical search is added. Vehicle recognition is added. Law-enforcement access expands.
The physical camera may look exactly the same while the surveillance capability behind it changes substantially.
That is why we focus on function, not simply appearance.
A useful test
When we are unsure whether something belongs within this campaign, ask:
- Does it routinely observe members of the general public who are not suspected of anything?
- Does it create records tied to vehicle location and time?
- Are those records stored after the immediate observation?
- Can someone search the historical records later?
- Are observations connected across multiple locations or cameras?
- Can information be shared or searched across organizations?
- Can government access the resulting information?
- Can software analyze the observations to identify movement patterns or associations?
The more the answer becomes yes, the closer the system gets to the surveillance practice DeFlock Metro Detroit exists to oppose.
Not every box has to be checked.
A system does not need every possible capability before it becomes concerning.
A network may have no advanced AI features but still create a large searchable location history.
That can be enough to raise our core concern.
Another product may have sophisticated video analytics but no meaningful system for tracking ordinary vehicle movements across locations.
That may raise different issues without becoming part of this campaign.
Context matters.
Connected Flock products deserve scrutiny too.
Flock also sells acoustic sensors and live-video cameras that can operate in the same platform as its plate readers. Those products do not all collect the same data, and we do not pretend they do.
They become directly relevant to this campaign when they expand, trigger or help interpret a government system for persistent public tracking—for example, when an acoustic alert surfaces nearby vehicle observations or when live and recorded video is combined with ALPR evidence in the same investigative platform.
We evaluate the function, integration, access and retention rather than assuming every Flock-branded device is identical.
Read our sourced guide to Raven, Condor and the connected platform →
Software that joins vehicle observations or public video with police records, public information, open-source intelligence and outside agency data also belongs in that functional analysis.
Read our guide to Flock Nova, data fusion and private-camera connections →
The same functional rule applies outside Flock. Leonardo/ELSAG markets SignalTrace sensors that detect supported broadcast Wi-Fi, Bluetooth and RFID signals, build recurring electronic signatures and can correlate them with vehicle observations. A government system designed to turn ordinary device emissions into searchable movement and association data falls squarely within this campaign’s concern even though the vendor and data type differ from a traditional ALPR.
Read: Leonardo SignalTrace and wireless-device tracking →
What if ALPR is used at one controlled entrance?
That can present a different question.
A restricted facility using a plate reader only at its own controlled entrance is not identical to hundreds of cameras placed throughout public roads, routine collection of ordinary traffic, historical search, regional sharing and movement analysis.
Both technologies may involve plate recognition.
Their surveillance impact is not identical.
Our strongest objection is to broad public movement tracking.
What if police temporarily target one known vehicle?
Again, that is different from mass collection.
There is a meaningful distinction between:
We have a legitimate investigative reason to locate this particular vehicle.
and:
We routinely record ordinary traffic so that whichever vehicle becomes interesting later may already have a searchable history.
Our campaign is primarily challenging the second model.
Targeted investigation is not mass surveillance.
We are not saying government can never watch anything.
We are saying surveillance power should begin with a reason to investigate rather than routine collection first.
Replacement systems count.
If a municipality removes Flock and installs another vendor offering substantially the same mass vehicle-tracking capability, we do not consider that success.
The important questions are functional:
Does it routinely collect vehicle-location observations? Does it store them? Can government search historical movement? Can observations be connected across locations? Does broad sharing or analytical capability remain?
If yes, changing the vendor logo did not solve the problem.
Product names can be misleading.
Companies change product names. Companies merge. Companies acquire other companies. Software features get reorganized.
A municipality may describe something as vehicle intelligence, public-safety technology, camera infrastructure, real-time crime technology, traffic safety or another broad label.
We look at what it does.
Not just what the sales brochure calls it.
We will not stretch the definition just to make the campaign bigger.
Scope discipline matters.
If something does not fit the surveillance practice we are working to remove, we can say so.
That technology may still deserve criticism. Someone may still organize around it. We may personally have concerns about it.
But every privacy concern does not need to become a DeFlock Metro Detroit campaign.
A focused organization is more useful than one that gradually becomes against all technology we find creepy.
Why keep the scope narrow?
Because local campaigns need achievable goals.
For ALPR systems, residents can often identify:
- a vendor;
- a contract;
- a budget;
- a renewal;
- a government body;
- and a decision.
That gives us something concrete to change.
Do not renew the agreement.
Remove the system.
Do not replace it with an equivalent network.
That is a campaign.
Scope also protects credibility.
If we call every camera mass surveillance, people stop listening.
If we say:
This particular system routinely records vehicle locations, stores them, connects observations across a network and lets authorized users search the history later.
that argument is much harder to dismiss.
Specificity helps.
Our line
We are not opposed to security.
We are not opposed to investigations.
We are not opposed to cameras as a category.
We are not opposed to technology.
We oppose routine, networked, searchable tracking of ordinary people’s movements by or for government.
That is the line.