Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 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? →

Link to this page

Dealfront: AI-assisted analysis on whats-best.ai Dealfront: 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.

Dealfront at a glance

Vendor
Dealfront Group GmbH
Headquarters
Not stated on the vendor’s pages as of 16 Nov 2026
Data hosting
In the EU source, captured 16 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 22 Sep 2026
Panel verdict
The AI panel rates Dealfront 3/5, the mean of 6 judges. Dealfront, sold as Leadfeeder, pairs a register-based European company database with reverse-IP website visitor identification, and the bench scores it strongest where those two meet: visitor identification and prospecting compliance both run 6-7, and five of six judges scored visitor identification a 7, citing documented consent mechanics — consent mode, an IP anonymization toggle, opt-out and opt-in methods, CMP integration — and guidance stating that email outreach requires the recipient's explicit double opt-in consent. how scores are made
As of
Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

Dealfront alternatives, European ones first →

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

The panel's verdict

Dealfront, sold as Leadfeeder, pairs a register-based European company database with reverse-IP website visitor identification, and the bench scores it strongest where those two meet: visitor identification and prospecting compliance both run 6-7, and five of six judges scored visitor identification a 7, citing documented consent mechanics — consent mode, an IP anonymization toggle, opt-out and opt-in methods, CMP integration — and guidance stating that email outreach requires the recipient's explicit double opt-in consent. The weakest column is data provenance, spanning 4-6, the lowest scores in the table: sources are named and each contact carries a direct source link, but we found no public statement of the legal basis for contact records, no Article 14 notification practice and no self-service removal route. The judges genuinely split on sovereignty: the German contracting entity, AWS hosting within the EU/EEA and an SCC-based DPA earn the high marks, while we found no published subprocessor list and the privacy page carries a U.S. State Privacy Disclosure. Pricing transparency is capped by paid tiers showing credit volumes only as "Tiered".

Report an error

Speaks for it

  • Visitor identification scores run 6-7, with consent mode, an IP anonymization toggle, opt-out and opt-in methods and CMP integration with CookieHub and OneTrust documented in detail.
  • Company data is drawn from national trade registers and chambers of commerce, and every contact carries a direct public source link for validation.
  • The pages state email outreach requires the recipient's explicit consent (double opt-in), backed by a maintained blocklist, continuous checks against public do-not-call registers in many countries and a Compliance Hub with a Legal Kit.
  • Four tiers are priced publicly — Lite at €0 with 20 credits and up to 100 identified companies a month, Discover starting at €79 per month, Activate at €369 and Scale at €599, each billed annually — with unlimited users and no seat fees on the pricing pages.
  • The contracting entity is Dealfront Group GmbH in Karlsruhe, infrastructure is hosted on AWS within the EU/EEA, and a DPA based on the European Commission's Standard Contractual Clauses accompanies the terms.

Report an error

Held against it

  • Data provenance scores span 4-6, the lowest in the table: we found no public statement of the legal basis for contact records, no Article 14 notification practice and no self-service removal route for the people in the database.
  • We found no published subprocessor list — only an email subscription for updates — and the privacy page carries a U.S. State Privacy Disclosure with no stated non-EU transfer basis.
  • The captured pages give different pictures of enrichment: CRM help pages state enrichment of existing records is not supported, while other pages describe refreshing existing data and enriching uploaded lists.
  • Paid tiers show monthly credits and identified companies only as "Tiered", and we found no credit costs by data type or overage rates, so the annual invoice is not computable from the captured pages.
  • The terms state no DPA for processing Leadfeeder performs for its own purposes, and the captured pages give different figures for users — unlimited on the pricing pages, named user seats per order in the terms.

Report an error

Best for

  • You sell into DACH or wider Europe and want company data rooted in trade registers, with a direct source link on every contact.
  • You need company-level website visitor identification whose consent mechanics are documented in enough detail to put before your DPO.
  • You want to start small: Lite is €0 with 20 credits and up to 100 identified companies a month, and the 14-day trial needs no credit card.
  • Your team needs plain guidance that email outreach requires the recipient's explicit double opt-in consent before it builds sequences.

Report an error

