Your work stays connected to your account and projects.

What Genesis handles

• Account details such as email, display name, profile image, role, and authentication factors.
• Projects, games, scenes, assets, scripts, references, settings, review decisions, and collaborator access records.
• Ask Genesis prompts, responses, selected skills, feedback, and bounded project context needed to answer a request.
• Generation requests, provider receipts, usage, cost, job state, validation results, and publish or export history.
• Operational data such as session cookies, request identifiers, security events, privacy-bounded automatic crash envelopes, diagnostics, and bug reports you choose to send.

Why it is used

Genesis uses this data to authenticate you, save and render your work, run reviewed AI and generation actions, enforce budgets and permissions, collaborate safely, diagnose failures, prevent abuse, and maintain release evidence. Automatic crash reports contain a local route path, release identifiers, and a bounded technical error record; they exclude URL query values, prompts, authored content, assets, referrers, raw network addresses, and credentials.

A hosted-game report can be sent without an account. It contains a closed problem reason, an optional note of up to 500 characters, and server-resolved release identifiers. A keyed anonymous fingerprint supports abuse prevention and retry safety; the playable token, raw network address, user agent, email, game state, screenshot, and browser diagnostics are not stored. Reports are visible only in Genesis's authorized admin inbox.

AI actions are scoped to the current account, project, or editor room. Genesis presents reviewed changes before authored state is changed where the workflow requires review. Provider credentials and another user's private content are not included in your account export.

Services involved

Genesis relies on configured hosting, database, storage, authentication, observability, and AI or media-generation providers. A provider receives only the material required for the action you request, subject to that provider's terms and the deployment's configuration. Paid generation remains a separate estimate-and-approval step.

Retention and deletion

Account and project data is retained while the account or shared production work remains active. Short-lived processing records expire according to their recorded retention class; operational, cost, security, and immutable review records may be retained longer for integrity and reconciliation.

Deleting an account removes the sign-in identity, profile details, API keys, personal Ask Genesis history, memberships, presence, and active sessions. The account email is also removed from retained audit entries, bug reports, and known copied-email fields. Authored games and assets, including shared work, plus cost records, immutable receipts, and audit history remain under an anonymized identifier so collaborators keep their work and the production ledger stays coherent. A deletion request is permanent and the account cannot be reactivated.

Your controls

• Download a structured JSON copy from Settings → Security → Download account data.
• Export binary assets, complete games, and published packages from their Project, Asset, or Editor delivery controls.
• Revoke other sessions, manage two-step verification, change profile details, or delete the account from Settings.
• Use the in-product bug reporter for a privacy or data-correction request; include no password, API key, or authenticator code.
• Use Report on a hosted game without signing in; do not include personal or account information in the optional note.

Questions

Visit Genesis support for recovery steps and the authenticated reporting path. This private-preview notice will be updated when the product's providers, purposes, or commercial terms materially change.