The Ratchet
A contract is not a single act. It is a document that keeps being edited, and the edits are where the meaning is set. A city signs to buy a network of cameras under terms that promise the vendor will not sell what the cameras collect. That promise is the thing that lets a council vote yes. The cameras go up; the detectives start pulling the footage; the city builds a year of its police work on top of the feed. And then the document, which lives on the vendor's own servers and can be amended at will, begins to change. The protective sentence is removed and called redundant. The licence over the data is made perpetual. The forum for any dispute moves to a private arbitrator under the law of another state. The exit a government uses, simply not appropriating the money next year, is made harder in the very same revision. None of these edits, read alone, is plainly the move. The move is the sequence, and its timing: every degradation lands after the customer has already installed, integrated, and come to depend on the thing. This is the layer Volume III is about, and this case is its anchor.
§01 · The clause that made it approvable
Begin where the city began, with the sentence it could point to. Early Flock contracts carried plain protective language: the vendor does not own, and shall not sell, Customer Data. That sentence is not decoration. It is the specific assurance a city manager carries into a council chamber and a privacy-anxious public meeting; it is what converts "we are putting automated plate readers on every arterial road" into something a body of elected people can approve. A binding promise enforceable by the buyer, written into the agreement, is a thing with legal weight: if the vendor sold the data, the customer could sue on the contract.verified
On the strength of language like that, the placement happens. The hardware goes into the ground at intersections and on poles. Detectives begin to query the network as a matter of routine; cases come to assume the feed exists. Neighbouring agencies are granted access and the city's cameras join a wider lattice of shared reads. Within months the city is not a buyer evaluating a product; it is an institution whose daily operation runs through the vendor's system. That is the precondition the rest of the case depends on, and it is worth naming as a structural fact rather than a complaint: the protection that made the deal approvable, and the dependency that makes the deal hard to leave, were installed in that order, the protection first.analysis
§02 · Four edits, seven months
Now the layering. In the seven months before a contract dated the sixteenth of February 2026, the vendor's terms were amended at least four times. Each amendment, taken by itself, has a clean cover story: a redundancy removed, a standard industry provision added, a simplification, a routine update. Read one at a time, none of them is the move. Read down the column, the document that emerges is a different instrument than the one the city approved.reported
| The edit, as the document carries it each defensible on its own |
What it does to the deal read down, not across |
|---|---|
| Remove a "redundant" sentence. The line "Flock shall not sell Customer Data" is deleted, described as housekeeping, not a change of position. | The enforceable promise is gone. What protected the buyer is now, at most, a statement on a blog. |
| Broaden the licence. The grant shifts from data use "as may be necessary to provide the Services" to an "irrevocable, perpetual" licence, plus a right to use the data "to support and improve" the vendor's products. | The licence no longer ends with the contract, and the data is opened to the vendor's own product development. |
| Move the forum. Disputes are routed to private arbitration under the law of Georgia. | A public body loses the public courtroom, in its own state, on the public record. |
| Widen the liability shield. The vendor's protections against liability are expanded, reaching toward willful misconduct and gross negligence. | The cost of a breach tilts toward the taxpayer, away from the party holding the data. |
| Narrow the exit. Termination is made harder, including where a council declines to approve, or fails to appropriate funds for, the next term. | The standard government off-ramp is shrunk, precisely the one cities were starting to use. |
Say the cautious part plainly. Companies amend their terms constantly, and most amendments are exactly the housekeeping they claim to be. The claim here is narrower and turns on timing, not on motive: that the protections present when the customer consented were removed once consent was no longer cheap to reverse, and that the removals were framed as routine. Whether anyone intended that arc is not the case's to assert. That the document travelled it is.analysis
§03 · You own it. You cannot reach it.
The integration step is the headline the customer is left holding: you own one hundred per cent of your data. Set that sentence against the clauses underneath it. The amended licence grants the customer formal ownership, and in the same breath gives the vendor "the exclusive right to determine and control the method, timing, format, and medium" by which the customer reaches its own data. Customers have reported receiving degraded, low-resolution copies stripped of metadata such as timestamps. Ownership, here, has been separated from access, from control, and from any practical ability to do the things ownership is supposed to mean.reported
Two ordinary words are doing the laundering, and they are worth pulling apart. The first is the definitional one. "Customer Data" in the amended terms folds several prior categories, customer-generated records, training data, footage, into a single bucket, and then a single licence is granted over the whole bucket. In an earlier version a customer might own metadata but not the footage; in the new version the customer "owns" everything while the vendor holds a perpetual licence to use all of it. The merge is what makes the licence total: widen the definition, and one grant now reaches everything.reported
The second word is "ownership" itself, deployed as a stamp. A licence that grants the vendor perpetual use and exclusive control of access is, in substance, a structure in which the vendor holds the data. Stamp the word "ownership" on the customer's side of that structure and it reads, in a press release and a sales deck, as customers own everything, when what the contract grants is closer to the opposite. Ownership is not false on paper. It is simply irrelevant to control once the licence has taken the control away.analysis
The customer owns one hundred per cent of a thing it cannot reach, cannot withdraw, and cannot take anywhere else.
§04 · The door that shrinks as you reach for it
This is the spine of the volume, so slow down on it. A private buyer who hates a contract can usually walk at renewal. A government has a particular, structural version of that exit: it can decline to appropriate the money. A council can vote not to approve next year's contract, or simply not fund it, and in the normal run of things that is the end. Across the past year, that is exactly what cities began to do with this vendor; by the civil-liberties account, nearly fifty of them declined to approve or renew.reported
The amended terms answer that exit by narrowing it. The contract is made harder to terminate, the summary notes, "including when a town or city council votes not to approve a contract or fails to appropriate the funds for it." Read those two facts together and the shape appears: the standard way a government leaves is being constricted at the same moment governments are using it. The door is being made smaller as the hand reaches for the handle. And termination, even where it can be reached, ends the customer's access but not the vendor's licence; you can stop paying and stop receiving, and the perpetual grant over everything already collected stays where it is.reported
There is a further question raised here, and it is carried as a question, not a holding. Analysts note that a narrowed non-appropriation exit may collide with a basic rule of municipal finance: government contracts generally cannot bind future budgets, because a present council cannot commit money a future council has not appropriated. If the terms try to convert a declined appropriation into a continuing obligation, the argument runs, they may be reaching for an unconstitutional debt. That is a live legal theory about where this drafting leads, advanced by readers of the contract; it is not a court ruling, and this case files it as exactly that.reported
And underneath the legal question sits the plain one. A reader who obtained and read the full agreement set it against the vendor's public marketing, which continued to tell customers they "own one hundred per cent of the data collected," and described the website's promises as advertising for terms the contract had already removed. The gap between the front of the package and the clause on the inside is not hidden. It is just on two different surfaces, and almost no one reads both.reported
§05 · The grammar, and a fifth move
The series keeps a small grammar of how an agent is kept out of a sentence, the four discharge moves. This case is a clean showcase of all four, which is part of why it anchors a volume.
The definitional dodge is the merge of every data category into one "Customer Data" bucket, so that a single licence can reach everything at once. The agent substitution is the swap of obligor: a binding contractual prohibition enforceable by the customer, "shall not sell," is replaced by a vendor blog assurance, "cannot and does not sell," moving the promise from a courtroom to a press release. The agent deletion is the removal of the protective sentence itself, described as deleting a redundancy, so that the actor doing the removing disappears behind the passive frame of "simplification." The integration stamp is the word "ownership," assigned to the customer to make a licence-grants-everything structure read as customers-own-everything.
But the four established moves all describe how a clause is worded. This case does something they do not fully name, and it earns the volume a fifth entry in the grammar.
▸ Discharge Move 05 · The Retroactive Ratchet
Terms degrade after dependency is established, through a mechanism the obligor controls unilaterally. The instrument itself, a contract that lives on the vendor's own surface and can be amended at will, is the move. Protections present at the point of consent are removed once consent is no longer reversible at low cost.
Signature: a protection exists at signing; the counterparty installs, integrates, and comes to depend; the protection is then removed or inverted and framed as housekeeping; and the exit that would answer the change is narrowed in the same revision. The degradation and the exit-narrowing appear in the same document version. That co-location is the fingerprint: the door is shrunk in the same act that gives you a reason to use it.
Distinct from agent deletion, which removes the actor from a single clause. The retroactive ratchet operates one level up, at the instrument, and along the time axis: it weaponises when a change lands relative to dependency, not just how a clause is written.
Name the move and the whole case resolves to one sentence. The harvest, the vendor's perpetual hold on a city's record of its residents' movements, never depended on keeping the city as a customer. It was drafted to survive the city leaving. That is not a claim about anyone's heart. It is a description of what the terms do.analysis
§06 · What this case is not
The series audits its own instinct here, because a contract case is easy to overstate.
It is not a claim that this is illegal. Vendors are entitled to revise their terms, and customers are bound by agreements they sign; whether any of these edits crosses a legal line is for courts and regulators, and the constitutional-debt point is carried as a live theory, not a verdict.
It is not built on the loudest available material. The vendor's chief executive has used heated language about the cities cancelling, words like "terroristic" and "coordinated attack" appear in the reporting, and they are tempting and entirely beside the point. They belong to a separate case about rhetoric. Including them would trade an unimpeachable spine, the deleted sentence and the narrowed exit, for an argument about tone. The spine is kept clean on purpose.
It is not a claim of verified clause-by-clause fact where the source is paywalled. The trade-press outlet that reported some of the clause detail was not read directly here; its specifics are carried only as quoted by the civil-liberties summary, and never dressed up as independently confirmed.
It is not an accusation of motive. "By design" is used only of the drafting, that a perpetual licence is written to survive termination, and where a sentence risked implying intent it was changed to "by operation of the terms." The lock-in, the trap door, the unconstitutional debt: these are analysts' conclusions, attributed to them. The facts under them, a sentence deleted and called redundant, a licence made perpetual, an exit narrowed in the same revision, roughly fifty cities declining, carry the case without anyone's intent being assumed.
- § Standing on
- verified Flock Safety, "Terms & Conditions Update," company blog, 17 February 2026 (the vendor's own statement that it removed the sentence "Flock shall not sell Customer Data," calling it redundant). Primary admission. flocksafety.com
- reported footnote4a.org, "The Deal has been Altered Further," 18 February 2026 (quoting the amended contract: "irrevocable, perpetual" licence and the right to "support and improve" the vendor's products; the marketing claim that customers "own 100% of the data collected"; the unconstitutional-debt question). footnote4a.org
- reported American Civil Liberties Union, analysis of the Flock terms, 16 April 2026 (formal ownership paired with the vendor's "exclusive right to determine and control the method, timing, format, and medium" of access; termination made harder including on council non-approval or failure to appropriate, with nearly 50 cities declining in a year; arbitration under Georgia law; expanded liability shields; summary citing IPVM). aclu.org
- reported haveibeenflocked.com (customers reportedly receiving degraded, low-resolution copies of footage stripped of metadata such as timestamps). haveibeenflocked.com
- reported Brookings Register, letter to the editor, 22 May 2026 (a reader who obtained the full contract describing the website's "own 100%" promise as advertising for terms already removed from the agreement). Local source. brookingsregister.com
- analysis Caveat carried in the open: IPVM's clause-level reporting is paywalled and was not read directly for this case; its specifics are taken only as quoted in the ACLU summary, and are not treated as independently verified. The exact mapping of which of the four amendments carried which change is not fully on the public record; the case rests on the documented before-and-after, not on the sequence of individual edits.
- analysis The structural reading and Discharge Move 05 (the retroactive ratchet): terms degrade after dependency is established, through an instrument the obligor amends unilaterally; the degradation and the exit-narrowing co-locate in one document version. Mechanism, not motive; extends the four discharge moves to five.