Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Lead Forensics Ltd · www.leadforensics.com

Report an error on this page Is this your product? →

Link to this page

Lead Forensics: AI-assisted analysis on whats-best.ai Lead Forensics: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Lead Forensics at a glance

Vendor
Lead Forensics Ltd
Headquarters
Not stated on the vendor’s pages as of 1 Oct 2026
Data hosting
In the EU by default; pages mention the United Kingdom source, captured 1 Oct 2026
Free plan
Not stated on the vendor’s pages as of 1 Oct 2026
Panel verdict
The AI panel rates Lead Forensics 2/5, the mean of 6 judges. Lead Forensics is a B2B website visitor identification tool: a JavaScript tag matches visitor IPs against a database the vendor describes as exclusively owned, then pushes identified companies into CRMs including Salesforce. how scores are made
As of
Vendor pages captured 29 Sep 2026 to 1 Oct 2026; evaluated by the panel 29 Oct 2026. all sources

Lead Forensics alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Lead Forensics is a B2B website visitor identification tool: a JavaScript tag matches visitor IPs against a database the vendor describes as exclusively owned, then pushes identified companies into CRMs including Salesforce. Scores cluster at 5-6 on visitor identification and CRM sync and export, the clear strengths, crediting company-level identification with real-time alerts, value scoring, and a documented Salesforce flow that enriches existing records and auto-assigns priority leads. Data coverage is the weakest criterion, flat at 2: the pages state no record counts, country breakdowns, verification method or refresh cadence. Prospecting compliance sits at 1-2, since the product is capture-and-route and we found no public information on search filters, suppression lists or cold-outreach guidance. The judges split on data provenance, 2 to 4: the higher scores credit per-record traceability to source, the lower ones the absence of a named GDPR legal basis for contact records. Sovereignty is uniform at 4 — servers stated as based in the UK/EU, subprocessor list inside the Data Processing Agreement. No prices appear on the captured pages.

Report an error

Speaks for it

  • Company-level visitor identification via reverse IP against a B2B database exclusively owned by Lead Forensics, with unmatched IPs purged after validation
  • The Salesforce integration checks whether a company already exists, enriches the record with the latest visitor insights, and auto-creates and assigns priority leads
  • Native integrations push identified leads to Salesforce, HubSpot, Microsoft Dynamics, Pipedrive, Zoho and Zapier
  • Each contact record can be traced back to its original source, with the third-party suppliers acting as independent data controllers
  • ISO/IEC 27001:2013 certification is published, with the current certificate valid until 1 December 2026

Report an error

Held against it

  • The captured pages state no record counts, country-by-country coverage, verification method or refresh cadence for the matching database
  • No GDPR legal basis is named for the contact records, and we found no removal route beyond the Do not sell my data option
  • We found no public information on firmographic search filters, saved lists, do-not-contact suppression or cold-outreach guidance for EU contacts
  • The subprocessor list sits inside the Data Processing Agreement rather than on public pages, and the contracting entity's jurisdiction is not confirmed on the captured pages
  • Cookie-law compliance responsibility is placed on the website operator, and we found no public information on consent-platform integrations or a stated position on §25 TDDDG

Report an error

Best for

  • You need to know which companies visit your website and get real-time alerts routed to the right rep while the visit is still warm
  • Your team works in Salesforce and wants existing account records enriched with visitor insights, with priority leads auto-created and assigned
  • You want alerts when customers land on key pages, to surface up-sell, cross-sell or win-back opportunities

Report an error

Avoid if

  • You need to size the database before buying — ask the vendor: the public pages we read do not show it
  • Your workflow depends on firmographic search, saved lists and do-not-contact suppression — ask the vendor: the public pages we read do not show it
  • You must demonstrate EU-only data residency to a client's data protection officer — the vendor states only that servers are based in the UK/EU
  • You need to compute an annual cost before entering a sales conversation — ask the vendor: the public pages we read do not show it

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Coverage, accuracy & freshness

Show reasoning
How this is scored

How much of the target market the database actually covers — judged on DACH and EU coverage as much as North American — and what the vendor documents about verification and refresh, because accuracy claims cannot be checked from outside.

