Hunter
Rest of world Report an errorPanel 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 Hunter Web Services, Inc. · hunter.io
Compare with Snov.io → 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.
Hunter at a glance
- Vendor
- Hunter Web Services, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- In the EU by default; pages mention Belgium source, captured 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 22 Sep 2026
- Starting price
- “Starter Start outreach with essential tools 34€ /month 588€ 408€ billed yearly” (vendor’s words) source, captured 16 Nov 2026
- Panel verdict
- The AI panel rates Hunter 2/5, the mean of 6 judges. Hunter is documented as an email finder, verifier and cold-outreach engine. how scores are made
- As of
- Vendor pages captured 22 Sep 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
Hunter is documented as an email finder, verifier and cold-outreach engine. The bench scores it highest on pricing transparency at 6-7: all four self-serve tiers are public — Free at 0€ with 50 credits per month up to Scale at 209€ /month with 300,000 credits per year — with unlimited users on every plan, a -30% yearly discount and taxes stated as not included. Data coverage clusters at 4: verification is documented check by check, but coverage is stated only as global, on 650M+ public sources (sources, not records), with no public information on country figures or last-verified dates. Visitor identification is the low point at 2: the pages document only database-side buying signals. Prospecting compliance sits at 4; provenance and sovereignty each span 5-6 and CRM sync and export 4-5, the spread reflecting judges crediting the disclosed collection method and Belgian hosting against those weighing the Delaware contracting entity and the unaddressed duty to notify people when added. The captured pricing pages give different figures for the Inbox Protection add-on, from 5.34€ and from 5.40€ a month per email account.
Speaks for it
- All four self-serve tiers priced publicly with credits included, unlimited users on every plan and a -30% yearly discount.
- Email verification documented in full — syntax, domain, MX, SMTP, catch-all and disposable checks with valid, accept-all and invalid statuses — and found emails come pre-verified.
- Collection method disclosed plainly — addresses published on public pages plus pattern generation, robots.txt respected — with a conducted legitimate-interest assessment and DPIA and a self-service claim route to update or delete a profile.
- Native CRM integrations with HubSpot, Zoho, Salesforce and Pipedrive, a Zapier connector, CSV export and a documented REST API whose leads endpoint adds, updates and deletes records.
- Company search filters across 487 industries, headcount, keywords and technologies, with saved ideal-customer-profile searches and weekly auto-suggested prospects.
Held against it
- Visitor identification scored 2, with no public information on a tracking script, reverse-IP identification or a consent position for one.
- No public information on country-level or DACH coverage figures, total record counts, a refresh cadence, per-record last-verified dates or credit-back for bounced addresses.
- No public information on a suppression or do-not-contact list, do-not-call register checks or country-aware handling of German contacts, while the buyer remains an independent controller.
- The contracting entity is Hunter Web Services, Inc. of Delaware under Delaware governing law, with the privacy policy stating personal data may be transferred to providers and third parties in various countries.
- The captured pricing pages give different figures for the Inbox Protection add-on — from 5.34€ and from 5.40€ a month per email account — with no public credit cost per action, overage rate or rollover terms.
Best for
- You want a self-serve email finder and verifier with a free start — the Free tier is 0€ with 50 credits per month and no credit card required.
- Your team builds B2B lists from firmographic and technographic filters and syncs them into HubSpot, Zoho, Salesforce or Pipedrive.
- You send cold email from your own connected Gmail or Outlook accounts and want sequences with A/B testing and inbox warm-up in one platform.
- You want hosting on Google Cloud Platform in Belgium with a published subprocessor list and a self-serve data processing agreement, and can accept a Delaware contracting entity.
Avoid if
- Your core need is knowing which companies visit your own website — the documented platform is an email finder, verifier and outreach engine, and visitor identification scored 2.
- Your reps need to call as well as email — ask the vendor: the public pages we read do not show it
- Your procurement requires a contracting entity and governing law inside the EU — Hunter Web Services, Inc. of Delaware contracts under Delaware law, with an EU representative in Ireland.
- You buy a lead database for a specific market such as DACH and need coverage evidence per country — coverage is stated only as global.
The scores
| Criterion | Panel median |
|---|---|
| Coverage, accuracy & freshness | 2 of 5 |
| Data sources & lawful basis | 3 of 5 |
| Visitor identification & intent signals | 1 of 5 |
| Prospecting workflow & outreach rules | 2 of 5 |
| CRM sync, enrichment & export | 2.5 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 3.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
Verification is properly documented — syntax, domain, MX, SMTP, catch-all and disposable checks with confidence scores — and Discover filters on 487 industries, headcount, keywords and technologies, but coverage is never broken down by country or region and there is no last-verified date per field; the only scale figures are 650M+ public sources and 1.2B+ leads contacted. The privacy policy states the robot does not process personal phone numbers, and we found no public information on direct-dial or mobile data, so my reps can only email out of this database, not call it. 1 3 8 6
The RevOps Manager
Verification is documented properly — syntax, domain, MX, SMTP, catch-all and disposable checks with valid, accept-all and invalid statuses, and found emails come pre-verified — and company search goes beyond name and domain with 487 industries, headcount, keywords and technologies. But coverage is only claimed as global: we found no public information on country-level or DACH coverage, record counts by data type, phone or direct-dial data, a stated refresh cadence, or credit-back terms when data bounces. 8 6 7 3
The Data Protection Officer
The pages document a B2B lead database built on 650M+ public data sources, with 487-industry, headcount, keyword and technology filters, and a verification method broken into syntax, domain, MX, SMTP, catch-all and disposable checks, plus a freshness rule that profiles disappear within 3 months of leaving their public sources. We found no public information on total contact or company record counts, a country or regional coverage split including DACH, per-record last-verified dates, or any credit-back for inaccurate data. Accuracy claims rest on the vendor's own checks with no documented buyer remedy. 1 3 6 8 7
The ABM Marketer
Verification is the strong suit — the captured pages document the full check set (syntax, domain, MX, SMTP, catch-all detection, disposable filtering) with valid/accept-all/invalid statuses, and the firmographic filters run to 487 industries, headcount and technologies. Coverage is stated only as global, and we found no public information on country or DACH-level figures, total contact counts, phone data, or a refresh cadence beyond a rule that profiles drop within three months of leaving their public source pages. 8 6 7 3 1
The DACH Sales Director
The database is billed as global, built from '650M+ public sources', with genuinely detailed email verification (syntax, domain, MX, SMTP, catch-all, disposable filtering) and Discover filters across 487 industries, headcount, keywords and technologies. For my DACH market there is nothing to hold onto: we found no public information on coverage figures for Germany, Austria or Switzerland, on register-sourced company data, on a refresh cadence or last-verified date, or on bounce and credit-back terms. 6 8 1 6
The Skeptic
The verifier is documented in unusual detail — syntax, domain, MX, SMTP, catch-all and disposable checks, three result statuses, spam-trap and honeypot detection — and the company database filters on 487 industries, headcount, keywords and technologies. We found no public information on total record counts, coverage broken down by country, a refresh cadence or last-verified dates, or credit-back terms for bounced addresses; the 650M+ figure counts public sources, not records. 8 6 1 6
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
Sources are named as emails published on public websites plus pattern-generated addresses, a Legitimate Interest Assessment and DPIA are described with summaries available on request, and people in the profiles database get a self-service claim, update and delete route — more cover than most vendors in this category give a buyer. We found no public information on notifying people when they are added, on a published balancing test, or on EU records being handled differently from US ones. 3 4 9
The RevOps Manager
The privacy policy is unusually candid about how the database is built — addresses collected from pages where they were published plus pattern-generated addresses from public sources, robots.txt respected, private consumer data skipped — with a Legitimate Interest Assessment and DPIA said to be conducted and summaries available on request. People in the database get a self-service claim page to update or delete their record, and profiles drop off within three months if they leave the public source. We found no public information on informing people when they are added, or per-record source and collection-date traceability. 3
The Data Protection Officer
The privacy policy discloses collection methods (addresses published on public web pages plus pattern-generated addresses), states that a Legitimate Interest Assessment and DPIA were conducted with summaries available on request, and gives people in the Profiles Database a self-service claim route to update or delete their record, with removal within 3 months. What is not documented is an Article 14 notification actually sent to people when they are added, a per-record source and collection date, or a published balancing test. Good sourcing disclosure and a genuine removal route, but the notification duty is left unaddressed. 3 9
The ABM Marketer
Collection is disclosed concretely — addresses taken from pages where they were published or generated by pattern analysis from public sources, robots.txt respected, private consumer data left unprocessed — with a legitimate-interest assessment and DPIA conducted (summaries on request) and a self-service claim page where people in the database can update or delete their record. We found no public information on an Art. 14 notification practice to the people collected, or per-record source and collection dates. 3 4 9
The DACH Sales Director
The privacy policy names its source categories plainly — addresses published on websites plus pattern-generated addresses from names and organisational affiliations — honours robots.txt, skips private consumer data, and gives people in the database a self-service claim route to update or delete their profile, with removal within three months if the source page disappears. A legitimate-interest assessment and DPIA exist but only as summaries on request, and we found no public information on an Art. 14 notification practice or on EU records being handled differently from US records. The captured pages also characterise the sourcing differently — the policy describes collection and pattern generation from public pages, a guide page calls the data 'permission-based' — and I judge on the policy detail. 3 4 9
The Skeptic
The collection method is disclosed plainly — emails picked up where published on public web pages and pattern-generated from names on public sources, robots.txt respected, private consumer data skipped — alongside a conducted legitimate-interest assessment, a self-service claim route to update or delete a profile, and removal within three months. It stops short of the hard part: we found no public information on per-record source or collection date, the assessment itself is available only on request, and we found no public information on notifying people when they are added. 3 4
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
We found no public information on identifying the companies behind visits to our own website — no tracking script, no reverse-IP lookup, no consent or TDDDG position stated. The pages do show intent-style buying-signal filters and a Signals feature for following target companies and timing outreach, but the source of that intent data is not named. 1 7
The RevOps Manager
There is intent-adjacent material on the database side — filters built on purchase-intent data and a Signals module for following target companies to time outreach — but none of it identifies who is visiting your own website. We found no public information on a tracking script, reverse-IP company identification, or any stated consent position for one. 7 1
The Data Protection Officer
The captured pages show company-level buying signals and intent-data filters inside the lead search, but we found no public information on identifying the companies behind a customer's own website visits, on any reverse-IP tracking script, or on the vendor's position on consent for such a script under the German telemedia rule. With no documented visitor-identification script there is nothing for me to assess on consent-before-tracking. 1 7
The ABM Marketer
For my core need — knowing which of my accounts is in market — the captured pages show only database-side signals: a Signals module with per-plan limits, follow target companies and know when to reach out, intent-data filters, and weekly auto-suggested prospects. We found no public information on identifying companies behind website visits, a tracking script or cookieless mode, a named third-party intent source, or a stated consent position for a script under German law. 1 7 2
The DACH Sales Director
Discover offers filters based on 'Kaufabsichtsdaten' and a Signals module for following target companies and timing outreach, so buying-signal capability is evidenced. But we found no public information on identifying the companies behind website visits, on any tracking script and its consent behaviour, or on a position under §25 TDDDG — the captured pages present an email-finding and outreach platform. 1 7
The Skeptic
The documented platform is an email finder, verifier and outreach engine — its module list contains no website-visitor identification, and we found no public information on a tracking script or any position on consent for one. The only adjacent features are company buying-signal following and intent-data filters in the company database, with no stated source, mechanism or consent basis. 11 1 7
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
Search is genuinely strong — headquarters location, 487 industries, headcount, keyword indexing, similarity search from existing customers, saved ICP criteria with new prospects auto-suggested weekly, plus CSV export and bulk domain search. But we found no public information on a suppression or do-not-contact list, and the compliance story is a marketing claim about transparent, GDPR-compliant sourcing rather than country-aware flagging or guidance wired into the outreach workflow — my German reps get nothing that flags UWG §7 consent requirements. 2 9 1 7
The RevOps Manager
Search and list building are strong: firmographic and technographic filters with a choice of 487 industries, saved ideal-customer-profile searches that keep surfacing matching companies, weekly auto-suggested prospects, saved-lead quotas, CSV export and cold-email sequences. Once the list exists, though, the legal weight sits with the buyer — we found no public information on a suppression or do-not-contact list, do-not-call register checks, or country-aware outreach guidance, only marketing-level claims that the data is GDPR-compliant. 6 7 2 9
The Data Protection Officer
The workflow is real: firmographic and technographic search with saved ideal-customer-profile criteria, weekly auto-suggested prospects, lead lists with CSV export, and email sequences from connected Gmail or Outlook accounts. We found no public information on a suppression or do-not-contact list, on country-aware flagging of German contacts under UWG §7, or on concrete cold-outreach guidance beyond the general claim of helping customers comply with data protection regulations. Once a list is exported the customer is the independent controller, and nothing documented helps them behave like one. 1 4 1 7
The ABM Marketer
Search and outreach are well covered: firmographic, keyword and technographic filters, saved ICP searches with ongoing matching, per-plan saved-lead limits, CSV export, and cold-email sequences through connected Gmail or Outlook accounts with AI writing help. The compliance support documented is a general claim of GDPR-compliant, publicly accessible B2B data; we found no public information on a suppression or do-not-contact list, country-aware flags for German contacts under UWG §7, or checks against do-not-call registers. 6 7 3 9 1
The DACH Sales Director
Filters cover industry, headcount, technologies and keywords, saved leads run to 30 million entries, ICP searches can be saved with ongoing matching, CSV export is confirmed, and sequences send cold email from connected inboxes — solid mechanics. What I need before putting a German rep on this is absent from the pages: we found no public information on a suppression or do-not-contact list, checks against do-not-call registers, or country-aware handling of cold calls and consent under UWG §7; the compliance language is a generic promise to 'help you comply with data protection regulations'. 1 2 6 7
The Skeptic
Search and list building are strong — 487 industries, headcount, keyword and technology filters, saved ideal-customer-profile searches that keep matching companies, weekly auto-suggested prospects, CSV export — and outreach runs cold sequences from your own or managed inboxes. But the buyer is told they "will remain an independent Controller", and we found no public information on a suppression or do-not-contact list, country-aware flags for German contacts, or guidance on cold-outreach consent rules. 7 6 2 1 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 — 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
My team can work out of this: native sync to HubSpot, Zoho, Salesforce and Pipedrive, a Zapier connector to 5,000+ endpoints, a documented RESTful API whose Leads endpoint adds, updates and deletes leads, CSV export, and bulk enrichment. We found no public information on field mapping or deduplication in the CRM sync, on bidirectional re-enrichment, on published API limits or per-call credit costs, or on what happens to exported data after cancellation. 2 4 11 1
The RevOps Manager
Good plumbing: native integrations to HubSpot, Salesforce, Zoho and Pipedrive plus a Zapier connector, a documented RESTful API, and a Leads API that can add, update and delete contacts programmatically, with CSV export on top. But field mapping, deduplication and scheduled re-enrichment are what decide whether my CRM stays clean, and we found no public information on any of them; the terms cover money — upgrade fees non-refundable, cancellation effective at end of period — but say nothing about which data we may keep after the subscription ends. 1 11 2 4
The Data Protection Officer
Native integrations with HubSpot, Zoho, Salesforce and Pipedrive, a Zapier connector, a documented API with add, update and delete on leads, and CSV and Google Sheets export cover the basics, and the terms place Hunter in the processor role for enrichment while the customer remains an independent controller. We found no public information on field mapping or deduplication, on propagation of objections or deletions into synced records, or on which data a customer may keep after cancelling. For an exported contact database, that silence on objection propagation is the gap that concerns me most. 3 4 11 1
The ABM Marketer
Native integrations to HubSpot, Zoho, Salesforce and Pipedrive plus a Zapier connector, a documented REST API with a free tier, a Leads API that adds, updates and deletes contacts in JSON, CSV export, and a Google Sheets add-on that enriches existing sheets with emails, industries and lead data. We found no public information on field mapping or deduplication, bidirectional sync with scheduled re-enrichment, or data-retention rights after cancellation. 1 6 11 10 2
The DACH Sales Director
Native integrations for HubSpot, Zoho, Salesforce and Pipedrive, a Zapier connector, a documented API with v2 endpoints, a leads API supporting add, update and delete, plus CSV and JSON export — that is real connectivity. We found no public information on field mapping or deduplication, scheduled re-enrichment or propagation of deletions into synced systems, published API limits and credit costs per call, or what a customer may keep after cancellation; the terms cover cancellation timing and refund of the unused portion when Hunter terminates, not data retention rights. 4 11 1 7
The Skeptic
Native integrations with HubSpot, Zoho, Salesforce and Pipedrive, a Zapier connector, CSV export, and a documented REST API whose leads endpoint can add, update and delete records, with bulk enrichment aimed at CRMs and pipelines. We found no public information on field mapping or deduplication, bidirectional re-enrichment, stated API rate limits or per-call credit costs, or what happens to data access after cancellation. 1 11 6
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
Hosting is stated as Google Cloud Platform in Belgium with a published subprocessor list and a self-serve data processing agreement, which is decent paper. But the contracting entity is Hunter Web Services, Inc. of Wilmington, Delaware under Delaware governing law, an Irish GDPR representative stands in for the EU, and the privacy policy says personal data may be transferred to providers and third parties in various countries under Standard Contractual Clauses — so the substance is not European end to end. 3 4 5
The RevOps Manager
Hosting is named and European — Google Cloud Platform in Belgium — with a published subprocessor list, a self-serve data processing agreement, and any transfers outside the EEA named with Standard Contractual Clauses and the IDTA as the basis. But the contracting entity is Hunter Web Services, Inc. of Delaware under Delaware governing law, with an Irish representative standing in for GDPR purposes; we found no public information on a transfer impact assessment or a data-partner list. 3 5 4
The Data Protection Officer
Hosting is stated on Google Cloud Platform in Belgium, a subprocessor list is published, and a data processing agreement is self-serve, which is more than many US vendors show. But the contracting entity is Hunter Web Services, Inc. of Delaware under Delaware governing law with an Article 27-style representative in Ireland, and the policy itself says personal data may be transferred to providers and third parties in various countries under Standard Contractual Clauses and the IDTA. A database of EU residents' email addresses therefore rests with a US controller in law even though the servers are European. 3 4 5
The ABM Marketer
Hosting is European and named — Google Cloud Platform in Belgium — with a published subprocessor list, a self-serve data processing agreement, and non-EEA transfers covered by Standard Contractual Clauses and the UK transfer agreement. The contracting entity is Hunter Web Services, Inc. of Delaware, governed by Delaware law with an Irish GDPR representative, so the contracting side sits outside the EU even though the database lives inside it. 5 3 4 10
The DACH Sales Director
Servers sit on Google Cloud in Belgium, a subprocessor list is published, a self-serve data processing agreement is offered, and transfers outside the EEA are named with Standard Contractual Clauses and the IDTA as the basis. But the contracting entity and controller is Hunter Web Services, Inc. of Wilmington, Delaware, under Delaware governing law, with only an EU representative in Ireland — a database of EU business contacts answering to a US controller, which caps it for me. 3 4 5
The Skeptic
Hosting is Google Cloud in Belgium with a published subprocessor list, a self-serve data processing agreement, and SCCs and the IDTA named as the transfer basis for data leaving the EEA and UK. The chain still runs through a Delaware contracting entity under Delaware law with an appointed EU representative in Ireland, and the privacy policy states personal data may be transferred to providers and third parties in various countries. 5 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 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
Almost everything my team needs to budget is public: Free at 0€ with 50 credits per month, Starter at 34€/month with 24,000 credits per year, Growth at 104€/month with 120,000, Scale at 209€/month with 300,000, yearly billing at -30%, unlimited users on all plans, taxes stated as excluded, and add-ons with from-prices — though the captured pages give different figures for Inbox Protection, "From 5.34€/mo" and "From 5.40€/mo" per email account. Credit Pack and overage pricing is not stated publicly and credit rollover is unstated, so the Enterprise tier and anything beyond the listed credits still takes a sales call. 2 4 2 2
The RevOps Manager
Every main plan is priced publicly with credits included: Free at 0€ with monthly credits, Starter at 34€/month with 408€ billed yearly and 24,000 credits per year, Growth at 104€/month with 1,248€ billed yearly and 120,000 credits per year, Scale at 209€/month with 2,508€ billed yearly and 300,000 credits per year, unlimited users on all plans, and prices stated exclusive of taxes. Add-ons carry public prices too, though the captured pages give different figures for Inbox Protection and custom email accounts, 5.34€ and 5.40€ per month per email account. What stops a buyer computing the full annual invoice: the Enterprise tier is custom, credit packs and overage rates show no public price, and rollover is only addressed as credits being available upfront for the whole year. 2 2 2 4
The Data Protection Officer
Every self-serve tier is public with credits included, from Free at 0€ with 50 credits per month up to Scale at 209€ /month with 300,000 credits per year, plus yearly billing at -30%, unlimited users, prepaid annual terms, a stated no-refund policy and VAT exclusion. The captured pages give different figures for the Inbox Protection add-on price, and we found no public information on overage rates, credit rollover or per-call API credit costs, while the Enterprise tier is a sales conversation. A buyer can compute most of the annual invoice from public pages, but not all of it. 2 4 11 2 2
The ABM Marketer
All four self-serve tiers are priced publicly with monthly and yearly billing and credits per tier (Starter 34€/month at 24,000 credits per year up to Scale 209€/month at 300,000), seats are unlimited on every plan, taxes are stated as not included, and refunds are refused on user cancellation. Gaps remain: credit costs are not itemized per action, rollover and overage rates are not stated, the Enterprise tier is talk-to-sales, and the two captured pricing pages give different figures for the Inbox Protection add-on (from 5.34€ and from 5.40€ per month per email account). 2 2 2 4
The DACH Sales Director
Every main tier is public with credits and billing period — Free at 0€ with 50 credits per month, Starter at '34€ /month' with '408€ billed yearly' and 24,000 credits per year, Growth at '104€ /month' with 120,000, Scale at '209€ /month' with 300,000, a 30% yearly discount, unlimited users, taxes stated as not included, and pay-as-you-go credits for API and bulk tasks. Still not computable end to end: we found no public information on credit-pack prices, credit expiry beyond 'available upfront for the whole year', overage rates or refunds for inaccurate data (the terms state upgrade fees are non-refundable), and the captured pricing pages give different figures for the Inbox Protection add-on — from 5.34€/mo and from 5.40€/mo per email account. 1 2 4 2 2
The Skeptic
All four self-serve tiers are priced publicly with credits included per tier, unlimited users on every plan, priced add-ons, VAT treatment stated ("the prices do not include taxes"), and the yearly discount, auto-renewal and non-refundable cancellation terms in the open. What a buyer cannot compute from these pages: the credit cost of a single email, verification or API call, overage rates, credit expiry on monthly plans, and any credit-back for inaccurate data — and the captured pages give different figures for Inbox Protection, from 5.34€ and from 5.40€ a month per email account. 2 2 2 4
European sovereignty — proven facts
2 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 by default
unverified
Why unverified?Hosting is in Belgium but the policy says personal data may be transferred to providers and third parties in various countries, relying on SCCs/IDTA for transfers outside the EEA and UK, so it is not EU-only. |
2/4 pts | 3 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 DPA is only referenced by URL and incorporated by reference; its full text is not reproduced in the excerpts. |
1/1 pts | 4 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Hunter
Is Hunter European?
No. whats-best.ai classifies Hunter as Rest of world.
Where does Hunter store data?
Hunter stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention Belgium as hosting location, per the vendor’s page captured 16 Nov 2026.
Does Hunter have a free plan?
Yes. Hunter has a free plan, per the vendor’s page captured 22 Sep 2026.
What are the best alternatives to Hunter?
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: Hunter alternatives.
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 — Data processing agreement. The DPA is only referenced by URL and incorporated by reference; its full text is not reproduced in the excerpts.
- Weak sourcing — Hosting location. Hosting is in Belgium but the policy says personal data may be transferred to providers and third parties in various countries, relying on SCCs/IDTA for transfers outside the EEA and UK, so it is not EU-only.
- 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.
- 44 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
- 16 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
- 14 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
- 5 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
- 1 compliance 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 support 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage hunter.io Checked 16 Nov 2026 +1 earlier capture: 22 Sep 2026 Details →
- 2 Pricing page hunter.io Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 22 Sep 2026 Details →
- 3 Privacy policy hunter.io Checked 16 Nov 2026 Details →
- 4 Terms of service hunter.io Checked 16 Nov 2026 Details →
- 5 Security / trust page hunter.io Checked 16 Nov 2026 Details →
- 6 Coverage, accuracy & freshness — found from sitemap hunter.io Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 7 Coverage, accuracy & freshness — found from sitemap hunter.io Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 8 Data sources & lawful basis — found from sitemap hunter.io Checked 16 Nov 2026 Details →
- 9 Data sources & lawful basis — found from sitemap hunter.io Checked 16 Nov 2026 Details →
- 10 CRM sync, enrichment & export — found from sitemap hunter.io Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 11 CRM sync, enrichment & export — found from sitemap hunter.io Checked 16 Nov 2026 Details →
- 12 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →