Provision record
Weights & Biases · Weights & Biases Privacy Policy · View original document ↗

Data Controller vs. Processor Distinction

High severity Common · 279 of 352 platforms
Stay ahead of the changes
Track Weights & Biases and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF
Document Record

What it is

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

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.

Consumer impact (what this means for users)

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

ZipRecruiter Medium

In certain instances, our clients hire ZipRecruiter to provide services on behalf of the client. In such case, we process Personal Data under the direction of that client (the data controller) and have no direct relationship with the individuals...

MyFitnessPal Medium

We use your personal information to send you newsletters and other promotional communications, including information about MyFitnessPal's new offerings, features, offers, events, webinars, and other information.

Lyft Medium

We may infer certain information from your interactions with the Lyft Platform and other personal information available to us. For example, if you frequently ride to or from airports, we may infer you are a frequent traveler.

See all platforms with this clause type →
ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

(1) REGULATORY FRAMEWORK: The controller/processor distinction is governed by GDPR Art.

Insight

Unlock the full institutional analysis

Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.

Applicable agencies

  • Federal Trade Commission (ftc)
    Oversees unfair or deceptive business practices and can investigate companies that mislead consumers about data collection, sharing, or use.
    Who can file: Anyone affected by the company's practices (US or international)
    What you need: Your account details, a timeline of relevant events, and a description of the specific issue
    What to expect: Complaints inform FTC enforcement priorities and investigations but do not result in individual resolution or compensation
    File a complaint →

Applicable regulations

EU AI Act
European Union
CCPA/CPRA
California, USA
Colorado AI Act
US-CO
ePrivacy Directive
European Union
EU AI Act - High Risk Provisions
EU
FTC Act Section 5
United States Federal
GDPR
European Union

Provision details

Document information
Document
Weights & Biases Privacy Policy
Entity
Weights & Biases
Document last updated
May 5, 2026
Tracking information
First tracked
April 30, 2026
Last verified
April 30, 2026
Record ID
CA-P-004031
Document ID
CA-D-00494
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
d22dfd2783d85c7762f7d1c8bc9218e673b92d92ddc4211e1ac86525625d3354
Analysis generated
April 30, 2026 05:25 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Weights & Biases
Document: Weights & Biases Privacy Policy
Record ID: CA-P-004031
Captured: 2026-04-30 05:25:00 UTC
SHA-256: d22dfd2783d85c77…
URL: https://conductatlas.com/platform/weights-biases/weights-biases-privacy-policy/provision/CA-P-004031/data-controller-vs-processor-distinction/
Accessed: Sept. 13, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
High
Categories

Other risks in this policy

Related Analysis

Get the research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.

Frequently Asked Questions

What does Weights & Biases's Data Controller vs. Processor Distinction clause do?

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.

How does this clause affect you?

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 many platforms have this type of clause?

ConductAtlas has identified this type of provision across 279 platforms. See the full comparison.

Is ConductAtlas affiliated with Weights & Biases?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Weights & Biases.