Are you a player? This page is for you. It explains in plain language what Kubian does with your information when you play a game or use an app that has Kubian protection built in. If you are a game developer, please read the full Developer Privacy Policy instead.
In short: Kubian quietly checks in the background that your device and the game you installed are genuine, so cheaters can't ruin your game. To do that Kubian collects and stores two app-scoped device signals — your Android ID (resettable since Android 8) and your Widevine DRM ID (Widevine MediaDrm ID), which cannot be changed or reset like Android ID — and uses them only inside that specific game to verify your device and enforce bans. We never sell your information, never show you ads, and never follow you from one game to another. If you stop playing a game for 60 days, we automatically pseudonymize that game's records about your device (see Section 3 — this is not full anonymization, because we keep secure codes so you can reconnect later). The game studio is responsible for handling, deleting, and controlling how and where your data is used for their game. You can ask for your data to be deleted at any time (see Section 5), and if the studio does not respond you can escalate to us at [email protected] for enforcement.
1. What is Kubian, and who does what with your information?
Kubian is a security service made by Static Labs LLC that game studios put inside their games to stop cheating and tampering. Two roles matter:
- The game studio (the Data Collector): the company that made the game you play. They decide whether Kubian runs in their game at all — without them switching it on, nothing is ever collected — and they are the ones you should contact first about your data. They do not pick which technical details are gathered; that set is fixed and defined by Kubian (see Section 2).
- Kubian / Static Labs LLC (the Data Processor): once a studio switches Kubian on, Kubian automatically gathers only the fixed set of technical signals needed to verify that your device and game are genuine — nothing more. We never collect anything outside of a game that integrated Kubian, and we never act on your information except to provide the security service to that game.
2. What information is involved?
When you open a game protected by Kubian, your device proves it is genuine using built-in hardware security. To do that, Kubian collects, stores, and handles on its servers:
- Android ID: a device signal scoped to a single app. Since Android 8.0 it can be reset by you (for example by reinstalling or resetting the app), but it is still different in every game.
- Widevine DRM ID (Widevine MediaDrm ID): a persistent device signal from your device's secure hardware (Widevine). Unlike Android ID, it cannot be changed or reset by you — it persists across app reinstalls, cache clears, and factory resets. Like Android ID, it is still scoped to a single app: the same phone or headset produces a different Widevine ID value in different games.
- Technical check results (for example: is the device rooted, is the bootloader locked, is the operating system up to date, does the installed game match the official version).
- Per-game device identifiers — random-looking IDs that Kubian creates from the Android ID and Widevine
DRM ID above (a per-game 16-digit
user_account_idplus temporary project-scoped unique IDs) so the game can recognize your device for security (such as enforcing a ban against cheaters). These derived IDs are not raw copies of your hardware IDs.
Your IDs are different in every game. The underlying device signals Kubian uses work like your Android ID: they are scoped to a single app, so the same phone or headset produces different values in different games. Kubian cannot connect your identity between two different games, and neither can the game studios — nobody can follow you across apps using Kubian data.
What we never do: sell your information, use it for advertising or tracking you across apps, or share it with ad networks.
3. How long is information kept? (60-day pseudonymization — not anonymization)
Each game gets its own separate records, kept only while needed for security and cheat prevention.
If you don't open a game for 60 days, Kubian automatically pseudonymizes that game's device records — it does not fully anonymize them: the raw Android ID and Widevine DRM ID values are fully removed from active records and replaced with secure, irreversible, keyed codes (hashes). Nothing you care about is lost: if you come back to the game later, those codes let Kubian seamlessly reconnect your account and progress, which is exactly why this is pseudonymization and not true anonymization. Records needed to keep an active cheating ban in force are kept separately as isolated pseudonymous codes only, so bans can't be dodged by waiting them out.
4. Security
We protect information with encryption in transit and at rest, keyed hashes instead of raw identifiers wherever possible, and strict limits on which systems and staff can access it. Ban-related codes are stored in an isolated repository with separate access controls.
5. Your rights: access, correction, deletion, portability
Depending on where you live (including under laws like Oregon's OCPA and the GDPR where it applies), you may have the right to see, correct, delete, or receive a copy of your information.
The game studio is responsible for your data for their game. The game developer / studio is the Data Collector: they are responsible for handling, deleting, and controlling how and where your data is used for their game. Kubian / Static Labs LLC is only the Data Processor — we do not operate the game's player database or legal team, and we cannot manually verify who owns an in-game account without the studio's help.
How to ask:
- Step 1 — contact the game studio first. Because the studio is the Data Collector for your data, they are responsible for handling your request for their game. Ask them to delete your data and to forward the request to Kubian. Follow the response time stated in that game's own privacy policy.
- Step 2 (if the studio does not respond in time) — escalate to us directly at [email protected] to request immediate intervention. Include: (1) the specific game name, (2) your in-game account ID / player UID or other identifier the studio uses for you, and (3) your contact email so the studio can reach you directly. We generally respond within 30 days.
What happens after you escalate:
- Internal compliance demand (not a court subpoena): using our platform-level access, Kubian opens an internal compliance case against that studio and formally mandates a response. We ask the studio to: (a) confirm what information was collected for that account, (b) verify that you are identifiably the legitimate owner of that in-game account, and (c) contact you directly to complete verification and deletion / copy / correction. To avoid playing middleman, we will share contact details between you and the studio so you can finish verification directly. Once ownership is verified, we give the studio the technical steps to flag that game's Kubian-held records for permanent deletion.
- If the studio still does not respond within 7 to 14 business days: Kubian starts issuing compliance strikes and violations against that developer's project for failing to meet privacy expectations — up to 3 strikes over the course of ~3 weeks of continued non-response (formal warning with dashboard flags, then operational restrictions such as freezing security-profile changes or new player registration, then full project suspension / termination pulling the game's Kubian access).
- Once the studio responds: the project stays suspended until all related filings, bills, and legal disputes are handled. Kubian then promptly provides the studio's contact information back to you, notes the prior non-response requiring immediate intervention, and steps back — Kubian only stays in the middle when required to contact the developer directly or to execute the backend deletion.
One important limitation to know: because your Android ID and Widevine DRM ID values are different in every game, Kubian can only find and delete your information game by game — we have no way to look up your name, email, or global device fingerprint server-side and find you in a game you never told us about. To be fully forgotten, make the request to each game you played. This is deliberate: it means no one, including Kubian, can track you across games. If a game has no approved Data Collection Request linking real identities to device records, Kubian will explain this blindspot: deletion, portable copy, or correction is still possible for that specific game with your supplied in-game account ID, but Kubian cannot identify your device outside that game. Remaining server-side device data in that state is pseudonymized (see Section 3), and otherwise expires automatically after 60 days of inactivity.
Banned accounts: if your device has an active ban for cheating, the law allows security records needed to keep that ban in force to be preserved as pseudonymous codes while the ban lasts. Everything else is still deleted.
6. Children under 13
Games using Kubian are intended for players aged 13 and older. Kubian does not knowingly process information from children under 13; where an under-13 player is identified, Kubian works to block or restrict that interaction. If you are a parent or guardian and believe your child under 13 has used a Kubian-protected game, contact the game studio first, or us at [email protected].
7. The game's own privacy policy
The studio that made your game may collect and use information of its own, beyond what Kubian handles. Always also read that game's privacy policy to understand the studio's own practices — Kubian doesn't control those.
8. Changes to this policy
We may update this page from time to time. Material changes will be posted here, and continuing to play a Kubian-protected game after posting means you accept the updated policy. The full developer-facing Privacy Policy at https://kubian.app/Privacy-Policy contains the complete technical terms, incorporated here by reference.
9. Contact
Questions about this policy or your information: [email protected] (Static Labs LLC, Oregon, USA).
© 2026 Static Labs LLC. All rights reserved. · Oregon, USA