Mystery belongs to the presentation, not to data handling. This notice explains the traces that may be created when you visit or contact 0FZ.
Information received
If you use the contact channel, 0FZ receives the fields you choose to provide. The server and protective systems may also record routine technical information, including an IP address, browser type, requested address, referring page, and timestamp.
Why it is used
Information may be used to operate and protect this site, prevent abuse, deliver and respond to messages, maintain backups, and meet legal obligations. It is not used to build an advertising profile or sold as personal data.
Cookies and connected systems
The public site does not intentionally deploy advertising or behavioral-analytics cookies. WordPress, the contact form, and authenticated administration may use essential cookies or security tokens. Hosting, email, security, and backup providers may process limited information where necessary to perform those functions.
Retention and disclosure
Records are kept only as long as reasonably needed for operational, security, communication, backup, or legal purposes. Information may be disclosed to supporting providers, when required by law, or when necessary to protect the site and its users.
Your choices
Privacy rights vary by location. You may request access, correction, or deletion through the . Some records may need to be retained for security, backup, or legal reasons.
Effective: 25 July 2026
Interactive signal channel temporarily unavailable. Public records remain available.
Browser progress data
0FZ stores non-sensitive game progress and accessibility preferences in browser storage on your device. That progress stays local unless you deliberately submit the optional witness form described below; only then are the selected completion facts copied into a separate form submission.
When Transmission One first reaches its archived state, the browser sends only that completion transition to the same 0FZ site. It does not send the selected route, answers, handle, email, or other game state. The response sets a signed, HttpOnly completion cookie that unlocks the separate Dead Drop contact route for 180 days. The cookie survives reloads, browser restarts, and chapter restart; Reset All asks the site to clear it. Ordinary web-server logs may still record the request in the same way as other page requests.
If persistent browser storage is unavailable, validated progress uses temporary browser session storage so play can continue across pages and reloads in the same tab. This fallback ends when that tab closes. If both storage methods are unavailable, progress remains only in the current page memory.
No account is required. The stored data includes chapter flags, normalized puzzle drafts, recovered or pinned evidence IDs, branch choices, casualty state, and sound, volume, motion, or effects settings. It does not include raw failed answers, terminal commands, device data, contact information, or anything entered into the contact form. Contact form submissions use a separate route and are not part of browser progress data.
You can clear local progress through the game reset controls or through your browser controls. A chapter restart retains accessibility settings, a bound witness identity, and the earned Dead Drop completion cookie; it clears an unbound choice so the next completion may bind a handle. A full reset removes only 0FZ-owned browser progress and continuity keys and requests removal of that cookie. If this browser held a bound identity, that continuity key cannot be recovered after Reset All. Neither reset deletes a witness record, public handle, Gravity Forms entry, or operator email that you previously chose to submit; a published handle remains reserved on the server.
Optional witness records
Finishing Transmission One does not automatically submit a witness record. The separate witness form is accepted only while this browser carries the signed completion grant. If you deliberately choose to bind a handle or continue with an unbound receipt, that form transmits the selected completion-route details, a receipt timestamp, your IP address, browser user agent, and anything you enter in the handle or email fields. The grant supports the intended browser flow; it does not prove which person completed the chapter.
A bound handle is published in the discoverable Transmission One witness archive. Its private continuity key remains only in the same browser profile. A lost first response can be retried from that same browser while its pending receipt and original completion grant remain available; a handle, email address, or new browser grant cannot recover it. Optional email verification does not restore identity on another browser or device. An optional email address remains private but may persist with the protected form entry even if you do not select notice consent or never complete verification. It becomes eligible for a Transmission Two opening notice only after separate opt-in and verification. An unbound receipt stores no handle or email and never creates a public registry row; Continue Unbound applies only to that completion, so chapter restart offers the choice again.
A daily WordPress cleanup is configured to clear full IP and user-agent values from protected form entries once they are at least 30 days old; WordPress cron can run later than its scheduled time. The fixed operator receipt contains only a masked IP range and coarse browser, operating-system, and device categories, plus any email you deliberately entered. WordPress cannot erase that Gmail copy automatically. For a verified erasure request, the operator must search the mailbox by event ID or submitted email, delete every matching receipt, and empty Gmail Trash; otherwise the mailbox copy remains under the Gmail account retention settings until it is manually deleted. The mailbox is not part of the public archive.
A daily cleanup is configured to remove unbound receipts once they are at least 90 days old. A bound public handle and optional private email remain with the witness record until they are unpublished or erased through the site privacy-request process. Withdrawing verified notice consent makes the address ineligible for future transmission notices but does not itself delete the private email, public handle, form entry, or operator receipt. Only the handle, Transmission 001 label, and returned status are exposed by the public archive command.
CONTINUITY LINK UNAVAILABLE — PROGRESS WILL END WITH THIS TAB.