0 — Not a data product: the tool supplies no contact or company data and only manages leads the customer brings.

3 — Total record counts for the database with the data types offered (email, phone, company data) and email verification mentioned.

5 — Coverage stated by country or region with Europe or DACH included, email verification described, firmographics beyond name and domain (industry, size, revenue), and a refresh cadence or last-verified date stated.

8 — Coverage broken down by country, industry and data type (email, direct dial, mobile), verification method and refresh cadence documented, company data drawn from official registers where available, and a bounce or credit-back guarantee with stated terms.

10 — The vendor is accountable for its data: per-country coverage and accuracy methodology published, every field carrying a last-verified date visible to the user, register-sourced company data, and credit-back terms that make inaccuracy the vendor's cost rather than the buyer's.

Report an error

The SDR Team Lead

Identified businesses come with name, address and phone, and an optional contact feature adds job title, LinkedIn, phone and email — the fields my SDRs need exist. But the captured pages give no record counts, no per-country coverage, no verification method and no refresh cadence, so I cannot judge whether the emails will land or the numbers dial through. I buy connect rate, not record counts, and nothing here lets me estimate either. 4 5

Report an error

The RevOps Manager

This is a data product — matched businesses show name, address and phone number, and an optional contact feature adds first name, surname, job title, phone and email — but we found no record counts, no country-by-country coverage and no public information on verification or refresh cadence for the database behind the IP matching. 4 5

Report an error

The Data Protection Officer

The core product is company-level visitor identification, with an optional contact data feature offering first name, surname, job title, LinkedIn URL, phone and email from approved third-party suppliers. The captured pages give no record counts, no coverage by country or region, no email verification method and no refresh cadence or last-verified date, so accuracy claims rest solely on the statement that each record can be traced to its source. 4 5

Report an error

The ABM Marketer

The owned B2B database behind the IP matching carries no record counts, country breakdown, verification method or refresh cadence on the captured pages, so I cannot judge DACH depth against North American. Documented data types are business name, address and phone for matched companies, plus optional contact fields (email, phone, job title) from third-party suppliers — a data product, but well short of stated coverage. 4 5

Report an error

The DACH Sales Director

The portal displays firmographics — business name, address and phone number — and an optional contact-data feature adds first name, surname, job title, phone, email and LinkedIn URL through third-party suppliers. But the captured pages state no record counts, no coverage broken down for Germany, Austria or Switzerland, and we found no public information on a verification method or refresh cadence, so I cannot tell a Mittelstand prospect how many of their targets are actually in there. 4 5

Report an error

The Skeptic

The pages describe an IP-matching database "exclusively owned by Lead Forensics" and an optional contact-data feature listing first name, surname, LinkedIn URL, job title, phone and email, with firmographics going as far as business name, address and phone number. But we found no public information on record counts, coverage by country or region (DACH or otherwise), email verification, refresh cadence, or any bounce or credit-back guarantee. 1 4 5

Report an error

Data sources & lawful basis

Show reasoning
How this is scored

Where the personal data in the database comes from and on what legal basis it is processed — as evidenced on the vendor's own pages. Covers Art. 6(1)(f) legitimate interest, the Art. 14 notice to the people in the database, and whether they can find, object to and remove their record.

0 — The vendor states that it leaves the legal basis for the personal data it sells entirely to the buyer, or that records are collected without the people in them being able to object.

3 — Sources described in general terms (public sources, partners), a GDPR legal basis named, and an opt-out or removal route for people in the database.

5 — Source categories named (registers, company websites, contributory networks, licensed partners), legitimate interest under Art. 6(1)(f) stated as the basis for EU records, a privacy notice addressed to the people in the database, and a self-service opt-out or removal process.

8 — The above plus an Art. 14 notification practice described (people informed when added), contributory or browser-extension collection disclosed as such, a legitimate-interest assessment summarised publicly, and EU records handled differently from US records where the law differs.

10 — Provenance is traceable per record: the source and collection date available for each contact, Art. 14 notices sent and documented, the balancing test published, objections honoured across the whole dataset and suppressed permanently, and no data sourced by scraping behind logins or from contributors' address books without their contacts' knowledge.

Report an error

The SDR Team Lead

