Get the weekly 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. No account.
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
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.
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 βMonitoring
RunPod has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"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
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. The California Consumer Privacy Act and its regulations address Global Privacy Control (GPC) signals separately from Do Not Track; RunPod's policy does not specifically address GPC signal recognition, which is a distinct and regulated opt-out mechanism under CCPA regulations. GOVERNANCE EXPOSURE: Low to Medium. The non-response to Do Not Track signals is commonly observed in industry practice. However, the policy's silence on Global Privacy Control signal recognition is a potential compliance gap under CCPA regulations, which require businesses to treat GPC signals as valid opt-out requests for sale or sharing of personal information. JURISDICTION FLAGS: California creates the most direct exposure due to CCPA GPC signal requirements. If RunPod does not honor GPC signals, this may constitute a CCPA compliance issue separate from the Do Not Track disclosure. CONTRACT AND VENDOR IMPLICATIONS: No direct B2B vendor implications from this provision alone. COMPLIANCE CONSIDERATIONS: Compliance teams should evaluate whether RunPod's platform technically recognizes and honors Global Privacy Control signals as required by CCPA regulations, and whether this is disclosed in the Cookie Notice. The Do Not Track disclosure does not address GPC, which is a separate legal requirement.
Full institutional analysis
Regulatory citations, enforcement risk, and due diligence action items.
Monitor: same-day alerts on the platforms you choose. Analyst: full institutional analysis.
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.
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.
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.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by RunPod.