Privacy, kept on your machine.

Local run receipts

Unless you select --no-receipt, the CLI writes a JSON receipt to .clean-env/receipts/<id>.json in your current project. A receipt can contain the command (with known secret values scrubbed), working directory, timestamps, platform, exit status, manifest SHA-256, and variable names, source names, required status, and secret flag.

Receipts never contain declared secret values. Non-secret literal values are not stored in the receipt either. You control these files: delete the receipt directory, use --no-receipt, or select another local path with --receipt <path>.

Website and proofreader

The landing site does not send your manifest text anywhere, store it in browser storage, set cookies, or load third-party fonts, scripts, analytics, or telemetry. It uses a same-origin service worker only to cache the site shell for offline reading. Your browser may keep that cache until you clear site data.

Security and contact

Do not put a literal secret in a manifest. Inject it into the CLI process through your operating system’s keychain tooling and reference its variable name with from_env. For privacy questions or a suspected issue, open a private report through the project’s source repository.