We can get things wrong. When better evidence shows up, we want the public record to get better with it.
See something wrong?
Use RPG Dungeon LLC's public contact page and tell us which Flock Blocking location or record you're looking at. If you can, include the source, record reference, or a screenshot so we can reproduce the problem quickly.
The most useful reports tell us what looks wrong, what you think the correct information is, and what evidence supports the change.
How we handle corrections
New evidence doesn't quietly erase the old source history.
An installation lead doesn't become an “active camera” unless the evidence supports that jump.
A crowd-mapped point stays crowd mapped unless an agency record actually confirms it.
If we turn an agency street address into map coordinates, we say those coordinates were derived.
We only merge or split estimated sites when the evidence gives us a reason to.
If a factual claim we published was wrong or materially misleading, we correct it and record that correction below.
Correction log
— records-request status corrections
Warden: changed “Acknowledged” to “Records received.” The October 1 closing letter included in the released ZIP says the request was fulfilled and closed.
Newcastle: changed “Action needed” to “Partial records.” The October 2 response supplied records and a December 4 installment estimate; its invitation to ask questions or voluntarily narrow scope was incorrectly treated as a required clarification.
Yakima County Sheriff's Office: changed “Acknowledged” to “Partial records.” The October 5 response says an installment is available in the Records Center and estimates the next installment or update by February 1, 2027.
These corrections concern the request tracker. A records release or request closure does not establish current camera operation.
What doesn't count as a correction
Wanting an accurate public record removed because a location is sensitive or unpopular doesn't make the record factually wrong. Site design, navigation, features, methodology improvements, deployment work, and routine data refreshes also do not belong in this log unless they correct a factual claim we published.
This page records corrections to factual claims we previously published. It is not a website changelog.