Home Privacy policy

Bureau of Ordinary Concern

Your information, without the dossier.

Effective October 23, 2026. This policy describes the application’s actual handling of submissions.

The form asks for a situation and some perspective. It does not ask who anyone is.

What the application stores

We store your selected category, written description, optional severity rating, contextual answers, moderation flags and status, random internal identifiers, fictional case reference, and submission and update times. A hashed deletion credential is stored so you can remove your record. A random submission key prevents duplicate filing when a request is retried.

The form does not ask for or have fields for names, addresses, contact details, immigration status, or identifying allegations. Do not put these in the description. Automated checks reject common identifying patterns, but cannot recognize every identifying detail. Moderators may delete inappropriate submissions.

Live messages and browser audio

Live contact is optional and starts only after you read the full satire disclosure and choose to connect. No phone number, name, email, or callback list is collected. The agent is the creator performing a fictional role.

Messages, random conversation identifiers, a hashed session key, and audio connection signals are stored privately for a maximum active session of 20 minutes. Signals can contain network addresses needed to connect browsers. Expired sessions cannot be read and are removed on a later conversation-start or administrator request. End & erase removes the active conversation and messages sooner. Closing a tab stops its microphone tracks; the session still expires if you did not choose End & erase.

Audio is transmitted through WebRTC between participants and is not recorded, transcribed, or stored by this application. Your voice and network metadata are necessarily processed to deliver the call. Direct connections can expose network addresses to the other participant. Cloudflare STUN is used for connection discovery; if the owner configures TURN, audio uses its relay. Do not share identifying details. Provider infrastructure backups and logs have separate lifecycles.

Who can see it

Only authorized administrators can read submissions through this application. There is no public feed, search, or case lookup. We do not publish, sell, or forward submissions to government agencies. Administrators can export private records for moderation; downloaded copies must be handled privately and are outside automatic application deletion.

Retention and deletion

Records are retained for up to 30 days of application availability. Expired records are excluded from review and removed from the active database when the next intake or administrator request runs. The hosting provider may retain separate infrastructure backups under its own policies.

You can delete a record earlier at Delete a submission using the case reference and deletion key from your receipt. We do not collect an email to recover a lost key. Deletion removes the active application record, including its text and contribution to live analytics.

Abuse prevention

For rate limiting, the server uses a keyed hash of the network address, time window, and action. It stores the hash and a counter, not the raw address. These records expire within one hour and are removed on subsequent requests. One-use human-check nonces expire after 30 minutes. We use a hidden spam field, request-size limits, content filters, and an arithmetic challenge. No advertising or behavioral tracking is installed.

Hosting, sign-in, and browser storage

The hosting infrastructure processes network addresses and request metadata to deliver and protect the site. A private preview may require platform sign-in. The public intake code does not attach an account identity to submissions. Administrator sign-in uses the hosting platform’s ChatGPT authentication and a server-side allowlist.

Text-size and contrast preferences are stored locally in your browser. Draft text stays in page memory and is cleared on reload or close. Receipts are only downloaded when you request it. Platform authentication may use its own cookies.

Security and privacy questions

This project uses encrypted HTTPS when deployed, server-side authorization, prepared database queries, and private storage bindings. Do not submit sensitive information. For deletion, use your receipt rather than sending personal details through another filing.