Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

by ZenLeads Inc. · www.apollo.io

Compare with Lusha → Report an error on this page Is this your product? →

Link to this page

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

Apollo.io at a glance

Vendor
ZenLeads Inc.
Headquarters
Not stated on the vendor’s pages as of 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 22 Sep 2026
Panel verdict
The AI panel rates Apollo.io 2.5/5, the mean of 6 judges. Apollo.io, from ZenLeads Inc. 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

Apollo.io alternatives, European ones first →

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

The panel's verdict

Apollo.io, from ZenLeads Inc. of Covina, California, is a lead-generation platform pairing a database of 240M+ contacts and 30M+ companies — one captured page gives 230M+ — with built-in sequences, visitor identification and Bombora intent data. Its strongest criterion is pricing transparency at a uniform 8: every self-serve tier is public — $0 with 900 credits per seat per year granted monthly, then $49, $79 and $119 per seat per month billed annually — and credit costs per data type are listed. CRM sync and export follows at 6-7. The weakest are data coverage at 3-4 and sovereignty at 3-4: coverage is published only as global figures with no country breakdowns, refresh cadence or last-verified dates, and the terms disclaim any warranty of data accuracy while subscriptions are non-cancelable and nonrefundable. Judges split on data provenance, 4 to 6 — some credit the disclosed contributor model and removal machinery, others the unnamed legal basis for EU records — and on visitor identification, also 4 to 6, where capability meets an undocumented consent position for the tracking script.

Report an error

Speaks for it

  • Every self-serve tier priced publicly — $0, $49, $79 and $119 per seat per month billed annually, with a 3-seat minimum on the top tier — plus credit costs per data type and per API endpoint published.
  • Bidirectional sync with Salesforce, HubSpot and Pipedrive, 200+ integrations, and a documented REST API with rate limits.
  • Exit terms grant a perpetual licence to contact data already incorporated into your own systems.
  • The contributor model is disclosed openly — 2M+ contributors, a removal page backed by a suppression list, and a separate Article 14 Processing Notice.
  • Sign-up is free with no credit card required, on a tier with 900 credits per seat per year, granted monthly.

Report an error

Held against it

  • Coverage is published only as global counts — we found no public information on country or DACH breakdowns, refresh cadence or last-verified dates.
  • The terms disclaim any warranty of data accuracy, and subscriptions are non-cancelable during the term with all payments nonrefundable.
  • We found no public information naming the legal basis for EU records or a balancing test.
  • The contracting entity is US-based ZenLeads Inc., processing stated in the United States and other countries, and we found no public information on EU hosting or where the contact database itself is held.
  • We found no public information on a consent position for the tracking script, on country-aware flagging of German contacts, or on checks against national do-not-call registers.

Report an error

Best for

  • You need to cost a self-serve prospecting stack precisely before committing — every tier price and the per-action credit costs are published up front.
  • Your team runs on Salesforce, HubSpot or Pipedrive and wants bidirectional sync plus a documented REST API for enrichment workflows.
  • You want to test before paying — sign-up is free with no credit card required, on a tier with 900 credits per seat per year, granted monthly.
  • You sell mainly to US website traffic — contact-level identification is offered for US visitors, with third-party intent from Bombora.

Report an error

Avoid if

  • You must evidence database depth for Germany, Austria or Switzerland before buying — the captured pages publish only global counts, with no refresh cadence or last-verified dates.
  • Your privacy sign-off requires a stated legal basis for the EU records you will export — the captured pages name none and summarise no balancing test.
  • Your German data protection review must clear the website tracking script — the pages document no consent position for it, and judges warned that surfacing names and job titles from traffic will not pass a German DPO review.
  • You need refunds or credit-back when data proves inaccurate — subscriptions are non-cancelable during the term and all payments are nonrefundable.

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

Big database, thin accountability: 240M+ contacts and 30M+ companies with seven-step email verification claiming 98% accuracy and phone numbers on offer — though the captured pages give different figures for contact count (230M+ on one, 240M+ on another). No coverage is broken down by country or region so I cannot judge DACH depth, no refresh cadence or last-verified date is stated, and the terms disclaim any warranty of data accuracy with all payments nonrefundable — every bounce is my team's cost, not the vendor's. 5 5 8 4

