Frequently asked questions

What is this site?

A public file on the Town of Morrison's Flock Safety license-plate-reader contract: a 22-page order form and agreement signed February 8, 2023 by the town manager, for a customer named “CO - Morrison PD.” Four cameras, $21,400 in all, renewing in 12-month blocks. Twenty-three months after the signature the town dissolved its police department, and Jefferson County Sheriff's deputies have patrolled Morrison since January 1, 2025. The document is published here in full, and the rest of the site asks what happens to a surveillance contract when the department it was signed for no longer exists. Start with The Program or the Timeline.

Who runs it, and who pays for it?

One person, who is not a journalist, a lawyer or a public official, and whom nobody asked to do this or paid for it. There is no organization behind the site, no campaign, no funder and no advertising. It is not affiliated with the Town of Morrison, the former Morrison Police Department, Flock Safety or anyone else named on it, and nothing here is legal advice.

Why is there no name on it?

Because the site is critical of a police surveillance program, and because it does not need one. Everything here is built so that you never have to take my word for anything: each factual claim points at a document or an article you can open and read for yourself, and the primary documents are published unaltered, with checksums, so you can confirm they are what I say they are. A name would add nothing to that, and the site publishes no personal information about anyone, including whoever maintains it. If I turn out to be wrong about something, the corrections policy applies no matter who I am.

Why build it at all?

Because a surveillance network went up over public roads, on a town manager's signature, and the record of how that happened was scattered across contracts, meeting minutes and news stories that nobody had put in one place. This site is that place. It is a spare-time project with no staff and no budget, which is the reason for the next section.

Did you use AI to make this site?

Yes, and I would rather you hear it from me than wonder. I used large language models, the technology behind AI chat assistants, throughout this site as a time saver. They drafted and edited most of the prose, working from my notes and from the documents. They wrote the HTML, the stylesheet and the scripts behind the site, including the one that draws the camera map from OpenStreetMap data and the one that checks every change for anything that could identify me. They helped me get through long documents quickly by pulling out the passages on price, term, renewal and data sharing so that I could go to the page and read them in context.

Here is what the models did not do. They did not decide what this site would be about, or what it would say. They did not find the contract. They did not choose what to publish or what to make of it. Those decisions were mine, and so is the responsibility for every word here.

Why admit that?

Two reasons. The first is that a site asking you to trust it owes you an account of how it was made. The second is that these tools make mistakes. They can invent a detail, misread a date, or state something confidently that is not so. That is part of why the rules on the Records page are what they are: named sources only, silence reported as silence, arithmetic labeled as arithmetic, and absence never treated as proof. The footnotes are there so you can check the model's work, and mine. The rules did not come from the tools. The tools are one of the reasons I needed the rules.

So did a machine write this answer?

The first draft, yes. I asked for help with this page too, then read it and changed what did not sound like me or was not true. That is how the whole site was made: drafted quickly with a tool, then read against the record by one person. It is not the same as having an editor, and I will not pretend otherwise. It is why corrections are logged in the open rather than made quietly.

Where did the documents come from?

The signed order form and agreement is published on the Records page with its SHA-256 checksum. It is, so far, the whole primary record: one 22-page document, signed for the town but with Flock's signature block left as unfilled template placeholders. If a fully countersigned copy exists, it will be published here. What the document refers to but does not include is listed on the same page.

How do I know any of this is accurate?

You don't have to take it on faith, which is the point of the design. Every factual claim carries a numbered footnote to a named, linked source. Where the record is silent, the site says so rather than guessing, and the blanks are marked in amber throughout. The camera counts come from a single OpenStreetMap query that is printed on the Records page so you can run it yourself, and the limits of that number are printed beside it. If a claim here is not supported by the source it cites, that is an error, and the corrections policy says what happens next.

I found a mistake, or I have a document you don't.

Then I want it. Mistakes get fixed on the page and logged on the Records page with the date, never silently. A document is worth more than an argument: a contract, an invoice, a staff report, a meeting packet or a records response will be published and credited, including one that contradicts this site.

The site publishes no contact address, for the same reason it carries no name. The surest route is to put the document into the public record, where this site will find it: give it to a local reporter, bring it to a public meeting, or post it somewhere it can be linked.

What is a Flock camera, in a paragraph?

A fixed camera, usually on its own pole, that photographs every vehicle that passes, reads the plate and records what Flock calls a vehicle fingerprint: make, type, color, and details like roof racks, bumper stickers and damage. The reads are stored and searchable, by the agency that bought the cameras and, depending on its settings, by other agencies across Flock's statewide and nationwide networks. They are not red-light or speed cameras and they do not issue tickets. The longer version, with the vendor's own language, is on The Program.

