Built for compliance-sensitive teams
Security, privacy, and acceptable use are core to the product — not an afterthought. Here is how Offendersearch handles them.
Encryption everywhere
TLS in transit, encryption at rest, and hashed API keys shown once at creation.
Key lifecycle control
An API key is a pure credential — issue as many as you need, scope them by team or environment, and rotate or revoke any one instantly without touching the others. Regular and Live are chosen per request, not per key.
Enterprise security controls
Access logging, change management, and monitoring built for enterprise security reviews.
HIPAA-ready + BAA
A BAA path for enterprise customers whose screening touches protected health workflows.
Acceptable use
Use is subject to our acceptable-use terms and applicable law, accepted at onboarding.
Provenance & audit
Every record carries source provenance with a lastCheckedAt timestamp for a defensible audit trail.
Legal & acceptable use
Our sex-offender data is derived from publicly available records. Use is subject to our acceptable-use terms and applicable law, accepted at onboarding. See our coverage page.
Offendersearch is not a consumer reporting agency and results are not a consumer report; do not use them for FCRA-covered decisions without appropriate process.
Trust FAQ
Is Offendersearch HIPAA-compliant?
We follow a HIPAA-ready path and offer Business Associate Agreements (BAAs) to enterprise customers whose workflows require one, such as healthcare and home-care screening.
How is data encrypted?
All traffic is encrypted in transit with TLS, and data at rest is encrypted. API keys are hashed at rest and shown in full only once at creation.
Do you restrict how the data can be used?
Use is subject to our acceptable-use terms and applicable law, accepted at onboarding.