Report an error

The RevOps Manager

Big headline counts of 240M+ contacts and 30M+ companies with a seven-step email verification process and a stated 98% email accuracy claim, but no coverage broken down by country or region — nothing specific on DACH or the EU — and no refresh cadence or last-verified dates anywhere. Worse for a buyer, the terms expressly disclaim any warranty of accuracy, completeness or currency of the data, so the accuracy claim carries no credit-back behind it. 5 4 1 6

Report an error

The Data Protection Officer

Headline counts are published — the captured pages give different figures for contacts, 230 million and 240 million, alongside 30 million companies — with emails and phone numbers as data types and a described seven-step email verification claiming 98 percent accuracy. We found no public information on coverage broken down by country or region, including DACH or Europe, on a refresh cadence or last-verified dates, or on bounce guarantees or credit-back terms; the terms instead disclaim any warranty of accuracy. The buyer carries the cost of bad records. 5 8 5 4

Report an error

The ABM Marketer

The database publishes headline counts — 240 million contacts and 30 million companies with seven-step email verification at a stated 98 percent accuracy and 65-plus firmographic filters — though the captured pages give different figures for the contact count, 230 million on one page and 240 million on another. I found no public information on coverage by country or region, DACH included, or on a refresh cadence or last-verified date, and the terms state that data accuracy is not warranted and subscriptions are nonrefundable. 5 5 6 8 4

Report an error

The DACH Sales Director

Headline global numbers (240M+ contacts, 30M+ companies), a seven-step email verification claiming 98% accuracy and 65+ filters including firmographics — but coverage is stated only as 'global': I found no public information breaking it down for Germany, Austria or Switzerland, no register-sourced company data and no stated refresh cadence, and the terms disclaim any warranty of data accuracy outright. 5 5 1 4

Report an error

The Skeptic

The pages give total counts — 240M+ contacts and 30M+ companies in one capture, 230M+ in another — with seven-step email verification claimed at 98% and 65+ firmographic filters, but we found no public information on coverage broken down by country, no Europe or DACH figures, and no refresh cadence or last-verified dates. The terms state outright that Apollo does not represent or warrant the accuracy, completeness, currency, reliability or quality of any data, so the homepage accuracy figure carries no contractual backing. 5 5 8 4

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

Provenance is disclosed more honestly than most: a proprietary contributor database fed by 2M+ contributors and by customer-submitted data, local business data from Google Maps, a removal page plus a suppression list so removed records are not re-added, and a separate Article 14 processing notice for people whose data was collected indirectly. But I found no public information naming a legal basis such as legitimate interest for the EU records it sells, no balancing test, and no per-record source or collection date. 3 4 5 5

Report an error

The RevOps Manager

The contributor network of 2M+ data contributors is disclosed as such, there is a self-service removal page with a suppression list so removed people are not re-added, and a separate Article 14 processing notice for indirectly collected data is referenced. But the captured pages never name the legal basis for EU records — no legitimate-interest statement or balancing test — and nothing is traceable to a source or collection date per record. 3 5 5 4

Report an error

The Data Protection Officer

Provenance is partly disclosed: a proprietary contributor database fed by two million contributors and by customer-submitted data that may be redistributed to other customers, with a separate Article 14 processing notice, a self-service removal page, deletion and correction rights, and a suppression list preventing records being re-added. The captured pages name no legal basis such as legitimate interest for EU records, summarise no balancing test, describe no sending practice for the Article 14 notice itself, and state no differentiation between EU and US records — so the controller who exports inherits records whose basis they cannot verify. 3 4 5

Report an error

The ABM Marketer

The contributory network is disclosed as such — two million-plus contributors, and customer-submitted data may be used to grow the Contributor Database that is sold to other customers — alongside a separate Article 14 Processing Notice, a self-service removal page and a suppression list that prevents records being re-added. I found no public information naming the legal basis for EU records, a published balancing test, or EU records being handled differently from US ones; transfers instead lean on Standard Contractual Clauses and the Data Privacy Framework. 3 4 5