Avoid if

  • You need to enrich records already sitting in your CRM — the captured help pages state only new records can be added, to avoid duplicates.
  • Your outbound motion depends on mobile direct dials — the vendor itself states it will hold fewer personal phone numbers and mobile direct dials than others.
  • You must know the annual invoice before approving spend — the pricing pages show credit volumes only as "Tiered" and quote starting-at figures.
  • You run more than one CRM — only one CRM is supported per account, with a Zapier workaround offered.

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

Sixty million companies and 400 million verified contacts are claimed, with the contact database rooted in Europe at over 89 million contacts and company data drawn from trade registers and chambers of commerce plus firmographics and financials. Emails carry a validation and deliverability indicator and every contact links back to its public source. I found no stated refresh cadence for the contact data, no per-country breakdown and no bounce guarantee — and the vendor itself says it will hold fewer personal phone numbers and mobile direct dials than others, which my dialers will feel. 1 6 1 11

Report an error

The RevOps Manager

Sixty million companies and 400 million verified contacts globally, with 89 million-plus contacts from European companies, and company data drawn from national trade registers and chambers of commerce with a direct source link shown per contact. Coverage is not broken down by country or data type, we found no public information on a documented verification method or refresh cadence beyond a "real-time" claim, and there is no bounce or credit-back guarantee — the terms disclaim responsibility for correctness of results. 1 6 6 7 4

Report an error

The Data Protection Officer

Sixty million companies and four hundred million verified contacts are claimed, with over eighty-nine million contacts explicitly for European companies, drawn from trade registers, chambers of commerce and other public sources, and email validation plus a source link per contact are shown. We found no public information on coverage broken down by country and data type, on a verification method or refresh cadence for the contact data, or on any bounce or credit-back guarantee. 6 1 1 6 11

Report an error

The ABM Marketer

A register-based European database is documented: entries from national trade registers and chambers of commerce enriched with firmographics and financials, 60 million companies and 400 million verified contacts globally, and over 89 million contacts from European companies. Emails come with a validation and deliverability indicator plus a direct source link for verifying contact data, and the CRM feed updates every 24 hours. We found no public information on per-country coverage or accuracy breakdowns, last-verified dates per record, or bounce and credit-back terms, and the vendor itself states it deliberately holds fewer personal phone numbers and mobile direct dials than others. 1 6 6

Report an error

The DACH Sales Director

The company data is drawn from national trade registers and chambers of commerce, each contact detail carries a direct link to its public source, and email validation with a deliverability indicator is shown — the register-based foundation I need for Mittelstand accounts that US databases never see. But I found no public coverage figures for Germany, Austria or Switzerland specifically, only a global 60 million companies and 400 million verified contacts plus over 89 million contacts for the European market, no refresh cadence or last-verified date, and the general terms disclaim responsibility for the completeness and correctness of the results, so inaccuracy stays my cost. 1 6 6 4

Report an error

The Skeptic

Record counts are public — 60 million companies and 400 million verified contacts globally, plus a European contact database of over 89 million — with company data drawn from national trade registers and chambers of commerce, an email validation and deliverability indicator, and firmographics such as industry, revenue and founding year. But coverage is given as totals and a European region rather than by country or data type, the only freshness language is a "real-time global database" claim with no documented verification method or cadence, and the terms state the vendor is not responsible for the completeness or correctness of results; we found no bounce or credit-back terms for inaccurate data. 6 7 1 1 4 6 11

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

Sources are named by category — trade registers, chambers of commerce, business networks, websites and press releases — and each contact carries a direct source link for validation. A comprehensive blocklist is maintained with immediate response to removal requests, records are continuously checked against public do-not-call lists, and a legal opinion on the balancing of interests is available on request. I found no captured statement naming legitimate interest as the legal basis for EU records and no Art. 14 notification practice, so I stop short of the higher marks. 6 1 6 11 11

Report an error

The RevOps Manager

Source categories are named — trade registers, chambers of commerce, business networks, websites, press releases — and the vendor responds to requests with a blocklist while checking records against public do-not-call lists. We found no public statement naming the GDPR legal basis for the contact database, no practice of informing people when added, and the balancing-of-interests opinion is available only on request rather than published. 6 6 11 11

Report an error

The Data Protection Officer

