Records, method, and corrections
Everything on this site traces back to one document set: the Flock agreement file for the City of Edgewater, Colorado, and the police department records that govern the cameras. This page lists what the set contains, the checksum of the copy this site was built from, what the set does not show, how the site was built, and how to report an error.
The documents
The site is built from one bundle: a single 38-page PDF, EDG_Flock_agreement_entirety.pdf,
1,643,164 bytes. The bundle has five parts, tagged below. Each citation on this site
gives the tag and the PDF page. The redacted copy is published in this repository (see Published file and checksums below).
| Part | Date as printed | What it is |
|---|---|---|
| [ADD] Addendum to Flock Group Inc. Services Agreement Order Form with the City of Edgewater, Colorado (PDF pp. 1, 3, 5) | Effective as of 12/12/2023; signed by the City 12/12/2023; countersigned by Flock 12/13/2023 | City-level terms. Signed by the Mayor and attested by the City Clerk. In a conflict with the Agreement, the Addendum controls. |
| [T&C] Flock Safety Terms and Conditions (PDF pp. 21–38) | Printed from flocksafety.com 4/28/2025; the page reads “Last Updated: October 4, 2024” | Vendor terms, incorporated into the agreement by Order Form section 11.4. |
| [OF] Exhibit A, Order Form (PDF pp. 11–19) | Customer signature dated December 12, 2023; Flock signature dated December 13, 2023 | Products, term, price, and the signature block. |
| [PORTAL] “Edgewater CO PD, Transparency Portal,” provided by Flock Safety (PDF pp. 7–8) | “Last Updated: Tue Aug 12 2025” | Public-facing policy summary and 30-day usage statistics. |
| [POL] Edgewater Police Department Policy Manual, Policy 422, “Automated License Plate Readers (ALPR)” (PDF pp. 9–10) | Lexipol copyright 2025/07/15; “Published with permission by Edgewater Police Department” | The department’s own rules for using the cameras. |
The Order Form and Addendum are the City’s contract documents. The vendor terms are part of the agreement by reference. The portal is a Flock-provided summary, and Policy 422 is the police department’s own rule set. Each part speaks for itself, and where two parts say different things, this site reports both (see the list of open conflicts below).
What the documents do not show
The document set does not contain:
- Council minutes, budget line items, or any vote approving the contract.
- The installation date, the installation locations, the deployment plan, or a map of the six cameras.
- Records-request responses, audit reports, or the number of searches made by named users.
- News coverage, watchdog or community reactions, or the experiences of other Colorado jurisdictions.
- The name of the current Chief of Police. Policy 422 refers to the office only.
- Any contact information for the City beyond the written-notice address in the Addendum.
The set also does not include news coverage, council minutes, CORA responses, or interviews. Where a page would normally rely on those, this site says so and does not fill the gap from memory. The one exception is the “Reported by other sources” section of the timeline, which lists council sessions reported by the Edgewater Echo and an EFF Atlas of Surveillance listing, each labeled as coming from outside the set. This site has not seen the council minutes or packets themselves.
Conflicts the site flags and does not resolve
- Retention. The portal and the Order Form say 30 days [PORTAL; OF p.13]. Policy 422.4 says data stored on the server “should be securely stored for 1 year after the creation of the data” [POL 422.4]. The documents do not say whether these describe different systems.
- Traffic enforcement. The portal lists traffic enforcement as a prohibited use [PORTAL]. Policy 422.3(g) says an alert “should be considered one element” of reasonable suspicion, and officers will not stop a vehicle based solely on an alert [POL 422.3(g)].
- Anonymized data. The vendor terms let Flock use anonymized data, including to train machine learning algorithms, and for “other Flock offerings” [T&C §4.3]. The Addendum bars use of City Records for any purpose other than services to the City [ADD p.1]. The documents do not say whether anonymized data is a City Record.
- Disclosure to third parties. The portal says data “is never sold to 3rd parties” [PORTAL]. The vendor terms allow disclosure of footage to law enforcement, government officials, and third parties in listed circumstances [T&C §5.3], and allow customer-requested third-party distribution [T&C §4.4]. The portal’s statement does not address disclosure.
- Sharing. The portal lists external organizations with access [PORTAL]. The Order Form includes state and nationwide lookup networks [OF p.17]. Policy 422.5(d) allows release to “other authorized and verified law enforcement officials and agencies at any time” [POL 422.5(d)].
- Audits. Policy 422.5(e) says ALPR system audits “should be conducted on a regular basis” [POL 422.5(e)]. The policy states no schedule, and the set contains no audit reports.
- Price (apparent discrepancy, not yet confirmed). The Order Form’s discount line does not reconcile on its face and has not been confirmed with the City or Flock. The $75,000 contract total and $15,000 annual figure are quoted as printed [OF pp.13–15].
- Installation date. The date the 60-month term starts, which is first installation, is not in the documents [T&C §7.1; OF p.17].
- Community cameras. The Order Form includes access to privately owned Flock cameras shared with the City [OF p.17]. The documents do not say whether any are in use.
Published file and checksums
The agreement bundle is published here as docs/edgewater-flock-agreement-bundle-redacted.pdf. It is the bundle as received, with two changes made before publication. Both are personal contact details, and both are blacked out in the page image, not only hidden: on page 11, the name, email address and phone number of a vendor contact; on page 13, the email address of a city accounts-payable contact. All document metadata (author, software, and creation fields) was removed. Nothing else was altered. The bundle is a scan with no text layer, so the page text cannot be searched or copied.
| File | SHA-256 |
|---|---|
| Published: edgewater-flock-agreement-bundle-redacted.pdf (2,380,443 bytes; 38 pages; redacted as described above) | fd0ce3c6d55468aac57fff1565e91daa2e9226baa06cc214597a33018e980d60 |
| Original as received: EDG_Flock_agreement_entirety.pdf (1,643,164 bytes; 38 pages; not hosted here) | 52e6ab0b1c3c5a5388fcbe5538063c146a63d58c0d925b85c80fa38be8067d97 |
How this site was built
Four rules govern everything here.
- Named sources only. Every fact on this site was taken from the text of the document set above and is cited to its tag and PDF page. Nothing rests on memory, news coverage, or an unnamed source.
- Numbers as printed. Figures are quoted as the documents print them. This site does not recompute a total or explain a figure the documents do not explain.
- Conflicts stay open. Where the documents disagree or leave a gap, the site says so and does not choose between them. The conflicts are listed above.
- Silence is reported as silence. That a record is not in the set is a fact about the set. It is not evidence that no such record exists.
This site is commentary and compilation. It describes what the documents say and what they do not say. It does not allege unlawful conduct by any person.
Corrections policy
This draft does not yet list a public corrections channel; one will be published with the site before it goes live. If a record exists that answers a question this site marks as open, the same issue tracker is the place to point to it.
If anything on this site is wrong, it will be corrected, and the correction will be logged below with its date. Corrections are made by changing the page and adding an entry to the log. Nothing is silently rewritten.
No corrections yet.