Surveillance map
beta

Take action

How to push back where you live

Every win on these maps started the same way: a few residents found the document, found the date it could be revisited, and showed up before the vote. This page is that method -- for surveillance contracts, data-center approvals, age-verification and digital-ID mandates, book removals, and police responses to what people post.

Start with a tool

If you already know what you want to do, go straight there. The guide below is for working out what to do first.

The short version

Almost everything on this site comes down to the same four things: a document somebody signed or voted for, the body that signed it, a date when it can be revisited, and a room where that happens. A surveillance contract, a data-center development agreement, a book-removal directive, an age-verification enforcement policy -- none of them are forces of nature. Someone approved each one, which means someone can revisit it.

The campaigns that worked did not wait for a sweeping privacy law or a court ruling. They got the document, found the date, and showed up with neighbours before it was renewed or approved. That is the whole method, and it is the same method whichever map brought you here.

A step-by-step start

The same six steps work for every topic on this site. What changes is which document you ask for and which body holds it, so each step names the specific thing to chase for your issue.

  1. Find out what your community already has -- or is about to approve

    Half these fights are about something already running; half are about something coming up for a vote. Check the maps first: surveillance for cameras, plate readers and monitoring tools already deployed near you; data centers for facilities operating, under construction, or proposed; speech for laws and enforcement in your state; digital-ID for age-verification and identity mandates. For plate readers specifically, deflock.org maps individual cameras. Then read your city, county, or school board's agendas and minutes for the last six months -- that is where the thing you are looking for was approved, usually without a headline.

  2. Get the document

    There is always a document. For surveillance it is the vendor contract and usage policy. For a data center it is the development agreement, the incentive or abatement package, and any nondisclosure agreement signed by officials. For book removals it is the district's materials selection and reconsideration policy, plus any directive circulated to staff. For age verification it is the enforcement guidance and vendor contracts. Our records request builder writes the request for your topic, cites your state's public-records law, and tells you which office holds it.

  3. Read it for the date that gives you leverage

    Every one of these has a moment when it is decided again, and that moment is your opening. Surveillance contracts have a renewal date, and many auto-renew annually -- miss the cancellation window and you have lost a year. Data centers have a rezoning or special-use hearing and a council vote. Statutes have an effective date and often a review or sunset clause. Policies have a review cycle. Find the date before you build the campaign, because it sets your calendar.

  4. Find one person on the inside willing to ask the question

    You do not need a majority on day one. You need a single council member, county supervisor, or board trustee willing to put the question on an agenda and ask it out loud. Most officials have never been asked what a contract costs, who signed the NDA, or what the water commitment is -- and many are uncomfortable once they find out. One member asking in public does more than fifty signatures.

  5. Ask for the receipts

    This is the step that flips rooms, and it is different for each topic. For plate readers and camera networks, ask for the audit logs: which agencies searched your data, how often, and for what stated reason -- town after town found federal or out-of-state queries nobody had approved. For a data center, ask for the utility load commitment, the water projections, and who pays for the new infrastructure. For age verification, ask for enforcement actions and how long identity documents are retained. For book removals, ask for the challenge log and the reconsideration minutes and check whether the written policy was actually followed. Specific numbers move officials; general concern does not.

  6. Show up, more than once, and aim for a clean outcome

    Not a petition alone -- people in the room, repeatedly. Our calendar finds meetings near your ZIP, and the letter builder writes what to send beforehand. Then know what you are asking for: the strongest results are a vote to terminate or not renew, a rejection or moratorium pending study, a repeal or amendment, or a directive rescinded and the written policy followed. A vague promise to "look into it" is how these come back next year.

Who to contact

Letters and records requests

These used to be a wall of copy-and-paste templates written for plate readers. They are now two builders that write the document for whichever topic you are working on, fill in your state's law, and tell you where to send it -- which is strictly better than a static template you have to edit by hand.

A few things to watch for

Every one of these fights has a way of coming back after you think you have won. The recurring pattern across all of them: the decision gets moved somewhere less visible. Watch for these by topic.

Data centers -- the code name and the split application. Projects routinely arrive under a shell company or a project code name, so the agenda item does not say who it is. Large sites are also split into phases or parcels so each piece stays under the threshold that would trigger a bigger review or a public hearing. Ask whether the applicant is a subsidiary, whether adjacent parcels are under common control, and whether the utility load figures assume later phases.

Age verification and digital ID -- scope creep past the original target. These are written for one category of site and then reach further, either by amendment or by how the enforcing agency reads them. Ask which sites the agency believes are covered, whether any exemption requests have been granted, and how long uploaded IDs or face estimates are retained -- retention is where the real exposure sits, and it is usually not in the statute.

Book removals -- the directive that bypasses the policy. Districts generally have a written reconsideration process, and the fights that matter are usually the ones where a title was pulled by administrative directive without it ever being used. Ask for the challenge log alongside the list of removed titles: gaps between the two are the whole story.

Police responses to speech -- the informal visit. A knock at the door or a warning phone call over a post often produces no charge, no report, and therefore no record for anyone to audit. Ask what policy governs when an online post can lead to contact, and whether those contacts are logged at all when no charge follows.

Surveillance -- the "free" first year. Many ALPR systems are installed with grant money that covers installation and the first year of service -- often a federal Department of Homeland Security grant, but just as often a state grant, and sometimes both. When the grant runs out, the city inherits the subscription bill (commonly $30,000 to $50,000 a year) and a data-sharing arrangement that can route local plate reads to federal agencies and fusion centers -- and, in a lot of smaller and mid-sized communities, to a Real-Time Crime Center (RTCC) that pools live camera, sensor, and plate-reader feeds for police. Ask how the cameras were paid for, which grant it was, what renewal will cost, and who can see the data once the grant money is gone.

Surveillance -- the switch. Some cities drop Flock and quietly move the same surveillance onto another vendor, often an Axon contract they already hold, with no public input. Removing Flock is not the goal; removing the dragnet is. Ask what replaces it.

Surveillance -- private and HOA cameras. A city contract usually covers only police-operated cameras. Privately owned ALPRs run by homeowner associations and businesses can keep feeding the same network. Canceling the city contract does not touch those.

Surveillance -- reinstalls and reactivations. More than one town canceled, only to find cameras quietly reinstalled or switched back on. Confirm the hardware is actually down, and keep checking.

Local groups and where to find them

Across the country, residents have started local DeFlock chapters to organize in their own towns. DeFlock keeps the full, current directory of them, and if there is one near you, it is the fastest way to find people already doing this work.

See the full directory at deflock.org/groups →

A few of the active chapters:

We link a chapter's own site only where we could confirm it. For the others, and for the most current roster, use the directory above.

Where to go for more

This guide is informational and general. Contracts, public-records rules, and council procedures vary by place, so confirm the specifics for your own community.

Already started?

Tell us so the map can show it

If your community has removed, paused, denied, restricted, or rejected any of this -- cameras, a data center, a book removal, an ID mandate -- send a sourced article and it goes in the review queue.

Submit a source →