Every Police Record Names Someone Who Needs Protection
Law enforcement records are unusual among government data: nearly every document exists because something happened to a specific, named person. An incident report identifies a victim, the witnesses who spoke to officers, the reporting party who asked not to be involved, and often a juvenile. A body-worn camera captures faces, voices, license plates, and the inside of someone's home. A CAD narrative logs the caller's address and callback number. Releasing, sharing, or analyzing any of it means deciding — line by line — whose identity travels with the record.
The pressure on those decisions has never been higher. Body-camera statutes in many states mandate public release of footage on a clock measured in days. Public-records laws reach incident reports, and journalists and civil-rights organizations request them in bulk. Prosecutors need discovery packets fast; regional fusion centers and neighboring agencies need data shared; researchers and city dashboards want crime data opened. Meanwhile victims of domestic violence, confidential informants, minors, and uncharged third parties have statutory and constitutional protections — including Marsy's Law provisions in many states — that make a leaked name a safety issue, not a paperwork issue.
The PII Detection API gives records units an automated first pass. Submit report narratives, transcript text, or CAD notes and receive every detected identifier back with its entity type, exact character offsets, and confidence score, plus an optionally masked version. Records technicians stop hand-searching thousands of pages and start reviewing pre-flagged spans — with the model catching identifiers in exactly the messy, jargon-heavy prose that police narratives are made of.