# Privacy, security & ownership

Engines of Creation, LLC operates EoC. This page explains practical product behavior. The [Privacy Policy](/legal/privacy), [Terms](/legal/terms) and any applicable source license contain the governing details. Contact [support](/help) or [nick@enginesofcreation.xyz](mailto:nick@enginesofcreation.xyz) about account, privacy or security concerns.

## Know where your work goes

| Action | Data boundary |
| --- | --- |
| Work in a browser project | Drafts and project records are stored on this device |
| Ask an AI service for help | The selected service receives the task and relevant context through the supported connection |
| Upload an optional private backup | Supported project data is sent to account-scoped storage; credential vault and session keys are excluded |
| Use a hosted Studio workspace | Its services process project source, revisions, output and related records |
| Publish a browser game | Its playable build and source become publicly accessible |

Private hosted project artifacts are encrypted at rest by the application. This does not mean AI requests remain entirely on your computer. Providers apply their own data-handling policies, and hosting services process ordinary technical request metadata.

## Protect your connections

A quick API connection is tab-local. Saved personal API connections use an encrypted vault on this computer, separated by account. The vault password is not recoverable by EoC. A locked vault protects stored data; it cannot protect an unlocked session from a compromised device or malicious extension.

For supported API requests, the relay temporarily receives the credential to contact the provider. Native subscription sign-in uses official provider clients. Never place credentials in prompts, game source, public assets or screenshots. A server environment file is a private configuration file, not encryption. See [AI connections](/docs/api-keys).

## Keep sharing deliberate

Publishing a browser game exposes its source. Check for private information and confirm the rights to every included asset before publishing. Discovery in the community catalog is a separate opt-in and review step. Unpublishing cannot recall copies that someone already downloaded or remixed.

You retain rights in your original contributions. Third-party code and assets keep their own terms. Licensed Studio source editions have separate conditions, including restrictions on source redistribution and applicable royalties. A source download or ownership statement does not override those licenses. Read the [Studio Source Code License](/legal/studio-source) for covered editions.

## Understand the protection boundaries

The product uses account and project access checks, explicit sharing controls, source checks, review, and recovery safeguards. Preview restrictions reduce exposure, but complete preview network isolation is not established. Do not use an untrusted project to handle secrets or sensitive material.

Automated tests and independent AI review are not an external security audit, certification, or assurance that generated code is safe for every use. Review code and dependencies before operating a real service or handling funds.

## Diagnostics and deletion

Optional build diagnostics have a separate account control; enabling private backups does not enable diagnostics. Visitor analytics have separate consent controls. Withdrawing consent stops future optional collection; it does not automatically delete prior records.

Local storage deletion, project-record deletion, public unpublishing and account-data deletion are different actions. Export anything you need first, then use the relevant control or contact EoC for an account-data request.