About Offendersearch
Offendersearch, Inc. operates a single API over the public sex-offender registries of every US state, the District of Columbia and the US territories. Software companies embed it so that screening, marketplace and compliance workflows can ask one question of every jurisdiction at once.
Who publishes this
A buyer embedding this data into their own product is answerable for it internally. So is the person it describes. Both are entitled to know exactly which entity stands behind it.
- Legal entity
- Offendersearch, Inc., trading as Offendersearch. Incorporated in New Jersey.
- What we operate
- A REST API, an MCP server, and this website. We publish public-record sex-offender data from official jurisdiction registries under a metered per-call contract. We do not sell advertising, we do not resell customer query data, and we do not operate a consumer-facing lookup site.
- Who is accountable for the data
- Offendersearch, Inc. is accountable for what the API returns. Responsibility sits with the company rather than with an individual byline: data operations, security and support are staffed roles reached through the single channel below, and a question about a record is answered by the team that owns that data — not routed to whoever happens to have written a page. Our data methodology sets out where records originate, how often they are refreshed, and how match strength is labelled.
How to reach a person
One inbox, one team, one response target: one business day. Every route below reaches the same people — the form simply arrives pre-labelled.
General and support
Integration questions, unexpected results, keys and billing. Contact form or support@offendersearch.app.
Sales and volume pricing
Volume rates, annual commitments and contract terms. Contact form, or see pricing.
Security and compliance
Security reviews, questionnaires, subprocessors and BAAs. Contact form, or read trust & security and HIPAA.
Record corrections and disputes
For anyone who believes a record about them is wrong — see the correction channel below.
Legal notices
Notices under the Terms of Service may be sent to support@offendersearch.app, which reaches the account and legal contacts.
Documentation
Field definitions, error codes and every response guarantee are in the API reference.
If a record about you is wrong
Registry entries are maintained by the jurisdiction that issued them, and they change as that jurisdiction updates them. If you are the subject of a record and believe what is published about you is inaccurate or out of date, there are two steps and they are worth taking in this order.
1. Ask the issuing jurisdiction to correct it
The registry that publishes a record is its authoritative source, and it is the only party that can change the official entry. Each state and territory registry publishes its own process for this, usually through the agency that administers it. A correction made there is the correction that lasts.
2. Tell us, and we will re-verify our copy
Email support@offendersearch.app with the subject “Record correction request”. Include the name as it appears, the jurisdiction, and — if you have it — the link to the entry on the registry’s own site. You do not need an account and there is no charge. We acknowledge within one business day, re-verify the entry against what the issuing registry currently publishes, and bring our copy into line with it.
What we can and cannot change
We can correct or remove what we publish about a record, and we will. We cannot alter the jurisdiction’s official registry entry, and we will not present a record as removed from a registry when the registry still publishes it — that would misrepresent the source. Where an entry has been amended or withdrawn by the jurisdiction, our copy follows it.
For customers reporting a data problem
If you are integrating and something in a response looks wrong, send the recordId, the source.recordUrl and the query that produced it to support. Those three make a record reproducible on our side, which is the difference between a fix and a conversation.
Read how the data is produced
Sources of authority, coverage by jurisdiction, refresh cadence and how match strength is labelled — in one page.