Lead Generation
Dealfront
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Dealfront Group GmbH · www.leadfeeder.com
Compare with Leadinfo → Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Leadfeeder, sold by Dealfront Group GmbH, is a B2B lead generation and sales intelligence product pairing a database of 60 million companies and 400 million verified contacts — built on national trade registers, chambers of commerce and other public sources — with company-level visitor identification. It scored strongest on CRM sync and export, 4 to 6, on native integrations with Salesforce, HubSpot, Pipedrive, Dynamics and Zoho plus API and MCP access; visitor identification held 3 to 4 and pricing transparency 4 to 5, with prices public from a €0 Lite plan to €599 per month, billed annually, and a 5%-per-year renewal cap. Data provenance was weakest at 2 to 3, with five of six judges at 2: we found no public information on the legal basis for the contact records, notice to the people listed, or a removal route. Sovereignty clustered at 4 — a German contracting entity and a built-and-hosted-in-EU claim, with subprocessor disclosure limited to an email subscription for updates — and the data processing agreement covers only processing on the customer's behalf, leaving the vendor's database records outside it.
Speaks for it
- Native integrations with Salesforce, HubSpot, Pipedrive, MS Dynamics and Zoho, plus API and MCP server access with automatic CRM data updates and enrichment on the higher tiers.
- Company-level visitor identification with a clean unit — a unique company per month, repeat visits counted once — that consumes no credits.
- Company data rests on named sources — national trade registers, chambers of commerce and other public sources — enriched with firmographics and financials.
- Public tier pricing — Lite at €0, then starting at €79, €369 and €599 per month, billed annually, with custom enterprise volumes — and a 5%-per-year cap on renewal increases.
- The contracting entity is Dealfront Group GmbH with German and Finnish affiliates, and the homepage claims built and hosted in the EU.
Held against it
- We found no public information on a legal basis for the 400 million contact records, on a notice to the people listed, or on a route for them to object or be removed — the only opt-out surface shown is a "Do Not Sell or Share" link on the cookies page.
- The data processing agreement covers only processing on the customer's behalf, and the vendor's own processing of its database records sits outside it.
- Subprocessor disclosure is limited to an email subscription for updates, with the independently assessed data residency, ownership and subprocessor-exposure attributes unknown.
- Paid-plan credit allowances read only "tiered", with no public information on credit costs per data type, credit expiry, overage rates or API pricing, and the captured pages give different figures for seats — unlimited users on the pricing page, named seats per order in the terms.
- We found no public information on the tracking script's consent position under the German TDDDG, on a cookieless or consent-mode option, or on suppression lists, do-not-call checks and cold-outreach guidance for the main EU markets.
Best for
- You want company-level visitor identification — intent filters, visit history and real-time alerts on target accounts — reaching your reps while interest is warm.
- Your sales team works in Salesforce, HubSpot, Pipedrive, MS Dynamics or Zoho and wants automatic CRM updates and enrichment plus API and MCP access instead of manual exports.
- You sell on European register-based firmographics and a German contracting entity with a built-and-hosted-in-EU claim matters to your procurement.
- You want to start free — the Lite plan at €0 with up to 100 identified companies a month, 20 credits, unlimited users and 7 days of history, plus a 14-day full-access trial without a credit card.
Avoid if
- You must document a lawful basis and an opt-out route for every contact your team emails — the terms state the vendor enters no data processing agreement for its own database processing.
- Your procurement needs a published subprocessor list before signature — the pages offer an email subscription for updates, and the assessed residency, ownership and subprocessor-exposure attributes came back unknown.
- You need a computable annual invoice before committing — credit allowances for paid plans are shown only as "tiered", and seats read differently on the pricing page (unlimited users) and in the terms (named seats per order).
- You expect the vendor to carry part of your outreach-compliance load — the terms' use restrictions cover internal use and publishing results, not what you may lawfully send to the contacts you export.
The scores
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 — No stated coverage, no refresh cadence, no verification method; accuracy asserted as a percentage with nothing behind it.
3 — Headline record counts for the whole database, thin or unstated European coverage, and no description of how often records are re-verified.
5 — Coverage stated per country or region including DACH, email verification described, a stated refresh cadence, and firmographics beyond name and domain.
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
The homepage gives me headline counts — 60 million companies and 400 million verified contacts — and it does say the company data comes from national trade registers and chambers of commerce. But we found no public information on per-country or DACH coverage, the verification method behind the "verified contacts" figure, any refresh cadence, or any bounce or credit-back guarantee — so I'm judging on a count, not on connect rate. 1 2
The RevOps Manager
Sixty million companies and four hundred million verified contacts is a headline count, not coverage documentation: no per-country or DACH breakdown, no refresh cadence, and nothing behind the "verified" label. Register and chambers-of-commerce sourcing plus firmographic and financial enrichment is a real plus, but I found no public information on verification method, last-verified dates or any bounce guarantee. 1 2
The Data Protection Officer
Headline counts of 60M companies and 400M verified contacts sit next to a real sourcing story — national trade registers and chambers of commerce, enriched with firmographics and financials — but we found no public information on per-country or DACH coverage, on how often records are re-verified, on the verification method, or on any credit-back terms for inaccurate data. 1
The ABM Marketer
Sixty million companies and four hundred million verified contacts is a headline number, and the company side is built on national trade registers and chambers of commerce enriched with firmographics and financials — that reads genuinely European. But I found no public information on per-country coverage breakdowns, how often contact records are re-verified, what sits behind the "verified" label, or any credit-back terms when data turns out wrong. Good enough to trust the firmographics on my three hundred accounts; the contact accuracy is an assertion. 1
The DACH Sales Director
Global headline totals — 60 million companies and 400 million verified contacts — sit alongside company data that explicitly rests on national trade registers and chambers of commerce, enriched with firmographics and financials, which is exactly the register basis my Mittelstand buyers want. But I found no public information on coverage broken out for Germany, Austria and Switzerland, on how the verified contacts are verified, or on a refresh cadence, so 'verified' and 'real-time' rest on assertion. 1
The Skeptic
The homepage leads with 60 million companies and 400 million verified contacts and names trade registers and chambers of commerce as the base, but we found no public information on per-country coverage, refresh cadence, or the verification method behind 'verified'. 'Real-time database' is the only freshness language on the pages, and it is an adjective, not a cadence. 1
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 — No statement of where contact data comes from or on what legal basis; "GDPR-compliant" asserted without explanation, and no way for a listed person to object.
3 — Sources described in general terms ("public sources", "partners"), legitimate interest named without any balancing, and an opt-out request form as the only route for data subjects.
5 — Source categories named (registers, company websites, contributory networks, licensed partners), legitimate interest stated as the basis for EU records, a dedicated privacy notice for 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
Company data sources are named — trade registers, chambers of commerce, public sources — but we found no public information on the legal basis for the 400 million contact records, any notice to the people listed, or a route for them to object or be removed; the only data-subject-facing option visible is a cookie "Do Not Sell" link. The data processing agreement covers only processing done on my behalf, and the terms state the vendor does not enter one for its own database processing, which is exactly the data my reps would be emailing. 1 3 4
The RevOps Manager
Sources are described only in general terms (trade registers, chambers of commerce, other public sources) and the basis rests on the "GDPR Compliant Built & Hosted in EU" assertion. I found no public information on a legitimate-interest basis, a notice to the people in the database, or a route for a listed person to object and be removed; the only opt-out shown is a do-not-sell choice in the cookie section. 1 3
The Data Protection Officer
Sources are named in general terms — trade registers, chambers of commerce, other public sources — which is more than nothing, but we found no public information on the legal basis for the 400M contacts, no Art. 14 notification practice, and no removal or objection route for the people in the database; "GDPR Compliant" is asserted on the homepage without explanation. 1 3
The ABM Marketer
Sources for the company data are named concretely — trade registers, chambers of commerce, other public sources — but I found no public information on where the contact records come from, on legitimate interest or any other legal basis for holding them, or on any route for a person in the database to find and remove their record. "GDPR Compliant Built & Hosted in EU" is asserted with nothing behind it, and the only opt-out surface I can see is a US-style do-not-sell option on the cookies page. 1 3
The DACH Sales Director
Source categories are named better than most — trade registers, chambers of commerce, other publicly available sources — but I found no public information on the legal basis for the contact database, on an Article 14 notice to the people listed, or on a way for a listed person to object to or remove their record; the terms even state that no data processing agreement covers the processing Leadfeeder performs for its own purposes. A bare 'GDPR Compliant' badge on the homepage is not a lawful basis I can defend to a customer. 1 3 4
The Skeptic
Source categories are named concretely — national trade registers, chambers of commerce, other public sources — which is better than 'public sources' boilerplate. But we found no public information on the legitimate-interest basis for EU contact records, any notice to the people in the database, or a route for a listed person to object or be removed, and the GDPR-compliant banner carries no explanation. 1 3
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, or person-level identification of EU visitors with no statement of legal basis.
3 — Reverse-IP company identification with a cookie-setting script, no statement about consent, and match rates claimed without method.
5 — Company-level identification with filters, visit history per company, a stated position that the script requires consent where it sets cookies, and a consent-mode or cookieless option.
8 — Company-level only for EU traffic by design, cookieless operation documented, integration with common consent management platforms, 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
Company-level identification is the core of the product — monthly identified-company limits with a clear per-company definition, visit history, real-time account alerts, and intent-signal filters — which is what my reps need to strike accounts already showing interest. But we found no public information on a cookieless or consent-mode option, or any statement about the tracking script's consent position where it sets cookies. 2 3
The RevOps Manager
Company-level identification is cleanly defined (a unique company per month, repeat visits counted once) with visit history by plan, high-intent triggers and alerts. But I found no public information on the consent position for the tracking script, on a cookieless or consent-mode option, or on where the intent signals come from. 2 3
The Data Protection Officer
Company-level visitor identification is the product's core — unique companies per month, real-time alerts, workflows triggered by high-intent visits — but we found no public information on a consent position under §25 TDDDG, no cookieless or consent-mode option, and nothing on how EU visitor traffic is treated; the privacy page shows a "Do Not Sell or Share My Personal Information" link and nothing on the tracking script's behaviour before consent. 2 3
The ABM Marketer
Company-level identification is the heart of this product and the pieces I need are there: intent and firmographic filters, per-company visit history, real-time alerts on accounts, and workflows that trigger when high-intent companies land on the site and push straight into the CRM. What I found no public information on is how the tracking actually works — reverse IP, cookies, cookieless — or any statement on consent under the German tracking rules, and the intent signals carry no named third-party source. The signal reaches my account owners while it is warm; the legal mechanics of collecting it are undocumented on these pages. 1 2 3
The DACH Sales Director
Company-level identification is described concretely — unique companies per month with repeat visits counted once, visit history, real-time account alerts, intent filters, and identification that consumes no credits. But I found no public information on the tracking script's consent position under the German TDDDG, on a cookieless or consent-mode option, or on the source of the third-party intent signals, which is the first thing a client's data protection officer will ask me. 1 2 3
The Skeptic
Identification is company-level with a clean unit definition — a unique company per month, repeat visits counted once — plus visit history, intent-signal filters and account alerts. But we found no public information on the tracking script's consent position under the German cookie rule, or on a cookieless or consent-mode option; the privacy page shows only a California-style 'Do Not Sell or Share' link. 2 3
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 — A search box and an export button; nothing on the pages about what the buyer may lawfully do with the contacts.
3 — Filters on firmographics and job title, saved lists, and a terms clause making the customer solely responsible for compliance.
5 — Advanced filters including technographics and triggers, company-level lists and alerts, a global suppression or do-not-contact list, and guidance on cold outreach rules in the main EU markets.
8 — The above plus country-aware handling (for example flagging German contacts where cold calls and emails require consent), 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
The 100+ firmographic and intent filters plus lists and workflow alerts get my team to the right buyer at the right company fast. But we found no public information on a global do-not-contact or suppression list, guidance on cold outreach rules in the main EU markets, or do-not-call register checks — the terms only restrict using or publishing results outside my own organization. 1 3 4
The RevOps Manager
Search and list-building are strong: a hundred-plus filters, intent filters, lists, real-time alerts and AI prospect lists. The compliance side is empty though — I found no public information on a suppression or do-not-contact list, country-aware handling of German contacts, or outreach guidance, and the terms only restrict use to the customer's own organization. 1 2 4
The Data Protection Officer
The funnel is well tooled — 100+ advanced filters, firmographic and intent audiences, a Lists module, export and sync actions — but we found no public information on a suppression or do-not-contact list, no guidance on cold outreach rules in any market, and the terms restrict use to the buyer's own organisation while saying nothing about what the buyer may lawfully send to the contacts it exports. 1 3 4
The ABM Marketer
The search side is real — a hundred-plus filters, firmographic and intent audiences, company lists and real-time alerts — and the terms restrict use to my own organisation. But I found no public information on a global suppression or do-not-contact list, on phone numbers being screened against national do-not-call registers, or on any guidance for cold-email and cold-call consent rules in Germany and the other main EU markets. The outreach risk stays entirely on my side of the table. 1 3 4
The DACH Sales Director
Filtering and list-building are genuinely strong — over 100 advanced filters, firmographic and intent filters, AI-built prospect lists, saved lists and workflows — but the legal side is left with the buyer: I found no public information on cold-outreach guidance for the German or other EU markets, on a suppression or do-not-contact list, on checks against do-not-call registers, or on country-aware flagging where a cold call needs prior consent. The only use restriction in the terms concerns internal use and publishing results, which is a licensing matter, not compliance help under UWG §7. 1 2 3 4
The Skeptic
The search side is real — 100+ filters, firmographic and intent audiences, lists, alerts and automations — but on the compliance side we found no public information on a suppression or do-not-contact list, guidance on cold outreach rules in the main EU markets, or checks against do-not-call registers. The terms restrict results to internal use and require consent for publication, which governs the vendor's data, not the buyer's legal risk. 1 2 4
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 — Manual CSV export only; no CRM integration and no API.
3 — A one-way push to one CRM, CSV export, and no statement on whether exported data may be kept after cancellation.
5 — Native sync with the major CRMs including field mapping and deduplication, enrichment of existing CRM records, and a documented API with stated limits.
8 — Bidirectional sync with scheduled re-enrichment, update and deletion propagated when a record changes or a person objects, webhook or API access with 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
Native integrations with Salesforce, HubSpot, Pipedrive, MS Dynamics and Zoho, automatic CRM data updates and enrichment workflows, plus API and MCP server access — that is the muscle I need to keep eight reps' pipelines fed without manual CSVs. We found no public information on field mapping and deduplication, API limits or per-call credit costs, or what happens to exported data and my access to it when the subscription ends. 1 2 3 4
The RevOps Manager
Native integrations with Salesforce, HubSpot, Pipedrive, Dynamics and Zoho, automatic CRM enrichment that keeps CRM data updated, and API and MCP access: that is more than a one-way push. But I found no public information on field mapping or deduplication, no documented API limits, and nothing on what exported data the customer may keep after cancellation — the only exit detail shown is automatic renewal with thirty days' notice. 1 2 3 4
The Data Protection Officer
Native integrations with Salesforce, HubSpot, Pipedrive, MS Dynamics and Zoho, automatic CRM data updates and enrichment, plus API and MCP server access, put this past a one-way push; we found no public information on field mapping or deduplication, API limits, propagation of deletions or objections, or what may be kept with the exported contacts after cancellation. 1 2 3 4
The ABM Marketer
Salesforce, HubSpot, Pipedrive, Dynamics and Zoho are native, the Scale plan carries unlimited exports and automatic CRM updates, workflows push to the CRM, and there is API and MCP access — my accounts reach the systems sales actually works in. I found no public information on field mapping, deduplication, API rate limits or credit costs per call, and nothing on whether exported records may be kept after cancellation or how an objection by a contact would propagate back. Delivery into the CRM is well documented; the exit and propagation questions are not answered on these pages. 1 2 3 4
The DACH Sales Director
Integrations cover the majors — Salesforce, HubSpot, Pipedrive, Dynamics, Zoho — plus automatic CRM updates and enrichment on Scale, API access, an MCP server, a browser plugin and LinkedIn audience sync. But I found no public information on field mapping or deduplication, on API rate limits or credit costs per call, or on whether exported contacts may be kept after cancellation. 1 2 4
The Skeptic
Native integrations with five major CRMs, automatic CRM data updates and enrichment on the higher tiers, and API plus MCP access are all stated on the pages. We found no public information on field mapping, deduplication, API limits or credit costs per call, and nothing on what happens to synced or exported records when the subscription ends. 1 2
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 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and EU residents' contact data processed outside the EU with no stated transfer basis.
3 — Non-EU contracting entity with an EU representative under Art. 27, or EU hosting offered while enrichment, support or AI processing stay non-EU.
5 — EU contracting entity and EU hosting as standard, but parts of the chain — data partners, enrichment sources, tracking infrastructure — are non-EU without an explained safeguard.
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
The contracting entity is Dealfront Group GmbH in Germany and the homepage claims built and hosted in the EU — the right starting point for a database of EU residents. But we found no public information on the hosting infrastructure, or on which subprocessors and data partners see the data — the only thing published is an email signup for subprocessor updates — and the data processing agreement expressly covers only processing on the customer's behalf, leaving the database records my team exports outside its scope. 1 3 4
The RevOps Manager
The contracting entities are German and Finnish, the homepage claims built and hosted in the EU, and a data processing agreement exists — but it covers only processing done on the customer's behalf, not the vendor's own database processing. No subprocessor or data partner is named beyond an email subscription for updates, and the independently collected sovereignty attributes mark data residency, ownership and subprocessor exposure as unknown. 1 3 4
The Data Protection Officer
A German contracting entity — Dealfront Group GmbH with German and Finnish affiliates — and the "Built & Hosted in EU" claim give a European core, but no subprocessor or data-partner list is published, only an email subscription for updates, and the data processing agreement expressly excludes the vendor's own processing, so the database records a customer exports are not covered by it. 1 3 4
The ABM Marketer
The contracting entity is Dealfront Group GmbH in Germany with a Finnish affiliate, and the vendor states the product is built and hosted in the EU — the fundamentals are European, which matters when the product is personal data about people who never chose the vendor. But I found no public information on the named hosting infrastructure or a published subprocessor and data-partner list — only an email subscription for subprocessor updates — and the data processing agreement is explicitly limited to processing on the customer's behalf, leaving the database records themselves outside its scope. European entity and claimed European hosting, with the transparency a DPO would want yet to be published. 1 3 4
The DACH Sales Director
Contracting with a German entity — Dealfront Group GmbH, with Dealfront Germany GmbH and Dealfront Finland Oy as affiliates — plus a homepage claim of built and hosted in the EU is the right starting point for a DACH buyer. But hosting is a marketing assertion with no named infrastructure, the only subprocessor disclosure is an email subscription for updates rather than a published list, and the independent checks found residency, ownership and subprocessor exposure unverifiable; the data processing agreement also excludes the processing done for Leadfeeder's own purposes, which is the contact database itself. 1 3 4
The Skeptic
The terms name Dealfront Group GmbH as the contracting entity and the homepage claims built and hosted in the EU, but we found no public information on hosting infrastructure or the subprocessor and data-partner list — the only disclosure is an email subscription for updates. The data processing agreement explicitly excludes the vendor's own processing of its database records, and the independently assessed attributes for data residency, ownership and subprocessor exposure all came back unknown. 1 3 4
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 monthly headline exists, but what a credit buys, whether credits expire, or the cost of an additional seat is unstated — the invoice is unknowable.
5 — Tier prices public with credit allowances given, but at least one commonly needed piece (mobile numbers, extra seats, API access, CRM sync) is unpriced or behind a sales call.
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
All four tiers are public — €0 Lite, €79, €369 and €599 per month billed annually, with a 14-day no-card trial, VAT excluded, annual-upfront payment terms and a 5% renewal cap in the terms. But paid-tier credit allowances appear only as "tiered", and we found no public information on credit costs per data type such as email versus mobile, credit expiry or overage — so I cannot price a quarter of prospecting for eight reps; the captured pages also give different signals on seats, with unlimited users on the plan page and named seats per order in the terms. 2 4
The RevOps Manager
Tier starting prices are public (€0, €79, €369 and €599 per month billed annually) with VAT treatment, upfront annual billing and the five-percent renewal cap stated. But credit allowances for paid tiers are given only as "tiered", and I found no public information on per-data-type credit costs, credit expiry, overage rates or API pricing. The captured pages also give different pictures on seats — unlimited users on every plan on the pricing page, named user seats per order in the terms. 2 4
The Data Protection Officer
Tier prices are public — Lite free at €0, then "Starting at €79 Per month, billed annually" up to €599 — with unlimited users on the pricing page, billing terms, VAT treatment and a 5% annual renewal cap stated; but credit allowances for the paid tiers read only "Tiered", and we found no public information on credit costs per data type, credit expiry, overage rates or API pricing, so the annual invoice is not computable. 2 4
The ABM Marketer
Four tiers are public with exact figures — Lite at €0, Discover "Starting at €79 Per month, billed annually", Activate "Starting at €369 Per month, billed annually", Scale "Starting at €599 Per month, billed annually" — plus unlimited users on all plans, VAT stated as excluded, and a 5% cap on renewal increases. But credits are the billing unit and I found no public information on how many credits an email, a phone number or a mobile costs, the paid plans show only "Tiered" credit allowances with no numbers, and credit expiry, overage rates and API pricing are all unstated. The headline is clear; the real annual invoice is not computable. 2 4
The DACH Sales Director
Tiers are public — a free Lite plan, then €79, €369 and €599 per month on annual billing — with VAT treatment, payment terms and a 5%-per-year renewal cap stated, and company identification consuming no credits. But paid-plan credit allowances are shown only as 'tiered', the pricing page lists unlimited users while the terms grant seats 'up to the number indicated in the Order', and I found no public information on credit costs per email, phone or mobile number, on credit expiry or rollover, or on overage rates — so the annual invoice is not computable from public pages. 2 4
The Skeptic
Five tiers are priced publicly with per-plan limits on identified companies, credits, users and history, VAT treatment and payment terms are stated, and renewal increases are capped at 5% a year. But we found no public information on what a credit costs per data type — email versus mobile — on credit expiry or rollover, on overage rates or on API pricing, and the captured pages give different figures for user seats: unlimited users on the pricing page, named seats per order in the terms. 2 4
European sovereignty — proven facts
2 of 4 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 ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | EU only ⚠ unverified | 3/3 pts | 5 Report an error |
| Subprocessors | US CLOUD Act reach ⚠ unverified | 0/2 pts | 5 Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Data residency. The EU/EEA hosting statement sits in security-page marketing copy rather than a contractual clause, and the infrastructure runs on AWS, a US-headquartered provider.
- Weak sourcing — Subprocessors. The page limits AWS to the EU/EEA area, but AWS is a US-headquartered provider and so may still be subject to the US CLOUD Act, and the excerpts name no other product subprocessors (the GDPR page references a subprocessor list without names).
- 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.
- 14 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
- 10 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
- 5 legal 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 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
- 1 integrations 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
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. 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.leadfeeder.com Checked 22 Sep 2026 Details →
- 2 Pricing page www.leadfeeder.com Checked 22 Sep 2026 Details →
- 3 Privacy policy www.leadfeeder.com Checked 22 Sep 2026 Details →
- 4 Terms of service www.leadfeeder.com Checked 22 Sep 2026 Details →
- 5 Security / trust page www.leadfeeder.com Checked 30 Sep 2026 Details →
- 6 Coverage, accuracy & freshness — found from sitemap www.leadfeeder.com Checked 1 Oct 2026 Details →
- 7 Coverage, accuracy & freshness — found from sitemap help.leadfeeder.com Checked 1 Oct 2026 Details →
- 8 Visitor identification & intent signals — found from sitemap help.leadfeeder.com Checked 1 Oct 2026 Details →
- 9 Visitor identification & intent signals — found from sitemap help.leadfeeder.com Checked 1 Oct 2026 Details →
- 10 Prospecting workflow & outreach rules — found from sitemap help.leadfeeder.com Checked 1 Oct 2026 Details →
- 11 Prospecting workflow & outreach rules — found from sitemap www.leadfeeder.com Checked 1 Oct 2026 Details →
- 12 CRM sync, enrichment & export — found from sitemap help.leadfeeder.com Checked 1 Oct 2026 Details →
- 13 CRM sync, enrichment & export — found from sitemap help.leadfeeder.com Checked 1 Oct 2026 Details →