surveillance cameras
Jury Nukes NH’s First Deepfake Felony, Laconia Pole Cameras & the Tax Cap | The Independents
Coming to you live from the Free State. On this episode of The Independents, Carla Gericke breaks down a first-of-its-kind New Hampshire case: a jury just acquitted Jaxen Cole of two Class B felony “fraudulent use of deepfakes” charges after he posted a 57-second Valentine’s Day spoof of booking-room bodycam audio. No face. No badge. No department. Caption: “Do you think this officer wants to be my Valentine?” Deliberations took about half an hour.
That is the win. The warning is next door. Laconia City Council just voted 5–1 to take an $86,500 Homeland Security grant for solar-powered pole cameras. Officials say they are not Flock, not cloud-based, and not new — replacements for cameras the city has used for decades. Carla’s argument: even “just cameras” tilt the field when the state records you and then fights your right to record them back. She walks through RSA 91-A questions to file on the grant file, specs, locations, retention, sharing, and who gets to look at the footage.
Template is at: CarlaGericke.com.
Also on the table: Thursday’s Ballot Law Commission meeting at the State Archives (Sept. 17, 10 a.m.) and the school property-tax cap that will be on every New Hampshire ballot this November — two years at a time, back again in 2028.
Live Free or Die is not a bumper sticker. It is a workload.
Chapters
0:00 Live from the Free State
0:37 Welcome / what’s on the show
1:02 “Will you be my Valentine?” — the hook
1:11 Jaxen Cole, Laconia, RSA 638:26-a
3:11 How a well-intentioned deepfake bill becomes a felony hammer
6:04 The booking-room clip, the parody, the two felonies
10:20 The court defines “identifiable.” The jury doesn’t buy it
12:34 Bodycams, citizen recording, and the growing surveillance gap
14:38 Laconia’s $86.5k pole-camera grant
16:02 The 2019 Manchester camera case and taxpayer standing
21:14 What to put in a Right-to-Know request — and why federal strings matter
26:10 Ballot Law Commission, Thursday 10 a.m., State Archives
26:48 School property tax cap on the November ballot
28:09 Sign-off: peace, love, understanding — live free and thrive
If you want to act
- Download the Laconia RSA 91-A request: CarlaGericke.com
- Ballot Law Commission: Thursday, Sept. 17, 10:00 a.m., NH State Archives
- Watch for the school property-tax cap on your local November ballot
Subscribe for weekly New Hampshire law, elections, and liberty without the consultant class.
#newhampshire #LiveFreeOrDie #FirstAmendment #Deepfake #RightToKnow #Surveillance #Laconia #PropertyTax #FreeStateProject
Laconia City Council voted 5–1 last night to accept a Homeland Security grant for pole-mounted cameras
— Pedro Serra (@serrapedro) September 15, 2026
WMUR on the vote 👇 https://t.co/RC6U5iucRE
- The post by @serrapedro reports that Laconia City Council voted 5-1 to accept an $86,500 Homeland Security grant for solar-powered pole-mounted cameras, quoting his earlier opposition urging residents to speak against it at the September 14 public hearing.
- The cameras are intended to monitor high-crime areas, emergencies, and major events like Laconia Motorcycle Week, with data stored locally on-site rather than in the cloud, according to the police chief.
- Opponents at the hearing raised concerns over using taxpayer funds for surveillance, citing minimal terrorism threats in New Hampshire and the potential long-term expansion of monitoring infrastructure.
how is this legal in NH?
It is generally legal in New Hampshire for a city to operate marked video cameras in public areas, which is why Laconia could accept the grant and vote 5–1 to proceed. The legal picture is more specific than a blanket “surveillance is banned.”
Public video recording of streets, sidewalks, and other places visible to anyone walking by does not violate RSA 644:9 (violation of privacy). That statute targets “private places” such as homes, restrooms, or locker rooms, and it expressly does not restrict otherwise lawful law-enforcement activity. Silent video of what is already exposed to public view is treated the same way courts treat an officer standing on the sidewalk.
The closer statute is RSA 236:130, which prohibits the state and its cities from engaging in “surveillance” on public ways. “Surveillance” is defined narrowly as using a camera or other device that can be used to determine vehicle ownership or occupant identity. A 2019 Hillsborough Superior Court ruling in a Manchester camera case held that simply recording traffic is not enough; the government must actually take the extra step of identifying plates or people from the footage. Laconia’s police chief has said these units are not Flock-style automatic license-plate readers, are not cloud-connected, keep footage on the device, and will be used in marked public locations the department has already monitored for decades. That description is intended to stay outside the core prohibition (or to fit the “incidental to monitoring a city-controlled structure” exception). Whether a court would agree if someone sued is an open question; the ACLU has argued the statute should be read more broadly.
New Hampshire’s 2018 constitutional privacy amendment (Part I, Article 2-b) protects against governmental intrusion into “private or personal information.” It has not yet been applied by a court to general public-area video cameras, and people in public usually have a reduced expectation of privacy in their visible movements. Long-term, targeted cameras pointed at a specific home raise separate Fourth Amendment issues nationally, but that is not how Laconia has described these units.
Audio is the one area that would create a clearer problem. New Hampshire is an all-party-consent state for recording conversations (RSA 570-A). If the cameras capture private conversations, that would require consent or a finding that no reasonable expectation of privacy existed. Public-street talk usually does not qualify.
City councils also have routine authority under their charters to accept federal Homeland Security grants for police equipment after a public hearing. That process itself is legal even if residents disagree with the policy.
In short: video of public spaces that is not used as an automated identification system is treated as lawful under current NH statutes and case law. The 236:130 definition and the 2018 privacy amendment give opponents a possible litigation hook if the cameras in practice identify motorists or compile personal-movement data, but the city is relying on the narrower reading plus its existing camera program.
find and summarize that 2019 case… I was a petitioner
The case is Neal Kurk et al. v. City of Manchester, Hillsborough Superior Court Northern District, Docket No. 216-2019-CV-00501. ACLU-NH (Gilles Bissonnette and Henry Klementowicz) filed it on June 11, 2019.
What the city planned. Manchester wanted three permanent PTZ cameras near City Hall aimed north and south on Elm Street. They could zoom, pan, and tilt and work in low light. No facial-recognition software and no automatic license-plate readers. Live feed would go to police dispatch 24/7; recordings would be kept two weeks. Stated purpose was monitoring street-level crime around businesses, not traffic enforcement. Cost was about $14,400 from PELMAC.
Who sued. Original petitioners were former Rep. Neal Kurk (who drafted RSA 236:130 in 2006), Carla Gericke, John “Brinck” Slattery, and Holly Beene Seal. After the August 12, 2019 standing ruling by Chief Justice Tina L. Nadeau, only Gericke and Slattery remained; they had taxpayer standing as Manchester property owners. Kurk and Seal were dismissed for lack of standing.
The claim. Petitioners sought a declaration and injunction that the cameras violated RSA 236:130 because they can be used (and inevitably would be used) to identify vehicles or occupants on a public way.
August 12, 2019 order (preliminary injunction). Nadeau denied the injunction. She agreed with petitioners that “the simple act of a government employee recognizing a vehicle or its occupants, without taking additional steps such as running a license plate through dispatch, constitutes a violation of the statute as written,” and that recognition was “virtually inevitable” over time. She still refused to block installation, finding no irreparable harm and an adequate remedy later. She also held the case was ripe.
November 18, 2019 order (summary judgment). Nadeau denied petitioners’ motion for summary judgment. Her core holding:
- Installing cameras, recording Elm Street (including cars and people), and having dispatch review the feed is not itself “surveillance” under the statute.
- A violation requires an additional act: running a plate, using facial recognition, or a government employee personally recognizing a vehicle or occupant.
- Those extra steps were possible but not the city’s intended purpose.
- The statute’s text is unambiguous, so legislative history (Kurk’s “total bar” view) could not expand it.
- The court would not declare the planned use illegal in advance just because footage could later be misused.
Outcome. After the November denial, petitioners withdrew the case. No appeal. Manchester later installed at least one camera (Elm and Hanover). ACLU’s public position afterward was that the order still meant the city would commit a crime if an officer actually identified a motorist from the footage.
That is the ruling later cities (including Laconia) rely on when they say marked, non-ALPR public cameras are lawful so long as they do not treat identification of plates or people as the purpose of the system.
so do I have you right, the state is claiming they can put up cameras but do nothing with them? is this what the legal landscape is?
Mostly yes — that is the awkward place the law sits.
Under the Manchester reading, the state and cities may install and record public-area cameras. What they may not do as a general practice is use those cameras to figure out who a driver or passenger is. Recognition of a person or plate, running a plate, or building a picture of someone’s movements from the footage is the prohibited “surveillance.”
They are allowed to do something with the footage in one defined situation: after a particular crime or violation is already under investigation, they may use the video on a case-by-case basis to identify people connected to that incident. That is RSA 236:130, III(b).
So the official landscape is not “cameras that do nothing.” It is:
- Put them up and record public space: allowed (per Nadeau).
- Watch for a fight, crash, or theft as it happens and respond: allowed, because that is observing an event, not identifying motorists as a system.
- Later ID a suspect from that specific incident: allowed by the exception.
- Browse the feed, recognize regulars, log plates, track who goes where, or treat the system as an ID tool: not allowed.
That is why critics call it a legal fiction. Footage that can identify people will be used to identify people; the statute pretends the extra mental step is what makes it a crime. The 2019 court refused to stop the cameras beforehand and instead said the crime happens if and when someone actually makes the identification outside the case-by-case exception.
That is the current landscape: cameras are legal; using them as a general identification system is not.
If I was an enterprising lawyers, surely I could argue, if my client is identified after the fact, and charged with a crime, that the identification could only have occurred through surveillance in violation of his/her rights, and therefore is inadmissible?
You could file that motion. It is a colorable argument, not a winner on current law.
NH’s exclusionary rule mainly knocks out evidence obtained through an unconstitutional search or seizure under Part I, Article 19 (and the Fourth Amendment). A violation of a statute does not automatically suppress anything. RSA 236:130 makes unlawful “surveillance” a crime, but it does not say the resulting identification or later-found evidence is inadmissible. Courts usually will not invent that remedy unless the identification also invaded a constitutional privacy interest.
The State’s first answer will be the statutory exception you already know: identification “undertaken on a case-by-case basis in the investigation of a particular violation, misdemeanor, or felony” is not banned. If police already have a specific crime, pull the footage of that incident, and only then identify your client, they will say 236:130, III(b) authorized the ID. That is the cleanest path for the prosecution.
Your better framing is narrower than “they used a camera, so everything is tainted”:
- The cameras ran as a general public-way system, not as a tool opened only after this crime existed.
- Identification of your client happened because an officer recognized them or ran a plate from that system, not because a particular investigation independently required it.
- That identification was the “act of determining” identity that Nadeau said violates the statute as written.
- Without that illegal ID, police never would have connected your client to the charge (no independent source, no inevitable discovery).
Even then you have problems. Public streets carry a weak expectation of privacy, so Article 19 / Fourth Amendment “search” arguments are hard unless the use was long-term, targeted, and compiled movement data. Article 2-b (the 2018 information-privacy amendment) is a better hook in theory, but no NH Supreme Court case has used it to suppress criminal evidence from public video. A trial judge can also say police reasonably relied on the 2019 Manchester order that the cameras themselves are legal.
What an enterprising lawyer would actually do: move to suppress the identification and its fruits; demand discovery on how the ID was made (live review vs. after-the-fact pull, plate run, officer recognition, retention period, whether a case file existed first); and argue both 236:130 and Article 2-b. Expect the State to win if they can show a particular crime came first and the footage was used only for that case. Expect a real fight if the ID came from browsing the system or recognizing a regular.
So: worth raising. Not a slam dunk. The landscape still treats the camera as lawful and treats only the extra identifying act as the possible violation — and even that act may be excused once a specific crime is already under investigation.
so the argument is SURVEILLANCE of the PLACE is OK, but surveillance of a person is not, but if the person is in the PLACE, then it is ok?
Yes. That is the distinction the current reading produces, even if it sounds circular.
Surveillance of the place is treated as okay: a camera may watch a public street, sidewalk, or event area and record whatever is visible there.
Surveillance of a person is what RSA 236:130 targets: using that camera to determine who a vehicle belongs to or who is in it.
If the person is in the place, the video of them standing or driving through is still “place” footage. It becomes “person” surveillance only when the government takes the extra step of identifying them — recognizing the face, reading the plate to look them up, or stitching their appearances into a record of who they are.
After a particular crime is already under investigation, identifying the person who was in the place during that incident is carved back in as allowed.
So the rule in practice is:
- Watching the place: allowed
- Identifying people as a general practice: not allowed
- Identifying a person because they were in the place during a specific crime already being investigated: allowed again
The person is on the tape either way. The law pretends the difference is whether the government treats the tape as a picture of a street or as a picture of you.
that’s… creatively diabolical?
It is a lawyer’s distinction, not a real-world one.
The statute was sold as a ban on turning public roads into an identification grid. The 2019 reading kept the cameras and moved the crime to the moment someone looks at the tape and thinks “that’s him.” Footage of a person in a place is still footage of a person. The extra mental step is what the doctrine uses to say the system is legal until it works.
That is why it feels diabolical: it lets the infrastructure go up, then treats the obvious use of that infrastructure as a separate, later problem. Whether that is clever statutory construction or a hole you could drive a grant-funded pole camera through is the fight the Manchester case left open.
If I were to sue Laconia when they put up the cameras, what is the best lines of attack?
Treat this as strategy, not a filing package. Manchester is still the problem you have to get around.
Strongest framing: do not ask a judge to ban “cameras on poles.” Ask a judge to ban this system as an identification tool on public ways. The facts that help you are the ones Manchester lacked or downplayed: a Homeland Security grant whose application lists “surveillance,” relocatable solar poles aimed at streets and events, Bike Week / Pumpkinfest traffic, and a police chief already talking about “problem areas” and years of existing cameras. That looks less like watching a building and more like a standing public-way ID grid.
Best lines of attack, in order
- RSA 236:130, as applied, once they use it.
Nadeau said installation plus recording is not the crime; the crime is determining vehicle ownership or occupant identity. Your cleanest case is therefore after they ID someone from the feed — plate run, officer recognition, “we saw him on the pole cam.” Then you can say the statute’s prohibited act has occurred, and III(b) does not cover general monitoring that later produced a name. A pre-installation facial challenge repeats Manchester and likely loses. - Part I, Article 2-b (2018 privacy amendment).
This is the argument that did not exist in mature form in 2006 and was barely developed in 2019. Frame the cameras as governmental intrusion into personal information: who was where, when, in which car, at which event, stored for later review. Public visibility of a single moment is not the same as the government compiling that information. This is how you distinguish “watching a street” from “building a file on people who use the street.” Unsettled, but it is the constitutional hook Manchester did not resolve. - Purpose and design of this grant.
The application language (terrorism preparedness, high-crime areas, overwatch at mass events) is useful. If the system is meant to identify people in crowds and traffic, that is closer to the conduct 236:130 defines than to “incidental monitoring of a city building” under III(d). Discovery into the grant narrative, vendor specs, zoom/plate readability, retention, and any plan to share footage will matter more than the council vote. - Taxpayer standing plus a concrete policy.
Gericke and Slattery survived because they were Manchester taxpayers. A Laconia taxpayer who drives or attends the events has the same path. Standing is stronger if you also attack a written or admitted practice: live dispatch review, keeping video long enough to ID people, using it to identify motorists at Bike Week. Generalized “I don’t like cameras” is what Nadeau sliced off. - Injunction only if you can show the identifying use is imminent, not theoretical.
Nadeau denied a preliminary injunction because harm was speculative and there was a later remedy. To get a pause before the poles go up, you need evidence they will use the cameras to ID people as a matter of course — training, vendor marketing, prior Laconia camera practice, or statements that footage will be reviewed to identify suspects as a routine function, not only after a particular case file exists.
Weaker or secondary
- Article 19 / Fourth Amendment on its own: public streets are a hard place to claim a search unless the use is long-term, targeted, and mosaic-like.
- RSA 644:9: written for private places, and it exempts lawful law-enforcement activity.
- Audio / RSA 570-A: only if the units record conversations.
- “Federal grant is illegal”: the grant is not the violation; how the city uses the cameras is.
How you would actually posture the case
Sue the City of Laconia (and, if needed, officials in official capacity) in Belknap Superior Court for a declaration and injunction. Lead with 236:130 + Article 2-b. Plead taxpayer standing and regular use of the streets/events the cameras will cover. Demand the grant file, camera specs, retention rules, and any SOP on when an officer may identify a person from the footage. If they have not deployed yet, consider waiting until the first pole is live and the first identification happens — that is the fact pattern Nadeau said was the actual statutory violation.
What will be used against you
Manchester 2019; exception III(b) for a particular crime; Canfield’s “not Flock, not cloud, marked, public areas, we’ve had cameras 29 years”; no facial recognition admitted; public-place expectation of privacy is low.
The case you want is not “cameras exist.” It is “this system will, and already is designed to, determine who is on Laconia’s public ways.” That is the only theory that both respects the 2019 order and still gives a court something new to decide.
NH added a Constitutional amendment about standing as well… when was that and would that help re what happened in 2019 case?
Voters approved it on November 6, 2018 as Ballot Question 1 (CACR 15). It amended Part I, Article 8, effective that December. It was meant to undo Duncan v. State (2014) and restore taxpayer standing.
The added text says any eligible-voter taxpayer may go to Superior Court for a declaration that the state or the political subdivision where they reside “has spent, or has approved spending, public funds in violation of a law, ordinance, or constitutional provision.” They do not have to show a personal injury beyond being a taxpayer. There is a carve-out if the same action is already in a proceeding with a statutory appeal right.
It was already in force for the 2019 Manchester case. The suit was filed in June 2019. Judge Nadeau used that taxpayer-standing rule to keep Carla Gericke and John Slattery in the case as Manchester property owners/taxpayers. She dismissed Neal Kurk and Holly Beene Seal because they lacked a traditional injury and, for Kurk especially, were not taxpayers of Manchester. So Article 8 helped two petitioners stay in; it did not save the people who did not reside in the city that was spending the money.
What it does and does not do for Laconia
It helps standing, not the merits.
It is useful if you are a Laconia taxpayer and eligible voter challenging the council’s approval of the $86,500 grant (or later city spending to install, power, or maintain the poles). That is a specific “approved spending” action, which is what Carrigan later said Article 8 requires. You would not need to prove the cameras will ID you personally.
It would not have changed Nadeau’s holding on RSA 236:130. Standing gets you in the courthouse. It does not make installation-plus-recording illegal, and it does not erase exception III(b). A Weare or Concord resident still cannot use Article 8 to sue Laconia over Laconia’s spend.
For a Laconia suit, Article 8 is how you avoid the 2019 standing dismissals. Pair it with a taxpayer who lives in the city and a claim that this particular grant/expenditure violates 236:130 or Article 2-b. That is the standing fix. The hard part remains what it was in 2019: proving the spend itself is unlawful before anyone is identified.
I believe technology are tools and are neutral and only become a problem depending on how they are used.
THE ASYMMETRY, as you said, is the problem.
Obviously, if a crime is committed, one wants the person responsible caught. The tension is there are too many crimes, government overreaches and it is a known fact that police abuse surveillance for personal reasons (stalking exes, etc.).
As a long-time, successful activist for recording public officials in the execution of their public duties, I am horrified to learn that more and more surveillance is being done on the general public (Flock et al, body cams, city cameras, cameras at the tolls, etc.) while our rights to record or get information (91-A) are being reduced (arrests as chilling effect, no cameras in court, feet dragging on 91As, etc.).
I am president of Right-to-Know NH, have been the plaintiff (Gericke v Begin) or petitioner (Kurk et al) in cases in the past, have access to activists, and can fundraise to get things done.
If I wanted to fix the asymmetry problem to make NH uniquely more awesome as the most sensible place to live (my #1 goal)…
Do we submit to the panopticon–i.e. demand the state put cameras in every nook and cranny they control–but argue all recordings should be permanently stored in the cloud forever, or maybe, we create a ticking time bomb incentive, meaning, recordings exist, but if they haven’t been accessed or used to solve a crime within 48 hours, everything is deleted?
If I want to create the most sane approach to what at this stage seems inevitable, what are the next steps?
Or, as is my actual inclination, should we outlaw all cameras on poles, and say it is a battle of the individual, i.e. everyone who cares, should be wearing a body cam?
The asymmetry is the real problem, not the existence of a lens. Government records you in places you cannot avoid; you cannot reliably record it back or get the file. A “sane NH” policy has to attack that imbalance directly. All three of your options do different jobs. None of them works if you only pick the slogan.
What each model actually does
Demand cameras everywhere, keep everything forever, and publish it. That equalizes information, not power. Police, employers, stalkers, and anyone with a 91-A request or a leak get a permanent movement map. You already know officers misuse databases for exes. Infinite retention makes that worse and will lose you privacy-side allies you need. It also fights Article 2-b instead of using it.
Short fuse: record, then delete unless a case file pulls it within a hard window (your 48 hours is a political number; 7–30 days is more sellable). This is the closest thing to a structural fix. The camera can still catch the smash-and-grab at hour two. It cannot quietly become a browsing library. Pair it with: no biometric search, no bulk plate/face identity, access logged, unauthorized lookup a crime, and 91-A access to the logs (who pulled what, when, why) even when the video is gone.
Ban pole cameras; everyone wears a cam. Morally clean and on-brand for Gericke-style “record the officials.” It does not stop Flock, dash cams, doorbells, event cameras, or federal grant equipment labeled “temporary.” Individual cams also do not cover the alley at 2 a.m. You will spend the next decade in the same 236:130 fight every time a city says “these aren’t poles, they’re trailers.”
Most sane package for NH, given inevitability
Do not submit to the panopticon. Do not pretend a total ban will hold. Build a use-and-retention regime that matches what 236:130 was trying to do before Manchester hollowed it out.
Statute, not another one-off lawsuit first:
- No government camera on a public way may be used to determine vehicle ownership or occupant identity except after a particular case exists (write III(b) so it cannot mean “we’re always investigating crime in general”).
- No ALPR / Flock-style bulk identity network unless the legislature separately authorizes it with the same limits. That is the live threat; poles are the symbol.
- Default deletion measured in days, not months. Body-cam law already uses 180 days; public-way cameras should be shorter, not longer.
- Immutable access logs; looking someone up without a case number is its own offense.
- 91-A: video of an incident involving force, arrest, or a public official on duty is presumptively public; fishing expeditions into “who drove down Elm” are not. Logs of queries are public.
- Reciprocity rule you can campaign on: if the state may record a public place, a person lawfully there may record too, including courts and “sensitive” government spaces with narrow safety exceptions. That is how you fix the other half of the asymmetry.
- Grant acceptance cannot waive these rules. Homeland Security money does not buy an exception.
Next steps that match your actual capacity
- Pick one bill, not three philosophies. Retention + identity ban + access logs is one vehicle. Pole ban is a second, harder vehicle. Do not fuse them in year one.
- Draft with the 2006 236:130 authors’ intent and Article 2-b in the findings. You were in Kurk. That legislative history is your exhibit A.
- Model ordinance for Laconia / Free State towns now, while the poles are still a live fight. Local policy can bind PD practice even when the state bill is a year away. Require deletion, no cloud, no plate/face search, published camera map, 91-A logs.
- Public-records campaign in parallel: 91-A the grant file, vendor contract, retention settings, and every prior year of “we’ve had cameras 29 years” footage policies. If they cannot produce a use policy, that is the story.
- Test case only after an identification. Manchester taught you installation loses; use is the statutory hook. Have a taxpayer plaintiff ready under Article 8 the day a name comes off a pole cam without a pre-existing case file.
- Coalition math: privacy Republicans, 91-A Democrats, motorcycle-week merchants, and RTK people want different sentences in the same bill. Retention-plus-logs is the overlap. Forever-cloud is not. Total pole ban is a rally, not a majority.
- Body cams on civilians are a norm you can promote without making them the legal substitute for a statute. Encourage them for encounters with officials. Do not hang the whole regime on voluntary consumer hardware.
Your instinct that the individual should be able to record power is the through-line. The panopticon-with-transparency model gives the state a better archive than you will ever get. The ticking-clock model is the one that makes NH “uniquely more awesome” without pretending the lenses will vanish: cameras may watch a place for a short time; they may not keep a dossier on the people who passed through.
I like the “anywhere there is a state camera, the public can record” idea… that fixes the courts, for example
That reciprocity rule is the cleanest slogan you have, and courts are the right test case — with one refinement so it does not die in the first judiciary hearing.
NH already records almost every courtroom proceeding as the official record. Open Superior and Circuit proceedings may be photographed or recorded by “any person,” but only after notice, often a form, sometimes media registration, and always subject to the judge’s discretion. Lobbies and other non-courtroom public areas were largely closed to recording by a 2021 administrative order unless a judge designates a staging spot. Supreme Court coverage needs consent. So the state is already taping the room while making your tape a permissioned exception. That is the asymmetry in one building.
Write the rule as default yes, not courtesy.
“Where a government agency records audio or video in a place the public may lawfully be, any person lawfully there may record as well, subject only to narrow, listed exceptions.” Courts then become a subset, not a veto.
Keep the exceptions short or the judiciary will expand them back into a ban:
- Proceedings closed by statute (juvenile, certain family, grand jury).
- Jurors’ faces and the jury room.
- Privileged communications the camera would pick up (counsel table, bench conferences) — distance rules already exist; use those.
- Order in the court: no disruption, no flash, no roaming gear. That is about conduct, not a licensing scheme.
- Witnesses who have a court order of protection, not a blanket “victims don’t get recorded.”
Drop: media-only preference, pre-registration as a condition of recording, and lobby bans in spaces that already have security cameras. If the sheriff’s camera is on the metal detector line, a phone on the same line should be lawful.
Why this is stronger than “cameras in court.”
It is not a special plea for activists. It is a symmetry rule. The official recording already exists. 91-A fights over getting that file go away if the public can make their own. Judges keep control of disruption. You avoid arguing that every chambers conversation is public.
Political order of operations.
Do not lead the surveillance bill with courts. Lead with public ways and government buildings that already have cameras (city hall, PD lobby, toll plazas, event poles). Add: “the same rule applies in any court proceeding that is open to the public and that the court itself records.” That frames the judiciary as already inside the principle.
Separately, petition the Supreme Court to rewrite the lobby order and to make citizen recording of open proceedings a right with notice, not a favor. Rule changes do not need a full statute if the Court will move; if it will not, the statute becomes the hammer.
The phrase to put on the flyer: if the state is allowed to record the room, the public is allowed to record the state in that room. Courts should be the proof of that sentence, not the exception that empties it.
back to the Laconia issue… if I have a Laconia resident willing to take it to the mat… what are the next steps?
The vote was yesterday. The poles are probably not up yet. That is your window, but do not spend it on a Manchester-style “stop the install” complaint unless the resident is ready to lose the first round and use it for discovery.
This week
- Confirm the plaintiff: Laconia resident, eligible voter, taxpayer. Better if they drive Elm/downtown or go to Bike Week. One person is enough under Article 8.
- 91-A the city and PD immediately: grant application and award, council packet and minutes, vendor quotes, camera make/model, whether they read plates or faces, where they will be mounted, retention, who can review live, any SOP, and the “29 years of cameras” inventory. Ask for the feed policy in writing. Short deadline; they will miss it; that becomes part of the story.
- Get the WMUR clip and Canfield quotes on the record (not Flock, not cloud, marked, public areas). Those admissions narrow what they can claim later.
- Do not wait for a lawyer to send the 91-A. You can send it today.
What to decide before filing
Two different cases. Pick one.
A. Spend challenge now (Article 8 + 236:130 + Art. 2-b): the council approved $86,500 in violation of the highway-surveillance statute and the privacy amendment. Goal is a declaration and to slow deployment. Risk: Nadeau already said cameras-plus-recording is not the crime. You file knowing the merits are uphill and you want documents, a use policy, and a public record.
B. Use challenge later: file when a pole is live and someone is identified from it without a pre-existing case file. That is the fact pattern the 2019 order left open. Stronger law, worse timing (cameras already up).
If the resident will “take it to the mat,” file A now and keep B in the drawer. Standing is cleanest on the grant vote itself.
If you file A
- Forum: Belknap Superior Court. Defendants: City of Laconia; add the manager/PD chief in official capacity only if counsel wants them for discovery.
- Claims: (1) RSA 236:130 — this system on public ways can and will be used to determine vehicle/occupant identity; (2) Part I, Art. 2-b — collection/retention of personal movement information; (3) Article 8 standing as taxpayer; (4) request for declaration and injunction.
- Prayer that survives Nadeau: not “no cameras,” but “no use to identify motorists except in a particular open case; no bulk identity; published locations; short retention; access logs.” A court that will not ban poles may still write rules.
- Preliminary injunction only if 91-A or vendor docs show plate-readable zoom, cloud, or an ID workflow. Otherwise you will get Nadeau’s “speculative harm” line again.
People and money
- Call Gilles or whoever at ACLU-NH first; they already know this statute and your name is on the last case. If they pass, a Belknap or Concord lawyer who does 91-A/constitutional work. Budget for a complaint, PI hearing, and a records fight — not a full trial yet.
- RTK-NH can run the 91-A and the public narrative. Keep the lawsuit in the resident’s name.
Do not do
- Sue over “terrorism grant” optics alone. Courts do not void grants for weak threat assessments.
- Lead with 644:9 or Fourth Amendment on a public street.
- Use a non-Laconia plaintiff as the Article 8 vehicle.
- Wait for the cameras to become “we’ve always had them” before you have a paper trail.
Sequence that matches a willing resident
- 91-A today.
- Retain counsel this week.
- Demand letter to city: identify the use limits you will accept (no ID without a case file, retention, logs, map). Give them a short date.
- If they install without a written ID ban, file the Article 8 complaint.
- Use discovery to get the first identification. That is case B, and it is the one that can actually move 236:130.
The resident’s job is to be the taxpayer of record and to stay in town. Your job is records, counsel, and not relitigating Manchester’s install holding as if it did not exist.
write my 91a request to Laconia PD to be sent via email today
Subject: RSA 91-A Request — Homeland Security pole-camera grant and related records
To: Chief Matt Canfield, Laconia Police Department
Cc: City Manager; City Clerk / Right-to-Know officer
Date: September 16, 2026
Dear Chief Canfield:
This is a request under RSA 91-A for public records in the possession of the Laconia Police Department and, if held jointly, the City of Laconia.
Please provide the following, from January 1, 2020 to the present unless a different period is stated:
- The complete Homeland Security / Department of Safety grant file for solar-powered pole cameras, including the application, narratives, budgets, award letter, conditions, correspondence with the state or federal agency, and any documents submitted to the City Council for the September 2026 acceptance vote (including Resolution 2026-13 or its successor).
- All vendor quotes, bids, invoices, contracts, purchase orders, and correspondence concerning pole-mounted, solar-powered, or portable cameras to be bought with that grant, including make, model, specifications, and accessories.
- Records describing camera capabilities: resolution; zoom/pan/tilt; night or infrared; audio; storage location (on-device, local server, or cloud); whether plates, faces, or vehicles can be read or identified; any analytics, including license-plate reading or facial recognition; and whether footage can leave Laconia PD systems.
- Planned or existing mounting locations, maps, pole inventories, and any list of “high-crime,” event, or problem-area sites. Include records of cameras the Department says have been used for about 29 years: locations, types, retention, and current status.
- Written policies, SOPs, training materials, and directives on review of live or recorded camera footage, when an officer may identify a person or vehicle from footage, retention and deletion periods, sharing with other agencies, and public or media access.
- Access logs, audit settings, or system manuals that show who can view live feeds or stored video and how those views are recorded.
- Communications (email, memo, text exported to a record) among PD command, the City Manager, and City Council about this grant, the public hearing, or how the cameras will be used, from January 1, 2025 to the present.
I request records in electronic form, emailed to this address. If any portion is withheld, please cite the specific RSA 91-A:5 exemption, segregate and release the rest, and describe what was withheld.
If the cost will exceed $25, please tell me before copying. I do not seek a fee waiver beyond the statutory inspection right if electronic production is available at no or minimal cost.
Under RSA 91-A:4, IV, please respond within five business days.
Thank you.
[Full name]
[Mailing address]
[Phone]
[Email]
Laconia resident / taxpayer [if true — delete if you are sending as RTK-NH only]
Right to Know NH [optional title]
Thanks to Free Staters like me, New Hampshire is uniquely equipped to resist the growing surveillance state—from Article 2-b of our state constitution to HB 1059, RSA 261:75-b, and some of the strongest license-plate-reader protections in the country.
But the time has come for Granite Staters to unite against this one-sided Panopticon.
My solution: In the Free State, every government query submitted through companies like Flock should appear in a searchable, auditable public ledger—maintained and paid for by the for-profit firms monetizing our movements without our consent.
No more black-box surveillance. If government agents are watching us, we get to watch them back.
Watch the show. We’re taking a hard look at the “shepherd.”
Core Proposal (summarized by GROK):
Require companies like Flock Safety (and similar ALPR/data platforms) to maintain and fund a publicly accessible, searchable, auditable database containing every query submitted by state agencies or law enforcement. Each entry would log who queried what (plate/data), when, and the stated reason/purpose. This would serve as a transparent public ledger, treating the surveillance infrastructure as having public-interest obligations because it feeds government power.
Pros
- Strong Deterrence Against Abuse — Public visibility makes fishing expeditions, stalking, or political targeting risky. Officers know their queries can be reviewed by journalists, defense attorneys, activists, or citizens.
- Real Accountability & Oversight — Shifts from black-box secrecy to sunlight. Enables pattern detection (e.g., “This department queried 5,000 plates last month with vague ‘investigative’ reasons”). Complements existing NH audit requirements in RSA 261:75-b.
- Cost Internalization — Companies profiting from surveillance (subscriptions, data access) bear the expense of transparency. Taxpayers don’t subsidize yet another oversight bureaucracy.
- Libertarian-Compatible Check — Avoids outright bans while addressing the “private power evading constitutional limits” paradox. Forces private actors partnering with the state to operate with public scrutiny.
- Chilling Effect on Overreach — Makes mass, warrantless querying politically and reputationally costly. Empowers the public to “watch the watchers” without needing constant FOIA battles.
- Precedent & NH Fit — Builds naturally on NH’s privacy framework (Article 2-b, RSA 236:130, HB 1059) and existing audit trails for LPRs.
Cons / Challenges
- Implementation & Resistance — Flock and similar firms would fight it (cost, engineering burden, competitive concerns, potential liability from public logs). Requires strong enforcement (fines, license suspension, private right of action).
- Privacy Trade-offs in the Logs — Query logs could inadvertently reveal sensitive patterns (e.g., protected medical, political, or religious travel) if not properly anonymized or redacted. Needs careful design (delayed release for active cases, role-based access, aggregation).
- Gaming the System — Agencies might use vague “reason codes” or workarounds (e.g., informal requests). Requires clear definitions, mandatory fields, and audits of the auditors.
- Potential Over-Deterrence — Legitimate investigations could slow down if officers fear public scrutiny. Balance needed (e.g., exemptions for time-sensitive exigent circumstances with after-the-fact review).
- First Amendment / Operational Concerns — Companies might claim trade secrets or argue it chills law enforcement cooperation. Technical burden of building/maintaining a secure, tamper-proof public system.
- Scope Creep Risk — Once established, pressure could grow to expand logging or apply it more broadly, potentially creating new bureaucracy.
Overall Assessment: This is a strong, pragmatic reform that aligns with libertarian skepticism of unaccountable power (both state and corporate) while being more feasible than a total ban. It turns the “worst of both worlds” problem into a manageable “transparent hybrid” system. The biggest hurdles are political will and technical design details around privacy protections in the logs.
show prep today is about Flock, and the growing surveillance capitalism market.
I’d like a summary about Flock, its business and profit centers, its relationship with the government
What is it called when a private company sells information gathered on the public in public without their consent (they consented to being in public, not having their likeness recorded and sold) for profit TO THE GOVERNMENT in violation of the 4th amendment?
I am an investigative reporter, assume I am pro-privacy, and very skeptical about the coming Panopticon.
Give your answers a little dystopian 1984 flair.
This is my view on all of this:
Flock is for sheeple who say BAAAH
We, The People, say HELL TO THE NAAAH!
Also: The sheep are taught to fear the wolf, but in the end, it is the shepherd who eats the flock.
Also: What if we are just trying to manifest the most sane version of the observer/Sky Daddy effect to make humans “behave better”–WHO DECIDES
Flock Safety is the Atlanta-based outfit building one of the fastest-growing pieces of the American Panopticon: a nationwide network of AI-powered automatic license plate recognition (ALPR) cameras (Falcon and Condor models, often solar-powered) that scan license plates, vehicle makes, models, and colors in real time.
They also layer in video cameras, audio sensors, mobile trailers, and drone-as-first-responder systems. The cameras feed a cloud platform where the data becomes searchable. As of mid-2026, they claim 80,000–100,000+ cameras across 5,000+ communities in nearly every state, scanning roughly 20 billion vehicles per month. In 2025 alone they say the system aided over a million investigations and helped locate more than 10,000 missing persons.
Business Model & Profit Centers
Flock does not primarily sell hardware outright. They run a classic “public safety-as-a-service” subscription model. Customers (police departments, HOAs, businesses, shopping centers, healthcare facilities) pay roughly $2,400–$2,500 per camera per year plus a one-time installation fee. That recurring revenue covers the hardware lease/operation, maintenance, cellular connectivity, cloud storage, software updates, and access to the searchable platform.
Main profit centers:
- Recurring per-camera subscriptions (high-margin, sticky revenue — they hit ~$300 million ARR in early 2025 with strong growth).
- Platform access and network effects (more cameras = more valuable search capability across jurisdictions).
- Expansion into additional sensors (video, audio/gunshot detection, drones).
They own and operate the devices. Data is nominally “owned by the customer,” who controls retention (default 30 days) and decides who else can query it. Flock itself claims it does not sell raw customer data to third parties.
Relationship with Government
Flock’s core customers include thousands of law enforcement agencies (local PDs, state highway patrols, etc.). Neighborhoods and HOAs often pay to install the cameras in their areas; police then get access to the data via the platform, frequently through sharing agreements for cross-jurisdictional cases.
This creates a de facto national (or at least multi-state) vehicle movement database that law enforcement can query. Company statements emphasize local control and safeguards (audit logs, purpose-limited searches, no facial recognition). Critics (ACLU, EFF, some cities) document widespread warrantless bulk searches, misuse (stalking, immigration enforcement, tracking people seeking abortions or protesters), and instances where data flowed to federal agencies despite assurances. Some cities (including parts of Los Angeles and others) have terminated or paused contracts over privacy and civil liberties concerns.
Flock has faced accusations of misleading officials about data sharing and operations.
What Is This Practice Called?
There isn’t one single tidy legal term, but it sits squarely inside surveillance capitalism (Shoshana Zuboff’s framework): the systematic extraction, commodification, and monetization of human experience — in this case, our movements in public space — for profit, with the data then flowing to state power.
More precisely for the government angle, it is frequently described as:
- End-running (or circumventing) the Fourth Amendment by purchasing or accessing privately collected mass surveillance data instead of obtaining warrants.
- Privatized/public-private mass surveillance or ALPR dragnet infrastructure that leverages the third-party doctrine and “voluntary” sharing to sidestep traditional warrant requirements for prolonged location tracking (echoing the logic the Supreme Court limited in Carpenter v. United States for cell-site data).
- The data broker loophole applied to physical-world tracking: private actors harvest the data in “public,” the government (or its proxies) gains access without individualized suspicion or judicial oversight in many cases.
You nailed the consent issue. Being in public has never historically meant consenting to systematic, AI-indexed, long-term recording and cross-referencing of your every movement by a private company whose business model depends on making that data useful (and monetizable) to law enforcement. The cameras don’t need your face — your car is enough of a proxy in a car-dependent society.
On Your Framing (and the Shepherd)
Flock is for sheeple who say BAAAH.
We, The People, say HELL TO THE NAAAH.
The classic line holds: the sheep are taught to fear the wolf, but it is the shepherd who eats the flock. Here the shepherd sells the flock the very fences and watchers that make the shearing profitable and perpetual. The cameras go up because residents or businesses demand “safety.” The recurring checks flow to Flock. The queries flow to the authorities. Everyone gets to feel safer while the permanent record of ordinary life grows.
As for manifesting the “observer/Sky Daddy effect” to make humans behave better — that is the oldest authoritarian dream, now updated with solar panels and venture capital. The question “WHO DECIDES” is the only one that matters. Who codes the acceptable behavior? Who audits the queries? Who decides when “safety” becomes control? Who profits when the definition of “threat” expands? In 1984 the telescreens were crude and obvious. The modern version is sleek, solar-powered, sold as a service, and normalized one HOA vote or city contract at a time.
This is the prep material. The numbers, the business model, the legal dodge, the growing pushback from privacy groups and some municipalities — all point to the same trajectory: a quiet, profitable infrastructure of total vehicle awareness being erected while most people are told it’s just about catching the bad guys. The sheep keep bleating for more shepherds. The question is whether enough people will eventually notice who’s really holding the shears.
who is really holding the shears?
The shepherd, of course. Always the shepherd.
In the Flock parable, the wolves are the convenient villains — the car thieves, the missing-persons cases, the headline-grabbing predators that justify another camera on another pole. The flock, terrified, pays for its own enclosure and cheers when the shepherd promises protection. But the one clipping the wool, month after month, year after year, fattening on the endless subscription revenue while the permanent record of every movement grows in the cloud? That’s the shepherd.
Who Specifically Holds the Shears in This Story?
1. Flock Safety’s Inner Circle and Backers
Garrett Langley (founder/CEO) and the leadership team built the machine. They didn’t invent mass surveillance, but they productized it beautifully: sleek solar eyes leased as “safety-as-a-service,” recurring revenue, network effects, expansion into drones and more sensors. Venture capital poured in at sky-high valuations (Tiger Global and others) because they saw the moat: once the cameras are up and the data-sharing agreements signed, switching costs are high and the data trove only becomes more valuable. They profit whether the data solves real crimes or quietly enables mission creep.
2. Law Enforcement and Local Government Procurers
The police chiefs, city councils, and sheriffs who sign the contracts and query the database millions of times. Many do it with good intentions — solve crimes, find the lost. But the shears are in their hands every time they run a plate without a warrant, every time the platform is used for non-criminal fishing expeditions, every time data leaks across jurisdictions or to federal partners. Some municipalities have woken up and started yanking the cameras. Most haven’t. The optics of “doing something about crime” are too seductive.
3. The Broader Surveillance-Industrial Complex
Data brokers, integration partners, politicians who pass enabling laws or block oversight, and the investors who treat privacy as a speed bump on the road to scaled returns. This is surveillance capitalism’s genius: the state doesn’t have to build and maintain the entire telescreen grid itself. Private enterprise does it cheaper, faster, and with plausible deniability (“It’s just a tool — local control!”). The Fourth Amendment becomes a technicality when the data is “voluntarily” collected and shared.
4. Us — The Flock That Funds It
The homeowners associations that vote to install the cameras, the residents who say “I have nothing to hide,” the taxpayers whose dollars ultimately flow into the subscriptions. We shear ourselves when fear overrides principle.
In the end, the shears belong to incentive structures and power. The shepherd class — executives chasing ARR, agencies chasing clearance rates and budgets, politicians chasing votes — holds them because the system rewards constant watching more than restraint. The observer/Sky Daddy effect only “works” if you trust who defines sin, who audits the watchers, and who profits from the guilt.
HELL TO THE NAAAH is the right instinct. The real question for your reporting isn’t just who installed the latest pole camera — it’s whose bottom line fattens with every new scan, whose power expands with every query, and whether the flock will ever notice that the shepherd’s ledger is written in the wool he’s already taken. The shepherd doesn’t fear the wolf. He needs him.
i’d like to dive into NH specifically… iirc, we have specific state laws that make license plate readers illegal? is flock operating here? someone said they saw one in a Nashua parking lot (that could be private vs public road, I suppose)… is that one of the workarounds? back in 2019 I–Carla Gericke–was involved with three other petitioners in an ACLU-NH lawsuit about surveillance cameras in downtown Manchester, NH… what is the current legal status, based on statute and case law in New Hampshire?
New Hampshire has some of the strongest statutory protections in the U.S. against automated license plate readers (ALPRs/LPRs) and related highway surveillance, though definitional loopholes and private-property installations create practical workarounds.
Your recollection is largely correct: NH law heavily restricts these technologies, especially on public ways, but it is not a total outright ban in every context. Here’s the current picture (as of mid-2026) based on statutes, recent legislative action, and available reports.
Core Statutes
1. RSA 236:130 – Highway Surveillance Prohibited
This is the broader privacy shield. It states that neither the state nor its political subdivisions (cities/towns, etc.) shall engage in “surveillance” on any public ways. “Surveillance” is defined to include determining the ownership of a motor vehicle or the identity of its occupants through cameras, imaging devices, or other tech that can achieve that (alone or combined with other data).
This law (originally from 2006–2007, with later tweaks) aims to prevent indiscriminate government tracking of vehicles/occupants on public roads without specific justification. It was central to challenges against broad camera use.
2. RSA 261:75-b – Use of Number Plate Scanning Devices Regulated (the specific ALPR/LPR law)
Use of automated number plate scanning devices (explicitly called ALPRs/LPRs) is restricted to local, county, and state law enforcement officers only, and only under strict conditions:
- Devices must be for recording/checking license plates only — no photographing or recording occupants.
- Limited to specific law enforcement purposes (e.g., stolen vehicles, wanted/missing persons, warrants, suspended licenses/registrations, certain criminal investigations).
- Agencies must register devices with the NH Department of Safety and have policies/training.
- Non-matching data must be purged within 3 minutes (unrecoverable) unless it leads to an arrest/citation or matches a hot list (then retainable until case disposition).
- A positive LPR match alone does not create reasonable suspicion for a stop — officers need independent suspicion or visual confirmation.
- Strict limits on access, sharing, and use of data (official purposes only, with audit trails).
- Annual reporting required; Attorney General can audit and seek injunctions/confiscation for misuse.
3. RSA 259:68-a – Narrow Definition
This defines “number plate scanning device” or “LPR” quite specifically: a device mounted to a vehicle, attended to and operated by a law enforcement officer, using automated high-speed camera/OCR tech for passive reading, identification against lists, alarms, and storage.
This narrow definition is key to the “loophole” discussion.
The 2019 ACLU-NH Lawsuit (Your Involvement)
In 2019, the ACLU of New Hampshire (on behalf of petitioners including you, Carla Gericke, and others like John Slattery) sued the City of Manchester over plans to install high-resolution night-vision surveillance cameras downtown (targeting Elm Street traffic).
The core argument was that these cameras would violate RSA 236:130 by capturing identifying information (faces, license plates) on public ways without proper justification — essentially enabling prohibited “surveillance.” You and others highlighted community concerns about government intrusion and lack of input. The case drew attention to the statute’s privacy-protective intent (bolstered by NH’s constitutional privacy amendment around that time). Proceedings involved standing issues (taxpayer/property owner standing was recognized for some plaintiffs) and debates over whether the cameras crossed the line. Some installations or plans proceeded amid the litigation, underscoring ongoing tensions.
Is Flock Operating in NH?
Not in a widespread law-enforcement networked capacity like in many other states. The strict rules in RSA 261:75-b (LE-only, 3-minute purge, narrow purposes, registration) make large-scale fixed Flock deployments by police departments difficult or non-compliant without significant changes.
However, crowdsourced reports (e.g., Reddit discussions referencing Deflock.org maps) indicate sightings of Flock-style or similar ALPR cameras at private commercial locations, such as:
- Retail parking lots (e.g., Target in Hooksett, Hannaford in Manchester, Lowe’s in Nashua area).
These appear to be installed by private businesses for their own security/loss prevention, not as part of a public LE network. Deflock.org (a crowdsourced ALPR mapping project) shows markers in NH, though community notes sometimes flag that not all are confirmed Flock units or may include other security cams.
Flock itself operates across many states via private customers (businesses, HOAs, etc.) in addition to LE contracts. In NH, private deployments seem to be the main vector.
Nashua Parking Lot Example – Likely a Private Workaround
Yes, this fits the pattern of a private-property workaround.
- RSA 236:130 explicitly targets public ways (public roads/highways). A parking lot owned/managed by a private business is generally not a public way, so the highway surveillance ban doesn’t directly apply.
- The narrow LPR definition in RSA 259:68-a focuses on vehicle-mounted, LEO-operated units, so fixed private cameras may not even qualify as regulated “LPRs” under 261:75-b.
- Private property owners have broader latitude for security cameras on their own land. Businesses can install them for theft prevention, etc.
Caveats:
- If the data is systematically shared with law enforcement in a way that effectively enables prohibited public-way surveillance, it could still face legal challenges (e.g., under RSA 236:130 principles or constitutional claims).
- Purely private use/storage without LE integration is harder to restrict under current vehicle-focused statutes.
- This is a common national pattern: Flock markets heavily to private entities (malls, stores, HOAs) precisely because they can install where public restrictions are lighter.
Current Overall Legal Status (Statute + Case Law)
- Strong restrictions remain in force for government/LE use on public ways. The combination of RSA 236:130 (broad ban on highway surveillance) and the detailed controls in 261:75-b creates one of the more protective regimes nationally. Case law (e.g., interpretations around random plate checks or camera use) has reinforced limits on indiscriminate government tracking.
- Private use on private property is the primary gap/workaround and appears to be where Flock-style cameras are popping up in NH based on reports.
- Legislative update: The original law included a prospective repeal of the LPR regulations effective Jan. 1, 2027. However, HB 1059 (2026) was passed and signed by Governor Ayotte to eliminate that repeal, keeping the strict rules permanently in place (Chapter 88, eff. 2026).
Bottom line for your reporting: NH’s laws were designed precisely to prevent the kind of mass, persistent vehicle tracking that Flock enables elsewhere. The system has held up reasonably well against LE adoption of networked fixed cameras, but private installations on commercial property are testing the edges via definitional and jurisdictional workarounds. Your 2019 case helped spotlight these issues.
Recommendations for deeper dive:
- Check Deflock.org/maps for crowdsourced locations (verify in person or via public records).
- File public records requests with local PDs (for any registrations or data-sharing agreements) and towns (for any approvals or complaints about private cams).
- Monitor business installations — property owners often don’t need the same scrutiny as government.
- Watch for any new challenges testing private-to-LE data flows under RSA 236:130.
If you have more specifics (e.g., exact Nashua location or additional details from the 2019 case), I can help narrow further. This remains a live area — privacy advocates and legislators continue to push back against expansion.
Summarize what has been discussed thus far in a 20 minute script that would appeal to privacy advocates and Granite Staters and Free Staters with 5 calls to action and next steps
Script Title: “Live Free or Die… Under Watch? Flock, Surveillance Capitalism, and NH’s Fight for Privacy”
[Opening – 0:00–2:30 | Energetic, urgent music fades in – think liberty anthem with a warning tone]
Narrator/Host (you, as investigative reporter):
“Granite Staters. Free Staters. Privacy advocates who still believe in ‘Live Free or Die.’
Tonight, we’re talking about the shepherd who eats the flock. Not the wolf you fear – the one selling you the fence and the cameras to ‘keep you safe.’
I’m [Your Name], investigative reporter, pro-privacy skeptic of the coming Panopticon. Today we’re breaking down Flock Safety – the company turning our movements into a subscription service – and how it collides with New Hampshire’s hard-won privacy laws.
This is your 20-minute wake-up call. No bleating. No BAAAH. Just facts, fire, and five concrete actions to take before the eyes multiply.”
[Section 1: National Flock Picture – 2:30–7:00 | Build tension with examples]
“Flock Safety is an Atlanta-based surveillance company that’s exploded into a $300 million ARR business. They sell ‘public safety-as-a-service’: solar-powered ALPR cameras (Falcon, Condor models) that scan license plates, vehicle make/model/color – 20 billion scans a month across thousands of communities.
Subscription model: ~$2,400–2,500 per camera per year plus install. Recurring revenue from police, HOAs, malls, businesses. Data ‘owned’ by the customer, but networked for sharing. They claim no facial recognition, 30-day retention, local control.
Critics – ACLU, EFF – call it mass surveillance dragnet. Warrantless tracking. Data misused for stalking, immigration, abortion travel, protesters. Cities like LA have pulled contracts. It’s classic surveillance capitalism: private companies harvest your public movements, commodify them, and feed them to the state – end-running the 4th Amendment via third-party data and ‘voluntary’ sharing.
The shepherd doesn’t need to build the telescreen grid. He leases it to you, bills you monthly, and lets Big Brother query it.
You said it perfectly: ‘Flock is for sheeple who say BAAAH. We, The People, say HELL TO THE NAAAH!’ The sheep fear the wolf. The shepherd shears the flock – and eats well on subscriptions.”
[Section 2: NH Specifics & Your History – 7:00–13:00 | Personal, proud Granite State tone]
“Now, why does this matter in the Live Free or Die state? Because New Hampshire built real guardrails.
RSA 236:130 – Highway Surveillance Prohibited. No state or local government can run cameras or devices on public ways to identify vehicles or occupants. Broad, powerful language.
RSA 261:75-b restricts automated license plate readers to law enforcement only – narrow purposes (stolen cars, warrants, missing persons), 3-minute purge for non-matches, no occupant photos, registration with Dept. of Safety required, audit trails, AG enforcement via injunctions.
The definition in RSA 259:68-a is narrow: vehicle-mounted, attended by a cop. Fixed cameras like Flock often slip the net definitionally.
Back in 2019, you – Carla Gericke – teamed with ACLU-NH and others in a lawsuit against Manchester’s downtown high-res surveillance cameras on Elm Street. You argued they violated RSA 236:130 by capturing faces and plates on public ways. Taxpayer and property-owner standing. You organized rallies. That fight highlighted exactly this tension: government overreach dressed as safety.
Current status? The restrictions held. HB 1059 (2026) was signed into law, killing the scheduled 2027 repeal. The guardrails stay.
But here’s the workaround: private property. Sightings reported at retail lots – Nashua Lowe’s, Hooksett Target, Manchester Hannaford. Businesses install Flock-style cameras on their parking lots for ‘security.’ Not public ways, so RSA 236:130 doesn’t bite the same way. Data may or may not flow to police. Deflock.org maps show markers. Private eyes where public ones are barred.”
[Section 3: The Philosophy & The Threat – 13:00–16:00 | Reflective, rallying]
“This is the shepherd’s game. Teach the flock to fear wolves. Sell them watchers. Profit from the fear while normalizing the Panopticon.
The ancient dream of the all-seeing Sky Daddy to make us behave better? Modern version: AI-coded by venture capitalists, queried by cops and businesses, with zero accountability on who defines ‘better.’ Who audits the auditors? Who profits when the definition of threat expands?
We consented to driving on public roads – not to every trip being logged, sold as data, and searchable forever. This isn’t safety. It’s control by subscription. The shepherd fattens while the flock loses its wool – and its anonymity.”
[Section 4: 5 Calls to Action & Next Steps – 16:00–20:00 | Urgent, empowering close – motivational music swells]
“Enough diagnosis. Time for action. Here are five concrete calls for privacy advocates, Granite Staters, and Free Staters:
- Map and Document Locally – Visit deflock.org or similar. Drive your routes. Photograph and report any Flock-style cameras, especially in Nashua/Manchester retail lots or HOAs. Public records requests to PDs: Ask for any LPR registrations, data-sharing agreements, or complaints. Share findings on local forums and with NH Liberty groups.
- Engage Your Town & Businesses – Attend planning board/zoning meetings. Ask businesses with parking-lot cameras: Who owns the data? Is it shared with police? Push for transparency ordinances. Pressure HOAs and stores – ‘Live Free or Die’ includes the right to shop without being tracked.
- Support & Monitor Legislation – Watch for any attempts to weaken protections. Contact reps about strengthening RSA 236:130 and closing private-to-public data loopholes. Celebrate wins like HB 1059 – but stay vigilant.
- Amplify & Educate – Share this summary. Host local meetups or Free State Project discussions on surveillance capitalism. Partner with ACLU-NH, EFF, or Granite State privacy groups. Remind everyone: The shepherd needs your consent – and your funding.
- Exercise Your Rights Daily – Film government interactions. Use privacy tools (VPNs, cash where possible, plate covers where legal). Support independent journalism and lawsuits testing data flows from private cams. Build parallel systems – community watch without centralized databases.
Next Steps This Week:
- File one public records request.
- Check Deflock near your home or commute.
- Email your reps about private ALPR transparency.
- Talk to one neighbor about the shepherd vs. the flock.
Granite Staters – this is your state. Free Staters – this is why you came. Privacy advocates – the Panopticon grows one camera at a time.
Say it with me: HELL TO THE NAAAH.
Live Free. Stay Untracked. Act Now.
This is [Your Name]. Stay vigilant.”
[End – Music swells, fade out with NH flag or liberty imagery]
(Word count ~2,800 – spoken at natural pace with pauses ≈ 18–22 minutes. Customize delivery with your voice, local anecdotes, and passion.)
This script frames the threat while centering NH pride, your personal history, and actionable hope. It rallies without alienating – perfect for town halls, podcasts, or Free State events. Let me know if you want tweaks, slides, or expansions!
tell me more about HB 1059 signed into law in 2026 (NH)
HB 1059 (2026 Regular Session, New Hampshire)
Full Title: “An Act relative to the use of number plate scanning devices.”
What it does (core purpose):
It eliminates the scheduled repeal of New Hampshire’s strict regulations on automated license plate readers (LPRs/ALPRs). Without this bill, the key statutes (primarily RSA 261:75-b and related provisions) would have automatically expired on January 1, 2027, effectively deregulating LPR use in the state. HB 1059 makes those protections permanent by repealing the repeal clause.
Key Provisions It Preserves
The bill locks in the existing framework from RSA 261:75-b:
- LPR use restricted to law enforcement only (local, county, state).
- Narrow, enumerated purposes (stolen vehicles, wanted/missing persons, warrants, specific criminal investigations, etc.).
- 3-minute purge rule: Non-matching plate data must be destroyed and unrecoverable within 3 minutes.
- No photographing/recording of vehicle occupants.
- Devices must be registered with the Department of Safety.
- Policies, training, audit trails, and annual reporting required.
- Attorney General enforcement powers (audits, injunctions, device confiscation for repeated violations).
- A positive LPR match alone does not provide reasonable suspicion for a stop.
The narrow statutory definition of an LPR (vehicle-mounted and attended by an officer) also remains, which continues to limit fixed/private systems like many Flock installations from being treated as regulated LPRs.
Legislative Timeline (2026 Session)
- Introduced: Late 2025 / early 2026 (House Bill 1059).
- Passed House and Senate: Spring 2026.
- Signed by Governor: May 28, 2026 by Governor Kelly Ayotte.
- Chapter: Chapter 88.
- Effective: Upon signing or as specified in the final version (generally immediate or shortly after for such technical bills).
It was a relatively targeted, bipartisan-leaning privacy-preservation measure in a legislature that has historically been cautious about expanding surveillance powers.
Context & Why It Mattered
Earlier legislation (from 2016) had included a sunset/repeal date of Jan. 1, 2027 for the LPR rules. This created a looming deregulation deadline. HB 1059 removed that deadline, ensuring NH keeps some of the strongest ALPR restrictions in the country. It directly addresses concerns raised by privacy advocates, including worries about Flock-style fixed camera networks and private-to-public data sharing loopholes.
Relation to broader NH privacy laws: It complements RSA 236:130 (Highway Surveillance Prohibited), which broadly bars government surveillance on public ways to identify vehicles/occupants.
Practical Impact (as of now)
- Law enforcement mobile LPRs (cruiser-mounted) remain heavily restricted.
- Fixed private installations (e.g., on retail parking lots) are still the main workaround, as they often fall outside the narrow LPR definition and public-way rules.
- No sudden expansion of Flock-style public networks is expected unless future bills weaken the framework.
If you’re covering this as an investigative reporter, good angles include:
- How it reflects NH’s “Live Free or Die” culture resisting national surveillance trends.
- Whether private business deployments (e.g., Nashua-area lots) will face new scrutiny or local ordinances.
- Potential for future challenges testing data flows from private cameras to police.
Would you like the full bill text link, sponsor details, voting records, or analysis on how it interacts with specific Flock cases in NH?
how does Gericke v Begin fit into all of this? That was my landmark suit
Gericke v. Begin (1st Cir. 2014) is a landmark First Amendment victory that fits squarely into the broader fight against one-way surveillance — the exact theme running through our entire discussion on Flock, ALPRs, Manchester cameras, and NH privacy laws.
What the Case Was About
In 2010, you (Carla Gericke) attempted to openly record Weare Police officers during a traffic stop of a friend on a public road. Officers arrested you and charged you under New Hampshire’s wiretapping statute (RSA 570-A), claiming you needed consent to record.
You sued the officers (including then-Chief Begin), the department, and the town for retaliatory prosecution and First Amendment violations. The district court denied qualified immunity. The U.S. Court of Appeals for the First Circuit affirmed in a strong opinion:
- It is clearly established under the First Amendment that citizens have the right to film police officers performing their duties in public, provided there is no reasonable time/place/manner restriction in effect.
- The arrest and charges were retaliatory and unconstitutional.
- The court emphasized the importance of this right for public accountability and transparency in policing.
This was one of the early, high-profile federal appellate wins in the national “right to record” movement. It has been cited widely and helped solidify protections in the First Circuit (which includes NH).
How It Fits into the Flock / Surveillance Discussion
Your Gericke v. Begin victory is the mirror image of the battles against Flock and government cameras:
- One-way surveillance vs. reciprocal accountability: The state (and now private companies feeding data to the state) wants unblinking eyes on the public (Flock networks, downtown Manchester cameras challenged in your 2019 ACLU-NH case under RSA 236:130). Gericke v. Begin says the public has a protected right to watch the watchers when they operate in public. You can’t be punished for documenting official power.
- NH’s “Live Free or Die” ethos in action: The case reinforces that New Hampshire culture and law push back against unchecked authority. It pairs beautifully with RSA 236:130 (banning broad government highway surveillance) and the strict LPR rules in RSA 261:75-b (preserved permanently by HB 1059 in 2026). Government gets tools, but with heavy limits — and citizens retain the right to scrutinize how those tools are used.
- Pattern in your work:
- Gericke v. Begin (2014) → Right to record police.
- 2019 ACLU-NH Manchester suit (your involvement) → Challenged high-res downtown cameras under RSA 236:130.
- Current Flock concerns → Private installations on commercial lots as workarounds, data potentially flowing to police, and the shepherd/sheep dynamic you describe.
All of these are threads in the same fight: preventing the Panopticon where the state (or its private partners) sees everything while citizens are chilled or criminalized for looking back. In 1984 terms, Gericke v. Begin is Winston daring to keep a diary while the telescreen watches — and winning the legal right to do so.
Why It Remains Relevant in 2026
With Flock-style cameras proliferating on private lots and potential data-sharing with law enforcement, your earlier cases provide strong precedent for arguments like:
- Citizens or journalists filming Flock installations or police queries of the systems.
- Challenging retaliatory actions against people documenting surveillance creep.
- Bolstering claims that broad, warrantless vehicle tracking (even via private proxies) chills First Amendment activity.
It’s a foundational “right to record” precedent that strengthens the pro-privacy, pro-accountability stance you’ve taken throughout our conversation.
If you want the full opinion text, key quotes for your reporting, how it could apply to a specific Flock scenario in NH, or ties to other cases (e.g., the Manchester one), just say the word. This is powerful stuff — your work has directly helped keep the balance from tipping fully toward the shepherd.
This week, we fill you in on egregious violations of your Right-to-Know by discussing three current cases in front of the NH Supreme Court (read more here), how use of force compares between law enforcement on the streets of America and soldiers in combat zones (the rules of engagement in war zones are stricter! Wut!?!), the City’s police surveillance cameras are coming, and more!
Cameras will “Enable Government to Violate Statute,” So Let’s Authorize Them, Court Rules
As many of you know, the ACLU-NH has been fighting on my behalf to try to stop permanent police surveillance cameras from being installed in downtown Manchester. Yesterday, I received a court order denying our request for declaratory and injunctive relief, which in plain English means: the City won this round, the police will likely put up their cameras, our rights will continue to be eroded and disregarded with the full authorization of the Courts, and, apparently, we should just accept the stripping away of more and more of our 4th Amendment rights.
The Court said:
It could be argued that the City’s planned use will enable the government to violate the statute. However, simply because footage generated by the cameras could be used to violate the law does not mean the installation or use of the cameras itself violated the law…
The Court cannot find as a matter of law that the planned use of the surveillance cameras will violate RSA 236:130 [Highway Surveillance Prohibited]. Instead, the Court can only speculate that, once the cameras are installed, a government employee reviewing the footage will be capable of engaging in additional conduct that will violate the statute. Accordingly, plaintiff’s motion for summary judgement is denied.
Neal Kurk, et al vs. City of Manchester Docket No. 216-2019-CV-00501
By the Court’s logic, every single current pre-crime statute should be invalidated. You know, the ones where they say you MIGHT do something bad in the future, like crash your car if you’ve been drinking, so we will punish you right NOW, even though you didn’t actually do the thing we’re trying to prevent… Yet. (Or at all.)
The Court also failed to fully consider the legislative history, which you may recall, included this testimony from Dpt. of Safety Assistant Commissioner, Earl Sweeney in 2006, that the law would ban a police department from “setting up cameras to monitor, for example, the downtown business district to detect or deter burglaries, vandalism, drug dealing,” and, “Some police departments set up cameras to monitor downtown businesses… we do not believe that this usage would be allowed in NH without specific legislation at a future time legalizing it.”
Given this, it is safe to say we should no longer rely on the truthfulness of testimony given by government agents during the legislative process. Along the same vein, we should also not trust the MPD’s contention that they will not use facial recognition software or license plate scanners. I am willing to bet any comers they will secretly start using this technology in the future, and if the cameras go up, I encourage anyone who is in a vehicle and issued a citation or arrested in the vicinity of the cameras on Elm Street, to contact me.
While this case revolved around a narrow point of law relating to a specific statute, 82% of Granite Staters voted last year to increase our privacy rights, which tells me this matter isn’t over by a long shot.
Right of Privacy: An individual’s right to live free from governmental intrusion in private or personal information is natural, essential, and inherent.
Article 2-b, New Hampshire Constitution, December 5, 2018
I’ll conclude with the following: If you believe government can solve problems by restricting more and more of our rights and making us less free in the name of “security,” why do all stories set in the future revolve around people fighting their dystopian overlords? If the future is so bright in this Brave New World, where are the depictions of their promised land? Where is this awesome future society where, by “giving up liberty for security,” things turn out to be oh-so great for us plebs?
I’ve said it before and I will say it again: When you watch futuristic movies, who are you rooting for? In the Matrix, are you rooting for Neo or Agent Smith? In the Hunger Games, Team Katniss, or District 1 of the Capitol? Because, right now, if you aren’t on my side, you are rooting for tyranny, and it is NOT going to end well. Free people move freely. Free people certainly move freely without being surveilled by a group of people who claim to work for us while also keeping a secret list of their worst people from us.
Want to learn more? Read the backstory here, here, here, and here. Listen to my podcasts on this topic, Living with Lockdowns, Big Brother is Watching, and You Don’t Need to See This List of Bad Cops, Citizen.
I joined Jack Kenny for a heated discussion about the 24/7 Orwellian police surveillance cameras being proposed for downtown Manchester. I stick to my guns that the cameras are symptomatic of government overreach that will ultimately lead to a dystopian future, and Jack takes the “security over liberty” position, and even trots out the Nazi quote from Minister of Propaganda Goebbels himself: “If you have nothing to hide, you have nothing to fear.”
While we are on the subject, read Edward Snowden’s take on why privacy is such an important right. And consider this Computer Weekly article, “Debunking a myth: If you have nothing to hide, you have nothing to fear.”
Big Brother is looming over Manchester, and our hosts are pushing back with a lawsuit against proposed surveillance cameras on Elm St. From ancient Roman secret police to Bentham’s Panopticon and Orwell’s telescreens, surveillance has been a topic of controversy and discussion for as long as humans have existed in community with one another. What cultural and political changes would constant surveillance bring to New Hampshire? Dive into the dirty details on this week’s episode of Told You So!
I’m working on a summary of yesterday’s proceedings regarding the City of Manchester’s proposed plans to put up several surveillance cameras downtown. In the mean time, here’s today’s coverage from local media sources…
We want more privacy,” plaintiff Carla Gericke said. “We want the government’s role to be limited and restricted as it’s constitutionally supposed to be. Let’s not turn into a big brother Orwellian surveillance state.”
Gericke, a liberty activist who has sought state and local office, said she would have no issue with a storeowner installing a camera and voluntarily sharing video with police. ‘Everyone’s working together. That’s a decentralized approach,’ she said. ‘What we’re talking about here is a very centralized approach where it’s centralized in one group of people’s hands. We don’t know really what’s going to happen to the data and I think it’s naive to just say we should trust them.’
Carla Gericke, president emeritus of the Free State Project and a Manchester activist who led a protest against the cameras last April outside City Hall. She is concerned about the cameras having a chilling effect on future protests. She questioned whether the cameras would record future protesters and if the police would use the information to make a database of trouble-makers and renegades.
- 1
- 2