Report an error

The DACH Sales Director

The contributory model is disclosed honestly (2M+ contributors feeding the Contributor Database), with an Article 14 Processing Notice, a self-service removal page and a suppression list so records are not re-added. But the captured pages name no legal basis for EU records — I found no Art. 6(1)(f) legitimate-interest statement, no publicised legitimate-interest assessment and no register sources, so the lawful-basis story is half told. 3 4 5 5

Report an error

The Skeptic

The privacy policy discloses the machine honestly: a Contributor Database built from 2M+ contributors and from data customers themselves submit, sold onward for B2B purposes and shared with online advertising partners, with Apollo registered as a business-to-business data broker, a separate Article 14 Processing Notice for people collected indirectly, and a removal page backed by a suppression list that prevents re-adding. An EEA representative and a DPO for the EEA and UK are named. We found no public information naming legitimate interest under Article 6(1)(f) as the basis for EU records, or summarising a balancing test. 3 4 5

Report an error

Visitor identification & intent signals

Show reasoning
How this is scored

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

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

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

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

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

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

Report an error

The SDR Team Lead

The identification machinery is strong: traffic matched against 240M+ contacts and 30M+ companies, contact-level enrichment with names, job titles and verified emails for US contacts, filtering by title, company size and tech stack, Slack and email alerts, intent topics per plan and third-party intent from a named provider, Bombora. On consent I found no public information — nothing on how the script behaves under Germany's consent rule, no cookieless mode and no consent-platform integration documented. 7 7 5 2

Report an error

The RevOps Manager

Account and contact identification against their database with filters by title, company size and tech stack, Slack and email alerts, sequences triggered on criteria, and third-party intent data from a named provider, Bombora. We found no public information on consent handling for the tracking script — no TDDDG position, no cookieless claim, no consent-platform integration — and the pricing page shows contact-level identification for US traffic only, with company identification for US and global. 7 2 5 5

Report an error

The Data Protection Officer

Company-level visitor identification is documented with filters, per-company analytics, alerts and sequences, and third-party intent is sourced from a named provider, Bombora. The same page says traffic is matched against 240 million contacts to surface names, job titles and verified emails — personal data of visitors — and contact-level identification is offered for US traffic; we found no public information on a consent position for the script under the German telemedia tracking law, on cookieless operation, or on consent-platform integration. Until the script's behaviour before consent is documented, this does not survive a review. 7 7 5 2

Report an error

The ABM Marketer

The core of what I need is documented: visitors matched to real companies and enriched against 240 million contacts and 30 million companies, third-party intent from a named source — Bombora — with tiered intent topics, and Slack and email alerts the moment a target account hits a high-intent page, dropping the visitor straight into a sequence. What the pages do not resolve: contact-level identification is US only, core plans cap identified companies at 100 per month unless I buy the inbound add-on, and I found no public information on consent-mode options, cookieless operation, or the vendor's position on consent for the tracking script under Germany's tracking rule. 7 5 2 2 7

Report an error

The DACH Sales Director

Functionally rich: account and even contact-level identification against 240M+ contacts, intent topics per tier, Bombora named as the third-party intent source, Slack and email alerts, and routing into sequences. But I found no public information on a consent position for the tracking script — nothing on §25 TDDDG, cookieless operation or consent mode — and identifying individual names and job titles from website traffic is precisely what a German DPO will reject. 7 2 5 5

Report an error

The Skeptic

The product matches traffic against the full database to surface names, job titles and verified emails — contact identification is listed for US visitors while company identification covers US and global — with intent scoring, a named third-party intent provider in Bombora, Slack and email alerts, and visitors dropped straight into outreach sequences. We found no public information on a consent position for the tracking script under §25 TDDDG, a consent mode, or cookieless operation — the first question a German DPO will ask. 7 7 2 5

Report an error