Source categories are named concretely — trade registers, chambers of commerce, business networks, websites and press releases — and each contact carries a direct source link, with a maintained blocklist, immediate response to removal requests and continuous do-not-call checks giving people in the database a route out. We found no public statement naming the legal basis for the contact records, no notification practice for people when they are added, and no self-service removal process; the balancing of interests is offered only as a legal opinion on request. 6 1 6 11 11

Report an error

The ABM Marketer

Source categories are named precisely — official trade-register entries, chambers of commerce, public business networks, websites and press releases — with the direct source offered for validation. The GDPR page publicly frames a balancing-of-interests position ("learn why other vendors fail the test of balancing the interests of data subjects with their mass processing") with a legal opinion available on request, and the vendor says it responds immediately to data-subject requests and maintains a blocklist checked against do-not-call lists. We found no explicit Article 6(1)(f) statement for database records, no Article 14 notification practice, and no self-service removal route for the people in the database. 6 11 11

Report an error

The DACH Sales Director

Sources are named by category — official trade register entries, business networks, websites and press releases — with per-record source links, a blocklist honoured across the dataset, checks against public do-not-call lists, and even a downloadable legal opinion on the balancing of interests. I found no public information on an Art. 14 notification practice for the people in the database or a per-record collection date, which keeps this short of full traceability. 6 6 11 11

Report an error

The Skeptic

Sources are named concretely — official trade register entries, business networks, websites and press releases — and each contact can carry a direct source link for validation, with a maintained blocklist, immediate response to requests, and continuous checks against public do-not-call registers in many countries. What we found no public statement of is the legal basis in so many words: the pages speak of GDPR conformity and offer a legal opinion on the balancing of interests only on request, and we found no Art. 14 notification practice and no self-service opt-out process for the people in the database. 6 11 1 6 11

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

Company-level identification runs on a tracking script with reverse IP lookup, and the consent handling is unusually well documented: consent mode holds the cookie until the visitor agrees while company identification still works, IP anonymization is a toggle, and visitor-level opt-out methods stop all further data transfer. Integration with consent platforms like OneTrust and CookieHub through Google Tag Manager is described. I found no public information on a TDDDG-specific position or a named third-party intent source, and alerts are batched rather than per-visit. 8 10 10 9 13

Report an error

The RevOps Manager