Contact records come from approved third-party suppliers acting as independent controllers, accessed via API, and the vendor states each record can be traced back to its original source — that per-record traceability is more than most show, and unmatched IPs come from publicly available sources. We found no public information naming the GDPR basis for the contact records, a privacy notice addressed to the people in them, or an opt-out beyond the "Do not sell my data" link. 1 4 5

Report an error

The RevOps Manager

Sources are described in general terms — a B2B database exclusively owned by Lead Forensics, publicly available sources for unmatched IPs, and approved third-party suppliers acting as independent controllers — with each contact record claimed traceable back to its source; we found no named GDPR legal basis for the database records themselves, and the only opt-out route shown is a Do-not-sell-my-data link alongside a privacy policy. 1 4 5

Report an error

The Data Protection Officer

Contact records come from approved third-party suppliers that the vendor says act as independent data controllers, unmatched IP data is drawn from publicly available sources, and each record is claimed traceable to its source. But the pages name no GDPR legal basis for the contact records themselves, describe no Article 14 notice to the people in the database, and offer no removal route beyond a do-not-sell option, while responsibility for the tracking cookie is placed on the website operator. 1 4 5

Report an error

The ABM Marketer

Contact records arrive via API from approved third-party suppliers acting as independent data controllers, with each record claimed traceable to its source — the most concrete provenance statement on the pages. No legal basis for those records is stated and no privacy notice addressed to the people in the database is shown; the GDPR material captured is the Article 28 processor DPA for customer data. A "Do not sell my data" option exists, but its scope for the contact database is not explained. 1 4 5

Report an error

The DACH Sales Director

Contact data comes from approved third-party suppliers acting as independent controllers, and each record can be traced back to its source — more transparency than most US-built databases give me. But the pages name no GDPR legal basis for those records, and beyond a privacy policy and a do-not-sell option we found no public information on a self-service removal route for the people in the database. 4 5 1

Report an error

The Skeptic

Contact records come from "approved third-party suppliers, which act as independent data controllers" — sources in general terms, unnamed — though each record is claimed traceable to its source, and unmatched IPs come from "publicly available sources". The pages name an Article 28 processor role for customer data and a "Do not sell my data" opt-out, but we found no public information naming the legal basis on which the people in the contact data were collected, and responsibility for the tracking cookie is placed on "the business operating the website". 1 4 5

Report an error

Visitor identification & intent signals

Show reasoning
How this is scored

Identifying companies behind website visits and surfacing buying intent — scored on what is identified (company or person), how the tracking works, and whether the vendor states that its script needs consent under §25 TDDDG and how it behaves without it.

0 — No visitor identification or intent data; the product does not look at website visits.

3 — Reverse-IP identification of the companies behind website visits through a tracking script, with visits listed per company.

5 — Company-level identification with filters and visit history per company, alerts or CRM handover of identified companies, and a stated position on consent for the script or a consent-mode option.

8 — Company-level only for EU traffic by design, cookieless operation documented, integration with common consent management platforms and the §25 TDDDG position stated, intent topics or page-level signals with the source of third-party intent data named, and alerts routed to owners.

10 — Identification that survives a DPO review: no personal data of visitors stored, the TDDDG and GDPR position published and specific, third-party intent data sourced from a named co-op or panel with its consent basis stated, and scoring on intent that the user can trace back to the underlying visits.

Report an error

The SDR Team Lead

This is the core of the product: a JavaScript tag matches visitor IPs against a vendor-owned B2B database, with value scoring, key-page alerts routed to the right rep and automatic push into CRM. The vendor states it cannot identify the visiting individuals, excludes sole traders and consumers, and purges unmatched IPs after validation — the story a DPO wants to hear. But the cookie is optional rather than absent, the captured pages put compliance responsibility on the website operator instead of stating a consent-mode or German TDDDG position, and no consent-platform integration is shown. 1 4 5 7

Report an error

The RevOps Manager

Company-level identification is the core product, with visit insights, alerts on key pages, routing to the right rep and CRM handover, and the vendor states the website operator is responsible for compliance while the cookie itself is optional; we found no public information on consent-mode or consent-platform integration, a §25 TDDDG position, or any named third-party source for the intent signals, and cookie-free operation is described for the trial only. 1 5 7

