Time remaining until the contract's estimated non-renewal notice date
Calculating.
until an estimated November 12, 2028, the last day the City can give the notice that stops the Flock contract from renewing itself. This is an estimate: 60 months from the December 12, 2023 signing, less 30 days. The term really starts at first installation, which the documents do not date, so the real date may be later.[T&C §7.1][OF p.13] How to take action →
The estimated notice window has closed. Unless the City gave written notice, the contract renews for another 24 months around December 12, 2028. How to take action →
Six Flock cameras. $15,000 a year. $75,000 total, as printed. Documented here.
The Edgewater Police Department uses six Flock Falcon license-plate-reader cameras under an Order Form the City signed on December 12, 2023. The contract prices a Flock Safety Platform at $15,000 a year over an initial 60-month term, and lists a contract total of $75,000.[OF p.13][ADD p.5] This site is built from one 38-page bundle: the City's Addendum, the Flock Order Form, Flock's vendor terms, the Police Department's Policy 422, and a transparency portal provided by Flock. It summarizes what those documents say.
According to the portal, the cameras detect license plates and vehicles, and not faces or people.[PORTAL] The documents disagree about how long data is kept: the Order Form and the portal say 30 days, while the Police Department's policy says server data should be kept one year.[OF p.13][POL 422.4] Where the documents are silent, this site says so rather than filling the gap.
A note on scope. This site covers only the City of Edgewater, Colorado, and only the Police Department's license-plate-reader cameras and the data they feed. A camera on a pole does not show whose it is, and this site does not attribute any camera to anyone it cannot be tied to in the documents. Portal figures are as of its update on August 12, 2025. Method and corrections: Records.
At a glance
- Who: The customer is “CO - City of Edgewater.” The Mayor, Steve Conklin, signed for the City on December 12, 2023, and the City Clerk, Lenore Pedroza, attested the same day. Flock countersigned on December 13, 2023. The Addendum says the Police Department “cannot contract on behalf of the City.” Policy 422 gives the Chief of Police, or a designee, responsibility for installation, maintenance, retention and access; it refers to the office only. The document set does not include council minutes or any vote approving the contract.[ADD p.1][ADD p.5][POL 422.2]
- What was bought: One Flock Safety Platform line at $15,000.00, covering FlockOS and six Falcon LPR cameras, both listed as “Included.” The Order Form also shows a $15,000 discount on that line. This is an apparent discrepancy that has not been confirmed with the City or Flock: the printed figures do not reconcile on their face, the documents do not explain the discount, and this site assumes no explanation.[OF p.13-15]
- Money and term: A 60-month initial term, then 24-month renewal terms. Billing is annual, with the first year invoiced at signing and payable Net 30. The contract total is $75,000.00 as printed.[OF p.13]
- When it starts: Under the vendor terms, the term begins “upon first installation of Flock Hardware,” unless the Order Form says otherwise. The installation date is not in these documents, so they cannot date the end of the first term.[T&C §7.1]
- What it can reach: FlockOS Essentials, as the Order Form lists it, includes access to privately owned Flock cameras shared with the City, lookup on the statewide and nationwide Flock networks, and “Direct Share” access to devices other agencies have shared. The portal lists about 90 external agencies with access, among them Denver CO PD, Lakewood CO PD, Colorado State Patrol, and the Colorado Bureau of Investigation. The portal's hotlists are NCIC, NCMEC Amber Alert, and the Colorado Crime Information Center.[OF p.17][PORTAL]
- The rules: Policy 422 says “reasonable suspicion or probable cause is not necessary before using an ALPR.” It lets data go to other verified agencies “at any time for legitimate law enforcement purposes,” and says audits “should be conducted on a regular basis.” The portal says hotlist hits “are required to be human verified prior to action.”[POL 422.3(b)][POL 422.5(d)-(e)][PORTAL]
- Vendor data terms: The City owns Customer Data, and “Flock does not own and shall not sell Customer Data.” The vendor terms also let Flock use anonymized data, “including the training of machine learning algorithms.” The Addendum bars Flock from using City Records for anything other than services to the City. The documents do not say whether anonymized data counts as a City Record.[T&C §4.1][T&C §4.3][ADD p.1]
Bracketed citations link to the source list at the bottom of this page.
Key figures
The six cameras are the contracted quantity and the portal's count; the documents do not verify how many are installed. The portal figures are the portal's own statistics for the 30 days before its August 12, 2025 update, not an audit. The $75,000 total is quoted as printed, and the printed discount line does not reconcile. The 0 reflects only the documents in this set: council minutes are not in it, so the count is a gap in the record, not a finding that no vote took place.
What the map can and cannot show
Every reported automated license-plate reader inside Edgewater’s city boundary, drawn from the same OpenStreetMap data and the same Overpass query the sister site uses. On October 13, 2026 the query returned no plate readers: no mapped surveillance node inside the boundary is tagged as an ALPR, and a second query for any camera tagged with the Flock manufacturer also returned none. The Order Form says six Falcon cameras are part of the contract, but the documents do not say where they are. An empty map therefore shows only that no volunteer has reported a reader, not that none exist.
man_made=surveillance and
surveillance:type=ALPR inside that boundary. The query returned zero results.
Boundary and roads © OpenStreetMap contributors (ODbL). Crowdsourced and
incomplete: an empty map is not evidence that the city has no cameras.
The bundle includes no installation locations, no deployment plan, and no map of the six cameras, so this site does not map them. The Order Form lists “Installation on existing infrastructure” as a one-time service line with no dollar amount.[OF p.17] The vendor terms say Flock owns the hardware, that the City may not “remove, reposition, re-install, tamper with, alter, adjust” it, and that Flock “shall have final discretion to veto a specific location.”[T&C §10.1-10.3]
Open questions the documents raise
These are conflicts or gaps on the face of the documents. The site flags them and does not resolve them.
- Retention The Order Form and the portal say 30 days. Policy 422.4 says data stored on the server “should be securely stored for 1 year.” The documents do not say whether these describe different systems, such as vendor cloud and department server. Open
- Traffic enforcement The portal lists “traffic enforcement” as a prohibited use. Policy 422.3(g) says officers “will not conduct a traffic stop based solely on an alert,” and that an alert “should be considered one element” of reasonable suspicion. Open
- Disclosure The portal says data is “never sold to 3rd parties.” The vendor terms allow disclosure to law enforcement and third parties when legally required or in good faith, and allow customer-requested distribution to third parties. The portal's statement does not address disclosure. Open
- Sharing The portal lists about 90 external agencies with access. The Order Form includes statewide and nationwide lookup networks. The documents do not say whether Edgewater's own cameras are searchable by other agencies. Open
- Audits Policy 422.5(e) calls for audits “on a regular basis.” The policy gives no schedule and does not say who receives the audits. No audit reports are in the document set. Open
- Community cameras The Order Form includes access to privately owned Flock cameras shared with the City. Whether any are in use is not stated. Open
What the questions mean for a resident, and what to ask for: Take Action.
The record, one page at a time
Each page stands on its own, and every claim on it is tied to a source. If you read one thing, read the first.
- The Program The contract, clause by clause: the terms, the fees, the renewal, and how the City can end it. Read first
- The Policies Policy 422, checked against the portal and the contract it is supposed to govern.Policy 422
- The Records The five parts of the bundle, what the set does not include, the method, and the corrections log.Reference
- FAQ Common questions about the documents, what they mean, and what this site does not know.Questions
- Take Action What the documents support asking the City and the Police Department for. Five asks
Sources for this page
- [ADD] Addendum to Flock Group Inc. Services Agreement Order Form with the City of Edgewater, Colorado. Effective as of 12/12/2023; signed for the City by the Mayor and attested by the City Clerk on 12/12/2023; countersigned for Flock on 12/13/2023.
- [T&C] Flock Safety Terms and Conditions, printed from flocksafety.com on 4/28/2025. The page says “Last Updated: October 4, 2024.” Incorporated into the agreement by Order Form section 11.4.
- [OF] Exhibit A, Order Form, dated December 12, 2023: products, term, price, and the signature block.
- [PORTAL] “Edgewater CO PD, Transparency Portal,” provided by Flock Safety. “Last Updated: Tue Aug 12 2025.” The 30-day figures are as of that update.
- [POL] Edgewater Police Department Policy Manual, Policy 422, “Automated License Plate Readers (ALPR).” Lexipol copyright 2025/07/15, “Published with permission by Edgewater Police Department.”
Page references are to the bundle's pages as tagged. Nothing in this set comes from news coverage, council minutes, records-request responses, or interviews. Corrections are welcome: corrections policy.