Provision record
RunPod · RunPod Privacy Policy · View original document ↗

Do Not Track Non-Response

Low severity Medium confidence Explicit document language Unique · 0 of 352 platforms
Stay ahead of the changes
Track RunPod and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF
Document Record

What it is

The policy discloses that RunPod does not respond to browser-level Do Not Track signals.

ⓘ

This analysis describes what RunPod'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)

This provision establishes that browser-level Do Not Track signals will not alter RunPod's data collection or tracking practices. Users who wish to limit tracking must use the opt-out mechanisms described elsewhere in the policy, such as the Cookie Notice opt-out or DSAR email.

⚠

Interpretive note: The policy does not address Global Privacy Control signal recognition separately from Do Not Track, and the legal status of GPC compliance under CCPA regulations creates interpretive uncertainty regarding this provision's completeness.

Consumer impact (what this means for users)

Under this clause, sending a Do Not Track signal via a browser will not affect how RunPod collects or processes personal information. Users seeking to limit tracking should instead use the Cookie Notice opt-out or submit an opt-out request to dsar@runpod.io.

Cross-platform context

See how other platforms handle Do Not Track Non-Response and similar clauses.

Compare across platforms →
▸ View Original Clause Language DOCUMENT RECORD
"
Some Internet browsers may be configured to send 'Do Not Track' signals to the online services that you visit. We currently do not respond to 'Do Not Track' signals. To find out more about 'Do Not Track,' please visit http://www.allaboutdnt.com.

Excerpt from RunPod's Privacy Policy

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

REGULATORY LANDSCAPE: The FTC has historically encouraged but not mandated Do Not Track compliance; there is no current federal legal requirement to honor Do Not Track signals in the United States.

Insight

Unlock the full institutional analysis

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

Applicable agencies

  • State Attorney General
    State AGs in California, New York, Texas, and other states can investigate violations of state consumer protection and privacy laws, including CCPA (California), SHIELD Act (New York), and equivalents.
    Who can file: Residents of states with comprehensive privacy laws — primarily California, Virginia, Colorado, Connecticut, and Utah
    What you need: Evidence of the violation, explanation of how your state rights were affected, and your account or contact information with the company
    What to expect: Outcomes vary by state. May result in investigation, enforcement action, or requirement for the company to change practices. No direct individual compensation in most cases.

    Search "[your state] attorney general consumer complaint" to find your state's direct complaint form

Provision details

Document information
Document
RunPod Privacy Policy
Entity
RunPod
Document last updated
May 5, 2026
Tracking information
First tracked
July 9, 2026
Last verified
July 9, 2026
Record ID
CA-P-016108
Document ID
CA-D-00652
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
0c0dcb1e01be2cb2e4dea43a89b75099145bebdff905af66b2b8a8590f345027
Analysis generated
July 9, 2026 09:35 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: RunPod
Document: RunPod Privacy Policy
Record ID: CA-P-016108
Captured: 2026-07-09 09:35:07 UTC
SHA-256: 0c0dcb1e01be2cb2…
URL: https://conductatlas.com/platform/runpod/runpod-privacy-policy/provision/CA-P-016108/do-not-track-non-response/
Accessed: Sept. 26, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Low
Categories

Other risks in this policy

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 RunPod's Do Not Track Non-Response clause do?

This provision establishes that browser-level Do Not Track signals will not alter RunPod's data collection or tracking practices. Users who wish to limit tracking must use the opt-out mechanisms described elsewhere in the policy, such as the Cookie Notice opt-out or DSAR email.

How does this clause affect you?

Under this clause, sending a Do Not Track signal via a browser will not affect how RunPod collects or processes personal information. Users seeking to limit tracking should instead use the Cookie Notice opt-out or submit an opt-out request to dsar@runpod.io.

Is ConductAtlas affiliated with RunPod?

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