Prospecting workflow & outreach rules

Show reasoning
How this is scored

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

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

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

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

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

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

Report an error

The SDR Team Lead

The search and outreach core is what my SDRs need: 65+ filters including job changes, new hires and funding rounds, sequences that automatically respect unsubscribe signals, deliverability tooling, and a claim of ready-to-go GDPR, CAN-SPAM and DNC compliance tools. I found no public information on country-aware handling — no flagging of German contacts where cold calls and emails need consent, and no stated checking of numbers against national do-not-call registers. 5 8 1 9

Report an error

The RevOps Manager

Trigger filters for job changes, new hires and funding rounds, built-in opt-out handling so sequences automatically respect unsubscribe signals, and marketing pages claiming tooling for GDPR, CAN-SPAM, DNC and regional regulations. But we found no country-aware flagging of German contacts where cold outreach requires consent, no documented checking against national do-not-call registers, and no support for the Article 14 notice at first contact — the legal risk still sits with my team. 5 8 1 4 1

Report an error

The Data Protection Officer

Advanced filters for job changes, new hires and funding rounds, opt-out handling built into sequences, suppression handled in one platform, and a stated set of GDPR, CAN-SPAM and DNC compliance tools give the buyer real scaffolding; the documented removal workflow even requires the customer to delete retained records or document a legal basis on a 30-day cycle. We found no public information on country-aware flagging of German contacts for cold outreach, on checking numbers against national do-not-call registers, or on outreach opt-outs syncing back to the vendor's database. 1 8 9 5

Report an error

The ABM Marketer

Search runs on 65-plus filters including job changes, new hires and funding rounds with export limits per tier, sequences carry built-in opt-out handling, suppression is part of the platform, and the pages promise tools for GDPR, CAN-SPAM and DNC compliance. I found no public information on country-aware handling — German contacts flagged where cold calls and emails need consent under German unfair-competition law — and no documentation that phone numbers are checked against national do-not-call registers; the DNC mention is a marketing line rather than a described workflow. 5 8 1 2 9

Report an error

The DACH Sales Director

Advanced filters with hiring and funding triggers, built-in opt-out handling in sequences, and a removal workflow with 30-day review and legal-basis documentation. My test is country-aware handling — German contacts flagged where cold calls need consent under UWG §7 — and I found no public information on it, nor on checks against national do-not-call registers; the terms put marketing-law compliance squarely on the buyer. 5 8 9 1 4

Report an error

The Skeptic

Search runs on 65+ filters including job changes, new hires and funding rounds, sequences carry built-in opt-out handling, and the pages claim tooling for GDPR, CAN-SPAM and DNC; the terms put compliance with marketing laws squarely on the customer. We found no public information on country-aware flagging of German contacts under UWG §7, or on numbers being checked against national do-not-call registers — the DNC mention is a slogan, not a documented process. 5 8 1 4

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

Data moves well: bidirectional sync with Salesforce, HubSpot and Pipedrive, enrichment and cleansing of existing records, a documented REST API with credit costs published per endpoint, and exit terms stated plainly — exported contacts keep a perpetual license while my uploaded data may be destroyed at termination. I found no public information on scheduled re-enrichment or automatic propagation when a record changes or a person objects; the removal workflow documented asks my team to review a removal list every 30 days. 5 6 11 4 9

Report an error

The RevOps Manager

Bidirectional sync with Salesforce, HubSpot and Pipedrive, a documented REST API with per-call credit costs published per endpoint, and exit terms I can live with: a perpetual license to contact data already incorporated into our own systems, while data we uploaded may be destroyed on termination. What I could not find: field mapping or deduplication, a scheduled re-enrichment cadence, or any documented propagation of objections and deletions into synced records — exactly the gap that fills my CRM with stale duplicates. 5 11 4 10 2

Report an error

The Data Protection Officer

