Privacy | Codex Rescue

The error text you paste

Matching happens entirely in your browser. The text you paste into the matcher is:

not uploaded to any server,
not written into the page URL,
not written to browser storage,
not sent to analytics.

You can confirm this yourself: open your browser's developer tools, paste an error and run the match, and watch the network activity. The only requests that occur are the ones described below.

What is stored in your browser

Reset timers. The label you give a timer, the absolute reset time, the UTC offset you confirmed, and when you created it. Stored in localStorage under codexrescue.timers.v1. There is a Clear saved timers button on the limits page; clearing it removes the entry.
Beacon participation. If you light a Reset Beacon, the server sets a random, host-only cookie so it can tell whether this browser already participated in the current round. See below for what the server keeps.

No analytics script, advertising script or third-party tracking script is loaded by default. If a deployer switches on privacy-preserving analytics, this page is updated first. The site does not integrate a paid analytics platform.

What the server keeps

Two features involve a server request, and only these:

The reset signal API (/api/watch, /api/timeline). These read published data and return it. They do not receive anything about you beyond an ordinary HTTP request.
The Reset Beacon counter (/api/beacons). When you light a beacon, the server records a nickname drawn from a fixed vocabulary and a hashed participant identifier. It does not record your raw IP address beyond what is needed to rate-limit abuse, and it does not store the error text or anything else you typed.

The beacon counter stores a one-way hash, not a device fingerprint. There is no cross-site tracking, no advertisement identifier, and no attempt to identify you.

Cookies

The only cookie this site sets is the beacon participation cookie. It is host-only, so it is never shared with a parent domain, and it is marked HttpOnly and Secure.

What this site cannot do

It cannot read your Codex account, your usage, your plan or your reset time.
It cannot tell when your access returns.
It has no account system, so it holds no credentials of yours.

Changes

When the network behaviour of this site changes, this page is updated in the same change. The date below reflects the last time this page was reviewed.

Last reviewed: 2026-09-20.