I have nothing to hide. Why should I care?

Because the record of what has gone wrong with these systems is not hypothetical, and most of it happened to people who had nothing to hide either. Denver's cameras were searched more than 1,400 times for immigration-related reasons through the national network, without Denver's knowledge. Loveland's data reached Border Patrol. A Columbine Valley officer tracked the wrong woman to her door with Flock data and accused her of theft. Deputies in Texas used it to follow a woman seeking an abortion. In most of those cases the agency whose cameras were searched was not the agency doing the searching, and did not find out until afterward. That is a property of the network, not of any one department's good faith, which is why the sharing settings matter more than anyone's intentions. The cases are laid out, with sources, on Context.

Did anyone vote on this?

The record published here shows one signature, the town manager's, on a form naming “CO - Morrison PD” as the customer. Whether the Board of Trustees ever considered the contract, before signing or after the police department was dissolved, is one of the open questions on The Program. The board can still end it: the agreement allows termination for convenience at any time, at $500 per camera.

Is this site against the police?

It is against a surveillance program being bought, expanded and shared with very little public explanation. That is a complaint about process and disclosure, not about the people in uniform. The site does not allege unlawful conduct by anyone, and no record reviewed for it documents misuse of a plate-reader system by Morrison personnel. If the town said in public whether the cameras still operate, who holds the login and whether it is still paying, most of what this site documents would be resolved, and I would call that a good outcome.

What can I actually do about it?

Start with Take Action: five things a resident can do, when and where the Board of Trustees meets, what to ask for under CORA, and how to make three minutes at a public meeting count. Morrison's contract can be ended on any day, for convenience, at $500 per camera; it only needs someone to decide to. The county's own cameras, now that sheriff's deputies patrol the town, are a separate question.

How do I find the cameras near me?

The crowdsourced map at deflock.me, built on OpenStreetMap data contributed by volunteers, is the best public inventory there is, and it is linked from every page of this site. The map on this site's home page is drawn from the same data, and every dot on it links to that camera's location on the live map. It undercounts, because a camera nobody has mapped does not appear, and it can overcount, because a removed camera may linger in the data. If you see a camera that is not on it, you can add it; the map explains how.

Can I see what the cameras recorded of my own car?

Nobody knows yet, which is itself part of the story. In December 2025 a Colorado man asked Boulder police for the Flock images of the vehicle he drives, and the department refused to run the search, saying its systems may be accessed only for law-enforcement purposes as part of documented criminal investigations. He and a second plaintiff have since sued, and no court has ruled. Morrison's agreement reserves the system for law-enforcement use in the same way, so the same questions reach here. The case is on Context.

Can I file a records request myself?

Yes. Anyone can file under the Colorado Open Records Act; you do not need to be a resident or give a reason. What to ask Morrison for is spelled out on Take Action: whether the cameras still operate, who has access, what has been paid, and the sharing settings and audit logs. Agencies may charge for staff time after the first hour, so ask for specific records that already exist rather than for “everything about Flock.” Nothing on this site is legal advice; the statute and the agency's records custodian govern.

Does this site track me?

No. There are no analytics, no cookies, no advertising, no social-media buttons and no third-party scripts or fonts. Every page ships with a strict content security policy that forbids loading anything from anywhere but this site. The company that hosts the files sees the ordinary request logs that every website's host sees; the site itself adds nothing to them. Links to outside sources open in a new tab and are sent without a referrer.

Can I quote or reuse what is here?

Yes. The public records are public: download them, share them, print them. The site's own writing may be quoted or reproduced with a link back to the page it came from. Map data is from OpenStreetMap contributors under the Open Database License and should carry that credit. Please do not present anything here as the Town of Morrison's own material, because it is not.

Are there other sites like this one?

Yes. The same person, with the same method and the same rules, maintains sister sites on neighboring programs: deflockarvada.com (Arvada's city contract), deflockgolden.com (Golden's city contract), deflocklakewood.com (Lakewood's city contract) and flockmarinelli.com (the Jefferson County Sheriff's Office program). Each stands on its own record and keeps its own corrections log.

The police department is gone. Who runs the cameras now?

That is the question. The order form names “CO - Morrison PD” as the customer, and that department was dissolved on January 1, 2025. Whether the cameras still operate, who holds the login, whether the sheriff's office took over the data, and whether the town is still paying are open questions the record does not answer. They are set out on The Program.