Privacy Engineered
In mobile esports, trust is the ultimate competitive advantage. Your gameplay data, device metrics, and account information are the fuel for our performance engine. This policy isn't legalese—it's our architectural blueprint for handling that fuel with precision, transparency, and zero-velocity latency to your privacy.
Core Principle
Data minimization is our default. We collect only what is technically required to deliver a sub-10ms input latency overlay, and nothing more. Every byte has a purpose, and that purpose is documented below.
Collection Signal
The dashboard interface we build from your data. Every chart starts with a single, consented data point.
The Data Spec Sheet
Performance Metrics
CoreFrame rate (FPS), input lag (ms), network latency (ms), device thermal state. Used exclusively for real-time overlay calibration and aggregated benchmarking. Never linked to your personal identity.
Device Characteristics
AnonymousModel (e.g., SM-S918U), Android version, screen resolution. Required to deliver compatible performance profiles. Stored as a hashed identifier, not directly tied to your account.
Account Information
EssentialEmail address, chosen username. Used for account authentication, purchase history, and support ticket correspondence. Never for marketing without explicit, opt-in consent.
In-App Purchase Data
TransactionalTransaction ID, timestamp, items purchased. Processed via the Google Play Billing Library. Our servers only store a transaction hash for license validation. No payment card details are ever processed or stored by Zonlix.
What We Don't Collect
- Your precise GPS location (we don't need it for latency overlay).
- Your contact lists or social media connections.
- Any data from other apps on your device.
- Biometric data (fingerprint, face ID).
Your Data's Journey: A Transparent Timeline
1. Collection (On-Device)
Your device generates performance data points. This data is processed locally within the Zonlix app using Android's native APIs. It is not transmitted immediately.
2. Aggregation & Anonymization
During a session, data is aggregated into performance profiles (e.g., 'Game: Generic FPS, Device: Flagship 2025'). Direct identifiers are stripped. The only link to you is a random user session ID, which changes every app launch.
3. Transmission (Optional)
For our public benchmark leaderboard (optional feature), anonymized performance profiles may be transmitted. Your account email is never transmitted with this data. You control this via the 'Share Anonymized Benchmarks' toggle in Settings.
4. Storage & Deletion
Account data is stored on secure AWS servers in Frankfurt (Germany). Performance data is retained for 90 days to calculate trend lines. You can request permanent deletion via our support portal, which triggers a complete purge within 72 hours.
Common Privacy Pitfalls
Avoid these critical mistakes when evaluating any performance tool. Each represents a failure of transparency or engineering.
The "Performance" Excuse
Collecting location data to "optimize for your region." Network latency can be estimated from your connection, not your coordinates. Zonlix only requires IP-based region data (non-precise) for CDN routing.
The Social Graph Trap
Requesting contacts or friend list access for "leaderboards." This is unnecessary and invasive. Our leaderboard is opt-in and based on anonymous IDs. Your contacts are never accessed.
The Opaque Vendor Chain
Using third-party analytics SDKs that send data to unknown servers. Zonlix uses no third-party analytics. All data processing is handled by our proprietary, on-premise servers located in Berlin.
The Perpetual Permission
Asking for "Always On" permissions for non-critical features. Zonlix only requests the minimum permission required for the feature you're using (e.g., microphone only for in-app voice chat).
Our Foundational Constraints
Constraint 1
We operate under the assumption that a user's gaming identity should remain separate from their offline identity unless they choose to link them.
Constraint 2
All privacy policies are written for comprehension, not obfuscation. If a 14-year-old competitive gamer can't understand it, we've failed.
Constraint 3
Data residency is non-negotiable. German user data resides on servers in Germany. This is a legal and ethical requirement for our team.
What Would Change Our Policy?
Privacy is a dynamic practice. We update based on evidence, not trends. These are our change criteria:
Any policy change is announced via in-app notification and a dedicated blog post at least 30 days before it takes effect.
Direct Contact for Privacy Inquiries
For any questions, data access requests, or to exercise your GDPR rights, contact our dedicated Data Protection Officer.
Data Protection Officer
Alexanderplatz 110178 Berlin, Germany
Official Channels
Working Hours (CET)
Mon - Fri: 09:00 - 18:00
We respond to all privacy-related inquiries within 72 hours during business days.