Bi-directional sync with Salesforce, HubSpot and Pipedrive, 200-plus integrations, enrichment and cleansing of existing records, and a documented REST API with rate limits and credit costs per call are all stated, and exit terms grant a perpetual licence to contact data the customer incorporated into its own systems. We found no public information on objections or corrections propagating into synced records, on scheduled re-enrichment, or on an API versioning policy — and the same exit terms say the vendor may destroy the customer's uploaded data on termination. 5 11 4

Report an error

The ABM Marketer

Bidirectional sync with Salesforce, HubSpot and Pipedrive, contact and account stage sync, waterfall enrichment across third-party providers, and a documented REST API with per-endpoint credit costs and rate-limit behaviour published. Exit terms are stated plainly — a perpetual license to contact data incorporated into my own systems, with uploaded information possibly destroyed at termination — but I found no public information on objections or deletions propagating into synced records or on scheduled re-enrichment. 5 11 4 10

Report an error

The DACH Sales Director

Bi-directional sync with Salesforce, HubSpot and Pipedrive, waterfall enrichment of existing records, a documented REST API with published per-endpoint credit costs and rate limits, and clean exit terms: incorporated contact data carries a perpetual licence after termination while uploaded data may be destroyed. I found no public information on a versioned API with a deprecation policy or per-field change history, and re-enrichment scheduling is described only as refresh 'over time'. 5 11 4 9 1

Report an error

The Skeptic

Bidirectional sync with Salesforce, HubSpot and Pipedrive is stated alongside 200+ integrations and a documented REST API whose documentation publishes credit costs per endpoint, down to a credit per page of search results. Exit terms are plain — a perpetual licence to contact data already incorporated into your own systems, while data you uploaded may be destroyed on termination. We found no public information on scheduled re-enrichment, webhooks, or objections propagating automatically into synced records; the documented removal workflow is a customer-side review every 30 days. 5 11 4 9

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 ZenLeads Inc. of Covina, California, collecting, processing and storing personal information in the United States and other countries, with Lionheart Squared as EEA representative, HelloDPO as UK and EEA data protection officer, standard contractual clauses and Data Privacy Framework participation as the transfer basis, and a subprocessor list published. I found no public information on EU hosting; where the database lives is not stated on the captured pages. 3 4

Report an error

The RevOps Manager

The contracting entity is ZenLeads Inc. in the United States, processing personal information in the US and other countries where its affiliates and subprocessors operate, with an EEA representative named, transfers relying on Standard Contractual Clauses and the EU-US Data Privacy Framework, a DPA available and a subprocessor list published. EU hosting is not stated as standard anywhere on the captured pages, so this is a US-controlled database of EU contact data with transfer paperwork rather than European processing. 3 4

Report an error

The Data Protection Officer

The contracting entity is ZenLeads Inc., a United States company that states it may collect, process, store and transfer personal information in the United States and other countries; an EEA representative, a UK/EEA DPO contact, a data processing agreement, a subprocessor list and transfer bases in standard contractual clauses and the EU-US Data Privacy Framework are documented. No EU hosting option or database location is stated on the captured pages, so once a customer exports a list and becomes controller, the records about EU residents sit with a US controller under a transfer framework rather than in Europe. 3 4

Report an error

The ABM Marketer

The contracting entity is ZenLeads Inc., a United States company that collects, processes, stores and transfers personal information in the United States and other countries, with a published privacy policy, a data processing addendum, an EEA representative in Lionheart Squared and transfers based on Standard Contractual Clauses and the Data Privacy Framework. I found no public information on EU hosting, an EU contracting entity, or where the database itself is hosted. 3 4

Report an error

The DACH Sales Director

The picture is clear and American: ZenLeads Inc. of Covina, California as contracting entity, processing 'in the United States and other countries', transfers under the Data Privacy Framework and SCCs, an Art. 27 EEA representative and a published subprocessor list. That is a US-controller model with a named transfer basis; I found no public information on EU hosting or an EU contracting entity, and residency and DPA confirmation are marked unknown. 3 4

Report an error

The Skeptic

