Privacy Policy

1. Scope

This policy covers HuntPeople's website and product. It describes what we collect about you as a user, what we collect about the people you search, and what we do with each.

2. Information we collect about you

Your name and email address, a hashed version of your password, and your sign-in sessions. Which teams you belong to and your role in each. If you pay us: a billing profile (billing email, company name, country, address, tax ID) and the invoice and subscription records that go with it. We never see or store your card number, Stripe does.

Signing up asks for your date of birth, because you must be 18 or older to use HuntPeople. We check it and then throw it away. What we keep on record is the date you agreed to the Terms and the date you answered the age question, not the date you were born and not how old you are.

If you create an API key, we store a hash of it and its first twelve characters so you can tell your keys apart. The full key is shown once, at creation, and we cannot recover it afterward. We also store your team's prepaid credit balance and the ledger of what each search spent.

3. Information we collect about the people you search

The identifying clue you give us, and whatever the search finds. Each finding is stored as a fact: the field, the value, how strongly it ties to the person, whether we saw it written down or worked it out, when it was observed, and whether it describes the person or an organisation connected to them.

HuntPeople keeps one record per real person, shared across every customer, rather than a separate copy per search. A person you look up may already have a record because someone else looked them up first, and your findings can appear in another customer's view of that same person. Your edits, notes, and deletions are scoped to your team and never change what another team sees.

4. The audit log

We record, tied to the account and team that did it: a search, a batch upload, a download, an edit, a deletion, and a revert of an edit. Opening a record to read it is not currently logged, only actions that create, change, or take data out. If logging what is opened and read is ever added, this page will say so before that logging starts, not after.

Your team can see its own log. HuntPeople staff can see across teams, because a tool like this only stays accountable if someone can answer who ran a given search. We do not delete audit entries on request. Removing the evidence of an action would defeat the reason we keep it.

5. How we use this information

To run and deliver searches, operate your account, process payment, secure the service, prevent fraud and abuse, and improve the product. There is no advertising, no ad tech, and no third-party analytics anywhere in HuntPeople. Nothing here tracks you across other websites or builds a profile of you. We do count things about our own product, such as how often a search finds what it was asked for, and that counting is done on records we already hold rather than by watching you.

The AI model that decides which lookup to try next is called with a data-retention-refusal instruction on every single request, which restricts it to model providers that do not keep what was sent. We do not sell your information or your search activity to anyone.

6. Who we share it with

Three kinds of third party ever see it: Stripe, for payment; an email provider, for account and transactional email; and the model provider described above, for deciding which lookup to run next, under the no-retention instruction. The sources a search actually queries see the identifier being searched, since that is what performing a lookup requires. We do not disclose your search activity to marketers or data buyers.

7. Retention

We keep data until it's deleted; there is no automatic expiry today. Deleting your account removes your sign-in, API keys, and team memberships. For any team you were the sole member of, the whole team is deleted with it: its investigations, the facts they found, its job history, its credit and billing records, and any internal working notes that named the people you searched for. Your team's subscription is cancelled first; if that cancellation fails, the deletion is refused rather than run partway, so a deleted account can never end up still being charged. If you're the sole owner of a team that still has other members, deletion is refused until you transfer ownership or remove them. We will not take other people's team down with yours.

Two things are kept on purpose, not left behind by accident. Audit entries showing who searched, edited, or deleted what are never removed, for the reason given elsewhere on this page: they exist to hold our users accountable, not to describe you. And because HuntPeople keeps one shared record per real person across every customer, deleting your team doesn't delete a person outright if someone else has also searched them. The specific facts your team contributed are removed, and that person's summary is rebuilt without them, but the underlying record can still exist, held up by another customer's findings. A derived detail, like which company someone was connected to, can survive the same way if other customers' findings still support it, even after your own contribution to it is gone.

8. If you are the person who was searched

Email support@huntpeople.ai and tell us enough to identify your record. We will confirm what we hold and delete the facts stored on it. The audit entries showing that a lookup happened stay, since those exist to hold our users accountable rather than to describe you. There is no self-serve removal form yet.

9. Children

HuntPeople is intended for adults 18 and older. At signup, you must separately confirm you meet this requirement. We do not verify age beyond that confirmation, checking the box is not proof, and we have no way to independently confirm anyone's age. If we learn an account belongs to a minor, we will terminate it and delete what we can. Contact support@huntpeople.ai if you believe a minor's data has reached us.

10. Security

All production traffic runs over TLS, terminated at our edge with automatically renewed certificates. Passwords are hashed with a modern, purpose-built password-hashing algorithm, so we never hold your actual password. Your sign-in session is an opaque random token and only a one-way hash of it is stored, so our database cannot be turned back into a working login. An API key is shown to you once, at creation, and never again: we store only a hash and its first twelve characters, and cannot recover it. Your card number never reaches us.

Two things we would rather tell you than leave you to assume. Data in our database is not currently encrypted at rest. And HuntPeople staff can read across customer teams, for the accountability reason described in section 4.

11. International users

HuntPeople is built for and offered to users in the United States. We don't currently take technical measures to restrict access from other countries. If you use HuntPeople from outside the United States, that use isn't intended by us, and we make no representation that the service meets the privacy law of your country. You're responsible for your own compliance.

12. Changes to this policy

We may update this policy; the current version is always the one posted here.