The policy authorizes Rumble to collect identifiers, account credentials, payment information, viewing history, search queries, user communications, and user-generated content provided directly by users or generated through platform activity.
This analysis describes what Rumble'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 the foundational scope of data collection across Rumble's platform, covering both voluntarily provided data and behaviorally generated data such as viewing history and search queries, which are categories relevant to targeted advertising and data sharing disclosures elsewhere in the policy.
Interpretive note: The exact enumeration of all collected data categories depends on full document text; the HTML source provided was truncated, which limits confirmation of the complete scope of collection disclosures.
Under this provision, the agreement authorizes collection of a broad range of data categories including identifiers, payment details, viewing history, and search queries from all users who create accounts or use the platform's services.
How other platforms handle this
At Ledger, earning and maintaining our users' trust is a top priority. That's why we are deeply committed not only to protecting your privacy and securing your personal data, but also to being fully transparent about how we handle it.
We use information to enhance the quality, reliability, and/or accuracy of our AI Features by creating, developing, training, testing, improving, and maintaining AI and ML models run by Strava or our service providers. We use aggregated, de-identified data for this purpose. We also use personal info...
We collect your personal data when you use our Services, create a new eBay account, provide us with information via a web form, add or update information in your eBay account, participate in online community discussions or otherwise interact with us.
Monitoring
Rumble has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"We collect information you provide directly to us, such as when you create an account, upload content, make a purchase, or contact us for support. This information may include your name, email address, password, profile information, payment information, and any other information you choose to provide. We also collect information about your use of our services, including the videos you watch, the searches you conduct, your interactions with other users, and your communications with us.— Excerpt from Rumble's Rumble Privacy Policy
1. REGULATORY LANDSCAPE: The collection of identifiers, browsing activity, and viewing history engages the CCPA and CPRA, which classify such categories as personal information and impose disclosure, access, and deletion obligations. The FTC Act's unfair or deceptive practices standard applies to representations about data collection scope. Collection of payment information implicates PCI-DSS standards and applicable state financial privacy laws. Where EU or UK users access the platform, GDPR and UK GDPR would require identification of a lawful basis for each data category collected. 2. GOVERNANCE EXPOSURE: Medium. The breadth of collection categories is consistent with large-platform norms but requires accurate disclosure alignment with actual operational data flows. Misalignment between disclosed categories and actual collection would create FTC and CCPA exposure. 3. JURISDICTION FLAGS: California residents have statutory rights to know and delete the categories described. EU and UK users are not explicitly addressed, creating potential GDPR exposure. Canadian users are referenced in the policy, implicating PIPEDA and provincial privacy laws. 4. CONTRACT AND VENDOR IMPLICATIONS: Downstream vendor agreements should be reviewed to confirm that service providers receiving this data are bound by data processing agreements consistent with the disclosed collection purposes. The payment information category warrants specific vendor assessment against PCI-DSS requirements. 5. COMPLIANCE CONSIDERATIONS: Compliance teams should maintain a current data inventory mapping each disclosed collection category to specific operational systems and verify that the policy's disclosed categories remain accurate as platform features change. Consent mechanisms for behavioral data collection should be reviewed against applicable state and international standards.
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.
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 the foundational scope of data collection across Rumble's platform, covering both voluntarily provided data and behaviorally generated data such as viewing history and search queries, which are categories relevant to targeted advertising and data sharing disclosures elsewhere in the policy.
Under this provision, the agreement authorizes collection of a broad range of data categories including identifiers, payment details, viewing history, and search queries from all users who create accounts or use the platform's services.
ConductAtlas has identified this type of provision across 14 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Rumble.