Privacy policy
This policy explains the limited information involved when you visit DoomBench and follow links to the evidence it cites.
Information handled by the site
DoomBench accepts website feedback, evidence leads, and possible disclosures. A submission may include its text, a public source URL, an optional name, and an optional contact email. Signed-in visitors are attributed by default and can explicitly request anonymity. Potential disclosures may be sent without an account. Other anonymous submissions require an explicit choice and confirmation.
The site may also receive ordinary technical records needed to deliver and protect a website, such as request times, requested pages, device or browser information, network information, and error or security events.
Email addresses voluntarily entered into sign-in or consented feedback flows are normalized into one private contact registry. The registry records where an address was supplied, whether it was verified, relevant delivery results, account and feedback-contact status, newsletter status, lifecycle status, and first and latest activity dates. These statuses remain separate because retaining an address does not grant permission to use it for every purpose.
Public discussions
Section discussions are publicly readable. Posting, replying, voting, editing, or reporting requires sign-in with a verified email address. A public author label, comment text, timestamps, edit state, and vote counts may be shown beside a contribution. The authenticated account identifier and email are stored for ownership, abuse prevention, and moderation, but are not displayed in the public thread.
Vote changes, prior comment text, reports, and administrator visibility decisions are retained in audit records. Hiding or archiving a comment removes its public body without changing evidence, model profiles, or scores.
Public account sign-in
DoomBench sends a one-time 10-digit code to the email address a visitor provides. Codes expire after 10 minutes and can be used once. DoomBench stores the normalized email address and sign-in delivery state when a code is requested, including before the address is verified. Successful verification promotes that address to a verified account record. DoomBench also stores a profile name, an optional avatar URL, and a secure session record to attribute owned contributions and prevent abuse. Plaintext codes and session tokens are not stored.
Resend delivers sign-in email from no-reply@doombench.com. A default avatar is generated by DoomBench from a one-way digest of the account email. A visitor may instead provide an HTTPS avatar URL, in which case the image host receives the ordinary request information needed to deliver that image.
ChatGPT sign-in is used only for the restricted administrator area. It is not offered as a public account method.
Feedback, contact details, and possible disclosures
Contact email is optional and is stored only when the visitor explicitly agrees. It is added to the private contact registry with feedback-contact permission and may then be used to ask about that submission. A signed-in identity is stored unless the visitor explicitly requests anonymity. Private feedback submissions are visible only to authorized DoomBench administrators and do not change the index automatically. The private queue records status changes, editorial routing, administrator identity, timestamps, and private review notes in an append-only moderation history.
The feedback form is not an encrypted or secure whistleblower service. Visitors must not submit classified, illegally obtained, confidential, or personal information. DoomBench does not accept file uploads through this form.
Analytics
DoomBench uses AI Brain analytics to understand broad site usage and maintain the publication. Analytics and hosting systems may process limited technical and usage information when pages load. Feedback content and optional contact information are stored separately from public analytics.
How information is used
- Deliver, secure, diagnose, and improve the website.
- Understand which public pages and evidence are useful to readers.
- Review corrections, evidence leads, possible disclosures, and product ideas.
- Operate public discussions, count votes, handle reports, and moderate abuse.
- Deliver one-time sign-in codes and maintain signed-in account sessions.
- Contact a submitter only when an email address and consent were provided.
- Maintain purpose, provenance, delivery, and suppression status for voluntarily supplied email addresses.
- Investigate abuse, outages, errors, and threats to the service.
- Meet applicable operational or legal obligations.
Sources and external links
Evidence cards link to third-party publications, company sites, research pages, and other sources. Those services operate under their own privacy practices. DoomBench is not responsible for how an external service handles information after you follow a link.
Retention, safeguards, and changes
Technical information and submissions are retained only while operationally useful or required for review, audit, security, or legal obligations. Rejected or archived submissions remain separate from scored evidence. Accepted corrections enter a verified editorial queue and still require a separate evidence revision process. No online service can guarantee absolute security. Reasonable measures are used to restrict the private review queue and protect the systems involved in publishing DoomBench.
The contact registry may retain unverified, verified, consented, failed-delivery, unsubscribed, or suppressed addresses so DoomBench can preserve provenance, honour communication restrictions, prevent abuse, and avoid contacting an address contrary to its status. Account registration or feedback contact permission is not newsletter consent. DoomBench will require a separate affirmative newsletter subscription before sending newsletter or marketing updates. A visitor can use the feedback page to request access, correction, suppression, or erasure review for an address associated with them.
This policy may change as the site, its analytics, or its operational needs change. The updated date above identifies the current version.