Records, method, and corrections

That is the whole primary record so far: one document. Its key terms, 11 Falcon cameras, FlockOS Essentials, $27,500 a year, 60-month initial term, 24-month renewal terms, $137,500 contract total, 30-day retention, “Renewal is subject to annual budget appropriation,” are read clause by clause on The Program. The form also incorporates Flock’s standard online Terms of Service by reference; those terms are the vendor’s and can change, and no copy of the version in force at signing was part of the signed pages.

• Any Flock agreement predating July 2023. Readers were reported live in Golden from November 2021; something governed them.
• The department’s ALPR policy, described by the chief in August 2026 as “a policy with parameters, guidance, rules and an audit process,” and any audit it has produced.
• The network sharing settings: which agencies can search Golden’s cameras, and whether statewide or national lookup of Golden’s data is enabled. The city’s Ask Golden page says sharing is limited to Colorado law enforcement; the record showing the setting would verify it.
• The transparency portal the city said it was “launching … in the near future” on its Ask Golden page, and the “auditable search logs” the same answer describes.
• The deployment plan or camera location list for the 11 contracted cameras.
• The term-commencement record: the date of “first installation and validation” that starts the 60-month clock.
• Invoices, purchase orders and the annual budget line that appropriates the $27,500 each year.
• Search audit logs from the Flock “Insights/Analytics” tooling the order form describes.

To verify that the document you download is the document this site describes, compare its SHA-256 checksum. The file name below links to the copy this site serves:

deflockgolden.com is a static site: no analytics, no cookies, no trackers, no outside scripts. It follows the model of its sister sites, deflocklakewood.com and deflockarvada.com: publish the primary documents in full, footnote every factual claim to a named public source, and mark every gap in the record as a gap instead of filling it with inference.

Three kinds of statements appear on these pages, and each is labeled where it occurs. Document facts quote or restate the signed order form. Reported facts cite named news organizations or the city’s own published pages, and reflect what those sources said on their own dates. This site’s arithmetic, principally the June/July 2028 renewal dates, is computed from the contract’s terms and is labeled as arithmetic wherever it appears, because the contract itself names no calendar dates and ties its start to an installation date the record does not contain.

The camera count: exact query

The map and camera counts come from OpenStreetMap, the crowdsourced dataset behind the DeFlock project, retrieved September 29, 2026 via the Overpass API. The query selected nodes tagged man_made=surveillance inside the City of Golden administrative boundary (OSM relation 112204); those with surveillance:type=ALPR were counted, colored by their manufacturer tag, and linked to their coordinates on DeFlock’s live map. The raw query result is published at data/overpass-alpr-2026-09-29.json. Of the 19 ALPR-tagged nodes, 18 carry manufacturer=Flock Safety; two of those 18 carry operator=The Home Depot, and the rest carry no operator tag. One more surveillance node inside the boundary is not tagged as an ALPR and was excluded. Map data © OpenStreetMap contributors, available under the Open Database License; camera reports are volunteer contributions, crowdsourced and incomplete, and establish neither completeness nor ownership.

If anything on this site is wrong, it will be corrected, promptly and visibly. A correction that changes a factual claim will be noted on the page it changes, with the date and what changed. If you hold a record this site lacks, an earlier agreement, the policy, an audit, a council item, a location list, it will be published here with the same treatment as everything else: in full, with a checksum.

This site deliberately publishes no contact information for any individual beyond what official public pages publish for official purposes. To submit a correction or a record, use the repository or channel listed on the site’s hosting page, or any public channel that reaches the site’s maintainers.