No public evidenceLaunchDarkly and GDPR
CertReports found no public GDPR evidence for LaunchDarkly as of unknown date. This does not mean the vendor is non-compliant. It means CertReports found no public evidence at the last check.
Evidence
- Kind
- listing
- Issued or listed
- 26 Mar 2018
- Expires or valid through
- 16 Mar 2027
- Scope
- The nature of the processing consists of collecting, storing and transferring Personal Data to facilitate LaunchDarkly’s provision of the Service to Customer as further described in the Agreement. The categories of personal data transferred are determined solely by the data exporter. In the normal course of the data importer's Service, the categories of personal data transferred might include (but are not limited to): name, email address, telephone, title, and feature flag configuration entered by the data exporter or its end users. The purposes of the data transfer is so that LaunchDarkly can provide the Service to Customer as further described in the Agreement. The Personal Data shall be retained as directed by Customer as needed to provide the Services pursuant to the Agreement. The third parties that may process personal data on LaunchDarkly’s behalf are captured as subprocessors on our public facing list of subprocessors, available at https://launchdarkly.com/policies/subprocessors/
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | LaunchDarkly: Active: EU-US Certification, SW-US Certification, UK Extension Certification | Live pagesha256 7e6acb2db9 |
What GDPR means, and what it does not
"GDPR compliant" is a claim, not a certification. The verifiable facts are a public DPA, SCC usage, an EU representative, data residency options and a Data Privacy Framework listing.
Read the GDPR guide and browse all vendors with evidenceQuestions buyers ask
Is LaunchDarkly GDPR compliant?
There is no GDPR certification in general use. The verifiable facts are a public data processing agreement, standard contractual clauses, an EU representative and a Data Privacy Framework listing. See the legal artefacts and the DPF row on this page, each with its capture date.
How does CertReports verify this?
Every state carries a capture date, a source and a snapshot link. Registry rows come from the official registry data; vendor statements come from the vendor’s own page or trust centre; nothing is inferred. Vendors can dispute any row and corrections ship within two business days.
Alternatives with GDPR evidence
Similar vendors (shared product tags or the DevOps and observability category) whose GDPR row is verified or vendor-stated, ranked by similarity.
