Privacy & Data

Beta policy · Updated November 10, 2026

Local practice

Local practice stores settings, build designs, and diagnostic events in your browser. It does not grant verified Fuel or ownership. When upgrading to the Fuel career, old progression is archived on your device and designs are preserved. The archive does not copy authentication tokens.

Online beta

Connecting uses Supabase authentication and an arena server. Online records include an account identifier, callsign, Fuel transactions, item ownership, XP, mastery, cup state, and match outcomes. The server processes gameplay inputs and connection information to run matches and limit abuse. Guest identity is tied to the browser session; clearing its credentials can lose access unless an account recovery method has been linked.

Email and password features are available only when configured and enabled. Passwords are handled by the authentication provider and are not included in game telemetry. When Google sign-in is enabled and you choose it, Google provides your sign-in identity to Supabase so you can access the same pilot across browsers. Cloudflare Turnstile may process connection information during the online sign-in check. Hosting and authentication providers process requests under their own policies.

Optional usage metrics

Usage sharing is off by default. If you enable it, the beta can record limited event counts associated with your account, such as sessions and completed matches. These records do not contain email addresses, passwords, or wallet details. They help evaluate tutorial completion, return visits, and errors. Turning sharing off stops further submission.

Control and deletion

Use Career → Profile → Account & Data to export the legacy archive or delete your online account and associated game records. Account deletion is permanent. Browser archives and saved designs remain locally until you clear them or reset browser data. Deleting an anonymous session before linking a recovery method can make remaining guest records inaccessible; contact the project for help.

No wallet connection or token transaction is required. For privacy questions, contact the project through the official JUGGERNAUT account.