Whispers Guidelines

We document patterns, not accusations. Every observation describes a manipulation tactic and the signal that revealed it. No names. No identifiable institutions. The mechanism is the point.

This is not a confession board, a naming-and-shaming list, or a grievance forum. It is a structured field log of how manipulation works in the wild, contributed anonymously by the people who encountered it.

1. Submission. You submit an observation without a name or email field. Do not include names or identifying details in the observation itself.
2. Privacy filter. Before storage, an automated filter removes common direct identifiers. It cannot recognize every contextual clue, so the form still requires you to omit details you need kept private.
3. Review. An editor sees the filtered observation and checks that it describes a pattern, not a personal attack on an identifiable target.
4. Abstraction. The editor generalizes any remaining identity clues before publishing. We remove names, specific institutions, precise dates, and other identifying information.
5. Publication. The abstracted observation is published with a sequential number, a pattern label, a category, the mechanism, and the signal. The raw submission is never published.
6. Anonymous removal. The confirmation page provides a private removal code. Keep it if you may want to delete the observation later. Deceit stores only its hash and cannot recover the code.

The Whispers form does not ask for your name or email. Deceit cannot contact you about the observation. Your private removal code is the only credential for anonymous deletion.

Anonymity protects the submitter. It does not protect the target of an accusation. We do not publish accusations. We publish abstracted patterns. If a submission is, in the editor's judgment, an accusation against an identifiable target rather than a pattern observation, it will be rejected or abstracted beyond recognition.

Whispers is excluded from analytics. No tracking cookies, no analytics beacons, no marketing pixels. The submission page promises no tracking and keeps that promise.

Cloudflare still processes the network request to deliver the site and run Turnstile. Deceit uses secret-keyed, expiring rate-limit records, but does not attach an IP address or rate-limit identity to the stored observation. This design reduces identification risk; it cannot promise anonymity against details a submitter writes into the story or infrastructure records held by Cloudflare.

This form is for pattern documentation, not emergency reporting. If you are in danger or need support, visit deceit.site/help for crisis resources, recovery guidance, and practical safety tools.

If a submission involves active danger, harassment, or immediate safety risk, use local support and platform reporting tools first. Keep the submission for later.