The policy states that RunPod collects account identifiers (name, email, password), billing and payment information, and user communications directly provided by users during account creation and platform use.
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 defines the baseline categories of personal data that RunPod collects and processes, which establishes the scope of data subject rights requests and the perimeter of any applicable data processing agreements between RunPod and its enterprise customers.
Removal of explicit enumeration of collected personal data types reduces transparency about what specific information RunPod collects from users.
View full change record →This provision establishes transparent baseline disclosure of direct personal data collection practices, providing users clear understanding of what information RunPod collects.
View full change record →The agreement establishes that account identifiers, payment data, and user communications are collected at account creation and during service use. Under this clause, the data collected forms the basis for billing, service delivery, and support functions.
How other platforms handle this
If you choose to reveal any personal information about yourself to other users, you do so at your own risk. We strongly encourage you to use caution in disclosing any personal information online.
to request that your data be transferred to a third party (data portability)
Your organization may allow you to access and export your data in order to back it up or transfer it to a service outside of Google.
"We collect information you provide directly to us, such as when you create an account, use our services, or contact us for support. This includes: name, email address, and password; billing and payment information; communications you send us.Excerpt from RunPod's Privacy Policy
1) REGULATORY LANDSCAPE: Collection of billing and payment information engages PCI DSS standards administered by the Payment Card Industry Security Standards Council, and collection of identifiers and communications engages GDPR Articles 5 and 6 (lawful …
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.
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.
This provision defines the baseline categories of personal data that RunPod collects and processes, which establishes the scope of data subject rights requests and the perimeter of any applicable data processing agreements between RunPod and its enterprise customers.
The agreement establishes that account identifiers, payment data, and user communications are collected at account creation and during service use. Under this clause, the data collected forms the basis for billing, service delivery, and support functions.
ConductAtlas has identified this type of provision across 290 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by RunPod.