Skip to content
LeadMind
Start free

How LeadMind sources, checks and protects data

A plain account of where LeadMind’s data comes from, what its checks can and cannot prove, how people can get out of it, and what LeadMind does and does not promise. The privacy policy and terms are the binding versions; this page explains them.

Trust · Updated

Where the data comes from

  • Public business listings (Google Maps), business directories (Yellow Pages in the US and Canada, the Zillow agent directory for US real estate) and each business’s own public website.
  • Public LinkedIn pages only to fill gaps for person leads, and only where that source is enabled.
  • Every list is scraped live when a customer asks for it. LeadMind does not maintain a standing database of people or sell one.
  • Website checks are done by LeadMindBot, which identifies itself, obeys robots.txt, reads at most six public pages per site and never logs in.

The full picture is on the lead sourcing page.

What verification can and cannot prove

  • Email: on paid plans each lead email is checked for syntax, a working mail server, disposable and role addresses, and whether the receiving server accepts the mailbox, without sending a message. A deliverable result means the server accepted that mailbox at that moment; it does not guarantee a reply, an inbox placement or that the person still works there.
  • Catch-all domains accept every address, so no verifier can confirm a mailbox on them. LeadMind marks them risky, and inconclusive checks unknown, rather than guessing. See catch-all domains explained.
  • On the Free plan emails carry their source (listing, website or guessed from a naming pattern) but no verification status.
  • Phone numbers are normalised and checked for a plausible format, not dialled.
  • Website signals reflect what the crawler found on the pages it read; a booking tool hidden behind a login or loaded only after interaction can be missed.

Privacy and compliance

  • LeadMind collects business contact data only: business names, job titles, work emails and phones, websites, business addresses and public profile links.
  • The legal basis is legitimate interest in business-to-business prospecting (GDPR Art. 6(1)(f); UAE PDPL). The privacy policy is the public notice for people who appear in lists.
  • Contact fields are encrypted at rest, raw scrape material is deleted after 14 days, and deduplication keys are hashes.
  • Anyone can object, ask for deletion, opt out of sale or sharing, or ask what LeadMind holds on the data request page, without an account. Identifiers go on a suppression list so no future list includes them.
  • Once a customer exports a list, they are an independent controller of it and responsible for their own lawful basis, notices and opt-outs when they reach out.

What LeadMind does and does not guarantee

LeadMind doesLeadMind does not
Charge only for delivered leads; failed and cancelled jobs, duplicates and filtered rows cost nothingGuarantee a number of leads for a prompt; results depend on what is public
Scrape public sources live for each job and show which source ran and whySell or maintain a contact database
Remove duplicates against your last 30 days and honour every opt-outGuarantee that every listing is current or every field complete
Label every email with its source and, on paid plans, a verification statusGuarantee deliverability, replies or inbox placement
Score each lead for fit with a readable reasonPredict buying intent
Re-credit rows from a list that is materially wrong for the prompt, per the refund policySend email, run campaigns or contact anyone on your behalf

Questions about data, security or a vulnerability report: tafveez28@gmail.com. See also the refund policy.

Related