Privacy, and how data is handled here

“Privacy” here means two separate things, and this page covers both: what this site collects from you while you read it (next to nothing), and how it treats the data of the people who appear in the writeup — which is the whole reason this writeup exists in the first place.

1 While you’re reading this

This is a static set of pages. It is built to learn as little about you as possible.

• No analytics, no tracking pixels, no advertising, and no third-party scripts. The only JavaScript on the writeup is the small redaction toggle and the counters, and it runs entirely in your browser.
• No cookies are set, and nothing you do on the page is sent anywhere or stored by it.
• The pages are served with referrer: no-referrer and marked noindex, so they don’t feed search engines or leak where you came from.
• Like every website, the host or CDN that serves these files may keep standard server access logs (IP address, user-agent, timestamp) for security and reliability. That is outside these pages’ control and isn’t used to profile you.

2 The people who appear in the writeup

The writeup is about data — so it holds itself to a deliberately tight standard about whose data it shows:

• Only the operator and the bot are named. Every other person’s name, nickname and the dates around them are removed.
• User and channel IDs are blacked out by default; the reveal toggle is there so a technical reader can verify, not so anyone gets exposed by accident.
• Any display names shown are public Discord names already visible to everyone in the relevant server — nothing private is unmasked.
• Message content is trimmed to the minimum needed to make a point. Nothing is invented or rearranged to change its meaning.

3 Where the evidence came from

Nothing here was obtained by intrusion, account access, or any unauthorised means. The data files and the operator’s own messages were volunteered by the operator, and the public statements were said openly in his community server. No credentials, tokens, API keys, private emails, or the owner’s account ID are published anywhere in this writeup.

4 If you’re someone shown here

This matters most for the people the writeup talks about, so it gets its own section:

• Corrections. If something is factually wrong, it will be fixed. Accuracy is the entire point.
• Right of reply. The subject is welcome to respond, and a fair response will be linked or included.
• Removal & further redaction. If you were caught up in this without being a subject — a bystander, a name that slipped through — ask, and it will be removed or redacted further.

5 Children & sensitive data

This writeup does not knowingly publish a minor’s personal information or any special-category personal data. If you believe something here does, flag it at the address above and it will be acted on promptly.

6 Changes

If this policy changes in a way that matters, the date below will change with it. The standard it describes — show as little as possible, name as few people as possible, and fix what’s wrong — will not.

Last updated June 12, 2026