Document the incident.
Leave people out of it.

What belongs in the record

Minor incidents in web development, IT, AI, and engineering. Write in your own words. You do not need to be funny or know the technical cause. The joke concerns the situation, process, or tool behavior—not a person's experience level.

Leave out identifiable people, employers, clients, private conversations, confidential material, credentials, and promotional spam. Reports and witness statements are plain text only. An editor reviews each contribution before publication.

Publication permission

Submitting a report with permission lets the Bureau publish your account and chosen attribution on this website and its share cards. Editors may redact identifying details and lightly edit for clarity. A material rewrite is held for your approval through your private management link. No reply means no approval.

A witness statement has its own publication permission. If approved, it may appear on the related case and in a weekly docket. Its private link shows moderation status and provides withdrawal. Pending statements are visible only to the contributor and editorial desk.

The original stays private. Published community reports and statements are accounts supplied by contributors, not independently verified investigations. Invented Bureau cases are labeled fictional. Editors must not add invented quotes, events, causes, or damage.

Published anonymously

The default attribution is Anonymous developer. A pseudonym is optional. No account, email, location, or employer is requested. Anonymous does not mean untraceable: the hosting provider and abuse controls may process technical request data.

Private management links give access to status, approval where required, and withdrawal. Save them somewhere safe. We store protected representations of the tokens, not the links themselves. Anyone with a complete link can manage that contribution. With no contact address, a lost link cannot be recovered.

Reactions and content reports

“Evidence accepted” means that an incident sounds familiar. It is not factual verification or editorial approval. A long-lived anonymous browser cookie supports one reversible reaction per case; the server stores a protected representation rather than the cookie value. Clearing browser data or using another device can create another anonymous session.

Every case and published witness statement has a content-report action. Reports enter a private editorial queue and do not remove content automatically.

Retention and removal

Withdrawal removes the private contribution text, public case or statement, and first-party cards where applicable. A minimal private receipt and moderation record remain for editorial accountability until retention maintenance removes them. External copies and caches may remain.

The review retention period must be configured before intake opens. The editorial workspace provides a retention-maintenance control; this release does not promise automatic timed deletion.

Measurement and abuse controls

The service counts successful submissions, publications, and reactions without sending story text, pseudonyms, or private links to analytics. Rate limiting uses temporary hashed request keys; expired keys are removed on subsequent participation. Hosting request logs are controlled by the hosting provider.

Editorial standards

Acceptance and timing are editorial decisions. Intake can pause when the queue is full. You may withdraw through the relevant private management link. The Bureau does not automatically subscribe contributors to email or post their stories to social accounts.