CoreWeave acts as a data controller for information it collects directly from users, but may act as a data processor when enterprise customers run workloads that involve third-party personal data on CoreWeave's infrastructure.
This analysis describes what Weights & Biases's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
The data controller/processor distinction determines which party bears primary legal responsibility for data protection compliance, liability exposure, and regulatory obligations under frameworks like GDPR and similar regimes. This allocation affects contract enforcement mechanisms, audit rights, and the scope of permissible data handling activities.
If you are an enterprise customer using CoreWeave to process data about your own customers or employees, you are legally responsible for that data under GDPR — CoreWeave's role as your processor must be formalized in a written agreement.
How other platforms handle this
This Privacy Policy does not apply where Anthropic acts as a data processor and processes personal data on behalf of commercial customers using Anthropic's Commercial Services – for example, your employer has provisioned you a Claude for Work account, or you're using an app that is powered on the ba...
When our business customers use certain Services, we generally process and store limited personal information on their behalf as a data processor. For certain products such as Docusign's Contract Lifecycle Management (CLM) and Identity products, we may act as a processor and as a controller in certa...
Mixpanel acts as a data processor on behalf of its customers (the controllers) when processing end user data through the Mixpanel analytics platform, and as a data controller with respect to data it collects about its own website visitors and account holders.
Monitoring
Weights & Biases has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
(1) REGULATORY FRAMEWORK: The controller/processor distinction is governed by GDPR Art. 4(7) and (8), with processor obligations specified in Art. 28 (written DPA required), Art. 29 (processing only on controller's instructions), and Art. 32 (security obligations). UK GDPR and Swiss nFADP impose equivalent requirements. CCPA's service provider framework (§1798.140(ag)) creates analogous obligations for California-regulated data flows. (2)
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
We read the privacy policies and terms of service of 38 AI platforms. Here is what they say about training, retention, arbitration, and liability.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
The data controller/processor distinction determines which party bears primary legal responsibility for data protection compliance, liability exposure, and regulatory obligations under frameworks like GDPR and similar regimes. This allocation affects contract enforcement mechanisms, audit rights, and the scope of permissible data handling activities.
If you are an enterprise customer using CoreWeave to process data about your own customers or employees, you are legally responsible for that data under GDPR — CoreWeave's role as your processor must be formalized in a written agreement.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Weights & Biases.