No public evidenceDataRobot and GDPR
CertReports found no public GDPR evidence for DataRobot 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
- 4 Feb 2020
- Scope
- DataRobot's primary purpose for processing personal data is to provide its enterprise AI platform to our customers, and provide related customer service, training, and communications related to our products and company. We also process personal data to market and sell our product to businesses who may be interested in our software. We collect the following types of personal data: business contact information; employer, job title and public facing employment information; social media information; connection information including IP address, browser and geolocation information based on IP address; persistent online identifiers (e.g. cookies); credit card information (processed by our third party payment processor) We may share personal data with our affiliates, business partners, third party service providers and agents, with social media widgets, through business transfers, and as required for legal compliance, legal claims, security, fraud prevention and safety purposes.
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | DataRobot: Inactive | Live pagesha256 caaafa9dd4 |
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 DataRobot 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 AI infrastructure category) whose GDPR row is verified or vendor-stated, ranked by similarity.
