Privacy

What this site records, what it does not, and what happens to anything you send us.

The short version

No public accounts, no advertising, and no third-party tracking. A first-party counter records only approximate daily visitors and page views; personal information is otherwise held only when you submit a correction request.

What the server records

Operational logs record request time, method, path, and status. Transient in-memory rate-limit counters use the network address. No profiles are built and no cross-page identification occurs.

First-party audience counts

Each page load and in-site navigation sends an empty event to this site's own server. It contains no page path, title, referrer, campaign data, screen details, or client identifier. A secret-keyed, day-specific transformation of the network address estimates daily unique visitors without storing the raw address or creating a cross-day identifier. The day-specific codes expire after two completed UTC days; only daily aggregate visitor and page-view totals remain.

Cookies

No advertising or public-visitor analytics cookies. One functional cookie stores a sidebar preference; hosting infrastructure may set a technical routing cookie. A signed eight-hour security cookie is set only after the owner signs in to the private analytics page.

Correction requests

A correction request stores the request details, proposed value, justification, contact details, and source network address. Personal content is encrypted, visible to reviewers only, excluded from public pages, the API, and exports, and erased automatically after 12 months while the decision remains.

Organizations named in claims

The site republishes narrowed allegations: attacker prose, leaked-material links, contacts, and infrastructure are stripped, and rows that fail safety checks are quarantined. Affected organizations can use the claim correction form on any claim page.

Your choices

No account data normally exists. Correction submitters can request early erasure, and the functional cookie can be blocked without losing access. Privacy questions go to the listed contact email; see also the terms of use.

Explore the tracker

Victim records are provider-reported allegations, not independently verified breaches. Published for research, defense, and educational use.