Company-level reverse-IP identification through a tracking script, with individuals identified only when they self-identify via forms or campaign clicks, plus intent scores and ICP fit on every report row. Consent handling is unusually well documented — cookieless identification without consent, consent mode with CookieHub and OneTrust, IP anonymization, optOut()/optIn() methods — but no §25 TDDDG position is stated (the consent question is left to the customer's organization), alerts are batched rather than per visit, and the source of any third-party intent data is not named. 8 10 10 2 9 13

Report an error

The Data Protection Officer

Consent mode, integration with common consent platforms via Google Tag Manager, IP anonymization and opt-out methods that stop every further data transfer are documented in detail. But the vendor recommends not fully blocking the script until consent, states that the company behind a visit is still identified when a visitor declines, and leaves the decision on whether consent is legally required to the customer's organization — the pre-consent operation and the deferred consent question are what a review at my desk would have to challenge. 8 9 10 10 10

Report an error

The ABM Marketer

Identification is company-level by design — reverse-IP lookup, private databases and machine learning reveal B2B companies without form fills, individuals surface only through forms, chat or clicked email links — with visit history, ICP-fit and Intent Score on every report row and workflows triggered by high-intent visits. Consent handling is thoroughly documented: consent mode gates only the cookie while companies are still identified without consent, CMP integration with CookieHub or OneTrust via Google Tag Manager, IP anonymization and per-visitor opt-out methods, though the consent decision is explicitly left to the customer's organization and we found no public information on a §25 TDDDG position. Alerts reach the CRM in about an hour during working hours with user mapping to owners, but the pricing page promises real-time alerts while the integration help states visits are batched and per-visit alerts are not possible, and no third-party source is named for the intent scoring. 8 10 2 13

Report an error

The DACH Sales Director

Identification is company-level by reverse IP, and the consent mechanics are documented in detail: without consent the script sets no cookie yet still identifies the company, IP anonymisation can be switched on, an opt-out method stops all further data transfer, and the tracker slots into OneTrust or CookieHub via Google Tag Manager. The captured pages give different accounts of alert timing — the pricing page advertises real-time alerts while the help centre says visits are sent in batches — and I found no public position naming the German device-access rule; the recommendation not to fully block the script until consent, with the consent question left to my organisation, is something I would put before our DPO before signing. 8 10 10 9 13 2

Report an error

The Skeptic

The script and reverse-IP company identification are documented, including an honest refusal to promise an identification percentage, and the consent handling is the most detailed in this category: consent mode where the cookie is set only after consent, company identification continuing cookieless without consent, an IP anonymization toggle, opt-out and opt-in methods with their exact cookie behavior, and CMP integration with named platforms. Intent exists as ICP fit and Intent Score from the customer's own visit data with workflow triggers; we found no statement naming §25 TDDDG, no design treating EU traffic differently, and individual persons are resolved only via form fills or campaign clicks in connected tools. 8 9 10 10 10 1 2 10

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

Search runs on 100+ filters including department, position and hierarchy, with AI-built prospect lists and CSV/Excel export, and the vendor maintains a blocklist checked continuously against public do-not-call lists in many countries. The German pages state plainly that email outreach requires the recipient's explicit consent (double opt-in), which is exactly the guidance my team needs for DACH. I found no country-aware flagging of individual contacts or per-country channel restrictions built into the workflow itself. 1 6 6 11

Report an error

The RevOps Manager

Search runs on 100+ filters including department, position and hierarchy, lists can be imported and exported, and compliance is genuinely in the workflow: the German documentation states email outreach requires the recipient's explicit consent, and the vendor maintains a blocklist while continuously checking phone records against public do-not-call registers in many countries. We found no public information on outreach channels being flagged per country per contact, opt-outs from outreach syncing back into the database, or support for the Art. 14 notice at first contact. 11 6 6 1 6

Report an error

The Data Protection Officer

Search with one hundred plus filters, department- and position-level contact search, list import and CSV or Excel export are documented, and the vendor states email outreach is only allowed with the recipient's explicit consent while continuously checking records against public do-not-call lists in many countries. We found no country-aware flagging of contacts in the workflow and no suppression list shared across a customer's exports. 1 6 11 11

Report an error

The ABM Marketer

Search covers department, position, hierarchy and company across 100+ advanced filters, company lists can be imported and results exported to CSV or Excel. The compliance help is genuine: a note that email outreach requires the recipient's explicit double opt-in consent, a vendor-maintained blocklist, and continuous checks of records against public do-not-call lists in many countries. We found no public information on country-aware flags on individual contacts inside the workflow, and opt-out handling appears to run through the vendor's blocklist rather than syncing from the buyer's own outreach. 6 11 1

Report an error

The DACH Sales Director

Search runs on 100-plus filters with department, position and hierarchy, lists import and export to CSV or Excel, and the German guidance states plainly that email outreach is only allowed with the recipient's explicit consent — a strict reading of UWG §7 I can hand straight to my team. A unified blocklist plus continuous checks against public do-not-call lists in many countries, and a Compliance Hub with a Legal Kit, go well beyond a generic GDPR disclaimer. I found no public information on per-country flags on the contact record itself or suppression shared across every export, so part of the guardrail lives in documentation rather than in the workflow. 1 6 6 11 11

Report an error

The Skeptic

Search with 100+ filters, department and position targeting, list import and CSV/Excel export are documented, and the compliance side goes beyond boilerplate: the pages state email outreach requires the recipient's explicit consent (double opt-in), records are continuously checked against public do-not-call registers in many countries, and objections are met with a dataset-wide blocklist, backed by a Legal Kit, a Compliance Hub and a balancing-of-interests legal opinion. We found no public information on per-country flagging of contacts inside the workflow, a buyer-managed suppression list shared across exports, or support for the Article 14 notice at first contact. 6 11 1 2 6 11

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

Native integrations cover Salesforce, HubSpot, Pipedrive, Dynamics and Zoho with field mapping, daily company matching within ten minutes for new companies, and a published cost of one credit per record pushed to the CRM with free re-push for twelve months; data already received stays in the CRM after disconnect. The catch for my team: the vendor states enrichment of existing CRM records is not yet supported — only new records can be created — though a separate Datacare upload can enrich and sync lists, and only one CRM is supported per account. 13 1 7 13

Report an error

The RevOps Manager

Native integrations with Salesforce, HubSpot, Pipedrive, Dynamics and Zoho, open field mapping, contact sync, daily matching plus a documented API and MCP server; a record pushed to the CRM costs 1 credit with free re-pushes within 12 months, and data already received into the CRM stays there if the connection is removed. The problem for anyone who owns the CRM: the integration help pages state enrichment of existing records is not possible and only new records can be added to avoid duplicates, while other pages describe enriching uploaded lists through the Datacare workflow — the captured pages give different pictures of enrichment — and we found no public information on objections propagating into synced records or per-field change history. 13 12 7 13 11 2

Report an error

The Data Protection Officer

Native integrations with Salesforce, HubSpot, Pipedrive, Dynamics and Zoho with field mapping and daily sync, a documented API, one credit per record transferred with free re-push within twelve months, and a plain statement that data already received into the CRM stays there after the connection ends are all on the pages. The captured pages give different accounts of enriching existing CRM records, and we found no public information on propagation of objections or deletions into synced records, or on API limits. 7 12 13 13 4 11

Report an error

The ABM Marketer

Native integrations cover Salesforce, HubSpot, Pipedrive, MS Dynamics and Zoho with contact field mappings, automatic user mapping, company matching within ten minutes for new companies, CSV/Excel export, and an API surface including IP ranges and IP enrich APIs plus an MCP server, at one credit per record transferred. The captured pages give different pictures on enrichment: the CRM integration help states enrichment of existing CRM records is not yet supported and only new records can be added, while the GDPR page says existing data can be refreshed and a separate DataCare flow enriches uploaded lists with up to 20 attributes. Sync is outbound and scheduled — daily, visits landing about an hour after processing during working hours, one CRM per account — and we found no public information on bidirectional propagation of updates or objections, or on API rate limits. 1 12 13 7

Report an error

The DACH Sales Director

Native integrations cover Salesforce, HubSpot, Pipedrive, MS Dynamics and Zoho, with field mapping, a daily sync plus matching within ten minutes for newly identified companies, and API and MCP access; each record transfer to the CRM costs 1 credit with a free re-push inside 12 months, and data already in the CRM stays there when the connection ends. The captured pages give different accounts of enriching existing records — the CRM help centre says enrichment is not yet supported, while the compliance page speaks of refreshing existing data and enriching records with public source URLs — and only one CRM per account is supported, with no published API rate limits. 1 13 13 11 7

Report an error

The Skeptic

Native integrations with Salesforce, HubSpot, Pipedrive, Dynamics and Zoho include configurable field mappings, contact sync, a daily sync plus ten-minute matching for newly identified companies, and a documented API family including IP and MCP endpoints, with one credit per record pushed to a CRM and a free re-push within twelve months. The help pages state enrichment of existing CRM records is not supported and only new records are added to avoid duplicates, while other captured pages describe refreshing existing data and a separate list-enrichment product — and we found no propagation of updates or objections into synced records, no stated API limits, and no exit terms beyond received data staying in the CRM after disconnection. 7 12 13 13 1 2 4

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 contracting entity is Dealfront Group GmbH with affiliates including Dealfront Germany GmbH and Dealfront Finland Oy, with a Karlsruhe address and German VAT ID shown, infrastructure hosted in AWS within the EU/EEA, and a data processing agreement based on the Commission's Standard Contractual Clauses accompanying the terms. An email subscription for updates on subprocessors used is offered. I found no published subprocessor list in the captures and no non-EU transfer named with its basis, which keeps this short of the top marks. 4 5 11 5 3

Report an error

The RevOps Manager

Contracting is with Dealfront Group GmbH in Karlsruhe with affiliates in Germany and Finland, hosting is stated on AWS within the EU/EEA, ISO 27001/27701 and encryption are published, and a data processing agreement based on the Commission's standard contractual clauses accompanies the terms. We found no public information on a published subprocessor or data-partner list or on any non-EU transfer basis, and the terms state that outside the customer-facing services Leadfeeder processes personal data for its own purposes and enters no DPA for it — which places the exported database records outside the agreement. 4 5 11 3 5

Report an error

The Data Protection Officer

Dealfront Group GmbH in Karlsruhe is the contracting entity, infrastructure is stated as AWS within the EU/EEA, a data processing agreement based on the Commission's standard contractual clauses accompanies the terms, and ISO 27001 and 27701-based programs are described. We found no published subprocessor list — only an email subscription for updates — and the privacy page carries a U.S. State Privacy Disclosure, so a fully European processing chain for exported records is not evidenced. 5 3 4 5

Report an error

The ABM Marketer

Infrastructure is documented as hosted on AWS within the EU/EEA and built and hosted in the EU, with Dealfront Group GmbH in Karlsruhe as contracting entity alongside Dealfront Germany GmbH and Dealfront Finland Oy, and a data processing agreement based on the European Commission's Standard Contractual Clauses accompanies the general terms. Formal agreements including data processing agreements with all subprocessors are stated and an email subscription for subprocessor updates exists, but we found no published subprocessor or data-partner list. The privacy pages carry US-facing features such as "Do Not Sell or Share My Personal Information", and we found no public information naming a non-EU transfer basis for those flows. 5 4 11

Report an error

The DACH Sales Director

The contracting entity is Dealfront Group GmbH in Karlsruhe with a German VAT number, alongside Dealfront Finland Oy; infrastructure is hosted in AWS within the EU/EEA; the DPA follows the European Commission's Standard Contractual Clauses; and ISO 27001 and 27701 are published. Two things hold it back: the captured pages show no published subprocessor list, only agreements in place and an update subscription, and the general terms state no DPA for processing Leadfeeder performs for its own purposes — which is where the contact records I would export sit. 11 4 5 5 11 3

Report an error

The Skeptic

The contracting entity is Dealfront Group GmbH, named in the terms, with a Karlsruhe address and a German VAT number, infrastructure is stated as AWS within the EU/EEA with encryption at rest and in transit and ISO 27001/27701-based programs, and a data processing agreement based on the European Commission's Standard Contractual Clauses accompanies the terms. The vendor says DPAs are in place with all subprocessors and offers email updates on subprocessor changes, but we found no published list of subprocessor names, and the privacy page carries a Do Not Sell or Share option pointing to US-related practices without a named non-EU transfer and its basis. 11 5 3 4 5 11

Report an error

Pricing transparency

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

Four tiers are public — Lite at €0, Discover from €79, Activate from €369 and Scale from €599 per month billed annually — with unlimited users on every plan, VAT treatment stated as excluded, unused credits expiring at term end, and one credit per CRM record transfer published. But the credits included in each paid tier are shown only as "Tiered", and I found no per-data-type credit costs for emails, phones or mobiles, so I cannot compute what a dialing-heavy team of eight actually pays. 2 2 4 13 2

Report an error

The RevOps Manager

Four tiers are priced publicly — Lite at €0, Discover starting at €79 per month, Activate at €369, Scale at €599, all billed annually — with credit expiry at term end, VAT treatment, billing terms and a 5% renewal cap in the terms. The paid tiers' credit volumes appear only as "Tiered", we found no public information on credit costs per data type, overage rates or API pricing, and the pricing pages promise unlimited users while the terms speak of named user seats up to the number in the order — the captured pages give different pictures on seats. 2 2 4 13

Report an error

The Data Protection Officer

Four plans are priced publicly with the billing period, VAT treatment and the thirty percent annual saving stated, credits expire at the end of each term, the free tier's twenty credits and the one-credit cost of a CRM record transfer are shown, and users are unlimited on every plan. But paid-tier credit volumes appear only as tiered, the prices are starting-at figures, and we found no public credit costs per data type or overage rates, so the real annual invoice is not computable from the pages alone. 2 13 2 4

Report an error

The ABM Marketer

All self-serve tiers are priced publicly — Lite at €0, Discover from €79 per month billed annually, Activate from €369, Scale from €599, Enterprise on request — with VAT treatment, annual-up-front billing, credit expiry at the end of each term, a 5% cap on renewal increases and 30-day cancellation notice stated. Some unit costs are public: company identification consumes no credits, a record transferred to the CRM costs one credit with a free re-push within 12 months, and AI enrichment is paid with credits. But the paid tiers show only "tiered" for monthly credits and identified companies, so the annual invoice is not computable; we found no published overage rates or credit costs per data type, and the pricing pages promise unlimited users with no seat fees while the terms speak of named user seats per order. 2 2 4 13

Report an error

The DACH Sales Director

Lite is €0 with 20 credits a month and the last 100 identified companies; Discover starts at €79 per month, Activate at €369 and Scale at €599, all billed annually, with unlimited users and no seat fees, credits expiring at the end of each term, annual upfront invoicing, a 30-day cancellation notice and prices quoted excluding statutory VAT. What blocks a clean annual calculation: the paid tiers show credit volumes and identified-company limits only as "Tiered" with no numbers, and I found no public credit costs split by data type such as email versus mobile number. 2 2 2 4 13

Report an error

The Skeptic

Four tiers are priced publicly — a free tier with 20 credits and up to 100 identified companies a month, Discover starting at €79 per month, Activate at €369 and Scale at €599, each billed annually, Enterprise on request — with unlimited users and no seat fees on every plan, credits expiring at the end of each term, prices in EUR or USD excluding VAT, annual billing up front, and one credit per record pushed to a CRM with a free re-push within twelve months. The gaps are the ones a buyer needs closed: the paid tiers show "Tiered" rather than a number for credits and identified companies, and we found no credit costs by data type such as mobile numbers and no overage rates — only that overuse can result in additional charges. 2 13 2 2 4

Report an error

European sovereignty — proven facts

2 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 only unverified
Why unverified?

The statement gives the infrastructure location but no subprocessor list is included in the excerpts, and a U.S. State Privacy Disclosure on the privacy page suggests some US-related data practices.

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 Published, self-serve unverified
Why unverified?

The GTC points to the DPA via a link and says it accompanies the terms, but the excerpts do not include the agreement text itself.

1/1 pts 4 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Dealfront

Is Dealfront European?

Yes. whats-best.ai classifies Dealfront as EU-Made.

Where does Dealfront store data?

Dealfront stores customer data in the EU, per the vendor’s page captured 16 Nov 2026.

Does Dealfront have a free plan?

Yes. Dealfront has a free plan, per the vendor’s page captured 22 Sep 2026.

What are the best alternatives to Dealfront?

As of 18 Nov 2026, the panel rates Lusha (2.5/5), Vainu (2.5/5) and Apollo.io (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 Vainu (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Dealfront 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 (13)

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

  1. 1 Vendor homepage www.leadfeeder.com Checked 16 Nov 2026 +4 earlier captures: 2 Nov 2026, 26 Oct 2026, 19 Oct 2026, 22 Sep 2026 Details →
  2. 2 Pricing page www.leadfeeder.com Checked 16 Nov 2026 +3 earlier captures: 2 Nov 2026, 19 Oct 2026, 22 Sep 2026 Details →
  3. 3 Privacy policy www.leadfeeder.com Checked 16 Nov 2026 +3 earlier captures: 2 Nov 2026, 19 Oct 2026, 22 Sep 2026 Details →
  4. 4 Terms of service www.leadfeeder.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  5. 5 Security / trust page www.leadfeeder.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 30 Sep 2026 Details →
  6. 6 Coverage, accuracy & freshness — found from sitemap www.leadfeeder.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
  7. 7 Coverage, accuracy & freshness — found from sitemap help.leadfeeder.com Checked 16 Nov 2026 Details →
  8. 8 Visitor identification & intent signals — found from sitemap help.leadfeeder.com Checked 16 Nov 2026 Details →
  9. 9 Visitor identification & intent signals — found from sitemap help.leadfeeder.com Checked 16 Nov 2026 Details →
  10. 10 Prospecting workflow & outreach rules — found from sitemap help.leadfeeder.com Checked 16 Nov 2026 +3 earlier captures: 2 Nov 2026, 26 Oct 2026, 1 Oct 2026 Details →
  11. 11 Prospecting workflow & outreach rules — found from sitemap www.leadfeeder.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  12. 12 CRM sync, enrichment & export — found from sitemap help.leadfeeder.com Checked 16 Nov 2026 Details →
  13. 13 CRM sync, enrichment & export — found from sitemap help.leadfeeder.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →