This section applies to the isolated 2.0/113 beta. The Firebase descriptions below apply to the published version. Both share Firebase Authentication; beta matches, rankings and history use staging 18144. Beta saves and settings remain in separate local storage, without Firestore cloud sync or automatically overwriting the published campaign. Export/import can copy a save. Test ratings do not automatically migrate to production. The separate VPS uses your user ID, temporary authentication credential, chosen name/team/country, actions and minigame inputs for play, reconnection and abuse prevention. Its rankings and history store participants, scores, outcomes and ratings; public identifiers are pseudonyms, not anonymous data. Results remain for the current and previous season; ratings for the current and three previous seasons. Seasons last 90 days. Technical traces contain phase, role and command type, not payloads or random entropy, and expire after seven days; internally they are linked to participant IDs. Waiting rooms expire after 15 minutes, active rooms after three hours and finished/cancelled rooms and request receipts after 24 hours. Purging runs while the service is running. Your public name is optional: disabling it in Settings displays Player XXXX in rankings, history and existing shared results. Anyone with a ten-character result link can see the public names, countries, score and date. Account erasure removes profiles, ratings, rooms and traces, replaces identifiers in results and revokes shared links; a permanent ledger retains the erased identifier and date for recovery. A restored backup must be reconciled with the latest deletion ledger before access is reopened. In beta Settings, deleting beta match data affects only staging and preserves Firebase identity and published saves. For complete account deletion, contact us and specify both services: removing the shared Firebase identity also affects the published version. Local erasure is separate. Consistent local backups run every six hours and on shutdown, retaining at most 14 copies, not a guaranteed 84-hour period. A weekly task encrypts a backup with age, uploads it to private Google Drive and verifies recovery. It requires the operator PC, Codex and connections to be available. The private key stays off the VPS and Drive, with local custody and an external recovery copy. Drive retention is currently manual; no automatic purge guarantees an eight-week limit. HTTPS protects transport; IP addresses support routing and rate limits and are not stored in room records. Normal proxy access logging is disabled; error logs may contain IP/path and rotate daily with seven retained rotations. Application logs omit credentials, user IDs and request bodies and retain two files of at most 5 MB. Contact and ownership verification below also allow deletion without reinstalling the app.
Operator: Max Bonàs / Toti Lab Studio. Contact: maxbonas@gmail.com.