Report an error

The Data Protection Officer

Identification is company-level by design — the vendor states it cannot identify the individuals who visited — via a JavaScript tag with an optional year-long first-party cookie, plus a cookie-free trial mode, alerts and automatic handover to CRM with value scoring on website behaviour. The only published consent position is that the website operator is responsible for compliance; we found no mention of the German telemedia consent requirement or integration with consent management platforms. 1 4 5 7

Report an error

The ABM Marketer

Reverse-IP company identification against an exclusively owned B2B database, real-time alerts when a target business lands on the domain, key-page alerts, and a Salesforce flow that enriches the existing account record and auto-assigns the priority lead to the right user while the visit is still warm. The cookie is optional, the trial runs cookie-free, and unmatched IPs are purged. We found no public information on consent-platform integrations, a specific position on German tracking law, or third-party intent data with a named source — visitor-value scoring rests on first-party behaviour only. 1 4 5 7

Report an error

The DACH Sales Director

This is the core of the product: a JavaScript snippet collects the IP address and standard request data, matches them against an in-house B2B database, and the vendor states plainly that the individuals behind the visits cannot be identified, with sole traders and consumer details excluded. Alerts, customizable prioritisation, automatic assignment and CRM handover are documented, and the first-party cookie is optional with a cookie-free trial; however, the vendor places cookie-law responsibility on the website operator, and we found no public information on consent-platform integration or a stated position on the German consent rule for such scripts. 5 1 7

Report an error

The Skeptic

This is the core product: JavaScript on the site, IP matched against an owned B2B database, company-level results only — the vendor states the visitors themselves cannot be identified, sole traders are excluded, the cookie is optional with a cookie-free trial, and unmatched IPs are purged. Alerts on key pages, value scoring on firmographics plus behavior, and routing to owners inside Salesforce are documented. The consent story stops at pushing responsibility to the website operator: we found no public information on a consent-mode option, consent-platform integrations, or a stated position on §25 TDDDG. 1 4 5 7

Report an error

Prospecting workflow & outreach rules

Show reasoning
How this is scored

Search, list building and outreach — and whether the product helps the buyer stay within UWG §7 and the GDPR once the list exists, rather than leaving the legal risk entirely with the customer.

0 — No search, list building or outreach; the product only stores leads entered or captured elsewhere.

3 — Search with filters on firmographics and job title, saved lists, and export of the contacts found.

5 — Advanced filters (technographics, hiring or funding triggers), saved searches with alerts, a suppression or do-not-contact list, and guidance on GDPR or cold-outreach rules for EU contacts.

8 — Country-aware handling (for example German contacts flagged where cold calls and emails require consent under UWG §7), phone numbers checked against national do-not-call registers where they exist, and opt-outs from outreach synced back to the database.

10 — Compliance is part of the workflow: outreach channels restricted or flagged per country and contact type by default, suppression shared across the whole account and every export, the Art. 14 notice supported at first contact, and a documented record of how each contact entered the buyer's pipeline.

Report an error

The SDR Team Lead

The product is built around capturing companies that already visited, not searching a database: an optional contact-data feature attaches names, titles and emails to identified businesses, but we found no public information on firmographic search filters, saved lists, do-not-contact suppression or country-aware outreach rules. Nothing on the captured pages helps my team stay inside UWG §7 once a list exists — that risk sits entirely with us. 1 4 5

Report an error

The RevOps Manager

This is lead capture and routing, not a prospecting database: the captured pages show no search with firmographic or job-title filters, no saved lists, no suppression or do-not-contact handling, and no guidance on cold-outreach rules, while export is described only as available depending on configuration and contracted services. 4 5 7

Report an error

The Data Protection Officer

The captured pages show identified companies routed to sales reps in real time and contact data with emails and phones available for outreach, but no search filters on firmographics or job title, no saved lists, no do-not-contact suppression list, and no guidance on German or EU cold-outreach rules. The compliance FAQ places the controller role and the duty to answer data subject requests on the customer, with Lead Forensics assisting where required by law and contract. 1 4 5

Report an error

The ABM Marketer

The workflow is capture-and-route rather than search-and-build: alerts and CRM pushes on identified companies, with an optional contact data feature supplying names, titles, emails and phones for outreach. We found no public information on firmographic search filters, saved lists, contact export, a do-not-contact suppression list, or guidance on cold-outreach consent rules for EU contacts; the one stated compliance posture puts website cookie responsibility on the customer. 1 4 5

Report an error

The DACH Sales Director

What is documented is capture and routing — real-time alerts when a target business lands, automatic lead creation and assignment into Salesforce — plus an optional contact-data feed with job titles, phones and emails. We found no public information on contact search with firmographic filters, saved lists, export of found contacts, or suppression and do-not-contact handling, and we found no public information on guidance for German cold outreach under §7 UWG, so that risk sits entirely with my team rather than the tool. 1 7 5

Report an error

The Skeptic

The captured pages show a website visitor identification tool rather than a database search workflow: we found no public information on firmographic search filters, saved lists, do-not-contact suppression, guidance on cold-outreach rules for EU contacts, or do-not-call register checks. The optional contact-data feature does supply email and phone via API from third-party providers, and export is described only as available "depending on configuration and contracted services". 1 4 5

Report an error

CRM sync, enrichment & export

Show reasoning
How this is scored

Getting the data into the systems where sales works — CRM sync, enrichment of existing records, API — and what happens to exported data, and to the buyer's access to it, when the subscription ends.

0 — Data can only be viewed inside the product; the vendor states no export and no integration.

3 — CSV export and a push of contacts to at least one named CRM.

5 — Native integrations with the major CRMs (Salesforce, HubSpot or similar) with field mapping or deduplication, enrichment of existing CRM records, and a documented API.

8 — Bidirectional sync with scheduled re-enrichment, update and deletion propagated when a record changes or a person objects, webhook or API access with stated limits and credit costs per call published, and data retention rights after cancellation stated plainly.

10 — The vendor treats the buyer's CRM as the system of record: objections and corrections propagated into synced records automatically, full change history per field, a versioned API with a deprecation policy, and exit terms that say exactly which data the customer may keep and for how long.

Report an error

The SDR Team Lead

Leads flow to where my team works: native integrations push identified companies to Salesforce, HubSpot, Dynamics, Pipedrive, Zoho and Zapier, and the Salesforce one checks whether the company already exists, enriches the record with the latest visitor insights, auto-creates and assigns priority leads and runs reports inside Salesforce. Self-service export is described only as available depending on configuration, and data is deleted or returned when the agreement ends. We found no public information on a documented API, bidirectional sync or field mapping. 4 6 7

Report an error

The RevOps Manager

The Salesforce flow is what I want to see — it checks whether the company already exists in the CRM, enriches the existing record by appending the latest visitor insights instead of creating a duplicate, assigns priority leads to owners and raises reports inside Salesforce — with native integrations for HubSpot, Dynamics, Pipedrive and Zoho, and deletion or return of customer data stated at contract end; we found no public information on field mapping, a customer-facing API, webhook limits or bidirectional sync. 4 6 7

Report an error

The Data Protection Officer

Native integrations with Salesforce, HubSpot, Microsoft Dynamics, Pipedrive, Zoho and Zapier push identified leads out automatically, and existing Salesforce records are enriched with visitor insights and alerts routed to team members. Export exists but only 'depending on configuration and contracted services', and data is deleted or returned when the agreement ends; we found no public information on field mapping, deduplication, a customer-facing API, or credit costs per call. 4 6 7

Report an error

The ABM Marketer

Six named CRM integrations including Salesforce, HubSpot, Dynamics, Pipedrive and Zoho, with the Salesforce flow documented in detail: company matched against existing records, enrichment with the latest visitor insights, automatic lead creation and assignment, plus in-CRM reporting. Export is described only as platform functionality "depending on configuration and contracted services"; we found no public information on field mapping, deduplication, a customer-facing API or bidirectional sync, though end-of-contract deletion or return of customer data is stated. 4 6 7

Report an error

The DACH Sales Director

