Lusha
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Lusha Systems Inc. · www.lusha.com
Compare with Apollo.io → Compare with Cognism → 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.
Lusha at a glance
- Vendor
- Lusha Systems 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
- Starting price
- “Starter $ 37 .45 USD / month Billed yearly 4,800 credits per year” (vendor’s words) source, captured 22 Sep 2026
- Panel verdict
- The AI panel rates Lusha 2.5/5, the mean of 6 judges. Lusha is a B2B lead generation platform selling verified contact data, company-level website visitor identification and CRM enrichment; persona-weighted totals run 5.0 to 5.9. 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
Lusha is a B2B lead generation platform selling verified contact data, company-level website visitor identification and CRM enrichment; persona-weighted totals run 5.0 to 5.9. It scores strongest on CRM sync and export at 6–7, for native Salesforce, HubSpot, Pipedrive, Zoho and Dynamics connectors with published per-CRM export caps, and on data provenance and visitor identification, both at 6. Its weakest criterion is data coverage at 4: the captured pages give different figures for total contacts, 290M+ on some and 515M+ on others, we found no public information on a country or regional breakdown, and none on bounce or credit-back terms. Judges split on sovereignty, 4 to 6: the data protection officer scored 6 for customer data stored in Ireland with EU SCCs, a UK addendum and a published transfer impact assessment, while other scores sit at 4, citing the Delaware contracting entity and transfers to the United States, United Kingdom, Australia and Israel. Prospecting compliance runs 5–6 and pricing transparency 5–6; four tiers are priced publicly and we found no public information on credit costs per data type.
Speaks for it
- Native CRM connectors for Salesforce, HubSpot, Pipedrive, Zoho, Dynamics and more, with documented field mapping, webhooks and published per-CRM export caps
- Company-level visitor identification only, individuals never identified, with 1–100 intent scoring routed to Slack alerts, CRM updates or sequences
- Customer data stored and processed in Ireland, with EU SCCs, the UK addendum, a published transfer impact assessment and an annual government access report
- Public tier pricing — Free at $0 with 40 credits per month and no credit card required, Starter at $37.45 per month billed yearly, Pro at $52.45, Premium at $299.95 — plus visitor identification at 2 credits per unique company per month with return visits and saved companies free
- Named source categories — community contributions, licensed directory partners, public sources — with a trust-centre opt-out, a suppression list and published 2024 request statistics showing deletions honoured
Held against it
- We found no public information on coverage broken down by country or region, or on bounce or credit-back terms for inaccurate records
- The captured pages give different figures for total contacts — 290M+ on some, 515M+ on others — and different accounts of whether data brokers are a source
- We found no public information on credit costs per data type, extra-seat prices or overage rates, so the annual cost of a real team is not computable from public pages
- The contracting entity is a Delaware-formed corporation, and we found no public information on an EU contracting entity, a published subprocessor list, or where the contact database itself is hosted
- Do-not-call screening covers UK TPS/CTPS and US numbers only, on Scale plans only, with the legal basis for outreach and opt-out handling placed on the customer
Best for
- You run outbound through Salesforce or HubSpot and need documented export limits, field mapping and webhook enrichment inside your existing CRM
- You want company-level website visitor identification on a Pro, Premium or Scale plan, metered at 2 credits per unique company per month, and already run a consent management platform
- You need a provenance and transfer story for a DPO review — named source categories, legitimate interest, an opt-out route, SCCs and a published transfer impact assessment
- You can budget from published tier prices without needing per-contact credit costs computed in advance
Avoid if
- You sell mainly into Germany, Austria or Switzerland and need per-country coverage figures — the captured pages show only global totals and give different totals across captures
- You require an EU contracting entity or processing confined to the EU — the contracting entity is a Delaware corporation and the pages name transfers to the United States, United Kingdom, Australia and Israel
- Your outreach compliance depends on German UWG §7 handling or do-not-call screening beyond UK TPS/CTPS and US tables — ask the vendor: the public pages we read do not show it
- You must compute the full annual cost of a multi-rep team before signing — we found no public information on credit costs per data type, extra seats or overage rates, and Scale is contact-sales
The scores
| Criterion | Panel median |
|---|---|
| Coverage, accuracy & freshness | 2 of 5 |
| Data sources & lawful basis | 3 of 5 |
| Visitor identification & intent signals | 3 of 5 |
| Prospecting workflow & outreach rules | 3 of 5 |
| CRM sync, enrichment & export | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3 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
I get counts by data type — 165M+ emails, 117M+ direct dials, 29M+ companies — plus email confidence levels and a last-update date on every phone and email, which is what my reps check before dialing; the captured pages do give different figures for total contacts (290M+ on one capture, 515M+ on later ones), so I take neither as settled. What I cannot find is coverage broken down by country — nothing tells me how deep the German or DACH pool runs — and we found no public information on a bounce or credit-back guarantee. Signals refresh weekly and contact records refresh continuously, which lifts this above bare record counts. 1 5 1 8 1
The RevOps Manager
Big totals with the data types broken out — the captured pages give different figures for verified contacts, 290M+ on some pages and 515M+ on others, plus 165M+ emails and 117M+ direct dials — alongside email confidence tiers, a last-update date on every phone and email, continuous refresh, weekly signal refresh and firmographics down to revenue range and headcount. We found no public information on coverage broken down by country or region, including Europe or DACH, on per-country accuracy methodology, or on credit-back terms when data proves wrong. 1 5 1 8
The Data Protection Officer
Total counts are published by data type — verified contacts, emails, direct dials and companies — with email confidence levels, continuous refresh, weekly signal refresh and a last-update date shown per phone and email. We found no public information on coverage broken down by country or region, so DACH and EU depth cannot be judged, and no bounce or credit-back terms. The captured pages also give different figures for total contacts (290M+ and 515M+). 1 5 1 1 8
The ABM Marketer
Totals are published for companies, emails and direct dials — the captured pages give different figures for total contacts — with confidence levels per email, last-update dates on phones and emails, and continuous refresh plus duplicate merging. What decides it for me is that coverage is never broken down by country or region, so I cannot see how deep this runs in DACH or the wider EU, and I found no public information on bounce or credit-back guarantees. 1 5 1 1
The DACH Sales Director
The totals are big and the hygiene is real — 515 million-plus verified contacts, 165 million-plus emails, 117 million-plus direct dials across 29 million-plus companies, with high/medium/low email confidence and a last-update date shown per phone and email. But I found no country or region breakdown in the captured pages, so I cannot tell a Mittelstand buyer what Lusha actually holds on Germany, Austria or Switzerland, and I found no register-sourced company data or credit-back terms for inaccurate records. 1 5 1 1
The Skeptic
Grand totals everywhere — the captured pages give different figures for total contacts, 290M+ on some and 515M+ on others, alongside 165M+ emails and 117M+ direct dials — and per-record hygiene is better than most: confidence levels per email, last-update dates on phones and emails, continuous refresh, duplicate merging and a CSV error-report route. But we found no public information on coverage by country or region, so there is no German, Austrian or EU figure to check, and no bounce or credit-back guarantee appears on the captured pages — inaccurate contacts go into a report while the credit stays spent. 1 5 1 1 1
Data sources & lawful basis
Show reasoningHide reasoning
How this is scored
Where the personal data in the database comes from and on what legal basis it is processed — as evidenced on the vendor's own pages. Covers Art. 6(1)(f) legitimate interest, the Art. 14 notice to the people in the database, and whether they can find, object to and remove their record.
0 — 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
Source categories are named — community members volunteering email signatures and headers, licensed directory partners, public sources and Google/Microsoft APIs — with legitimate interest stated as the basis, a trust-center opt-out, a suppression list and 2024 request stats showing deletions actually honoured. The contributory community collection is disclosed as such, which I respect. We found no public information on an Article 14 notification practice or a published balancing test, and the pages describe sourcing from trusted data brokers on the privacy notice while the data-quality guide states no data is purchased from third-party brokers — different descriptions I would want clarified before pointing a DPO at it. 3 5 6 9 3
The RevOps Manager
Sources are named by category — community members sharing email signatures, licensed directories, public sources, and a Google or Microsoft API path when users connect email — with legitimate interest stated as the basis, a self-service opt-out via the trust center and a suppression list so opted-out contacts stop appearing. We found no public information on notifying people under Article 14 when they are added, on a published balancing test for the legitimate interest, or on EU records being handled differently from US records; the captured pages also give different accounts of broker sourcing, one naming trusted data brokers and another stating no purchase from third-party data brokers. 3 5 6 9
The Data Protection Officer
Source categories are named in detail — community members sharing email signatures and headers, licensed directory partners, public sources and an in-house inference system — with legitimate interest stated as the basis, a privacy notice, a trust-centre opt-out, a permanent suppression list and published 2024 request statistics showing deletions honoured. We found no public information on an Article 14 notification practice, a published balancing test, or different handling of EU versus US records, and the captured pages give different statements on whether data brokers are a source. Provenance is not traceable per record. 3 5 6 9 3
The ABM Marketer
Source categories are named plainly — community members donating email headers and signature blocks, licensed partner directories, public sources and a machine-learning completion layer — with legitimate interest stated as the legal basis and a trust-centre opt-out feeding a suppression list so opted-out contacts stop appearing. The contributory collection is disclosed as such, but I found no Art. 14 notification practice described and no published balancing test. 6 9 3 5
The DACH Sales Director
The data-sources page names its categories plainly — community members sharing email headers and signature blocks, licensed partner directories, public sources and an insight system — legitimate interest is stated as the basis for the business contacts, and there is a genuine privacy notice for the people in the database plus a self-service opt-out via the trust centre backed by a permanent suppression list. What I did not find is a described Art. 14 notification practice, a published legitimate-interest balancing test, or EU records handled differently from US records. 3 5 6 9
The Skeptic
Source categories are named plainly — community members donating email signatures and headers, licensed directory partners, public-source scans — legitimate interest is the stated basis, and the opt-out is real, with 11,000-plus requests complied with in 2024 behind a suppression list. The privacy notice describes sourcing from trusted data brokers while the data-quality documentation states no data is purchased from third-party brokers; the captured pages give different accounts of this. We found no public balancing test and no described practice of informing people when they are added beyond notice where the law requires it — and the vendor itself states it collects no opt-in consent from the people in those donated signatures. 3 5 6 9 3
Visitor identification & intent signals
Show reasoningHide reasoning
How this is scored
Identifying companies behind website visits and surfacing buying intent — scored on what is identified (company or person), how the tracking works, and whether the vendor states that its script needs consent under §25 TDDDG and how it behaves without it.
0 — No visitor identification or intent data; 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
The pixel matches visitor IPs against 29M+ company profiles, company-level only and never individuals, then scores each company 1–100 into hot, warm or cold from named inputs — sessions, high-intent pages, recency — with paths like /pricing boosting the score and alerts routing to Slack, the CRM record or a sequence. Requiring a consent management platform before the pixel can be installed is a real stated position on consent. We found no public information on a §25 TDDDG position or cookieless operation, so my German DPO still has open questions. 7 8 7 7 8
The RevOps Manager
Company-level identification only, individuals never identified, via a lightweight pixel matching visitor IPs against 29M+ company profiles, with intent scored 1 to 100 from sessions and high-priority pages, page and country exclusions, and hot visits routable to a Slack alert to the owner, a CRM record update or a sequence. The vendor requires a consent management platform with an opt-out before installing the pixel and requires your privacy policy to disclose the tracking, but IP addresses are collected session-based, and we found no public information on a cookieless mode, on the §25 TDDDG position specifically, or on EU traffic being handled differently by design. 7 8 8 8
The Data Protection Officer
Identification is company-level only through an IP-matching pixel, with visit history, a 1-100 intent score banded hot, warm or cold, high-priority pages and routing into Slack alerts, CRM updates and sequences. The vendor requires a consent management platform on the site before the pixel is installed and places legal compliance on the customer, while the pages document that IP address, pages visited, timestamp and referrer are collected. We found no public information on a stated position naming the German Telekommunikation-Digitale-Dienste-Gesetz, cookieless operation, or EU traffic being handled differently by design. 7 8 8 8
The ABM Marketer
The core pitch mostly lands for me: company-level identification only, never individuals, firmographics on every match, an intent score from 1 to 100 banded hot, warm or cold from pages visited, sessions and recency, and routing I can actually use — a Slack alert to the account owner, a CRM update or a sequence that fires the moment a visit is scored. A consent management platform is required before the pixel goes in, but I found no documented cookieless operation and no specific §25 TDDDG position, and the intent is first-party page behaviour only, with no third-party intent source named. 7 7 7 8 8
The DACH Sales Director
Company-level reverse-IP identification is well documented — 29 million-plus profiles matched, visits scored one to a hundred into hot, warm and cold from pages, sessions and recency, high-priority page and country exclusions, and routing into a Slack alert to the owner or a CRM update — and the vendor insists a consent management platform be in place before the pixel is installed. It is a session-based JavaScript cookie rather than cookieless, and the legal framing speaks only of GDPR and CCPA; I found no position on §25 TDDDG and no EU-specific design. 7 8 7 8
The Skeptic
Company-level only with individuals explicitly not identified, and the pixel is documented honestly as a session-based analytics/marketing cookie collecting IP addresses matched to companies, with a hard requirement for a consent management platform before installation and an instruction to disclose the technology in the site privacy policy. Intent scoring is traceable in its inputs — sessions, high-intent pages, days visited, recency, banded cold to hot — with routing to Slack alerts, CRM updates and sequences, and 75%-plus claimed match accuracy where you only pay for successful identifications. We found no public information on cookieless operation or a §25 TDDDG position, and the intent signals come from Lusha's own database rather than a named third-party source. 8 8 7 8
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
I get the filters that matter — surface only contacts with an email, phone or direct dial — plus bulk save and export to CSV or CRM, and the Do Not Call feature hides UK TPS/CTPS and US registered numbers across search, the extension and CSV enrichment, though only on Scale plans. The compliance guidance puts the legal basis, opt-out handling and country calls on me as the customer, and for Switzerland it explicitly tells me to evaluate local requirements myself. We found no public information on country-aware flagging of contacts, for example German contacts under UWG §7, or on screening against German do-not-call registers. 5 9 10 8
The RevOps Manager
Search with data-availability filters, dated signals like funding rounds, hiring surges and job changes, saved companies and CSV or CRM export are documented, plus genuine outreach guidance with country notes for Spain and Switzerland and the buyer told to honour opt-outs. Phone numbers registered on national do-not-call tables are hidden from search, the extension, tables and CSV enrichment, but only for the UK and USA, only when an admin selects those countries, and only on Scale plans. We found no public information on German UWG §7 handling, on technographic search filters, or on outreach opt-outs syncing back into the database. 5 9 10 1
The Data Protection Officer
A Do Not Call feature hides numbers registered on the UK TPS/CTPS and US tables across search, the extension and CSV enrichment — available only on Scale plans — and the help pages give country-specific guidance for Spain and Switzerland plus opt-out guidance. The vendor states plainly that the customer is responsible for the legal basis for outreach and for managing opt-out requests, which are not synced back into the database. We found no public information on German contacts being flagged where UWG §7 requires consent. 9 10 5
The ABM Marketer
Search with availability filters, saved tables and export to CSV or CRM, buying signals covering job changes, funding rounds and hiring surges, and genuinely country-aware pieces: phone numbers on the UK and US do-not-call tables are hidden from search, the extension and CSV enrichment, with country-specific guidance for Spain and Switzerland. But the do-not-call feature sits on Scale plans only, the pages state that customers must manage opt-out requests and the legal basis themselves, and I found nothing on German UWG §7 flagging or per-country channel restrictions. 5 9 10 1
The DACH Sales Director
There is a compliance page that names legitimate interest, instructs customers to run opt-outs, and is refreshingly honest that unsolicited B2B email in Switzerland is not automatically compliant — plus a do-not-call feature screening UK TPS/CTPS and US numbers across search, extension and CSV enrichment. But the legal basis for outreach sits squarely with the customer, the do-not-call tables stop at the UK and US, and I found no German handling under UWG §7 or opt-outs synced back into the database. 9 10 1
The Skeptic
There is a genuine compliance page — customers must establish their own legal basis, manage opt-outs and include opt-out mechanisms, with country notes for Spain and a frank statement that Swiss B2B outreach compliance is not confirmed — plus a do-not-call feature hiding numbers registered on the UK TPS/CTPS and US registries across search, extension, tables and CSV enrichment. But that feature sits on Scale plans only, covers two countries, and we found no public information on UWG §7 flags for German contacts or checks against German do-not-call registers. Suppression of opted-out individuals is vendor-side; managing the buyer's own outreach opt-outs is explicitly the customer's responsibility. 3 9 10
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
Native integrations across Salesforce, HubSpot, Pipedrive, Zoho, Dynamics, Bullhorn and more, with field mapping, webhooks that auto-enrich new HubSpot contacts, and per-CRM export caps spelled out platform by platform — that is the muscle my team lives in daily. API, MCP and CSV export are documented, and the terms say I may keep using the data after termination. We found no public information on bidirectional sync, on opt-outs propagating into records already pushed to my CRM, or on credit costs per API call. 4 11 12 13 11
The RevOps Manager
Native connectors for Salesforce, HubSpot, Pipedrive, Dynamics, Zoho and more with configurable field mapping, webhooks that auto-enrich contacts as they are created, documented per-CRM export caps with resume behaviour, an API with webhooks and MCP, and exit terms I can quote: customers may continue to use the data after termination, configuration is deleted 30 days after cancellation and visitor history after 90 days. Duplicate detection is described for the vendor's own records rather than for CRM sync, and we found no public information on bidirectional sync, scheduled re-enrichment of existing records, or updates, objections and deletions propagating into synced records, while API limits are stated only as strict with no credit cost per call published. 4 11 12 2 11
The Data Protection Officer
Native integrations cover Salesforce, HubSpot, Pipedrive, Zoho, Dynamics and more, with documented field mapping, per-CRM export caps, webhooks and an API with stated strict rate limits. Retention at cancellation is stated plainly — visitor history kept 90 days, configuration deleted after 30 — and the terms permit continued use of exported data after termination. We found no public information on updates or deletions being propagated into synced records when a record changes or a person objects, or on credit costs per API call. 4 11 12 13 11
The ABM Marketer
Native integrations across Salesforce, HubSpot, Pipedrive, Dynamics, Zoho and more with documented field mapping and per-CRM export caps, webhooks that auto-enrich new HubSpot contacts, an API plus MCP access, and exit terms I can live with — the customer may continue using the data after termination and may export it. What keeps this from going higher is that I found no evidence of bidirectional sync or objections propagating into synced records, and the API is described only as having strict rate limits, with no published numbers or per-call credit costs. 11 12 4 13 1
The DACH Sales Director
Native Salesforce, HubSpot, Pipedrive, Dynamics, Zoho and more with documented field mapping and CRM permissions, webhooks that enrich records the moment they are created, and published per-CRM export caps for real-time and background runs; the terms even let the customer keep using the exported data after termination. What I did not find is propagation of objections or deletions into synced records, and API rate limits appear only as "strict" with no numbers or per-call credit costs. 4 11 12 11
The Skeptic
Native integrations across Salesforce, HubSpot, Pipedrive, Zoho, Dynamics, Bullhorn and more, with documented field mapping, documented CRM permissions, webhook enrichment of new records, CSV and API export, and unusually candid per-CRM export caps with resume behavior. Exit terms are stated plainly: the customer may continue using the data after termination. We found no public information on bidirectional sync, propagation of deletions or objections into synced records, numeric API rate limits (described only as strict), credit costs per API call, or a versioning and deprecation policy. 4 11 12 11 1
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
The contracting entity is Lusha Systems Inc., a Delaware corporation in Boston, and customer-provided data is stored and processed in Ireland — but with access by employees in Israel and transfers to the United States, United Kingdom, Australia and Israel, covered by EU SCCs, the UK addendum and a published transfer impact assessment, plus a DPA incorporating SCCs. There is no EU contracting entity and no published subprocessor list, and we found no public information on where the contact database itself is hosted. Ireland storage plus real transfer paperwork is decent for a US/Israel vendor, but it is not sovereignty. 3 13 7
The RevOps Manager
The contracting entity is Lusha Systems Inc., a Delaware corporation, while personal data provided by customers is stated to be stored and processed in Ireland, with EU SCCs and the UK addendum as transfer tools, onward access by employees in Israel disclosed, a data processing agreement incorporating the SCCs, and a published transfer impact assessment dated February 2026. We found no public information on a published subprocessor list, an EU contracting entity or controller, or where the B2B database records people export are themselves hosted; the privacy notice names overseas recipients in the United States, United Kingdom, Australia and Israel. 3 13
The Data Protection Officer
Customer data is stored and processed in Ireland, and non-EU access is named with its legal basis: a Delaware-incorporated contracting entity, access by employees in Israel and by subprocessors, EU standard contractual clauses and the UK transfer addendum, a public transfer impact assessment dated February 2026 and an annual government access report. We found no published subprocessor or data-partner list and no named hosting infrastructure, and the contracting entity and ultimate ownership sit outside the EU. 13 3
The ABM Marketer
The contracting entity is Lusha Systems Inc., a Delaware corporation subject to US law, customer data is stored in Ireland, and non-EU transfers to the United States, United Kingdom, Australia and Israel are named with SCCs, the UK addendum, a DPA and a published transfer impact assessment behind them. That is a real transfer basis rather than silence, but I found no EU contracting entity, no published subprocessor list, and the captured pages do not state where the contact database itself is held. 13 3 6
The DACH Sales Director
The contracting entity is Lusha Systems Inc., a Delaware-formed, Massachusetts-registered corporation in Boston, customer-provided data is stored and processed in Ireland, and transfers run to the United States, United Kingdom, Australia and Israel under the EU SCCs and the UK addendum, backed by a published transfer impact assessment and a DPA incorporating SCCs. That is documented US-jurisdiction processing with Irish storage; I found no EU contracting entity, no named infrastructure and no published subprocessor or data-partner list. 3 6 13
The Skeptic
The contracting entity is Lusha Systems Inc., a Delaware corporation subject to US law, with employees in Israel accessing customer data and overseas recipients named in the US, UK, Australia and Israel — yet the transfer basis is stated rather than skipped: EU standard contractual clauses, the UK addendum, and a published transfer impact assessment built on the EDPB framework. Customer-provided data is stored in Ireland. We found no published subprocessor list, no EU contracting entity, and no statement of where the B2B contact database itself is hosted. 3 13 7
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
Four tiers are priced publicly with credits per tier — Free at $0 with 40 credits per month, Starter at $37.45 per month billed yearly with 4,800 credits per year or $49.9 monthly for 400 credits, Pro at $52.45, Premium at $299.95, Scale on request — and visitor identification budgets cleanly at 2 credits per identified company, once per unique company per month, with return visits and saved companies free. Rollover is described as varying by plan and VAT exclusion shows on the annual offer. What I still cannot compute is the contact side: no credit cost per email versus direct dial versus mobile, no extra-seat price and no overage rate, so the real annual bill for a ten-rep team stays a guess. 8 8 2
The RevOps Manager
Four tiers are priced publicly with credits and billing period per tier — Free at $0 with 40 credits a month and no credit card, Starter at $37.45 per month billed yearly with 4,800 credits a year, Pro at $52.45 and Premium at $299.95 — plus 25% off yearly billing, a stated rollover policy per tier, VAT treatment shown on the structured offer, and visitor identification at 2 credits per unique company per month with return visits, saved companies and bot traffic free. What stops me computing a real annual invoice is that we found no public information on credits per data type such as email versus phone versus mobile, per-seat costs beyond included seats, overage rates or any refund rule for inaccurate data, and Scale pricing is contact sales. 8 8 8 2
The Data Protection Officer
Every tier except Scale carries a public price with billing period and included credits — Free at $0 with 40 credits per month, Starter at $37.45 USD per month billed yearly with 4,800 credits per year, Pro at $52.45 with 7,200, Premium at $299.95 with 40,800 — and visitor identification is priced at 2 credits per unique company per month with return visits and saved companies free, alongside per-plan rollover rules. We found no public information on credit costs per data type such as mobile numbers, per-seat pricing beyond included seats, overage rates or a minimum term, and Scale is a sales conversation. 2 8 2
The ABM Marketer
Four tiers are priced publicly with credits, seats and billing period per tier — Free at $0 USD per month with 40 credits, Starter at $37.45 USD per month billed yearly with 4,800 credits a year, Pro, Premium and a 25% yearly discount — VAT treatment is stated, and visitor identification is metered cleanly at 2 credits per unique company in a given month with return visits and saved companies free. Scale is contact-sales only, credit rollover is only partly described, and I found no public information on credit costs per data type, overage rates, extra seats or minimum term. 2 8 8
The DACH Sales Director
Free, Starter, Pro and Premium are all priced publicly with billing period, yearly credits granted upfront, included seats and a 25 percent yearly discount, website visitors cost 2 credits per unique company with return visits and saved companies free, and VAT is shown as excluded — a buyer can plan a good part of the invoice. But what a credit buys per contact reveal — email versus phone versus mobile — is not stated, Scale pricing is a sales conversation, and rollover is described only in outline, so the annual cost of a real DACH prospecting team is not computable from public pages alone. 2 2 8 2
The Skeptic
Four of five tiers are priced to the cent with billing period, credits per year, upfront grant, a 25% yearly discount and VAT excluded, and the visitor side is fully computable — 2 credits per identified company per month, return visits free, saved companies free forever, bot traffic excluded, in a separate pool with configurable limits. But the number a buyer needs most — what an email, a direct dial or a mobile number costs in credits — we found no public information on, and we found no public price for additional seats or API access, while Scale is contact-sales. Credit rollover appears only as a cryptic table fragment rather than an explained rule. 8 2 8 2
European sovereignty — proven facts
0 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
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | 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 | — | uncited Report an error |
| Transfer impact assessment |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
Questions about Lusha
Is Lusha European?
No. whats-best.ai classifies Lusha as Rest of world.
Where does Lusha store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Lusha have a free plan?
Yes. Lusha has a free plan, per the vendor’s page captured 22 Sep 2026.
What are the best alternatives to Lusha?
As of 18 Nov 2026, the panel rates Dealfront (3/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 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: Lusha 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 — Transfer impact assessment, Legal entity, Hosting location, Open source. Not confirmed on the vendor’s own pages as captured.
- 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.
- 47 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
- 37 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 19 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
- 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
- 7 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
- 5 subprocessors 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 support 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
- 4 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 data 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
- 4 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. 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 (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.lusha.com Checked 16 Nov 2026 +4 earlier captures: 2 Nov 2026, 26 Oct 2026, 19 Oct 2026, 22 Sep 2026 Details →
- 2 Pricing page www.lusha.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 19 Oct 2026, 22 Sep 2026 Details →
- 3 Privacy policy www.lusha.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 4 Terms of service www.lusha.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 5 Coverage, accuracy & freshness — found from sitemap docs.lusha.com Checked 16 Nov 2026 Details →
- 6 Data sources & lawful basis — found from sitemap www.lusha.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 7 Visitor identification & intent signals — found from sitemap www.lusha.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 1 Oct 2026 Details →
- 8 Visitor identification & intent signals — found from sitemap docs.lusha.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 19 Oct 2026 Details →
- 9 Prospecting workflow & outreach rules — found from sitemap docs.lusha.com Checked 16 Nov 2026 Details →
- 10 Prospecting workflow & outreach rules — found from sitemap docs.lusha.com Checked 16 Nov 2026 Details →
- 11 CRM sync, enrichment & export — found from sitemap docs.lusha.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 12 CRM sync, enrichment & export — found from sitemap docs.lusha.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 13 Transfer-impact assessment (TIA) — found from the homepage www.lusha.com Checked 16 Nov 2026 Details →