AOS / D01 · Personal information inventory

Personal Information Collection List

A row applies only when you use that feature. Optional or future fields are not collected merely because they appear here; the collection interface must identify required fields at the time of collection.

Status
Public version
Last updated
20 August 2026
Sections
06

01 · Public site

Delivery and security metadata.

Fields: IP address, user agent, requested URL, referrer when supplied by the browser, request time, response status, request ID and security diagnostics. Source: your browser and infrastructure. Purpose: deliver, secure and troubleshoot the service. Retention: the shortest operational period configured with the production host, extended only for a documented incident or legal duty.

  • +Required for network delivery
  • +No account matching for advertising
  • +No precise device location request
  • +Tool calculations remain in page memory

02 · Account

Identity, credentials and sessions.

Fields: user ID, email, display name, role, account status, email-verification time, creation/update time; password hash and password-change time; session ID, token hash, expiry, revocation, last-seen and creation time. Source: you and the authentication service. Purpose: register, authenticate, secure and administer accounts.

  • +Required for an account
  • +Password itself is not stored
  • +Session tokens are returned to the client but stored server-side only as hashes
  • +Production retention follows the Privacy Policy and deletion workflow

03 · Game launch and saves

The state required to continue a voyage.

Launch fields: user or anonymous subject ID, game ID, scenario, game version, locale, return URL, entitlement codes, capability scope, ticket/session expiry and use time. Save fields: user ID, game ID, slot, revision, save schema, game version, opaque save payload, checksum, create/update/delete time.

Purpose: open the intended game safely, authorise save access, detect conflicting writes and restore progress. Avoid putting real names, contact details or other unnecessary personal information in game-provided free text.

  • +Anonymous launch IDs are not automatically account IDs
  • +Save payload content depends on the game build
  • +Maximum request size is technically limited
  • +Deletion follows account and save controls

04 · Catalogue, order and payment

Transaction and entitlement records.

Fields: account ID; product, price, currency and quantity; order ID/number/status/amounts/idempotency data/timestamps; payment provider, provider references, amount/status/checkout URL/failure data/timestamps; refund and dispute status when implemented; entitlement ID/status/grant/revoke/expiry; security and audit event metadata.

Purpose: quote the correct price, prevent duplicate orders, process and reconcile payment, deliver access, provide support, prevent fraud and meet tax/accounting duties. Full card or bank credentials should be collected by the selected payment provider, not this site.

  • +Collected only when commerce launches
  • +Required to perform a purchase
  • +Some records survive account closure where law requires
  • +Provider-specific fields must be added before launch

05 · Support and rights requests

Only send what the request needs.

Fields may include sender email, subject, message, page or account identifier, browser/device description and attachments you choose to provide; for a rights request, proportionate identity-verification evidence and request outcome. Purpose: answer, investigate, document consent or comply with legal rights.

Retention: until the request and reasonable follow-up are complete, then deleted or minimised unless the record is needed for security, transaction, complaint or legal evidence.

  • +Never send a password or session token
  • +Mask payment and identity-document numbers
  • +Remove unrelated people from screenshots
  • +Support content is not used for advertising

06 · Not in the current implementation

Absence is part of the inventory.

The reviewed code does not request contacts, SMS, camera, microphone, photos, precise location, biometric identifiers, government identity numbers, health data, advertising identifiers or social graph data. It also contains no analytics, advertising or social SDK.

If a future feature needs any such information, it requires a necessity review, an updated inventory, clear just-in-time notice and any separate or explicit consent required by law before collection begins.

Next route

No provider should appear in production without a named entry.

See third-party processing