The contracting entity is ZenLeads Inc. of Covina, California, and the privacy policy states Apollo is based in the United States and may collect, process and store personal information there and in other countries where its affiliates, service providers and data partners operate, relying on Standard Contractual Clauses and the EU-US Data Privacy Framework for transfers. Lionheart Squared serves as the Article 27 EEA representative, and a data processing addendum and a subprocessor list are published. We found no public information on EU hosting or on where the contact database itself is held. 3 4

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

I can nearly compute the annual invoice: every self-serve tier priced per seat per month billed annually ($49 / $79 / $119 with a three-seat minimum at the top), credits per data type published (email 1, phone 8, enrichment 1-8, waterfall ranges), credit expiry with no rollover, add-ons at $119 per team per month billed annually, taxes excluded, and API credits documented endpoint by endpoint. Only the international dialer ("varies by region") and unstated overage rates stay opaque — and the no-refund rule on subscriptions is at least published plainly. 2 2 11 4

Report an error

The RevOps Manager

Every self-serve tier priced per seat per month billed annually with credits per data type public — Email 1 credit, Phone number 8 credits, mobile +8 on enrichment — plus credit expiry with no rollover, taxes excluded, add-on prices for the dialer and inbound visitor identification, monthly company-identification caps, and API credit costs per endpoint. What keeps me from computing the full annual invoice: no overage rates, international dialer pricing only as "Varies by region", and no refund rule for inaccurate data — the subscription is expressly non-cancelable and nonrefundable. 2 2 11 4 2

Report an error

The Data Protection Officer

Every self-serve tier is publicly priced per seat per month billed annually with credits per seat per year, credits per data type — one for an email, eight for a phone number, one to eight for enrichment, plus detailed per-endpoint API costs — credit expiry without rollover, seat rules, tax treatment, and visitor-identification volumes per tier and add-on. Two gaps remain: the international dialer is priced only as 'Varies by region', and there is no refund rule for inaccurate data — subscriptions are non-cancelable during the term with all payments nonrefundable. 2 4 11 2

Report an error

The ABM Marketer

Every tier is public — $0, $49, $79 and $119 per seat per month billed annually with credits stated per tier — and credits per data type are published: one credit per email, eight per phone number, one to nine per enrichment depending on mobile, plus per-endpoint API costs and waterfall worst-case ranges. Credit expiry at end of billing cycle with no rollover, the per-seat policy, add-ons at $119 and $639 per team per month billed annually, taxes excluded and nonrefundable terms are all stated; the international dialer "varies by region" and no overage rate is published, so the full annual invoice is close but not fully computable. 2 2 11 4

Report an error

The DACH Sales Director

A buyer can compute the bill: every tier priced ($0 / $49 / $79 / $119 per seat per month billed annually, minimum 3 seats on the top tier), credits per data type (email 1, phone 8, mobile +8 on enrichment, waterfall ranges), credit expiry with no rollover, add-ons ($119 Advanced Dialer, $119–$639 Inbound per team per month billed annually), visitor-identification volumes per tier and per-endpoint API credit costs, with taxes stated as excluded and subscriptions nonrefundable. Overage rates and the regionally variable international dialer stay opaque. 2 2 11 4 2

Report an error

The Skeptic

Every self-serve tier is public — $0 with 900 credits per seat per year granted monthly, $49, $79 and $119 per seat per month billed annually with 30,000, 48,000 and 72,000 credits — and the credit economics are spelled out: an email is 1 credit, a phone number 8, people enrichment 1–9 credits, US dialling 1 credit per 30 seconds, credits expire at the end of the billing cycle and will not roll over, and prices exclude any applicable taxes. The international dialer "Varies by region", we found no public information on overage rates, and subscriptions are stated non-cancelable and nonrefundable — so there is no refund rule for inaccurate data to compute an invoice against. 2 11 4 2

Report an error

European sovereignty — proven facts

0 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 Not determined — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Data processing agreement Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Apollo.io

Is Apollo.io European?

No. whats-best.ai classifies Apollo.io as Rest of world.

Where does Apollo.io store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does Apollo.io have a free plan?

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

What are the best alternatives to Apollo.io?

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: Apollo.io 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 (12)

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

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