Leadinfo
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Leadinfo B.V. · www.leadinfo.com
Compare with Dealfront → Compare with Albacross → Report an error on this page Is this your product? →
Link to this page
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.
Leadinfo at a glance
- Vendor
- Leadinfo B.V.
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- In the EU; pages mention Ireland source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Leadinfo 2.5/5, the mean of 6 judges. Leadinfo is company-level website visitor identification from the Dutch vendor Leadinfo B.V. how scores are made
- As of
- Vendor pages captured 8 Nov 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Leadinfo is company-level website visitor identification from the Dutch vendor Leadinfo B.V. The bench scored it strongest on visitor identification, 6-7, where real-time reverse-IP recognition, a cookieless tracking option and a stated non-retention of IP addresses are documented in depth; data provenance clusters at 5 on named public sources, legitimate interest under Article 6(1)(f) and a self-service opt-out. It is weakest on pricing transparency, 3-4, where we found no public information on the prices of the Starter, Scale or Pro tiers — the public pages show seat counts of 3, 10 and unlimited plus addon from-prices — and on data coverage, 3-4, where counts of 220 million companies and more than 300 million decision makers are published without public information on verification or a refresh cadence. No disagreements were flagged; the widest spread, 4-6 on CRM sync and export, rests on a 4 that weighed finding no public API documentation and one-month post-cancellation retention of account data against praise for the HubSpot and Salesforce depth. The captured pages also give different signals on transfers outside the EEA.
Speaks for it
- Visitor identification scores 6-7, with real-time reverse-IP company recognition, a cookieless tracking option, consumer IPs filtered out and IP addresses stated as not saved
- Data provenance clusters at 5, on named public sources such as the trade register, a legitimate-interest basis under Article 6(1)(f), and a self-service opt-out that deletes the record and stops recollection
- HubSpot and Salesforce integrations are documented in depth — matching on domain, phone and chamber-of-commerce number, field mapping, deals, tasks and visit notes — among 67 free CRM integrations
- The vendor recommends obtaining visitor consent before activating the tracking script and supplies template texts for informing website visitors
- Add-ons carry public from-prices — Autopilot Starting at € 39/seat, Leadbot Business Starting at € 59 /seat, Liquid content Starting at € 39 /mo — alongside a 14-day trial without payment details and repeat company visits counted once
Held against it
- Pricing transparency scores 3-4: we found no public information on the prices of the Starter, Scale or Pro tiers or the lead volumes each includes, so the annual cost is not computable from the captured pages
- Data coverage scores 3-4: the published counts of 220 million companies and more than 300 million decision makers come without public information on email verification, a refresh cadence or last-verified dates
- Prospecting compliance clusters at 4, with no public information found on suppression lists, country-aware flagging of German contacts under UWG §7, or do-not-call register checks, leaving outreach-law risk with the buyer
- Sovereignty scores 5-6: hosting is stated in Ireland on AWS EMEA SARL, yet the privacy policy acknowledges sharing outside the EEA under safeguards, discloses team.blue group sharing, and we found no public information on a published subprocessor list
- We found no public information on a documented API, on scheduled re-enrichment, or on propagating objections and deletions into synced CRM records
Best for
- You run HubSpot or Salesforce and want identified website visitors matched to existing companies on domain, phone or chamber-of-commerce number before anything new is created
- You want real-time, first-party page-visit signals routed to an account owner, with a cookieless tracking option available
- Your sign-off requires a named lawful basis and a working self-service opt-out for the people profiled in the vendor's database
- You want to evaluate before committing, using the stated 14-day trial without payment details
Avoid if
- You must compute the annual cost before signing — the public pricing pages show addon from-prices and seat counts of 3, 10 and unlimited, with no public information on tier prices or lead volumes
- Your outreach needs built-in suppression or country-aware handling of German contacts — we found no public information on these, and the help centre places the outreach-law risk with the customer
- You require public assurance that personal data stays within the EEA — the privacy policy acknowledges sharing outside the EEA with safeguards in place, and the captured pages give different signals on transfers
- Your data quality bar requires verification or freshness figures — the pages publish headline counts, and we found no public information on email verification or a refresh cadence
The scores
| Criterion | Panel median |
|---|---|
| Coverage, accuracy & freshness | 2 of 5 |
| Data sources & lawful basis | 2.5 of 5 |
| Visitor identification & intent signals | 3.5 of 5 |
| Prospecting workflow & outreach rules | 2 of 5 |
| CRM sync, enrichment & export | 3 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 1.5 of 5 |
Coverage, accuracy & freshness
Show reasoningHide 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.
The SDR Team Lead
Headline counts of 220 million companies across 195 countries, 45 data points and over 300 million decision makers, with financials and optional credit information, tell me database size but nothing I can act on. We found no public information on email verification, a refresh cadence, or any accuracy or credit-back terms, so the connect rate my team lives on is unverifiable from these pages. 1 2 9
The RevOps Manager
The captured pages give headline counts — 220 million companies across 195 countries, 45 datapoints, a database of over 300 million decision makers — with sources described as public, such as the Chamber of Commerce, and optional credit information. We found no public information on verification methods, refresh cadence, per-country or per-field breakdowns, or any bounce guarantee, so I cannot judge DACH or EU depth from numbers this shape. 1 2 8 9
The Data Protection Officer
Headline counts are public — 220 million companies, a database of over 300 million decision makers, coverage across 195 countries and 45 data points per profile — and company data is said to be drawn from publicly accessible sources such as the trade register. We found no public information on email verification, a refresh cadence or last-verified dates, so accuracy and freshness rest entirely on the vendor's word. 1 2 5 8
The ABM Marketer
The pages state scale — 220 million companies, a database of 300 million decision makers, 45 data points, 195 countries — with company data drawn from public sources such as the trade register. We found no public information on verification method, refresh cadence, per-country coverage figures or any accuracy guarantee, so I cannot judge how fresh the records on my target accounts are. 1 2 9
The DACH Sales Director
The vendor states a database of 220 million companies across 195 countries, 300 million decision-makers and 45 data points, with company data drawn from public registers such as the Handelsregister and optionally enriched with credit information. We found no public information on coverage broken down for Germany, Austria and Switzerland, on email verification, or on any refresh cadence or last-verified date. 1 2 5 9
The Skeptic
Headline counts are public — 220 million companies, a database of more than 300 million decision makers, 45 data points, 195 countries — with data types running to decision-maker contact details, LinkedIn profiles, financials and optional credit information. We found no public information on email verification, a refresh cadence, a last-verified date, or a bounce or credit-back guarantee, so nothing behind those counts can be checked from outside. 1 2 5 8
Data sources & lawful basis
Show reasoningHide 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.
The SDR Team Lead
The trade register and public sources are named, legitimate interest under Article 6(1)(f) is stated as the basis, and the privacy policy addresses the people profiled and names the Dutch supervisory authority. A self-service opt-out is documented, with a stated commitment to delete data on objection and not collect it again — that is the full middle level, but nothing on an Art. 14 notification practice or a published balancing test. 2 3 5 9 10
The RevOps Manager
Source categories are named (public sources, trade register, Chamber of Commerce), legitimate interest under Article 6(1)(f) is stated as the basis, and there is a self-service opt-out page where objecting deletes the record and stops re-collection — the fundamentals are documented. We found no public information on an Article 14 notification practice for the decision-maker contacts or a published balancing test. 3 9 10 5
The Data Protection Officer
The basis for EU records is named — legitimate interest under Article 6(1)(f) — sources are described as public ones such as the Chamber of Commerce, and a self-service opt-out page promises the record is deleted and never collected again. We found no public information on an Article 14 notice to the people added to the decision-maker database or on a published balancing test, which is the gap that concerns me most. 9 2 5 10 3
The ABM Marketer
Source categories are named (public sources, trade register), legitimate interest under Article 6(1)(f) is stated as the basis, and there is a self-service opt-out that deletes the record and stops re-collection, which is more than most. We found no public information on an Article 14 notification practice for the people in the database, a published balancing test, or differentiated handling of EU versus US records. 3 9 10
The DACH Sales Director
Registers are named as the source category, legitimate interest under Article 6(1)(f) is stated as the basis, and the people in the database have a self-service opt-out that deletes their record and stops recollection. We found no public information on an Article 14 notification practice or a published balancing test. 3 5 9 10
The Skeptic
Sources are named as publicly known ones including the trade register, legitimate interest under Article 6(1)(f) is claimed as the basis, and a self-service opt-out exists that deletes the record and stops recollection — an honourable suppression rule. We found no public information on the vendor itself notifying people under Article 14, a published balancing test, or a source and collection date traceable per record. 3 5 8 9 10
Visitor identification & intent signals
Show reasoningHide 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.
The SDR Team Lead
This is the product's core and it is documented in depth: real-time company-level identification, visit history per company, cookieless tracking as an option, IP addresses stated not to be saved, consumer IPs filtered out, and trigger rules on country, size and page visits that hand companies to HubSpot or Salesforce with an owner attached. The vendor recommends obtaining visitor consent before activating the script and names consent or legitimate interest as the bases. We found no public information on a stated position under §25 TDDDG or third-party intent topics from a named source, which keeps it below the top levels. 1 2 3 5 8 11
The RevOps Manager
Company-level reverse-IP identification is thoroughly documented: real-time recognition, page-level visit history, a cookieless tracking option, consumer IPs filtered out, IP addresses stated as not saved, and triggers routing companies to owners in the CRM — plus a recommendation to obtain visitor consent before activating the script. We found no public information on consent-management-platform integration, a statement specific to the German TDDDG consent requirement, or a named third-party intent source, so it stops short of the top band. 2 5 7 8 9
The Data Protection Officer
Identification works by matching visitor IP addresses against a trade-register-backed database, consumer addresses are dropped before a profile is built, IP addresses are said not to be retained, a cookie-free tracking mode is documented, and the vendor recommends obtaining visitor consent before activating the script. We found no public information on a specific §25 TDDDG statement, consent-platform integration, or a named source for third-party intent data. 8 3 2 5 7
The ABM Marketer
This is the core of the product and it is documented in depth: real-time IP-matched company identification with a cookieless option, consumer IPs filtered out before profiling, a stated recommendation to obtain visitor consent before activating the tracking code, and page-level signals pushed to the CRM under trigger rules with a named company owner — the alert reaches the account owner while the visit is warm. We found no public information on a §25 TDDDG position, consent-platform integration, or any third-party intent source; the signals are the customer's own website visits, and IP addresses are stated not to be saved. 2 3 5 8 11
The DACH Sales Director
Real-time IP-based company identification with per-company page history, trigger rules into the CRM, a documented cookie-free tracking option, and a stated position that IP addresses are not stored. The German GDPR page recommends obtaining visitor consent before activating the tracking code, but we found no public information on a specific §25 TDDDG position or consent-management-platform integration, and the intent signals are first-party page visits. 2 5 8 9 11
The Skeptic
Real-time reverse-IP company identification is the core product, documented with visit history, filters on characteristics, size and pages visited, and handover to HubSpot or Salesforce, plus a cookieless tracking option, consumer IPs dropped, and IP addresses stated as not saved. The vendor recommends obtaining visitor consent before activating the script and names both consent and legitimate interest as bases; we found no public position on §25 TDDDG, no consent-management-platform tie-ins, and no third-party intent data with a named source. 2 3 5 8 9
Prospecting workflow & outreach rules
Show reasoningHide 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.
The SDR Team Lead
Persona filters on job title, lead scoring, a decision-maker contact database and outreach automation across email and LinkedIn give my SDRs a working loop, and a help article sets out the user's GDPR obligations around the tracking. We found no public information on a suppression or do-not-contact list, saved searches with alerts, or country-aware flags for German contacts under UWG §7, so the outreach-law risk sits with us rather than in the workflow. 1 2 4 5 9 11
The RevOps Manager
Job-title personas, trigger filters on size and page visits, and automated email and LinkedIn outreach exist, and the help centre tells buyers to record Leadinfo in their processing register and privacy statement — that is genuine guidance, not silence. We found no public information on a suppression or do-not-contact list, saved searches with alerts, or country-aware flagging of consent-required contacts. 1 2 9 11
The Data Protection Officer
Job-title personas and trigger rules allow segmentation, automated LinkedIn and email outreach is sold as an add-on, and the help centre at least instructs customers to record Leadinfo in their processing register and privacy statement, with template texts for informing website visitors. We found no public information on a suppression or do-not-contact list, country-aware flags for German contacts under UWG §7, or do-not-call register checks, so the outreach risk stays with the buyer. 2 1 9 5
The ABM Marketer
There is job-title filtering via personas, trigger rules on country, headcount and page visits, multichannel outreach via email and LinkedIn with automation add-ons, and template texts to help customers inform website visitors. We found no public information on a suppression or do-not-contact list, country-aware handling of German contacts under UWG §7, or opt-outs syncing back to the database — so the outreach compliance risk stays with me, the buyer. 1 2 5 11
The DACH Sales Director
Job-title persona filters, a 300-million decision-maker database, multichannel email and LinkedIn outreach, and export through the service interface are documented, and the vendor instructs buyers to record the processing and offers template texts for informing visitors. We found no public information on suppression or do-not-contact lists, on country-aware flagging of German contacts under UWG §7, or on do-not-call register checks, so the cold-outreach legal risk sits with the customer. 1 2 4 5 9
The Skeptic
The outreach machinery is the focus — automated LinkedIn requests, email, persona filters on job title, trigger rules on country, employee count and page visits — with export through the service interface and GDPR guidance telling users to name the tool in their privacy statement and processing register. We found no public information on a suppression or do-not-contact list, country-aware flagging of German contacts where cold outreach requires consent, or checks against do-not-call registers. 1 2 4 9 11
CRM sync, enrichment & export
Show reasoningHide 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.
The SDR Team Lead
HubSpot and Salesforce are documented to unusual depth — matching on domain, phone and chamber-of-commerce number before creating anything, field mapping, deals, tasks, visit notes and auto-link triggers — plus 67 free CRM integrations and export through the service interface at any time. We found no public information on a documented API or scheduled re-enrichment, and the only post-cancellation statement found is that account data is kept one month after the service ends. 2 3 4 11 12
The RevOps Manager
The HubSpot and Salesforce integrations show real care: field mapping, matching on domain, phone and chamber-of-commerce number before creating anything, linking visitors to existing companies, deals, tasks, visit notes and owner assignment — that is dedup done right. But we found no public information on a documented API, webhook limits, scheduled re-enrichment, or propagation of objections and deletions into synced records; on exit, the terms say data remains the customer's property and can be exported at any time through the service interface, with account data kept one month after cancellation. 2 3 4 11 12
The Data Protection Officer
The HubSpot and Salesforce integrations are documented in real depth — field mapping, duplicate matching on domain, phone and chamber-of-commerce number, owner routing, deals, tasks and visit notes written into existing company records — alongside 67 CRM integrations and export through the service interface. We found no public information on a documented API or on propagating a deletion or objection into records already synced, and that is precisely the moment the customer becomes controller. 11 12 2 4 3
The ABM Marketer
HubSpot and Salesforce are documented in real depth — auto-linking visitors to existing companies, matching on domain, phone and chamber-of-commerce number, field mapping, owner assignment, deals and tasks created from the identified company — alongside 67 free CRM integrations, export at any time through the service interface, and the customer keeping ownership of their data. We found no public information on a documented public API, scheduled re-enrichment, or how deletions and objections propagate back into synced records. 2 4 11 12
The DACH Sales Director
HubSpot and Salesforce integrations are documented in real detail — auto-linking, matching on domain, phone and chamber-of-commerce number, field mapping, deals, tasks and visit notes, with deals and tasks visible back inside the tool — alongside 67 free CRM integrations, real-time sync, export at any time and customer data remaining the customer's property. We found no public information on a documented API with stated limits or on propagation of objections and deletions into synced records. 2 4 11 12
The Skeptic
HubSpot and Salesforce integrations are documented down to field mapping, duplicate matching on domain, phone and chamber-of-commerce number, linking visitors to existing companies, and creating deals and tasks, among 67 free CRM integrations, and data can be exported at any time through the service interface. We found no public information on a documented API with stated limits or credit costs, propagation of objections or deletions into synced records, or exit terms beyond a one-month retention of account data after cancellation. 2 3 4 11 12
European sovereignty
panel opinion
Show reasoningHide 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.
The SDR Team Lead
A named Dutch contracting entity with a Chamber of Commerce number, hosting stated on servers in Ireland with AWS EMEA SARL under a processor agreement containing the latest standard contractual clauses, certifications to ISO/IEC 2700x and BSI C5, and a customer data processing agreement on request. We found no published subprocessor or data-partner list — only team.blue group sharing for marketing statistics and reporting — and the privacy policy permits sharing outside the EEA where safeguards exist without naming those transfers or their basis. 3 4 5 6
The RevOps Manager
Leadinfo B.V. is a Dutch company with a chamber-of-commerce registration, Dutch law and Dutch courts, hosting stated in Ireland on AWS EMEA SARL with ISO/IEC 2700x and BSI C5 certified data centres, and a processor agreement available on request. The captured pages give different signals on transfers — the GDPR pages claim EU-only processing while the privacy policy says personal data may be shared outside the EEA with safeguards in place — and no subprocessor list beyond AWS is published. 3 4 5 6
The Data Protection Officer
Leadinfo B.V. is the named Dutch contracting entity with a chamber-of-commerce number, hosting is placed in Ireland on AWS EMEA SARL under an Article 28 agreement with current standard contractual clauses, Dutch law governs, and the privacy policy acknowledges transfers outside the EEA under appropriate safeguards. We found no public information on a published subprocessor or data-partner list, the privacy policy names no server location while the hosting claim sits on the GDPR marketing page, and sharing of personal data with team.blue group companies for marketing and reporting is disclosed without further detail. 3 5 6 4
The ABM Marketer
Hosting is stated to be in Ireland on AWS EMEA SARL, a European entity in Luxembourg, the vendor is the Dutch Leadinfo B.V. with a chamber-of-commerce number, a data processing agreement is available on request, and the data centres carry ISO/IEC 2700x and BSI C5 certifications. We found no public information on a published subprocessor list beyond AWS and team.blue group sharing, and transfers outside the EEA are acknowledged with safeguards but no named legal basis. 3 5 6
The DACH Sales Director
A Dutch B.V. with a chamber-of-commerce number contracts the service, hosting is stated in Ireland on named AWS EMEA SARL infrastructure under an Article 28 agreement containing the latest standard contractual clauses, ISO 27001 is claimed, and a data processing agreement is available on request. We found no published subprocessor list, the privacy policy acknowledges possible transfers outside the EEA under unspecified appropriate safeguards, and personal data may be shared within the team.blue group. 3 5 6
The Skeptic
The contracting entity is a Dutch company with a chamber-of-commerce number, hosting is stated as Ireland on AWS EMEA SARL under an Article 28 agreement containing the latest standard contractual clauses, ISO 27001 certification is claimed, and a data processing agreement is available on request. The privacy policy itself names no server location, concedes sharing with parties outside the EEA under unspecified appropriate safeguards, and discloses group-wide sharing with team.blue companies; we found no published subprocessor or data-partner list. 3 5 6
Pricing transparency
Show reasoningHide 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.
The SDR Team Lead
The pricing page publishes seat counts per package, addon prices quoted as "Autopilot Starting at € 39/seat" and "Leadbot Business Starting at € 59 /seat", a 14-day free trial without credit card, monthly advance billing, and the fair-pricing rule that repeat visits count once and ISPs are excluded. We found no public information on the prices of the Starter, Scale or Pro tiers themselves or the lead limits behind them, so I cannot compute an annual cost from these pages. 2 4 8
The RevOps Manager
Add-ons are priced plainly — Autopilot from €39 per seat, Leadbot Business from €59 per seat, Liquid content from €39 per month — with seat counts per package (3, 10, unlimited), monthly advance billing, repeat visits counted once, and clear over-limit behaviour where leads keep being collected but stay hidden. We found no public information on the base subscription price for any tier, so an annual invoice cannot be computed from the captured pages; a 14-day free trial without payment details is stated. 2 4 8
The Data Protection Officer
The public pages show addon from-prices — 'Autopilot Starting at € 39/seat', 'Leadbot Business Starting at € 59 /seat', 'Liquid content Starting at € 39 /mo' — plus seat counts per package, a 14-day trial without payment details, monthly advance billing and a counting model that charges unique companies only. We found no public information on the prices of the Starter, Scale and Pro tiers or the lead volumes each includes, so the annual cost is not computable from the captured pages. 2 4 8
The ABM Marketer
Add-ons carry public prices — Autopilot starting at €39/seat, Leadbot Business starting at €59/seat, Liquid content starting at €39/mo — with seat counts per package (3, 10, unlimited), monthly billing in advance, and a 14-day free trial requiring no payment details. We found no base price per package and no statement of how many identified companies each package includes on the captured pages, so I cannot compute the annual cost for my account list. 2 4 5
The DACH Sales Director
The pricing page documents the package ladder by seats (3, 10, unlimited), add-ons quoted as "Starting at € 39/seat" for Autopilot and "Starting at € 59 /seat" for Leadbot Business, monthly advance billing, termination notice, and counting rules such as repeat visits counted once and ISP traffic excluded. We found no public information on the base price of the Starter, Scale or Pro packages, on lead volumes included per tier, or on VAT treatment, so the annual cost is not computable from the captured pages. 2 4
The Skeptic
Public pricing stops at the edges: seat counts per plan (3, 10, unlimited), priced add-ons — Autopilot starting at € 39/seat, Leadbot Business starting at € 59 /seat, Liquid content starting at € 39 /mo — a 14-day trial without payment details, and stated currencies and payment methods, with payments declared non-refundable under the Distance Selling Act. We found no public information on the price of the Starter, Scale or Pro plans themselves, lead limits per tier, overage rates or VAT treatment, so the real annual cost is not computable from these pages. 2 4 8
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?The claim appears on the vendor's GDPR marketing page rather than in the privacy policy (which names no server location), and hosting runs on AWS EMEA SARL, whose parent Amazon Web Services is a US company. |
4/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 |
On request
unverified
Why unverified?The GDPR page also lists an "Auftragsdatenverarbeitung Leadinfo" link in its resources section, but the FAQ itself directs customers to contact Leadinfo for the signed agreement. |
0/1 pts | 5 Report an error |
| Transfer impact assessment |
Not needed, no transfer outside the EU/EEA
unverified
Why unverified?Based only on the GDPR page's hosting claim in Ireland; no separate transfer impact assessment document is published. |
1/1 pts | 5 Report an error |
Questions about Leadinfo
Is Leadinfo European?
Yes. whats-best.ai classifies Leadinfo as EU-Made.
Where does Leadinfo store data?
Leadinfo stores customer data in the EU, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention Ireland as hosting location, per the vendor’s page captured 16 Nov 2026.
Does Leadinfo have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Leadinfo?
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: Leadinfo alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 8 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The GDPR page also lists an "Auftragsdatenverarbeitung Leadinfo" link in its resources section, but the FAQ itself directs customers to contact Leadinfo for the signed agreement.
- Weak sourcing — Transfer impact assessment. Based only on the GDPR page's hosting claim in Ireland; no separate transfer impact assessment document is published.
- Weak sourcing — Hosting location. The claim appears on the vendor's GDPR marketing page rather than in the privacy policy (which names no server location), and hosting runs on AWS EMEA SARL, whose parent Amazon Web Services is a US company.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 4 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.leadinfo.com Checked 16 Nov 2026 Details →
- 2 Pricing page www.leadinfo.com Checked 16 Nov 2026 Details →
- 3 Privacy policy www.leadinfo.com Checked 16 Nov 2026 Details →
- 4 Terms of service www.leadinfo.com Checked 16 Nov 2026 Details →
- 5 Security / trust page www.leadinfo.com Checked 16 Nov 2026 Details →
- 6 Legal notice www.leadinfo.com Checked 16 Nov 2026 Details →
- 7 Visitor identification & intent signals — found from sitemap help.leadinfo.com Checked 16 Nov 2026 Details →
- 8 Visitor identification & intent signals — found from sitemap help.leadinfo.com Checked 16 Nov 2026 Details →
- 9 Prospecting workflow & outreach rules — found from sitemap help.leadinfo.com Checked 16 Nov 2026 Details →
- 10 Prospecting workflow & outreach rules — found from sitemap www.leadinfo.com Checked 16 Nov 2026 Details →
- 11 CRM sync, enrichment & export — found from sitemap help.leadinfo.com Checked 16 Nov 2026 Details →
- 12 CRM sync, enrichment & export — found from sitemap help.leadinfo.com Checked 16 Nov 2026 Details →
- 13 Structured-data backfill: markup only, no text or screenshot www.leadinfo.com Checked 8 Nov 2026 Details →