eucsoft

Lusha

Sales intelligence · lusha.com · last read 2026-11-09

At a glance

Is Lusha GDPR compliant?
No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Lusha itself publishes, each answer linked to its source and the date we read it.
Does Lusha have a data processing agreement (DPA)?
Yes. Lusha publishes a data processing agreement at lusha.com. It gives 10 days' notice before a new subprocessor is added. It commits to telling you of a personal data breach within 72 hours. Source and date
Does Lusha have a SOC 2 report?
Lusha states SOC 2 Type 2 on its own page, but does not say there how to get a report. In Lusha's words: “SOC 2 Type II -Independently audited for security, availability, confidentiality and privacy controls.” We read this on 2026-11-09. Source and date
Is Lusha ISO 27001 certified?
Lusha states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. We read this on 2026-11-09. Source and date
How does Lusha transfer personal data out of the EU?
Lusha's agreement relies on the EU standard contractual clauses and the UK transfer addendum. Source and date
Who are Lusha's subprocessors?
Lusha lists 27 third-party subprocessors; 0 of them name at least one processing country outside the EEA. We last read the list on 2026-11-09. Source and date
How do you report a security vulnerability to Lusha?
Lusha publishes a security.txt at www.lusha.com naming [email protected]. Source and date

The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.

Identity

Legal entityLusha Systems Inc.
HQ—
Parent company—
Ultimate ownership—
EU contracting entity—
LEI—
US CLOUD Act reachNot determined from the sources read
Sourcelusha.com · 2026-11-09

Data location

No data-location observation recorded yet.

The same question for every vendor: where SaaS vendors store EU data.

Lusha's subprocessor list names AWS, Google and Oracle for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.

Subprocessor chain

27 third parties · 0 with a country outside the EEA · all read 2026-11-09

SubprocessorCountryPurpose
Amazon Web Services, Inc.IEHosting
Amplitude, Inc.DEUser Analytics and Sessions User Recording
Braze, Inc.DEMarketing CRM
Clari, Inc.DEVideo Recording and Sales Forecast
Coralogix Ltd.DELog Analytics Platform.
DocuSign, Inc.DEElectronic Signature
Google LLC (rebranded as Google Workspace)IECloud Computing Collaboration Tool
Intercom, Inc.IECommunication chat
IPQualityScore, LLCDEFraud Detection
Ironclad, Inc.DEContract Maangment Software
Kickbox, Inc.IECustomer Email Validation
Mailgun Technologies, Inc.DECustomer Email Validation
Mailjet SASFREmail Service
MongoDB, Inc.DEMaintaining Billing data
Optimizely, Inc.DEA/B Testing Service
Oracle CorporationDEDatabase Management
Oracle NetSuite Global Business UnitDEEnterprise Software
Outreach CorporationDESales execution platforms and workflow tools for sales teams
Reblaze Technologies Ltd.NLSecurity
Rivery.io Ltd.DEData Integration
Salesforce.com, Inc.IESales CRM
Slack Technologies, LLCIEInternal Instant messaging
Survicate Sp. z o.o.DECustomer Feedback
UserVoiceBECustomer Feedback Platform
Wiz, Inc.DECloud Security
Workato, Inc.DEIntegration and Workflow Automation
Zoom Video Communications, Inc.IEVideo and Schedule Services

The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.

Every subprocessor in the registry, and which vendors name it: subprocessors.

Processing terms

From the vendor's data processing agreement · read 2026-11-09 · lusha.com

TermWhat the agreement says
Transfer mechanismSCC module 1
Transfer mechanismSCC module 2
Transfer mechanismSwiss FADP clauses
Transfer mechanismUK Addendum
Notice of new subprocessorsAt least 10 days in advance, by updating the sub-processor list; customer can sign up to receive notices of changes
If you object to oneCustomer may object within 10 days of the change being posted; if it does not, it is deemed to have accepted the new sub-processor
Breach notificationwithout undue delay and, where feasible, within 72 hours of becoming aware
AuditAudits and on-site inspections by customer or a mandated auditor, no more than once a year, during business hours, with at least 30 days' prior notice and confidentiality undertakings; the parties first agree on customer reimbursing any material costs

Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.

Which version applies

We found no version number or date in the agreement as we read it.

These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.

Assurance

Does Lusha have a SOC 2 report?

Lusha states SOC 2 Type 2 on its own page, but does not say there how to get a report. We read this on 2026-11-09.

  • Claimed “SOC 2 Type II -Independently audited for security, availability, confidentiality and privacy controls.”

Source: lusha.com, 2026-11-09

Of the 114 vendors in this registry whose own pages mention SOC 2, 57 say the report is available on request, 1 links to the report itself, and 56 state it without saying how to get it. The type is the one the vendor names.

Is Lusha ISO 27001 certified?

Lusha states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. We read this on 2026-11-09.

On the same list Lusha also names ISO/IEC 27017 and ISO/IEC 27701. Each standard's page says how it relates to ISO/IEC 27001.

Of the 122 vendors in this registry whose own pages state ISO/IEC 27001, 16 link to the certificate, 43 say it is available on request, and 63 state it without saying how to get it. A certificate names the certification body, the scope and the expiry date: those are the three things to check.

SchemeStatusScopeSourceObserved
CCPAClaimedValidated by TrustArc, global leaders in data privacy assurancelusha.com2026-11-09
GDPRClaimedCertified by European independent auditors ePrivacyseal GmbH.lusha.com2026-11-09
ISO/IEC 27001 · ISO27001ClaimedCertified for our Information Security Management System (ISMS), the foundation for all our other security and compliance certifications.lusha.com2026-11-09
ISO/IEC 27017 · ISO27017ClaimedCertified for cloud-specific security controls, extending our ISO 27001 information security management practices to cloud services.lusha.com2026-11-09
ISO 27701 · ISO27701Claimed—lusha.com2026-11-09
ISO/IEC 42001 · ISO42001ClaimedCertified for our AI Management System (AIMS), ensuring responsible development and governance of AI capabilities.lusha.com2026-11-09
ISO 31700ClaimedPrivacy by design for consumer goods and services.lusha.com2026-11-09
TRUSTe Responsible AIClaimedCertification for data governance alignment with global ethical standards and regulation.lusha.com2026-11-09
SOC 2 Type II · SOC2T2ClaimedIndependently audited for security, availability, confidentiality and privacy controls.lusha.com2026-11-09

Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.

SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.

Official registers

What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.

Support window

Not yet collected. This row will say not declared only once we have read a lifecycle or security page and found no period stated — see support windows.

Vulnerability reporting: [email protected] (security.txt, expires 2027-05-01; read 2026-11-09)

How other vendors publish theirs: security.txt across the registry.

Documents

What we read, how it was disclosed, and when.
DocumentDisclosureTranscriptionHTTPObserved
certificationsPublicfull2002026-11-09
dpaPublicfull2002026-11-09
subprocessorsPublicfull2002026-11-09

History

Nothing has moved since we started watching this vendor on 2026-11-09. Changes appear here only after a human has reviewed them.

Every reviewed change across the registry, newest first: vendor changes.