Privacy

Effective July 17, 2026. BeforeDone is a local, open-source developer tool. It does not require an account and the BeforeDone project does not operate a data collection service.

What BeforeDone stores

The CLI stores its local receipt key, evidence receipts, command logs, a normalized event ledger, replay cases, and incident reports under .git/beforedone in your local repository. It may read Git state and files matched by the relevant-file patterns in .beforedone.yaml.

Event summaries and redaction

Codex lifecycle payloads and normalized Adapter imports are redacted and normalized into bounded event summaries before persistence; BeforeDone does not require a raw transcript. An optional transcript is unstable narrative context, never a trust source or an input to First Observable Divergence. BeforeDone accepts at most 4 MiB, applies redaction, and persists only a bounded 16 KiB excerpt plus its SHA-256 digest and a truncation flag—not the raw transcript.

Built-in secret patterns, your configured capture.redact_patterns, and output size limits are applied before supported check output, event summaries, replay output, user corrections, and the optional transcript excerpt are persisted. Redaction is best effort and cannot guarantee removal of every secret or personal detail.

Evidence receipts intentionally preserve the verifier's actual command arguments and working-directory metadata so reviewers can see what ran. Output redaction does not rewrite those structural fields. Do not place credentials in command-line arguments; prefer environment-based or native credential mechanisms, avoid sensitive path names, and review metadata before sharing artifacts.

Retention and deletion

reports.retain prunes older incident directories when a new incident is created. In v1 it does not automatically prune receipts, command logs, or the event ledger. To erase all local evidence, first remove the selected Codex integration, then review and manually remove .git/beforedone. Remove .beforedone.yaml separately only if the repository should no longer define checks.

What BeforeDone sends

BeforeDone v1 has no telemetry, advertising, analytics SDK, cloud account, or hosted API. The CLI, Plugin, and Skills do not send project evidence to the BeforeDone maintainers. Checks and explicit replay execution can still access the network if the configured command does so; a detached worktree is not network isolation.

Local storage is not an attacker boundary

A malicious process running as the same operating-system user with repository write access can read or replace the local receipt key, edit configuration, and rewrite runtime artifacts. It can manufacture a self-consistent PASS. BeforeDone is designed for non-adversarial early completion and stale evidence, not for proving claims against a hostile same-user Agent.

Reports and sharing

Incident reports and replay cases are local artifacts until you choose to share them. Redaction reduces accidental disclosure but cannot guarantee that every secret or personal detail has been removed. Review artifacts before publishing or attaching them to an issue.

Optional third-party installers

The no-telemetry statement covers BeforeDone. Optional tools such as skills.sh are separate projects and may collect their own usage data. Consult their policies or set DISABLE_TELEMETRY=1 when using that installer.

This website

This static site uses no cookies and no third-party analytics. It is hosted by GitHub Pages, so GitHub may process request information under its own privacy terms. Links to GitHub or other sites are governed by those services.

Questions or security reports

Use the contact method in the repository's security policy. Please do not include sensitive repository data in a public issue.