Retrieve candidates
Normalize public names, shields, commands, ranks, and source-native identifiers to find plausible paths.
Public identity graph · release v1
myrights.nyc reconnects fragmented NYC police-accountability records without turning a plausible match into a fact. Every link carries its evidence, its source, and its uncertainty.
01 / Explore
Search a public NYPD profile by name or shield. The demonstration follows the evidence path into a source-defined identity, its historical states, and its accountable links.
This searches the current public release. It does not identify a person from a face or private encounter evidence.
Start with a public name or shield.
The result will show what is linked, how it was linked, and what remains unresolved.02 / Method
The identity layer is useful because it keeps the chain visible. It does not pretend that a name match, an OCR hit, or a current roster row is an authoritative identity key.
Normalize public names, shields, commands, ranks, and source-native identifiers to find plausible paths.
Compare title and shield states with dates and retain the temporal reasoning behind each link.
Candidate, corroborated inference, blocked, and unresolved outcomes stay visible instead of being flattened into “matched.”
03 / Use the data
Use the API for targeted reads and the versioned release files for analysis. Start with officer_id, then join through the published links and check the evidence class before treating a connection as usable.
04 / Limits
The strongest public product is candid about the boundary between a source fact, an evidence-backed inference, and an unknown.
Evidence-backed public-record linkage. Useful, reproducible, and still not the same as a direct government crosswalk.
A plausible path that should not be promoted without additional scope, date, or identifier evidence.
The source is missing an authoritative government key needed to make the cross-system join.