Native integrations are documented for Salesforce, HubSpot, Microsoft Dynamics, Zoho and Pipedrive, with the Salesforce integration enriching existing records, auto-creating and assigning priority leads, and building visit reports. We found no public information on field mapping, bidirectional sync or a customer-facing API with published limits, and end-of-contract handling is stated only as deletion or return of customer personal data under the DPA. 6 7 4

Report an error

The Skeptic

Native integrations for Salesforce, HubSpot, Dynamics, Pipedrive and Zoho are documented, with existing Salesforce records enriched with visitor insights, existing companies recognised rather than duplicated, priority leads auto-created and assigned, and alerts routed per account. We found no public information on a documented customer API, field mapping, or scheduled re-enrichment; on exit the vendor states it "will delete or return customer personal data" per the agreement. 4 6 7

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Where a database of EU residents' personal data is held, who the contracting entity and controller are, and which subprocessors see it. Independently sourced by the sovereignty pipeline; weighted heavily here, because the product itself is personal data about people who never chose the vendor.

0 — Vendor, contracting entity and processing of EU residents' contact data all shown to be outside the EU, with no transfer basis stated.

3 — A named contracting entity and a privacy policy or data processing agreement; a non-EU entity with an EU representative under Art. 27, or EU hosting offered while the hosting location of the database is not stated.

5 — EU hosting stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.

8 — EU contracting entity and controller, EU hosting on named infrastructure, subprocessor and data-partner list published, and any non-EU transfer named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, controller, hosting, data partners and every subprocessor European, certification published, and a DPA covering both the customer's data and the database records the customer exports.

Report an error

The SDR Team Lead

The vendor states its servers are based in the UK/EU, operates an Article 28 EU/UK GDPR data processing agreement, names transfer safeguards such as Standard Contractual Clauses for restricted transfers, and holds ISO 27001. But the contracting entity Lead Forensics Ltd is UK-based, the subprocessor list sits inside the data processing agreement rather than on public pages, and the hosting statement mixes UK with EU without naming infrastructure. 4 5

Report an error

The RevOps Manager

Servers are stated to be based in the UK/EU, an Article 28 EU/UK GDPR processing agreement is offered, restricted transfers use adequacy decisions or standard contractual clauses, and subprocessor changes come with notification and an objection right — but the subprocessor list sits inside the processing agreement rather than published, and we found no confirmation of the contracting entity's jurisdiction on the captured pages. 4 5

Report an error

The Data Protection Officer

The captured pages state that servers are based in the UK/EU, that a Data Processing Agreement under Article 28 EU/UK GDPR is offered, and that any restricted international transfers use named safeguards such as adequacy decisions, Standard Contractual Clauses and the UK transfer agreement. However, the contracting entity's jurisdiction, ownership and subprocessor exposure are not confirmed on the captured pages, the sub-processor list sits inside the Data Processing Agreement rather than published, and UK hosting alone is not EU hosting. 1 4 5

Report an error

The ABM Marketer

The pages state "Our servers are based in the UK/EU" and an Article 28 EU/UK GDPR DPA is offered, with subprocessors used for hosting, storage, authentication and contact data services — but the subprocessor list sits in the DPA rather than being published. We found no public information establishing the contracting entity's jurisdiction or ownership, and international transfers are addressed only by naming safeguard mechanisms (adequacy decisions, SCCs, UK IDTA), not by naming destinations. 1 4 5

Report an error

The DACH Sales Director

Servers are stated as "UK/EU" with the tracking script sending data there for processing, an Article 28 EU/UK GDPR DPA is offered, ISO 27001 certification is published, and restricted transfers are covered by named safeguards such as adequacy decisions and Standard Contractual Clauses. But the subprocessor list lives inside the DPA rather than on public pages, the contact-data suppliers are unnamed independent controllers, and the jurisdiction of the contracting entity is not confirmed on the captured pages — UK/EU hosting is not the EU hosting I need to defend to a German client's data protection officer. 5 4

Report an error

The Skeptic

"Our servers are based in the UK/EU" is the full hosting statement — no named infrastructure or region — alongside an Article 28 EU/UK GDPR processing agreement, ISO 27001 certification valid until December 2026, and international transfers covered by adequacy decisions, Standard Contractual Clauses or the UK IDTA. Sub-processors are used for hosting, storage, authentication and B2B contact data services, but the list sits in the processing agreement rather than on public pages, and the contracting entity's jurisdiction is not confirmed on the pages we read. 1 4 5

