Resistance Survival Guide #306
Local surveillance does not usually arrive with a siren. It arrives through city budget lines, police technology grants, vendor contracts, school safety agreements, traffic cameras, drone programs, license plate readers, camera registries, and quiet data sharing deals. By the time the public notices, the system may already be installed, connected, and normalized.
Mapping local surveillance infrastructure is not about paranoia. It is about civic literacy. The goal is to identify what technology exists in your city, who controls it, who pays for it, how data is stored, who can access it, and whether the public ever approved it. The EFF Atlas of Surveillance tracks police use of technologies such as drones, automated license plate readers, facial recognition, fusion centers, real time crime centers, and other surveillance tools across the United States.
This matters because surveillance systems often expand through ordinary administrative processes. A city may approve cameras as traffic tools, then connect them to police systems. A police department may buy license plate readers as a stolen vehicle tool, then allow searches for protests, immigration, abortion investigations, or general intelligence. EFF has reported that Flock Safety license plate reader data has been used in abortion related searches and protest related searches, which is exactly why local oversight matters before the machinery becomes permanent.
Why This Matters
Surveillance infrastructure changes the balance of power between residents and the state. A single camera is not the full story. The real issue is the network. Cameras connect to databases. Databases connect to vendors. Vendors connect to other agencies. Other agencies connect to federal systems. Suddenly, the camera on the corner is not just watching traffic. It may be feeding a searchable system that can reconstruct movement, association, protest activity, school drop offs, clinic visits, religious attendance, and everyday life.
The ACLU Community Control Over Police Surveillance model argues that police should not acquire or use surveillance technologies without public notice, public debate, and democratic approval. That is the core principle here. Residents should not have to discover surveillance after it has already been installed.
The safest organizing position is simple. Do not guess. Document. Do not spread rumors. Verify. Do not only look at the device. Follow the contract, the policy, the data, the grant, the vendor, and the agency access rules.
Key Takeaways
Local surveillance infrastructure includes more than cameras. It can include automated license plate readers, drones, real time crime centers, fusion centers, facial recognition systems, camera registries, body worn cameras, gunshot detection, cell site simulators, social media monitoring tools, predictive policing software, and third party investigative platforms.
The Atlas of Surveillance is the first place to check because it gives residents a searchable starting point for known law enforcement surveillance tools in their area.
City council agendas, police budget documents, procurement portals, grant records, and vendor contracts often reveal surveillance systems before press releases do.
Automated license plate readers are especially important because they can log license plates, locations, and timestamps as vehicles pass by. The ACLU of Massachusetts has warned that these systems allow police to track where motorists are and where they have been.
Real time crime centers are worth watching because they can consolidate cameras, license plate readers, drones, gunshot detection, emergency call data, and other feeds into a single command system. The Atlas of Surveillance separately tracks real time crime centers as a surveillance category.
Public oversight should come before purchase, not after installation. The ACLU model for Community Control Over Police Surveillance calls for public approval before local agencies acquire or use surveillance technologies.
Step by Step Guide
Step 1: Start With The Known Surveillance Map
Begin with the EFF Atlas of Surveillance. Search your city, county, police department, sheriff office, school district, and nearby regional agencies. Record every listed technology, including drones, automated license plate readers, facial recognition, real time crime centers, fusion centers, gunshot detection, camera registries, predictive policing systems, and third party investigative platforms.
Do not treat the Atlas as the final answer. Treat it as the first receipt. The Atlas is powerful, but local technology changes quickly. Your job is to confirm what is still active, what has expanded, what has expired, and what is missing from the public map.
Step 2: Build A Local Surveillance Inventory
Create a simple spreadsheet with one row for each technology. Include the agency name, technology type, vendor, date discovered, source link, contract amount, approval date, data retention period, sharing rules, policy document, and public meeting where it was discussed.
This inventory keeps the work factual. It also prevents confusion when several agencies use the same vendor. For example, your city police, county sheriff, school district, housing authority, transit authority, and downtown business district may all operate separate systems that still connect through shared vendor platforms.
Step 3: Search Public Meeting Records
Search city council agendas, county commission packets, school board agendas, transit authority minutes, community redevelopment agency records, and public safety committee meetings. Use search terms like surveillance technology, license plate reader, drone, camera registry, real time crime center, fusion center, public safety camera, Flock, Motorola, Axon, Genetec, Cellebrite, ShotSpotter, BriefCam, Fusus, Palantir, Rekor, and grant funded equipment.
Read attachments, not just agenda summaries. The most important details are often buried in staff memos, contract exhibits, budget amendments, and vendor quotes.
Step 4: Follow The Money
Look for police technology grants, homeland security grants, state public safety grants, federal pass through funds, private donations, police foundation purchases, and emergency procurement records. Surveillance systems may not appear in a normal police budget if they were bought through a grant, donated by a private group, or bundled into a broader public safety project.
When you find a grant, write down the grant name, award year, dollar amount, recipient agency, stated purpose, and any required reporting. That tells you whether the system was sold to the public as crime prevention, traffic safety, school security, emergency response, terrorism prevention, or downtown redevelopment.
Step 5: Identify The Vendor And The Data Path
The vendor matters because surveillance power often sits inside the platform, not just the device. A camera may be owned by the city, but the search tools, storage rules, audit logs, retention settings, and sharing features may sit inside a vendor system.
For every vendor, look for the master services agreement, data sharing terms, privacy policy, retention schedule, audit log rules, subcontractors, cloud hosting provider, and agency access controls. Ask who can search the data, whether searches require a warrant, whether federal agencies can access it, whether other local agencies can access it, and whether the public can see audit logs.
Step 6: Map The Physical Locations Carefully
For visible infrastructure, document general locations without creating a harassment target or encouraging tampering. Note intersections, public buildings, school perimeters, parking lots, transit stations, bridges, toll areas, courthouse zones, downtown corridors, and event venues.
Do not touch, cover, damage, disable, or interfere with equipment. That can create legal risk and distract from the real issue, which is public accountability. The goal is a lawful civic map, not a stunt.
Step 7: File Public Records Requests
Ask for contracts, purchase orders, invoices, grant applications, policy manuals, training materials, privacy impact assessments, data retention schedules, audit logs, access lists, sharing agreements, memoranda of understanding, camera locations, drone flight logs, real time crime center policies, and reports given to elected officials.
Use clear language. Ask for records by vendor name and technology type. Ask for active contracts and expired contracts. Ask for attachments and exhibits. Ask for records in electronic format. Ask for rolling production if the search will take time.
Step 8: Compare Policy To Actual Use
A policy may claim a tool is only for serious crimes, but audit logs may show searches for minor offenses, protests, school residency checks, immigration related requests, or vague intelligence purposes. That gap is where accountability lives.
EFF reported in 2026 that its analysis of millions of Flock Safety searches found mission creep beyond specific investigations. That is why residents should request audit logs and not settle for polished talking points.
Step 9: Check For Regional And Federal Access
Do not stop at your local police department. Search for county sheriff access, state police access, fusion center access, school police access, neighboring city access, federal task force access, ICE access, CBP access, FBI access, and Homeland Security access.
Surveillance networks become more powerful when data can move across jurisdictions. A local tool can become a regional tracking system if sharing settings are broad or poorly supervised.
Step 10: Turn The Map Into Public Questions
Once you have receipts, turn them into questions for public officials. Ask when the technology was approved, who approved it, how much it costs, who can access the data, how long data is kept, whether warrants are required, whether searches are audited, whether misuse has occurred, whether the public can review reports, and whether the city has a Community Control Over Police Surveillance law.
Ask calmly and specifically. The point is not to sound dramatic. The point is to make evasion obvious.
What To Search For
Search your city records for these terms: automated license plate reader, ALPR, LPR, Flock Safety, camera registry, public safety camera, drone, unmanned aircraft, real time crime center, RTCC, fusion center, facial recognition, face recognition, biometric, cell site simulator, Stingray, gunshot detection, acoustic detection, social media monitoring, predictive policing, video analytics, emergency operations center, public safety technology, intelligence led policing, data sharing agreement, and surveillance technology.
Also search vendor names. Common names to check include Flock Safety, Axon, Motorola Solutions, Genetec, Cellebrite, Rekor, Fusus, Palantir, BriefCam, ShotSpotter, SoundThinking, Clearview AI, Vigilant Solutions, and Thomson Reuters CLEAR.
What To Request
Ask for the contract, purchase order, invoice, council approval, grant application, policy manual, training materials, privacy assessment, data retention schedule, audit logs, search logs, user access list, sharing agreement, memorandum of understanding, vendor proposal, renewal notice, cancellation clause, and annual usage report.
If the agency says no responsive records exist, adjust the language. Some agencies do not call a tool surveillance. They may call it public safety technology, investigative software, intelligence support, situational awareness, case management, emergency response, or camera integration.
Safety Rules For Researchers
Stay lawful. Do not trespass, tamper with equipment, interfere with emergency systems, impersonate officials, access restricted systems, or publish private personal data. Photograph only from public places where photography is lawful. Keep your focus on public agencies, public contracts, public infrastructure, and public accountability.
Protect yourself and your team. Use a shared evidence folder, keep source links, preserve screenshots with dates, and separate confirmed facts from leads. Do not post an accusation until you can show the record behind it.
How To Use The Map
A good surveillance map should help residents ask better questions. It should show what exists, where it appears to operate, who owns it, who pays for it, who can access it, what policy governs it, what data it collects, how long the data is kept, and whether the public ever had a real vote.
Once the map is ready, use it to prepare public comments, local explainers, public records requests, letters to city council, school board questions, coalition briefings, and candidate questionnaires. Keep the tone grounded. The strongest argument is not fear. The strongest argument is documented power without documented consent.
In Closing
The surveillance machine depends on people not looking closely. It hides in plain sight through budget language, vendor promises, public safety branding, and the soothing phrase “just a tool.” But tools have owners, rules, prices, contracts, data trails, and consequences. Mapping local surveillance infrastructure gives the public a way to move from suspicion to evidence. That is how communities stop being managed by invisible systems and start demanding real oversight.
Source List
- EFF Atlas of Surveillance
- Electronic Frontier Foundation: Atlas of Surveillance
- MuckRock: How the Atlas of Surveillance built a platform to track law enforcement surveillance across the country
- ACLU: Community Control Over Police Surveillance
- ACLU: Community Control Over Police Surveillance Model Bill
- ACLU Massachusetts: Flock gives law enforcement all over the country access to your location
- EFF: More License Plate Reader Mission Creep
- EFF: How Cops Are Using Flock Safety’s ALPR Network to Surveil Protesters and Activists
- EFF: Flock Safety and Texas Sheriff Claimed License Plate Search Was Missing Person
- EFF: Free Surveillance Tech Still Comes at a High and Dangerous Cost
