A real forty-minute Washington commute, instant-replayed over a camera-density heat map. Then the part nobody photographs: retention math, the data debt many Americans have but very few could account for until now.
A real Washington commute laid over a hex-grid camera-density heat map. Press play. Each hex you cross lights up; a callout shows how many cameras are in that block; a running tally counts every kind of read the architecture takes from you, in real time. Cameras. Location. Movement. Speed. Patterns.
Every camera class has two lifespans. Solid mint is the official policy retention. Vermilion stripes are the residual tail: the litigation hold, the criminal-investigation freeze, the training carve-out, the vendor backup, the contractor archive. Toggle between policy and practice. Hover any class to read the exceptions.
In February 2026, the 84-year-old mother of NBC's Savannah Guthrie was reported missing from her Tucson home. Investigators canvassed neighborhood doorbell networks. That part is now routine. The unusual part came from her own house.
That is the single most important sentence in this dispatch. It is the difference between the retention policy on a vendor's website and the data that actually exists somewhere on the vendor's servers. Most readers think the first sentence describes the second. It does not.
The owner had not opted in. The owner had not paid. The owner believed the device had a documented behavior. The behavior was different. When the request came from law enforcement, the residual data was there to be returned.
The Capitol breach is the proof of concept for everything in the instant replay. The footage was never one composite file. The composite was built later, from device pings, cell-tower handshakes, geofence returns, facial-recognition matches, and crowd-sourced identifications. The funnel below is the shape that reconstruction takes.
The FBI's January 2021 geofence warrant required Google to identify every Android device inside a precise Capitol-grounds polygon during the breach window. The first return was about 5,723 devices. Those identifiers were narrowed against subscriber data, cell-tower handshakes, social-media posts, facial-recognition matches against driver's-license photos, employer records, and a large volume of voluntarily submitted public tips.
Within about a year, roughly 1,535 named individuals had been tied to specific conduct. As of multiple subsequent reporting points, more than 1,300 federal charges had been filed off that foundation.
Nothing in that pipeline required a single dedicated surveillance system. The pieces were collected by different agencies, vendors, platforms, and private participants, each for its own purpose, on its own retention clock. When something happened, the architecture rendered the day replayable. That is the precedent.
In theory, yes. In practice, the discovery path for surveillance footage is the longest, slowest, and most denied category of public-records request. The pipeline below is the one most requests actually travel.
Specific block, specific date and time, specific camera, specific incident or no incident. Statutory clock starts at 20 working days.
The agency acknowledges within statute. Then a fee estimate appears, then a search-time waiver appeal, then a 30 to 120-day actual response.
"Records compiled for law enforcement purposes" lets the agency withhold or heavily redact under 7(A) through 7(F). Most surveillance-footage requests land here.
Within 90 days, you challenge the exemption. Appeal panel review takes another 20 to 60 working days. Most appeals affirm the original determination.
Federal district court is the actual oversight. Lawsuits are expensive, slow, and the agency can still prevail. But it is also the path where most successful releases happen.
The footage your day produced is, in principle, a public record subject to disclosure. The path to actually getting it requires statutory standing, time to wait, money to pay, a willingness to litigate, and a reason the requesting party can articulate.
Most members of the public have none of those at the moment they would want their day back. The architecture that captured them was built without their participation. The architecture that would release it back to them requires substantially more.
Two consequences follow. First, the people most likely to retrieve footage about you are not you. Second, footage that "expires" under retention policy can still be summoned, after the fact, through litigation hold or law-enforcement preservation request, well past the date your privacy was supposed to begin again.
If retention worked the way the policies describe it, the curve would fall sharply and quickly. In practice, the curve has a long, fat tail. Every exception is a hold. Every hold extends the lifespan. Every extended lifespan accrues to the city's data debt.
The exceptions named on every retention policy are not edge cases. They are the architecture's pressure-release valves, and they all extend lifespan.
Each one is reasonable in isolation. Each one is necessary in isolation. In combination they describe the difference between a 90-day retention policy and a 5-year recoverable history.
Six defenses, each true in part. The point is not to refute them. The point is to show that a defense calibrated to one system at a time misses the architecture of a system of systems.
The District is one of the most protected cities on earth. The Capitol, the White House, the Pentagon, hundreds of federal facilities, dozens of foreign embassies. Cameras enable response, identification, crash reconstruction, missing-person searches, counterterrorism, transit safety, and event protection.
Courts have largely held that observation in public space is not a Fourth Amendment violation. The architecture operates within existing constitutional doctrine.
D.C. residents opted into the Capital Shield program through a published rebate. Cloud and vendor backups exist for legitimate continuity reasons. A camera that loses footage during an outage is also a camera that lost a missing-child case.
Most systems retain footage for finite windows: MPD 90 days, Flock 30 days, private rebate 48 hours. Footage held past those windows is usually held because it became evidence in an active matter. Premature deletion would destroy the public record.
WMATA's ~30,000 cameras have been cited in arrests, fare-evasion investigations, missing-person searches, and post-incident reviews. Body-worn cameras on transit police add accountability.
Body-camera programs, internal-affairs reviews, audit logs, and public-records requests provide accountability. FOIA Exemption 7 exists because public release of active-investigation material can compromise cases, endanger witnesses, and undermine prosecution.
Type a home address and a work address. Press the button. We project both into the same DC-area map you just watched, run an instant replay of a route between them across the same hex density grid, and report back how many cameras the route would cross. Nothing leaves your browser.