Privacy

What Outreach Email Finder stores when you run a batch, how long it keeps it, and how to reach us about it.

The batch you run

A batch is the list of domains you paste, the time it was queued, and the allowance it was counted against. A batch run from an account is linked to that account. An anonymous batch is linked to a salted hash of the IP address the request came from and to nothing else: the address itself is never written down, and the free tier day is counted by summing those batch rows, so the count exists without the address existing. The domain list is kept while the batch lives, because the batch page shows the results by domain.

The results

One row per address the sites published: the address, the exact page URL it was found on, the type of that page, how it was found on the page, how many of the fetched pages repeated it, and the check labels. There is no field for a person, a job title, a company or a mailbox owner, and we do not add one. The page that published an address is stored beside it for the life of the batch, which is what makes an answer to a question about that address possible.

How long we keep it

Results for a batch run from an account are deleted automatically 30 days after the batch. Results for an anonymous batch are deleted after 24 hours. The deletion job reads the same two constants this page does, so the window here is the window the code enforces, not a target. Deleting a batch takes its domains, its addresses and its source page URLs with it.

No shared contact database

An address lives inside the batch that found it. We do not combine batches into one contact database, we never return an address found for one user in the results of another, and we do not search the web to discover domains nobody named. A batch returns what the sites it names published, and nothing else is built from it.

Why we may read those pages

The person running a batch names every domain first, and the pages read are the ones a site publishes about itself: home, contact, about, team, and the other pages a link builder would open by hand. The addresses returned are the ones the site put in public view on those pages. Our basis for reading them is legitimate interest: business contact discovery, on pages a user named, with no guessing and no pattern building. The crawler page describes how those requests behave and how a site can block them.

Asking us about an address

Ask us what we hold and the answer names the batches involved and the stored source page URL for each address. The source URL is kept per row partly for that reason: an address in our tables can be pointed back to the page that published it. Your own request rights apply here as they do anywhere: mail [email protected] and say what you want to know, or what you want deleted.

If you act on a result yourself

We do not contact anyone whose address a result contains, and we do not tell them their address was found. If you are in the EU and use an address from a result for your own outreach, that use is yours: you are the controller for it, and the notice to the person, under Article 14 of the GDPR, is yours to give. We give none on your behalf.

Opting out

Anyone can add an address to the opt-out list, and an address on that list is never returned in a result. The list holds a SHA-256 hash of the address and no other field, so it cannot be read back as a set of addresses. Add an address to the opt-out list.

Requests and accounts

The endpoints behind the tool count requests in a short window, keyed by the same salted IP hash, so one network cannot use the service as a free load generator. Those counters expire with their window. An account holds an email address and the details needed to sign in, plus the monthly count of domains charged against a paid plan. Cards are handled by Stripe, and no card number reaches us.

Contact

Questions, data requests and deletion requests: [email protected].