Results and retention
What is stored, where, for how long, and what is never stored.
- Stored: bounded scorecard, requirement outcomes, cap reasons, structural metrics, run summary, adapter/model identity, version fields, and the produced-code diff as bounded text.
- Never stored: full source trees, archives, prompts, raw model responses, provider request bodies, API keys.
- Stores: Upstash Redis in deployment; an append-only local directory for organizer runs; bundled seed rows as a cold-start fallback.
- Retention: 90 days. The store interface has no update or delete; a re-run creates a new row.
Captured workspaces exclude .env files, keys, certificates, credentials, .git, node_modules, build output, binaries, and large generated content. The diff is text, not an artifact.
The public site has no accounts, cookies, analytics, or third-party telemetry. Reads are read-only; mutations are limited to the fake baseline with origin checks and shared rate limiting.