Privacy Policy
What we collect, why, and how long we keep it.
Draft for legal review. This notice describes how the service behaves today. It has not yet been reviewed by counsel and must be finalised, including the legal entity, contact details and jurisdiction-specific rights, before the service is offered commercially.
Who this covers
Two groups of people: developers who create an account on this website to use the console, and players of games that integrate Obscurity. For players, the session service records the fields listed below when a game that integrates it is run. Platform verification is built but not released; what it receives when a game uses it is listed in its own section. Client-side integrity signals are not built, and their planned collection is described separately.
Developers: data collected today
| Data | Purpose | Kept for |
|---|---|---|
| Name, email address | Identify your account, send account email | Until the account is deleted |
| Password | Sign-in. Stored only as an Argon2id hash | Until changed or the account is deleted |
| Session records: time, IP address, browser user agent | Keep you signed in; let you review and revoke sessions | Until the session expires or is revoked, then removed during routine cleanup |
| Organization, team, game and policy configuration | Provide the service | Until deleted by the organization |
| Server keys | Authenticate your game backend. Stored only as hashes | Until the game is deleted |
| Audit log: who did what, when, from which IP address | Security and accountability for your organization | Retention period to be confirmed |
| Contact form messages | Answer your enquiry | Retention period to be confirmed |
The website sets two cookies, both strictly necessary: a session cookie after you sign in and a token that protects forms against cross-site request forgery. There are no analytics, advertising or third-party cookies, and no third-party scripts or fonts are loaded.
Players: data recorded by a protected session
| Data | Purpose | Kept for |
|---|---|---|
| A public key generated for that one session | Authenticate the session's later requests. It does not identify a device or person across sessions | The evidence-retention period of the game's tier (Core 14 days, Advanced 30 days, Elite 30 days) |
| Windows build number, SDK version, SHA-256 of the game's executable | Compatibility, and comparison with the builds the studio released | |
| IP address of the request | Rate limiting and abuse handling. If the game switched on Anti-VPN, it is also compared with Obscurity's own list of VPN, proxy, Tor and hosting-provider networks, on our servers: the address is not sent to anyone else for this. If the game switched on IP bans, a ban can also restrict it for at most 30 days | |
| The player identifier the game's server supplies | Bind the session to the account it was verified for | |
| The admission decision, and when the session started and ended | Record of what was decided; usage metering | |
| Actions the game's own server rejected: the distance of a rejected move, or the name of an action on cooldown | Let the studio's team notice sustained rule-breaking | With the session |
| Misuse of a session the service observes: forged or replayed requests, reused join tokens | Protect the session; these are not treated as evidence against the player on their own | With the session |
| Detections (a rule's finding and its evidence) and a reviewer's decision and note | Human review before any decision about a player | With the session, or for as long as a restriction rests on them |
| Restrictions: the player identifier, the reason, who decided it and when it ends | Record of a studio's decision to restrict a player from its game, so it can be reviewed and reversed | One year after the restriction ends |
| A hash of the player identifier, per game and month | Count monthly active players for the studio's plan | 13 months |
The data reference lists every field. A game's studio may switch on automatic punishment, which acts only on findings within limits Obscurity sets (today, at most a temporary suspension; never a permanent ban); everything else is decided by a person at the studio. Every decision can be reversed. If a game tells you your account, PC or network is restricted, contact that game's support.
To enforce those decisions, games using SDK 0.6 report device identifiers: a random installation ID, the PC's system UUID, the system disk's serial and monitor serials. They are hashed on your PC before they are sent and stored only as keyed hashes that differ for every game, so one studio's records cannot be matched against another's. The one exception is the optional Global Ban Network, for games whose studio switches it on: there, a platform account the game's server verified and a TPM proven in platform verification are also kept as a hash that is the same in every participating game, so that a cheating ban validated by Obscurity can apply in other participating games. Reported hardware, installation IDs and network addresses are never used that way, and studios never see each other's records. Saved Wi-Fi networks, paired devices, names, installed programs, accounts with other companies, licence keys and payment details are never collected. The full list of what is and is not collected, with reasons, is in the data reference.
Players: platform verification
Only when a game's studio requires platform verification (TPM 2.0, Secure Boot, memory integrity or IOMMU), the game sends the data below once at the start of each session. This feature is built but not released, so no game uses it yet. It needs no administrator rights and changes nothing on your PC: when a requirement is not met you are told which one and what you can change, and that result is never treated as a finding about you.
| Data | Purpose | Kept for |
|---|---|---|
| The public half of the TPM's endorsement key, and its certificate if the TPM stores one | Tie the TPM's answer to one TPM and check that a TPM manufacturer certified it. The key identifies the PC's TPM, so it is treated as personal data. | Not kept. A hash of the key salted with the game's id is kept with the session: it lets that one game recognise a PC it has seen and cannot be matched across games or studios. |
| A TPM quote of this boot's measurements, and the measured values (PCRs 0-7 and 11-14) | The TPM's authenticated statement of how the PC booted, bound to a single-use server challenge. | Not kept. |
| Windows' measured-boot log for the current boot | Read whether Secure Boot, memory integrity and the IOMMU requirement were on when Windows started. The log lists the firmware and boot components that started. It holds no documents, messages, browsing data or credentials. | Not kept. It is discarded when the check ends. |
| The TPM's four-character manufacturer id | Decide which manufacturer's certificate applies. | The manufacturer named in the certificate is kept with the session. |
| The result for each requirement, the reason, and a few values read from the boot record (for example: Secure Boot on, hypervisor started, test signing off) | The admission decision, the advice shown to the player, and the studio's view of why sessions are refused. | Kept with the session for the retention period of the game's tier. |
Some TPMs do not store their manufacturer's certificate. For those, the service can ask the manufacturer (AMD or Intel) for it, which sends that manufacturer a hash of the endorsement key. This is switched off for this service.
Players: planned collection
If client-side integrity signals are released, a protected game will also send Obscurity the data below. This list will be finalised, and this notice updated, before any of it is collected.
| Data | Purpose |
|---|---|
| Integrity signals about the game's own files and process | Detect tampering with the protected game |
Our Discord server
Joining the Obscurity Discord server is optional, and Discord's own privacy policy applies to your account there. In that server an AI assistant answers questions. What you write in the questions channel, in a message that mentions the assistant, with the /ask command, or in a ticket while the assistant is answering is sent to Anthropic, the company that provides the AI model, to produce the reply. When a ticket is closed, a transcript of it is kept in a channel only our team can see. Messages that look like they contain a password, key or token are deleted and are not sent to Anthropic. The assistant cannot see your Obscurity account, and nothing from Discord is linked to it.
Text messages (SMS)
Obscurity offers support by text message at +1 (571) 556-1522. You join by texting SUPPORT and replying Y to our confirmation (see the SMS terms).
When you text us we keep your phone number, the messages you send and that we send you, their times, and whether you have opted in or out. We use them only to answer your questions and send the support, ticket and account messages you asked for. Messages are delivered through Twilio, which processes them on our behalf to send and receive them.
We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. Text-message originator opt-in data and consent are not shared with any third parties.
Reply STOP at any time to stop receiving texts; we keep a record that you opted out so that we do not text you again. We keep your messages until you ask us to delete them or until we no longer need them for support. To ask, text us or open a private ticket in our Discord server.
What we do not collect
Obscurity is designed not to collect personal files, documents, photos, messages, browsing history, credentials, keystrokes outside the game, or screenshots of your desktop. It does not scan memory unrelated to the protected game. Any future change to this would require a specific justification and an update to this notice first.
Who can access data
Data belonging to an organization is visible only to that organization's members, according to their role. Player data related to a game is visible to that game's organization and to Obscurity staff who need it to operate the service or review a decision. We do not sell data.
Your choices
You can change your name and password and revoke sessions in the console. To request access to, correction of or deletion of your data, use the contact form. Players should usually contact the game's publisher first, because the publisher decides how a game uses Obscurity.
Changes
Material changes to this notice will be announced on this page before they take effect.