Privacy Policy

• As the operator of this website and the customer account system. Information about you — the person visiting the site, signing up, or administering an account. We decide how that information is used, and this notice governs it.
• As a processor of search inputs on behalf of a customer. When a customer sends a name or date of birth to the API, that query is their data and their responsibility. We process it to answer the request under the Terms of Service, and the customer’s own privacy notice — not this one — governs the individuals behind those queries.

Account information. The name, work email address and organization you supply at signup, the accounts on your team, and the fact and timestamp of your acceptance of the Terms.

Billing information. Billing is handled by our payment processor. Card numbers are entered on the processor’s surface and are never transmitted to or stored on our systems; we hold the processor’s customer identifier, the subscription state, and the invoice history.

API credentials. API keys are stored as hashes. The full key is displayed once, at creation, and cannot be recovered afterwards — by you or by us.

Usage and audit records. For each API call: the key used, the account, the timestamp, the endpoint, the jurisdictions scoped, the response status and the billable outcome. These are what your invoice is computed from and what an audit of your account is reconstructed from, so they are kept whether or not a search matched anything.

Search inputs. The query parameters a customer submits. See Retention for how long these are held and in what form.

Website and advertising information. Standard server request data, and — where the visitor’s browser and any ad blocker allow it — a Google Ads measurement cookie plus the click identifier present in the URL of an ad click. That identifier is stored in the browser so that a conversion completed days later can be attributed to the click that produced it. It carries no name, and we do not use it to build a profile of you.

Support correspondence. What you send us, and our replies.

We do not sell personal information, and we do not share it for cross-context behavioural advertising as those terms are defined under California law. We do not use customer search inputs to market to anyone, and we do not disclose one customer’s queries to another customer.

• Cloud hosting and managed databases, which run the Services.
• Payment processing, for billing and invoicing.
• Transactional and support email delivery.
• Advertising measurement, for the conversion reporting described above.

• Account records are kept for the life of the account and for as long afterwards as we need them for tax, accounting and legal-defence purposes.
• Usage and audit records are retained after an account closes, because they are the evidence behind an invoice and the record an audit or dispute is answered from. They identify the account and the key, not the individuals behind the queries.
• Search inputs are retained only as long as needed to answer the request, support the customer, and protect against abuse. On written request from the account owner we will delete a customer’s retained search inputs, subject to any independent legal obligation to keep them.
• Support correspondence is kept while it remains useful to resolving the matter and to any subsequent dispute.

Do not send us protected health information without an executed BAA, and do not send us more personal data than a permitted search requires.

Make a request by writing to support@offendersearch.app or through the contact page. We reply within one business day and act on verified requests within the period the applicable law allows. We will ask you to verify your identity before acting, because acting on an unverified request is itself a disclosure.

If your request concerns data a customer sent us — a query about you submitted by a company using the API — we will refer you to that customer, who controls it. Where we know who they are, we will tell you.

• The authoritative copy is the jurisdiction’s. A change made there is the change that governs, and it is the one worth pursuing first.
• You can still raise it with us directly. Write to support@offendersearch.app with enough detail to identify the record and what you believe is wrong with it. Corrections are a first-class channel here, not an exception process — the route and how it is handled are described on the methodology page, and the same address is published as a records-correction contact point in this site’s machine-readable organization data.

You can block or delete cookies in your browser, and Google offers its own opt-out for ad personalization. Blocking them does not degrade the API and does not prevent you from using the site; the only thing it changes is our ability to attribute a signup to the ad that produced it.