The short version
- No people database. Every search goes to public sources at the moment you run it. Nothing is looked up from a stored profile, and we do not build one.
- Results are not stored. Result data is processed in memory, streamed to your browser and never written to our database.
- We do not sell personal data and we run no advertising trackers.
- Anyone can opt out. Email addresses are blocked instantly after a one-time code; usernames and phone numbers through a reviewed request.
How a search runs
When you search, Tracehound normalizes the identifier (for example, it strips a leading @ from a username or converts a phone number to international format) and checks it against the opt-out list. It then sends requests to each supported source in parallel. Each source answers in one of three ways: an account exists, no account exists, or no trustworthy answer was possible. Matches are sent to your browser as they arrive.
The profile details shown on a result card are the ones the source itself makes public at that moment. When the search ends, the result data is gone from our servers. If you want to keep it, export it (Pro and Max) or note what you need.
What is stored, and what is not
We keep the minimum needed to run accounts, billing and the opt-out list:
| Your account | Email address, an optional display name, plan and token balance. For Google sign-in, the Google account identifier, name and avatar URL that Google provides. |
|---|---|
| Sign-in codes | Stored only as hashes and valid for 10 minutes. There are no passwords. |
| Sign-in sessions | One record per signed-in device with its IP address and browser user agent, so you can see and revoke them. |
| Search history | Only the query, its type, the number of results, the status and the time. Off with one switch. |
| API keys | A SHA-256 digest of each key, never the key itself, with its name, first characters, and creation, last-used and revocation times. |
| Billing | Stripe customer and subscription identifiers. No card numbers. |
| Opt-outs | Keyed one-way hashes of opted-out identifiers, not the identifiers in readable form. |
| Messages | What you send us through the contact form. |
We never store:
- The results of your searches: profile data, avatars, bios, counts, links
- Any database or profile of the people you search for
- Card numbers or bank details
- Advertising or cross-site tracking identifiers
The full list of data categories, purposes, processors and retention periods is in the Privacy Policy.
Accounts and sign-in
- No passwords to steal or reuse. You sign in with a one-time 6-digit code sent to your email, or with Google. Your first sign-in creates the account.
- Sign-in codes are stored only as hashes, expire after 10 minutes and allow 3 attempts. After that you request a new one.
- Sessions last 30 days. Settings lists every signed-in device with its browser and IP address, and you can revoke any of them.
- Because a code goes to your inbox, the security of your account follows the security of your email. Protect it with two-factor authentication.
- The site is served over HTTPS only, with strict transport security and headers that block framing and content sniffing.
API keys
Pro and Max accounts can create keys for the HTTP API in settings, up to 5 at a time. A key acts as your account, so it is handled like a password:
- Shown once. The full key is displayed a single time, right after you create it. Each key carries 256 bits of randomness.
- Stored as a digest. We keep only a SHA-256 digest of the key, plus its name, its first characters (so you can tell keys apart), and when it was created, last used and revoked. Nobody, including us, can read a key back from what is stored.
- Revocable at any time. Revoking a key in settings takes effect on the next request. Deleting your account deletes its keys.
- Server-side only. Keys belong on your servers, never in browser or mobile code. The API sends no CORS headers, so other websites cannot call it from a visitor's browser, and repeated requests with invalid keys are rate limited.
Searches made through the API follow the same rules as the app: results are not stored, opt-outs are honored, and the Acceptable Use Policy applies.
Payments
Payments are handled entirely by Stripe. Card details are entered on Stripe's systems and never touch Tracehound servers. We keep only the Stripe identifiers needed to link your subscription to your account.
Your search history
History helps you rerun and keep track of your work. It stores only the query, its type, the number of results, the status and the time. You can delete a single entry, clear everything, or switch history off entirely in settings. Deleting your account deletes your history with it.
Opt-out for anyone
You do not need an account to opt out. On the opt-out page, enter an email address and confirm the one-time code we send to it. From that moment, searches for that address on Tracehound return nothing. Usernames and phone numbers cannot be verified the same way, so those are blocked through a short request that a person reviews.
Opted-out identifiers are stored only as keyed one-way hashes: we can check whether a search matches the list, but the list cannot be read back as a set of addresses or numbers. Opting out stops searches on Tracehound. It cannot remove your accounts from the sites where they exist.
Deleting your account
Account deletion is self-serve in settings. It removes your account, sessions and search history and cancels any active subscription. Records we must keep for tax or legal reasons, such as invoices held by Stripe, are kept only as long as the law requires.
Responsible use
Tracehound only shows what sources make public, but public is not the same as harmless. Results are research leads, not proof of identity. Tracehound is not a consumer reporting agency and must not be used for decisions about employment, housing, credit or insurance, or to stalk, harass or locate anyone.
Accounts used for abuse are closed. The Acceptable Use Policy sets out the rules in full. If you believe someone is using Tracehound against you, contact support@example.com and opt out your identifiers.
Reporting a vulnerability
If you find a security issue, email support@example.com with "Security" in the subject. Include what you found, how to reproduce it and the impact you expect. We will acknowledge your report, keep you updated while we fix it, and credit you if you would like.
While testing, please:
- Use only your own accounts and data, and stop as soon as you reach anyone else's.
- Avoid anything that degrades the service for others, such as load testing or spam.
- Do not use the search engine against people who have not agreed to it.
- Give us reasonable time to fix the issue before you disclose it.
We will not pursue legal action against good-faith research that follows these guidelines.