Data sources
Where every field comes from.
This is the question everyone arrives with, whether they are deciding to buy or asking to be removed. Every field we hold is listed with its source and the basis we hold it on.
| Field | Where it comes from | Basis |
|---|---|---|
| Domain | Certificate Transparency logs. Certificate authorities are required to publish every certificate they issue, and the logs are public and append only. | Public record |
| Business name, trade, platform, tech stack | Read from the homepage the same way a browser reads it, respecting robots rules and rate limits. | Published by the business |
| Contact address | Only what is printed on the business own site. The default is a role address such as info@ or hello@. | Published by the business |
| Social links | The profiles the site links to itself. | Published by the business |
| Deliverability result | A third party check run at the moment a buyer unlocks the contact. We store the result, not a guess. | Processor, named in the policy |
What we never do
Buy lists from a data broker
Not once, not as a supplement, not to fill a gap in coverage.
Scrape LinkedIn or hold a personal profile
Signing in with LinkedIn is a buyer authenticating with their own account, which is the opposite thing.
Guess an address
If a business has not published a way to reach it, we do not invent one and pattern match it from a name.
Log enriched contact data
Never at info level or above, so personal data does not end up sitting in an operational log.
Getting removed
One form, no account, no reason required. It applies at ingestion, at unlock and at export, and it holds through every future run.