MVP privacy notice
Small data footprint, clearly explained
Last updated: 13 August 2026
What we store
When you request a reset, vote or submit a comment, the server creates a random browser actor identifier. It is signed and stored in an HttpOnly cookie. In each active cycle, one browser can add one standard RESET signal and one additional terminal easter-egg signal.
Community content and AI review
Submitted comments, replies, optional public names, plan labels, helpful votes and poll choices are stored in Cloudflare D1. A server-side AI safety and relevance check may process submitted comment text when the operator enables that feature. Suggested wording is never published without the author choosing it. Only approved comments may be included in an aggregate Community Pulse brief. We do not require a public account, email address or Codex credentials.
Questions to Reset Agent
A public question may be sent to OpenAI together with aggregate site facts when agent answers are enabled. The site does not save the question or generated answer in D1; it stores only operational metadata such as use case, prompt version, model, timing, token counts and a safe error code. If OpenAI is unavailable, the server returns a clearly labelled D1-only fallback.
What we do not collect
The MVP does not request access to your OpenAI account, Codex usage, billing, precise location, contacts or payment history. Agent Fuel is a manually maintained indicator and does not track donations automatically.
Local time
Your browser formats UTC timestamps in its own IANA timezone. The timezone is used for display in the page and is not derived from GPS or IP geolocation.
Infrastructure and retention
The site uses Cloudflare Workers and D1 for its public service. Operational logs may be retained for security and reliability, without intentionally logging comment text, authentication tokens or secrets.