Report an error

Pricing transparency not rated — the vendor publishes no price

Show reasoning
How this is scored

Whether a buyer can compute the real annual cost from public pages alone — including credits per email, phone number and mobile, credit expiry, seat pricing, visitor-identification tiers and the API — in a category where the unit of billing is often invented by the vendor.

0 — No public prices at all; every tier is a sales conversation.

3 — A public "from" price, a free tier or one priced tier, while what a credit buys or the other tiers are not stated.

5 — Prices public per tier with the billing period and the credits or contacts included per tier; extras such as mobile numbers, additional seats or API access may still be on request.

8 — Every tier priced publicly with credits per data type, credit expiry and rollover, per-seat costs, overage rates, minimum term and VAT treatment stated.

10 — Complete price computability: the annual invoice derivable for a given number of seats, exported contacts by data type, identified companies and API calls, with every credit cost and the refund rule for inaccurate data published.

Report an error

The SDR Team Lead

Across the captured pages the only commercial entry points shown are a free trial and a revenue calculator — no tier prices, no credits, no seat costs, no visitor-identification tiers and no API pricing. Nothing here lets me put even a rough annual number in a budget before a sales conversation. 1 7

Report an error

The RevOps Manager

The only public offers we found are a free trial and a revenue calculator; no tier prices, credits, seat costs, billing periods or credit expiry appear on the captured pages, so a buyer cannot compute a real annual cost from them. 1 7

Report an error

The Data Protection Officer

The only public pricing signals are a free trial and a revenue calculator; we found no public information on tier prices, what a credit buys, credit expiry or rollover, seat costs, visitor-identification tiers or API charges. A buyer cannot compute an annual cost from the captured pages, as every commercial term beyond the trial appears to be a sales conversation. 1 7

Report an error

The ABM Marketer

No prices appear on any captured page — no tiers, credits, seat costs or billing period — just a free trial and a calculator that estimates missed leads rather than cost. The trial itself only adds the script, with no portal access. I cannot compute an annual figure from these pages. 1 5 7

Report an error

The DACH Sales Director

Public pages offer a free trial and a revenue calculator, and that is all: we found no public information on tier prices, billing periods, what a plan includes, per-contact costs, seats or contract terms. A Mittelstand buyer cannot compute even a rough annual cost before entering a sales conversation. 7 1

Report an error

The Skeptic

We found no public information on prices, tiers, credits per data type, seat costs, credit expiry or visitor-identification tiers on any page captured. The only cost-related items are a "Try for free" offer and a revenue-and-leads calculator, so a buyer cannot begin to compute an annual cost from these pages. 1 7

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location EU by default unverified
Why unverified?

The UK is outside the EU/EEA, and the Customer FAQ additionally states that personal data "may [be] process[ed] ... in countries where its systems, or approved sub-processors, operate" with SCCs/UK IDTA, so European hosting is the default rather than exclusive.

2/4 pts 5 Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Lead Forensics

Is Lead Forensics European?

Not determined: the vendor’s pages as captured do not say where Lead Forensics is based.

Where does Lead Forensics store data?

Lead Forensics stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 1 Oct 2026. The vendor’s pages mention the United Kingdom as hosting location, per the vendor’s page captured 1 Oct 2026.

Does Lead Forensics have a free plan?

Not stated on the vendor’s pages as of 1 Oct 2026.

What are the best alternatives to Lead Forensics?

As of 18 Nov 2026, the panel rates Dealfront (3/5), Lusha (2.5/5) and Vainu (2.5/5) highest among the other 48 Lead Generation products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Dealfront (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Lead Forensics alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (7)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page www.leadforensics.com Checked 29 Sep 2026 Details →
  2. 2 Visitor identification & intent signals — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →
  3. 3 Visitor identification & intent signals — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →
  4. 4 Prospecting workflow & outreach rules — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →
  5. 5 Prospecting workflow & outreach rules — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →
  6. 6 CRM sync, enrichment & export — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →
  7. 7 CRM sync, enrichment & export — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →