Standards
How it's verified.
Every record is compiled from public sources, independently cross-verified, and human-reviewed before publication — with a timestamp on every verification.
The pipeline
Compiled from public sources
Official rosters and public records, collected continuously across every jurisdiction.
Independently cross-verified
Every field is checked against a second, independent source before it can publish.
Human-reviewed, then published
A reviewer approves each change, and the approval is timestamped on the record.
Four guarantees, enforced in code
Identity-verified photos
Every published portrait passes an identity check and is served from our own storage. Image links never rot.
A portrait publishes only when its identity check has passed and the file is on our own storage — both conditions, or the field is omitted.
Confirmed social accounts
Handles publish only after independent confirmation.
Each handle is matched against a second, independent record of the same account before it appears; anything unconfirmed is omitted from the response.
Privacy-safe by design
Personal data is limited to what’s public and confirmed. Family data covers marital status and counts — never a relative’s name.
The rule is enforced in the data model itself: the record never stores fields outside the public, confirmed set, so the API cannot return them.
Clean responses
Every field present is verified data. Absent values are omitted — never sent as null.
Serialization drops empty and unverified fields before a response leaves the API, so the shape of a record is itself a statement of what has been verified.
Cadence
Federal records refresh weekly. Every jurisdiction is independently re-verified monthly, the judiciary on its own monthly cycle. Nothing publishes without passing a human approval queue.
Privacy stance
Privacy-safe by design: personal data is limited to what's public and confirmed. Family data covers marital status and counts — never a relative's name.