Privacy / Updated October 22, 2026

Privacy Policy

What leaves your machine, and what stays in your repository.

This policy describes the arnx CLI, arnx cloud, and this website, reviewed on October 22, 2026. CLI version 0.1.0. ARNX is the operator of arnx.dev; contact [email protected] about privacy or data requests.

Your own keys and arnx Cloud

With your own API keys, inference requests go from the CLI to the providers configured in .arnx/config.toml. Those providers receive the request content under your account and their API terms. BYOM does not mean all processing stays on your machine.

Start with $5 in Cloud credit. Tool calls, Docker tests, the before/after check, and report generation run on your machine. arnx cloud receives the diff, the files the agent reads, the tests it writes and their output, then passes them to its model providers. Read the Cloud service terms before sharing code. Contact [email protected] for provider, retention, or data-handling questions specific to your use.

arnx cloud accounts

Sign-in goes through GitHub. We receive your GitHub account ID, login, and email address if shared. Your credit balance and its ledger are kept per account.

Payments are processed by Stripe, which sends receipts and invoices by email. Card numbers go directly to Stripe; arnx never sees them. Top-ups open soon.

Review content passes through arnx cloud to its model providers. After a review, arnx cloud keeps account-linked review records, including status, timestamps, and billed usage by role, alongside the credit ledger. For questions about review-content retention, backups, or model providers’ handling of your data, contact [email protected].

What can be submitted to a model

.arnxignore and secret-file/content filters exclude recognized sensitive material. Filtering is not exhaustive. arnx allow-secret can allow particular key-shaped content; do not use it to expose real secrets.

Setup and review normally omit untracked files in repositories with commits. --untracked or [review] untracked = true includes them, and --no-untracked overrides that setting. With no commits yet, non-ignored files form the initial change. Inspect the scope before proceeding.

What remains local

Tests execute in Docker against a repository copy. Image builds can use the network; test runs have no external network, or an internal network for configured services. The CLI stores configuration, reviews, generated tests, acceptance records, and usage logs under .arnx/. Accepted tests are copied into project test directories. You control their retention and whether to commit them.

These reports can contain code and provider responses. Sanitize them before sharing. Read the execution boundaries.

This website

Privacy requests

Contact [email protected] to request access, correction, export, or deletion of personal data held by ARNX. For data held under your own model-provider account, contact that provider. We do not sell your data or use it for advertising. Processing by hosting, analytics, and model providers can occur outside your country.

Contact

ARNX
[email protected]