Community standards

Whispers guidelines

whispersofdeceit.com is a community observation layer for documenting manipulation patterns. These guidelines describe what to submit, what gets rejected, and how the editorial process works.

The principle

Document the pattern, not the person.

Patterns are documented, 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.

A useful observation

What to submit

  • Describe the tactic, not the person. No names of individuals.
  • No names of specific identifiable institutions. Generalize to a category (workplace, family, religious, medical, state, platform, relationship, school, financial, other).
  • Focus on the mechanism: how did the pattern work?
  • Include the signal: what tipped you off?
  • Use a vague time reference (last spring, a few years ago). Never precise dates.

Rejected at intake

What gets rejected

  • Names of individuals, specific organizations, or identifying details.
  • Accusations against identifiable targets. We publish patterns, not accusations.
  • Active emergencies or crisis disclosures. Use local support and platform reporting tools first.
  • Doxxing, threats, harassment, or incitement to violence.
  • Content you do not have the right to share.
  • Promotional material, spam, or off-topic submissions.

Editorial process

What happens after you submit

Nothing is published automatically. Every observation passes through privacy filtering, human review, and editorial abstraction.

  1. 01

    Submission

    You submit an observation without a name or email field. Do not include names or identifying details in the observation itself.

  2. 02

    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. 03

    Review

    An editor sees the filtered observation and checks that it describes a pattern, not a personal attack on an identifiable target.

  4. 04

    Abstraction

    The editor generalizes any remaining identity clues before publishing. We remove names, specific institutions, precise dates, and other identifying information.

  5. 05

    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. 06

    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.

Privacy

Anonymity and its limits

The intake is designed to collect the pattern without collecting an identity. That promise has clear limits.

Built for anonymity

No name. No email.

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.

No audience tracking

No analytics or marketing pixels.

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

The limit

Anonymity cannot make an accusation safe.

Anonymity protects the submitter. It does not protect the target of an accusation. Accusations are not published. Abstracted patterns are. 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.

The site is served from our own server; no third party sits in front of it. 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 our hosting provider.

If you need support

Use support resources first.

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.