Your data and how long we keep it
What happens to the addresses you verify, what the shared cache and your own browser keep, and what remains once you delete your account, and for how long.
PricklyMails verifies addresses without keeping them. Here is what we do keep, where, and for how long. Verification runs on our servers in Germany, inside the European Union.
The addresses you verify
An address you submit stays in memory while it is verified, and is never written to disk. It is erased as soon as its verification ends, and after 96 hours at the latest.
With the result, we keep a fingerprint of the address and another one of its domain. A fingerprint is one-way: it cannot be turned back into the address. It is also computed with a secret key, so a copy of our database alone would not let anyone match it against a list of guessed addresses.
These fingerprints and their results feed your history, the shared cache described below, and aggregate statistics. They stay attached to your account for as long as it exists.
The shared verification cache
When an address was verified recently, by you or by another customer, and that result covers the checks you asked for, we serve it again instead of asking the mail server once more. The cache is keyed by the fingerprint, never by the address, and a result it serves costs you no token. Another customer only ever gets a cached result for an address they submitted themselves.
A result is reused only while it is likely to still hold.
| Kind of result | Reused for |
|---|---|
| A fact about the address or its domain: malformed address, no working mail server, disposable or generic address, catch-all domain | 88 days |
| An answer about the mailbox: it exists, it does not exist, or it is full | 28 days |
| No clear answer: the server did not reply, asked to try again later, or refused the check | 4 days |
The copy in your own browser
So that your history and your batch reports can show the addresses, the dashboard keeps a copy of them in the browser that submitted them. It holds the addresses of your 16 most recent batches and of your 256 most recent single verifications. That copy never leaves your browser, and it is erased when you sign out and when you delete your account.
In any other browser, a reference stands in for each address, and a downloaded batch report has a Reference column in place of Email. To get the addresses in a report, download it from the browser that sent the list.
Your account
For your account itself, we keep your email address, a hash of your password (never the password itself) and your language, so our emails reach you in it. We also record each sign-in and each sensitive change to your account with its date, IP address and browser, and your Notifications page lists these events. To recognize the browsers you already use, we keep only a fingerprint of the cookie set in each of them.
When you delete your account
Deleting your account, as Account security explains, deactivates it at once: your API keys and agents stop working, a paid plan is canceled, and you are signed out.
Once 28 days have passed, the account's history is erased for good: your verification history, API keys, webhooks and their delivery logs, sessions and remembered devices, agents, and the record of your account's activity with its IP addresses and browsers. The account itself is emptied rather than deleted: its email address and password hash are overwritten, and only an anonymous number remains.
What is kept for accounting
French accounting and tax law require billing records to be kept for up to 10 years, even after the account is deleted. These are your subscription, your token balance and its transactions, your payments, and the record of the terms of sale you accepted at checkout. None of them holds an email address or a name: they refer to the account by its anonymous number only.
Your card details never reach us: Stripe processes them directly.
Your rights
To access, correct or delete your data, or to object to its processing, write to legal@pricklymails.com: we answer within 28 days. The privacy policy has every detail, including the providers involved.
Common questions
Can PricklyMails read the addresses I verified?
No. Our servers keep only fingerprints, which cannot be turned back into addresses, and the readable copy stays in your own browser.
Why does my history show references instead of addresses?
You are in a browser other than the one that verified them, or you signed out since, which erases the copy. The results are all still there; only the addresses live in the browser.
Does deleting my account remove my results from the cache?
Yes. The cache is made of the results kept with each account, so once your history is erased, 28 days after the deletion, your results no longer serve anyone.
Keep reading
- Verify your first address
Create your PricklyMails account, confirm it with the code we email you, then verify a first address in the dashboard and read the answer it gives.
- Read a verification result
What the verdict, the recommendation, the score and the reason of a PricklyMails result mean, and what to do with each address before you send.
- Verify a whole list
Verify a list in one batch: upload or paste it, follow its progress, read and download the report, and see what happens to duplicates and invalid lines.
- Tokens and plans
How billing works: tokens spent check by check, what each check costs, plans and top-ups, tokens that never expire, and what is refunded or never billed.
- Keep your account secure
Set a strong password, turn on two-factor authentication, sign out the devices you do not recognize, and know which security emails your account sends you.
- Create and manage API keys
Create an API key for a tool or a script, choose a live or a test key and the checks it runs, then revoke it the moment the tool no longer needs it.
- Connect an AI assistant
Let Claude, ChatGPT, Cursor or another MCP client verify addresses for you: create an agent, add the PricklyMails server, approve it, and revoke it anytime.