Privacy Policy
Development draft · 6 September 2026
Data R8VERS uses
The current service may process your email and authentication identifiers; username, profile details, avatar, country and preferences; game sessions and answers; discovery actions and My Finds; rave attendance, artists, notes, memories and photos; session, device and security information; and connected-provider identifiers or tokens if integrations are enabled. Future check-in features may use location only after permission is requested.
Why it is used
R8VERS uses this information to provide and secure your account, run games and progression, personalize music discovery, manage rave memories, prevent abuse, improve reliability, and meet legal obligations. Recommendation inputs include your chosen genres, game answers, and Keep, Pass, and Know It activity.
Visibility
Profiles, upcoming raves, rave history, and photos are private by default in the MVP data model. Information is made public only through a visibility choice offered by the product. R8VERS does not expose authentication IDs, email addresses, or provider tokens in public profile data.
Service providers
Supabase provides database and authentication services. Cloudflare provides hosting and R2 storage for private uploaded media. PostHog provides product analytics: it receives a randomly generated identifier stored in your browser (not tied to your name or email unless you sign up) and event data describing how you use the game — for example which mode you played, your score, and how a run ended — for both signed-in and anonymous players. Email delivery, music, and event-data providers will be listed by function and name before public launch. These services may process data where they operate under applicable safeguards.
YouTube players
Discovery can show a click-to-load YouTube player. R8VERS does not contact YouTube from that player until you choose to load it. When you do, YouTube receives information needed to provide and secure the player, which can include your IP address, device and browser information, the referring page, and your interaction with the player. YouTube processes that information under its own privacy policy. Loading or watching a video does not award R8VERS XP.
Deletion and retention
Deleting your account removes your authentication identity and identifiable active-service data, including profile-linked activity and owned media objects. Minimal records may be retained only for a defined legal, security, fraud, or dispute need with restricted access. De-identified aggregate statistics may remain when they cannot reasonably be linked to you. Backups and infrastructure logs expire on schedules that will be finalized before launch.
Your choices
You can correct account information in product flows and permanently delete the account from the Me screen. Applicable law may also provide access, correction, deletion, restriction, objection, portability, consent-withdrawal, complaint, or appeal rights. A verified request channel will be published before launch.
Storage and security
R8VERS uses authentication, access controls, private media storage, and signed access links to protect account data. A first-party cookie identifies your anonymous play session for up to 30 days so a run in progress isn't lost; a separate identifier stored in your browser's local storage supports the analytics described above. No system can guarantee absolute security.
Before public launch
The final operator and privacy contact, launch geography, minimum age, processors and transfers, retention periods, analytics and cookie disclosures, and location handling require approval before public signup opens. This development draft is not the final public-launch notice.