Accountability
Corrections & change log
The project is designed to preserve provenance and correct the record when better evidence arrives.
Report an error or challenge a source
Use RPG Dungeon LLC's existing public contact page and identify the Flock Blocking record or location you are challenging. Include the source, location, record reference, or screenshot that makes the issue easy to reproduce.
Open public contact page ↗
Useful correction reports explain what appears wrong, what the corrected information should be, and what evidence supports the change.
Correction rules
- New evidence does not silently erase old provenance.
- Installation candidates are not upgraded to active cameras without supporting evidence.
- Crowd-mapped records are not relabeled as agency confirmation.
- Agency addresses geocoded by Flock Blocking remain labeled as derived coordinates.
- Estimated-site reconciliation is changed only when evidence supports the merge or split.
- Material corrections should be recorded below.
Public change log
September 19, 2026 — launch transparency pages
Published the full evidence methodology, correction/change-log policy, and reusable public-records request template. Corrections route through an existing public contact page without exposing private campaign contact data.
Production QA also caught Cloudflare attempting to inject its Web Analytics beacon into the new pages. The site now applies no-transform to every canonical HTML route, preventing that injection without weakening Content Security Policy. Deployment preflight enforces this rule for future pages.
September 19, 2026 — continuation hostile QA
Re-tested production desktop/mobile behavior, accessibility, stale-data handling, source failure behavior, map-provider fallback, privacy leak boundaries, unsafe HTTP methods, and future dataset scaling. No launch-blocking defect was found.
September 18–19, 2026 — installation-site model
Separated individual evidence records from conservative estimated installation sites so raw source points are not presented as unique physical-camera counts.
September 18–19, 2026 — privacy and deployment hardening
Restricted the deployable bundle to sanitized public data, tightened security headers, removed unnecessary public dependencies, and verified that private backend material is not served publicly.
What is not a correction
A request to remove accurate public-record evidence solely because the location is sensitive or unpopular is not, by itself, evidence that the record is wrong. Flock Blocking will distinguish factual correction requests from requests to suppress accurate source material.
This log is intended for material research, methodology, privacy, and publication changes. Routine automated data refreshes are not individually logged.