Pre-release Sign-up is not open yet. Platform verification and the signed client download are in development. See what is available
Reference

Data collection and privacy

Every field the service stores about a player's session, why, who can see it and how long it is kept, plus the rules any future collection has to follow.

Developer accounts

The website and console store developer account data, organization configuration, hashed credentials, browser session records, the audit log and contact messages. The privacy notice lists each item with its purpose.

  • Passwords are stored as Argon2id hashes.
  • Server keys, session tokens, invitation tokens and email links are stored only as SHA-256 hashes of random 256-bit values.
  • The site loads no third-party scripts, fonts or trackers and sets only two strictly necessary cookies.

Session field reference

This is the complete list of what a protected session records. The client SDK sends the first five; the rest are produced by the service or supplied by the studio's game server.

FieldSourcePurpose
Session public keySDKAuthenticates later requests of that session. Generated per session and discarded with it; it does not identify a device or a person across sessions.
SDK version and protocol versionSDKCompatibility decisions and diagnosing integration problems.
Windows build number (for example 10.0.26100)SDKCompatibility support. No edition, product ID or hardware information.
SHA-256 of the game executableSDKComparison with the studio's registered builds.
Network address of the requestConnectionRate limiting and abuse handling.
Player IDStudio's game serverBinds a session to the account the studio verified it for, and counts monthly active players. The studio chooses the value; we recommend an opaque account ID. For metering only a hash of it is kept.
Decision, category, policy version, profile, enforcement modeServiceThe record of what was decided and under which configuration.
Start, last heartbeat and end times; end reasonServiceLiveness and usage metering.

Event field reference

When a game has reports and detections switched on, these events are stored against a session. The list is generated from the code that validates them; a field that is not listed is discarded on receipt.

EventSourceFields
movement.rejected
Your game server rejected a move because it exceeded the speed your rules allow.
Studio's game server measured: Distance the client tried to move, in your game's units.
allowed: Distance your rules allowed at that moment.
rate.rejected
Your game server rejected an action performed faster than its cooldown allows.
Studio's game server action: Your name for the action, for example "fire" (up to 32 letters, digits, dots, dashes or underscores).
session.signature_invalid
A request made in this session's name was not signed with the session's key.
Session service time only
session.replayed_request
A correctly signed request for this session reused a sequence number.
Session service time only
join.token_reused
A join token of this session was presented to your game server again after it had been redeemed.
Session service time only
join.player_mismatch
A join token of this session was presented for a different player than the one it was verified for.
Session service time only

A detection stores the detector and its version, a summary, the counts and ratios it computed, the thresholds it used, and a reviewer's decision and note. A restriction stores the player ID, the reason, who decided it, when it ends and, if lifted, who lifted it and why. See detections, review and restrictions.

Platform verification reference

Sent once per session, and only by games whose policy requires a platform item (Advanced and Elite tiers). Generated from the code that verifies it. Platform verification is built but not released.

DataPurposeKept
The public half of the TPM's endorsement key, and its certificate if the TPM stores oneTie 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 bootRead 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 idDecide 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.

The endorsement key is the one hardware identifier the service receives. It is used during the check and not stored; the per-game hash that is stored cannot be compared between games. The exception is a game taking part in the optional Global Ban Network: for it, a second keyed hash of the endorsement key, the same in every participating game, is also kept, and so is one of each platform account its server verified. Only those two kinds of identifier, and only from participating games, can link games. A result here is a compatibility outcome: it is stored apart from events and detections and can never become a restriction. See platform verification.

Not collected: files other than the hash of the game's own executable, running processes, window titles, screenshots, network-adapter addresses, account names, email addresses, messages, browsing history or credentials.

Enforcement identifiers

Used only to apply a case your team or automatic punishment opened (see detections, review and enforcement). Hardware values are hashed on the player's PC before they are sent; the server stores every value as a keyed hash that is different for each game, so two studios' records of one PC do not match.

IdentifierFromHow it is verifiedConfidenceLongest restriction on its own
Platform account (Steam, Epic, ...)game serverReported by the game's own server after its own sign-in checkhighno limit
InstallationclientRandom id the SDK creates per Windows user; deleted by removing the game's datalownever alone
TPM endorsement keyattestedProven by the TPM in platform verification, certified by its manufacturerhighno limit
System UUID (SMBIOS)clientReported by the PC; can be changed or spoofedmediumnever alone
Motherboard serial (SMBIOS)clientReported by the PC; can be changed or spoofedmediumnever alone
System disk serialclientReported by the PC; can be spoofed by a drivermediumnever alone
Monitor serial (EDID)clientReported by the PC; some monitors share a seriallownever alone
Network addressserviceObserved by the session service; IPv6 as its /64. Shared by households, offices and carrierslow30 days

Considered and not collected, among others: saved Wi-Fi networks, router and neighbour addresses, paired Bluetooth devices, computer and user names, the list of installed programs, device history, accounts with other companies (Microsoft, launchers), the advertising ID, licence keys, credential stores, two-factor devices, payment details, friends and party history. Obscurity never writes markers to firmware, the EFI partition, unpartitioned disk space, system files or the TPM's storage. The owner's full list of 576 fields with the decision and reason for each is kept in server/obscurity/data/identifier_catalog.json.

Access. A studio's members see the sessions of their own games in the console, and its game servers through the API with a game-scoped key. No studio can read another studio's sessions.

Retention. Session records are deleted after the evidence-retention period of the game's tier (Core: 14 days, Advanced: 30 days, Elite: 30 days). Events and detections are deleted with their session, except while a restriction that rests on them is in force. A restriction record is deleted a year after it ends. Monthly player counts keep a hash of the player ID for 13 months. Deletion runs as an operator-scheduled job.

Rules for further player data

These constraints apply to everything above and to any later addition.

  1. Purpose-bound. A field is collected only if a specific check needs it, and it is added to the table above before the release that collects it.
  2. Scoped to the game. The SDK inspects the protected game's own files and process and the platform security state. It does not read personal files, messages, browsing history or credentials, and does not capture the desktop.
  3. Hardware identifiers are personal data. The TPM endorsement key and the identifiers above identify a device. They are stored only as hashes specific to one game, linked to a player only through sessions the game's own server verified, and never linked to each other, so a restriction cannot spread along shared attributes.
  4. Evidence is kept for review. A detection keeps its timestamps, rule version, policy version and evidence summary so a decision can be examined and reversed.
  5. Diagnostics are protected. Crash reports and diagnostic bundles are treated as potentially sensitive and are not public.
  6. Tenant isolation. A studio can access data for its own games only.