Public information
Privacy Policy
This Policy explains how ROREL, the 2A practice tool, handles personal information and other user data.
- Effective:
- August 3, 2026
- Last updated:
- September 6, 2026
1. Information we handle
Depending on the features you use, we handle the following information.
- Email address, display name, Firebase Authentication UID, and sign-in information
- Learning progress, mastery, favorites, calendar and practice history, and trophies or achievements
- Video review requests, uploaded videos, submissions, and feedback results
- Billing status, Stripe customer and subscription identifiers, amount, currency, and purchase dates
- Support messages and information you choose to provide
- Page and feature usage, browser, device, cookie, local-storage, and similar technical information
2. Purposes
We use information for authentication; Service delivery and synchronization; learning records and recommendations; Premium and video-review administration; payments; support; analytics and improvement; fraud, abuse, and security prevention; legal compliance; and advertising for eligible Free users.
3. Payments
Stripe processes card and payment details. The Service does not directly store complete card numbers or card security codes. We retain only billing and transaction information needed to administer purchases, resolve issues, and meet legal obligations.
4. Uploaded videos
Uploaded video-review files are stored and accessed only to receive, review, deliver feedback, maintain the submission history, protect the Service, and respond to requests. We do not use them for advertising, social media, or teaching materials without explicit permission.
5. Service providers and transfers
We use Firebase Authentication and Cloud Firestore, Google sign-in and services, Stripe, Cloudflare R2, Vercel, Google Analytics, Google AdSense, YouTube, and Google’s consent-management tools where configured. Data may be processed in countries where these providers operate, subject to their terms and applicable safeguards.
Google authentication is handled by Google. ROREL does not receive or store your Google password. ROREL uses your email address, display name, and account identifier as needed for sign-in and providing the Service. We do not request access to other Google Account data such as Google Drive, Gmail, or contacts.
6. Analytics, ads, cookies, and consent
Google Analytics may process page paths, non-personal master identifiers, interactions, browser or device information, cookies, and similar technologies to measure and improve the Service. We do not intentionally send email, display name, authentication UID, uploaded video, support text, or payment details as Analytics event parameters.
Google AdSense may use cookies or similar technologies to deliver and measure ads for eligible Free users. Premium and Beta users do not receive ad slots under the current Service rules. In the EEA, United Kingdom, Switzerland, and other regions where required, we use Google’s consent-management mechanism or another appropriate consent mechanism before relevant processing.
8. Retention and security
We retain information only as reasonably necessary for the purposes above, account and transaction administration, dispute handling, security, and legal obligations. We use reasonable technical and organizational safeguards, but no online system can guarantee absolute security.
9. Your choices and requests
You may update available profile information and manage Premium from the relevant settings pages. Use the feedback form to request access, correction, deletion, or other rights available under applicable law. Identity verification or retention of legally required records may be necessary.
10. Children
If consent from a parent or guardian is required under applicable law, a child should use paid or account features only with that consent.
11. Changes and contact
We may update this Policy as the Service or legal requirements change. Material changes will be announced where appropriate. Privacy questions may be submitted through the feedback form.
For questions, use thefeedback form.