Privacy and Project Data
Atlas sends request context to the Atlas service and the selected model route. Running Codex or Claude Code locally keeps that runtime’s authentication on your machine, but it does not make Atlas an offline service or keep every prompt and result on your computer.
What can be included
| Context | How it is collected |
|---|---|
| Your prompt and conversation | The current request and retained conversational context |
| Installed-product information | Product identity, installed version, API information, and relevant catalog context |
| Project API surface | Exported types from assemblies the scanner includes, with public members and serialized private fields |
| User-authored source examples | Atlas can automatically include up to five supported script examples, bounded to 8,000 characters each |
| Selected source | Files selected for modification, review, tests, or correction |
| Attachments | Bounded object/graph snapshots, text-file content, and supported image, document, audio, or video data |
| Project instructions | Applicable AGENTS.md contents when enabled |
| Compiler information | Relevant diagnostics during correction and compilation-result information |
The client API scan is not initially limited to names that match your prompt. The service selects bounded relevant context for the model. Do not interpret “relevant context” as “only files I manually attached.” Package and Opsive vendor roots are excluded from user-source editing/example workflows; curated product API metadata is a separate input.
Local Codex route
Unity runs Codex using the local installation and its existing authentication. Atlas does not need the Codex login credentials to be uploaded. Atlas still assembles the request, validates results, and stores conversation and generation records. The model interaction also remains subject to the provider account’s terms and settings.
When Unity project tools are available, read-only inspection is on by default and Codex may inspect additional live project details. Turn off Use Unity project tools when available (Unity 6+) if you do not want live inspection. A separate per-project scene-editing opt-in permits bounded scene changes when you explicitly request them. See Providing context.
Claude Code route
Atlas runs your installed Claude Code program using its own authentication. Atlas does not read or upload that runtime’s credentials. The runtime sends model requests using its configured provider account. Atlas still coordinates the request, receives the result, validates generated source, and stores conversation and generation records.
External AI assistants
The optional Atlas plugin can return selected-object and graph snapshots, product API signatures, proposed and original source, and compiler diagnostics to the assistant you connect. That assistant’s own model, account and data settings apply to information it receives. Connecting an assistant does not make its work offline.
The Unity connection is disabled until you enable it for the project. The connection file contains a local credential: share its path only with the assistant you intend to connect, never the file contents. Disabling the connection stops access through that bridge. Credential rotation invalidates the previous credential, but a client that can still read the connection file can read the replacement; disable the connection to stop access.
Previews, operation records and original-file journals are stored under the project’s Library folder. Applying source follows your Atlas access setting and checks whether the file changed after the preview. A successful compile is separate from runtime verification. See AI assistants and skills.
API-key routes
When you configure an OpenAI or Anthropic key, it is sent to Atlas over HTTPS and stored encrypted on the server. The entered key is not retained by Unity. Atlas uses the configured key for that provider’s API requests.
Removing the key in Atlas stops Atlas from using that saved key. Revoke it at the provider as well if it should no longer be valid anywhere. Never paste a key into a prompt, screenshot, attached file, or AGENTS.md.
Local and server records
Unity stores bounded chat state in the project’s Library area so it can survive window closure and domain reload. Images and explicitly selected files also use project-local caches. Selected files are copied into the cache when attached; removing a chip does not delete the original. Generated files you apply are ordinary project files; saved plans are ordinary Markdown files.
Atlas maintains server-side conversation and generation records under its retention configuration. Clearing the local chat, removing an attachment chip, deleting the Unity cache, or signing out does not itself request deletion of server records or provider records. Removing a chip prevents it from being included in future requests in that chat; it cannot retract an earlier request.
For a data-handling or deletion question, contact Opsive through Support. Provider retention and account settings are separate from Atlas settings.
Before sharing project context
Remove secrets and unrelated personal data from source, instructions, and screenshots. Attach the smallest object or file set needed to explain the issue, and review your organization’s rules before sending confidential code. See Account and product access for device management.