Privacy Policy
How the event remembers you
This policy explains what data is used by the Chata Event 2026 website and game systems. The event is private, but the website is public enough that privacy rules still matter.
1. Who Runs This
Chata Event 2026 is operated by the event organizers for a private company event. For privacy questions, contact the organizer or GM team through the official event communication channel.
2. Data We Process
- Account data from Firebase Authentication, such as provider, email domain, and sign-in status.
- Character and game data, such as class, level, resources, inventory, skills, progression, battle state, tribe, and warband state.
- Event safety and fairness data collected while the mobile app is open and active, such as location-based game interactions, GPS accuracy, movement speed flags, and BLE/proximity evidence where the game uses it.
- Website analytics data if you allow analytics cookies, such as page views, clicked links, section views, music playback events, registration flow events, and pseudonymous signed-in character context on the character page.
- Optional mobile Firebase Analytics data if you allow it in the app, such as screen views; gameplay actions and results; settings and permission states; diagnostics; quantities, prices, durations, distances, and GPS accuracy; class, level, health, and story phase; and pseudonymous app, player, tribe, warband, battle, site, territory, trader, item, and skill identifiers.
- Technical data normally sent by browsers and Firebase services, such as device/browser information, timestamps, and basic security logs.
Website analytics
When analytics cookies are allowed and you are signed in on the character page, we may send a Firebase user ID to Google Analytics as a pseudonymous User-ID, plus non-identifying character segmentation such as class, tribe ID, whether a tribe is present, registration state, and level band. We do not intentionally send names, emails, or character names to Google Analytics.
Mobile app analytics
Mobile app analytics is separate from website cookie consent. Custom mobile analytics events are sent only after you allow analytics in the app. Google processes these events through Firebase Analytics as our analytics service provider. If server-side forwarding is enabled for a release, the organizer may also send the same consented event stream through its Google Tag Manager endpoint to Google Cloud and BigQuery.
We do not describe mobile analytics as anonymous because pseudonymous or stable app, player, and gameplay identifiers and contextual game data can be present. We do not intentionally include names, email addresses, login credentials, or exact GPS coordinates in mobile analytics events. Precise location is processed separately where required for gameplay and live event operations. Mobile analytics is not used for advertising and is not sold.
You can change this choice at any time in the mobile app under More → Account & Privacy → Optional mobile analytics. Turning it off stops future optional mobile analytics collection; it does not delete analytics already processed under an earlier choice.
The mobile app requests location access only while it is in use, after a signed-in playable character has completed startup. While the app is open, location supplies the map position and verifies nearby sites and encounters, walking and movement, territories, trades, team and revive proximity, location-gated services, safe zones, and event fairness. Live location tracking stops when the app is locked, inactive, or in the background, so location-dependent gameplay requires the app to remain open and active.
3. Why We Use It
- To register players and allow only eligible Optimics accounts.
- To run the game, character progression, combat, exploration, territories, trades, and GM support.
- To keep the event fair and recover broken game states.
- To understand whether the website, guide, music player, and registration flow are working.
- To protect the game systems from misuse, spoofing, abuse, or technical failure.
6. Retention
Game and account data is kept while the account is active for event operation, support, debugging, fairness, and post-event review. Event-wide retention periods may differ by record type, and the organizers may delete event data earlier, especially before reseeds, tests, or future event changes.
When you request account deletion, the account is blocked from further gameplay and its personal character data is removed. Cleanup normally finishes immediately; recoverable retries may continue for up to seven days. Shared battle, trade, tribe, operational, security, and analytics records may remain only where needed to preserve other players' records, prevent abuse, resolve disputes, or meet legal duties. In those retained records, your account identifiers and location are removed or replaced with a random deleted-player label.
7. Your Rights
Depending on applicable law, you may have rights to access, correct, delete, restrict, or object to processing of your personal data. You can initiate permanent account deletion in the mobile app under More → Account & Privacy → Delete account, or use the direct account-deletion page. For other requests, contact the organizer through the official event channel.