Skip to content

PRIVACY.md

Latest commit

 

History

History
76 lines (47 loc) · 5.71 KB

PRIVACY.md

File metadata and controls

76 lines (47 loc) · 5.71 KB
Raw

Privacy Policy — Altimate Code plugin for Codex

Effective date: July 18, 2026 Applies to: the altimate-code Codex plugin distributed from this repository, and the data flows it initiates through the altimate-code CLI.

This policy supplements the Altimate AI Privacy Policy and Terms, which govern Altimate services generally. Where this document is silent, the master policy applies. Questions: info@altimate.ai.

The short version

  • The plugin itself collects no data. It is a routing layer (a skill, a slash command, and a static session hook) that tells Codex when to delegate a task to the altimate-code CLI installed on your machine.
  • When a task is delegated, your task text is passed to the altimate-code CLI, which sends it to an LLM provider to plan and execute the work — the Altimate LLM Gateway by default, or a provider you configure (BYOK).
  • Warehouse queries, dbt commands, and file edits run locally on your machine, under your credentials. Your warehouse credentials are never sent to Altimate.
  • The plugin ships as opt-in. Adding the marketplace does not enable the plugin — you must explicitly install it from Codex's /plugins browser and approve its SessionStart hook before any delegation happens.

What the plugin does and does not do

The plugin contains no executable service of its own. Its only runtime behavior is a SessionStart hook that prints a fixed, static text block describing the skill's capabilities. It does not read your files, does not phone home, and does not collect analytics.

Data leaves Codex's process only when the delegation skill or the /altimate command fires and invokes the locally installed altimate-code CLI.

Data flows when a task is delegated

Data Where it goes Retention
Your task prompt (verbatim) Local altimate-code CLI → your configured LLM provider Altimate LLM Gateway does not retain full prompts and responses after processing. BYOK providers: governed by that provider's policy — Altimate never sees this traffic.
Warehouse credentials (profiles.yml, env vars) Stay on your machine; used locally by the CLI Never transmitted to Altimate
Warehouse query results, dbt output, file edits Produced locally; written to a local output file surfaced back to Codex Local only
Schema metadata indexed by the CLI Local index on your machine Local only

Bring Your Own Key (BYOK): if you configure your own provider (Anthropic, OpenAI, Bedrock, Azure OpenAI, Ollama, and others), your prompts go directly from your machine to that provider. Altimate is not in the path.

Usage telemetry

The altimate-code CLI emits anonymous product usage telemetry: event names, tool categories, token counts, timing, and error types. Telemetry never includes your code, queries, credentials, file paths, or prompt content, and error messages pass through a redaction layer (API keys, emails, and internal hostnames are masked). Events are keyed to an anonymous machine ID — a random UUID generated on first run and stored at ~/.altimate/machine-id, not tied to your hardware or identity. For logged-in users, the email identifier is SHA-256 hashed before sending. The full event list is published in the Telemetry reference.

Disabling telemetry: set the environment variable ALTIMATE_TELEMETRY_DISABLED=true, or add the following to ~/.config/altimate-code/altimate-code.json:

{ "telemetry": { "disabled": true } }

Retention: telemetry is sent to Azure Application Insights and retained according to Microsoft's data retention policies; we do not maintain a separate telemetry data store. To request deletion of your telemetry data, contact privacy@altimate.ai.

Third parties

  • LLM providers — the provider you configure processes your prompts under its own terms and privacy policy. The default Altimate LLM Gateway is operated by Altimate; see the Security FAQ for its data handling.
  • Cloud infrastructure — Altimate services and telemetry run on major cloud providers with encryption in transit (TLS) and at rest.
  • OpenAI — your use of Codex itself is governed by OpenAI's terms and privacy policy, independent of this plugin.

We do not sell your data, and we do not use your data to train models.

Security

All data transmitted to Altimate services is encrypted in transit using TLS. Altimate AI is SOC 2 Type 2 certified. To report a vulnerability, email security@altimate.ai (see SECURITY.md).

Your choices

  • Don't install the plugin — adding the marketplace makes it discoverable but does not install it; delegation happens only after you install from Codex's /plugins browser and approve its SessionStart hook.
  • Use BYOK — route prompts directly to your own provider so Altimate never sees them.
  • Disable telemetry — see above.
  • Contact us — for access, correction, or deletion requests, email info@altimate.ai.

Children

The plugin and the altimate-code CLI are professional developer tools, not directed at children, and not intended for use by anyone under 18.

Changes to this policy

We will update this document in this repository and revise the effective date when our practices change. Material changes to Altimate-wide practices are governed by the master Privacy Policy.

Contact

Altimate Inc. · 440 North Wolfe Road #150, Sunnyvale, CA 94085, USA · +1 (650) 254-6266 Privacy & general: info@altimate.ai · Security: security@altimate.ai · Support: support@altimate.ai