ZERO DELTA
Legal

Privacy Policy

Effective date: 1 October 2026
Publisher and controller: Zero Delta LLC (Commonwealth of Virginia, United States)
Contact: advisor@zerodelta.dev
Website: zerodelta.dev

1. Overview and core principles

Codex Advisor is an open-source, skills-only plugin integrated with Codex CLI and Codex desktop.

  • Local integration. The plugin runs from your own Codex installation. It has no Zero Delta-hosted service or remote backend; bounded consultation packets are sent through your authenticated Codex/OpenAI account.
  • No automatic Zero Delta relay. Consultation packets are sent directly through your authenticated Codex/OpenAI account. Zero Delta runs no proxy and collects no telemetry, and it does not automatically receive consultation packets or responses; Zero Delta may receive consultation content that you voluntarily include in support reports. We ask you to share only redacted receipts through the channels in Sections 6 and 7.
  • No telemetry or analytics. The plugin includes no telemetry, no analytics tracking, no crash reporting, and no MCP server.
  • Read-only child with post-execution validation. Advisor child processes are launched in a read-only sandbox and instructed to use zero tools. The launcher validates the recorded runtime after execution and rejects the result if it observes any tool call; this is an acceptance check, not preventive tool isolation. A prohibited tool call may read additional locally accessible data before rejection, and rejection cannot undo information already processed by OpenAI. The Codex runtime still sends the bounded consultation packet directly to OpenAI through your authenticated account.

2. Data categories, purposes, and recipients

Advisor handles a small, explicit set of data. This section names each category, its purpose, and who receives it.

  • Consultation packet and response, sent to OpenAI. When the root agent invokes a consultation, it compiles a bounded technical packet containing the decision question and the code context, architectural options, and repository boundaries it chose to supply. The packet is transmitted to OpenAI for inference through your authenticated account and allowance; OpenAI returns the response to your local Codex runtime. Consultations are locally launched, not locally inferred: inference is performed by OpenAI, not on your machine. The packet is not intended to carry credentials, secrets, personal data, or unrelated conversation history.
  • No automatic transmission to Zero Delta. Advisor has no relay, proxy, or telemetry backend. Zero Delta does not automatically receive consultation packets or responses; Zero Delta may receive consultation content that you voluntarily include in support reports. We ask you to share only redacted receipts through the channels in Sections 6 and 7.
  • OpenAI retention and controls. How long OpenAI retains consultation packets and responses is governed by your OpenAI account agreements and the account controls OpenAI provides, described in OpenAI's privacy policy. Advisor does not invent or enforce a separate retention period on OpenAI's behalf.

3. Local data and retention

  • Codex session logs. Consultation activity, receipts (ADVISOR CALL and ADVISOR RESULT), and decisions are recorded locally within your persisted Codex session logs, for example ~/.codex/sessions. They remain until you delete them or your host's own retention removes them. The plugin never uploads, copies, or shares persisted Codex session logs.
  • Configuration and catalog. The live advisor.toml bundled with the installed plugin controls the configured Standard and Specialist models and effort. Advanced settings and model-catalog data may be stored under your Codex home directory. These local files persist until you delete them.
  • Optional usage journal. The optional content-free usage journal is disabled by default. If enabled, it stores operational metadata and aggregate usage counters only — model identifiers, timestamps, and counters — and stores no consultation packets and no response content. Later journal writes prune entries older than 30 days and enforce a bounded count; there is no background deletion service.
  • Private consultation captures. Per-consultation captures are removed by the launcher's unconditional cleanup on normal exit; an abnormal stop may leave temporary files behind under your Codex home directory, and you can delete them yourself.
  • Model routing. Automatic Standard remains Terra/high for ordinary bounded architecture, interface, data-model, and generic-advisor decisions. Automatic Specialist remains GPT-6.1 Sol/high only when targeted evidence still leaves an eligible cross-system, compatibility/concurrency, competing-diagnosis, security/trust, recovery, irreversible-migration, or data-loss decision unresolved. The separate advisor-astra role is explicit-only, uses Astra/high, and is never selected automatically.

4. Authentication and credentials

Codex Advisor uses your existing local Codex host authentication. The plugin scripts do not request credentials or read or duplicate credential files. The consultation child is instructed to use zero tools, but a prohibited tool call could read data accessible in its read-only sandbox before the launcher rejects the result; this restriction is not a guarantee that the child cannot access credential files.

5. This website

This site is a set of static pages served from Zero Delta LLC's own hosting. It sets no cookies, loads no third-party scripts or fonts, and runs no analytics or tracking. The hosting provider Opalstack keeps standard web server access logs — the IP address, timestamp, requested path, and user agent of each request — which are processed by Opalstack and Zero Delta for security and operational purposes. The provider's standard log rotation retains these logs for about seven days, as documented for applications at docs.opalstack.com/user-guide/applications/ and for staff usage at community.opalstack.com/d/92-usage-check. Provider backup retention is separate and controlled by the provider.

6. Voluntary support email

If you email advisor@zerodelta.dev, Zero Delta and its email provider receive your name, email address, message, and any redacted diagnostics you choose to include, for the purpose of providing support. This correspondence is retained while your request is being handled and for any necessary follow-up or legal obligation. Advisor itself never sends email; contacting Zero Delta is always your choice. To request access to or deletion of your support correspondence, contact advisor@zerodelta.dev; such requests are handled subject to applicable constraints, including legal obligations that may require retention.

7. Voluntary GitHub issue reports

The GitHub issue tracker at github.com/dave-schmidt-dev/advisor/issues is an optional, public support channel. Filing an issue is voluntary and user-initiated; Advisor never opens, edits, or comments on issues on your behalf. If you file an issue, GitHub receives your GitHub profile identity, the issue text, and any redacted diagnostics, system versions, and ADVISOR receipts you chose to include, for the purpose of bug resolution and support. The report is received by Zero Delta and GitHub and is readable by anyone: public issues are public and searchable. We retain public issue discussions as support and bug-resolution history unless the content is removed. Editing a report or deleting your GitHub account does not guarantee that its earlier content disappears. You can edit content you control and email advisor@zerodelta.dev to request removal of personal data from reports we can manage. GitHub controls its own retention and backups; copied, cached, or quoted copies may remain elsewhere. How GitHub handles your data, including retention and account deletion, is described in GitHub's privacy statement.

For anything you would rather not file publicly, use the private email channel in Section 6 instead. Do not include secrets, credentials, or raw session logs in any report.

8. User control and data deletion

You can inspect, modify, archive, or delete local user state with standard operating system tools: Codex session logs, configuration and catalog files, and the optional journal (via journal clear and journal disable). For data held by OpenAI, use the controls of your OpenAI account. Uninstalling the plugin may leave user state and session logs behind; those are managed separately and can be removed by you.

9. Changes to this policy

Updates to this policy are posted on this page with a revised effective date.

10. Contact

Email is the contact channel for privacy inquiries: advisor@zerodelta.dev. A postal address is available on request.