How evidence is collected, stored and used
Encrypted before it leaves your browser. Read only by named reviewers. Never published in a way that re-identifies you without your written consent.
What happens to your submission
Submissions travel through a single, narrow pipeline. Each stage has a published rule and a named owner.
In your browser
The form encrypts the body of your submission before it leaves your device using a per-submission symmetric key.
In transit
TLS 1.3 with HSTS preload. Server certificate transparency monitored continuously.
At rest
Stored encrypted at rest in a Postgres cluster behind a firewall. Decryption keys are split between operations and review.
In review
A named reviewer accesses a decrypted copy in a session that is fully audit-logged. The plaintext is not persisted to disk.
Useful evidence - and evidence we will refuse
We are deliberately strict. The rules are public so you can decide before you spend the time.
Documented platform behaviour
Screenshots, chat exports, transaction records, complaint receipts, platform responses.
Pattern evidence
Multiple independent victim reports referencing the same handle / wallet / studio.
Independent journalism
Reporting from publications with a named editor, fact-check process and right-of-reply policy.
Refused - intimate content
We will not accept non-consensual intimate imagery in any form. Hash it via StopNCII or NCMEC and send the hash + context.
Refused - identifying minors
Do not send identifying material about any minor. Report to NCMEC / IWF / your national child-safety hotline first.
Refused - anonymous accusation
We will not act on accusations without underlying evidence and at least one verifiable identifier.
Ready to submit?
The intake is multi-step, you can save and return, and you can submit anonymously. Everything is encrypted at rest.