Generated from the canonical in-app source. Do not edit here.

Abuse Reports & Notice-and-Takedown

_Binding text (EN)_: 2026-09-11.2 · updated: 2026-09-09

Jurisdiction: MGA 512 (US) as reference; LGPD/CC Brazil for removal

1. The honest E2EE problem

In official courier mode we DO NOT read content, and therefore cannot pre-moderate, judge reports about what we never saw, or selectively delete what we do not store. This is deliberate.

2. What the architecture allows

Victim key disclosure: whoever received an envelope can export the key FOR THAT conversation/room. With the conversation key + the envelope, a human moderator can open and verify it against the signature. This only works for content the victim can access.

Delivery address: public and verifiable by whoever holds the matching private key. A court order that identifies a private key may, if the user complies, reveal its content.

Full-nodes: the host can read what you publish on it; reports go to the host and open as a CASE: the moderator sees the reported item and its disclosed evidence, nothing else.

3. How to report

Report through the in-app abuse channel (Settings → Help) or the abuse page on the official site. Include: a) your relationship to the case (victim/agent/stakeholder), b) description and, if possible, the envelopes and disclosed keys, c) a concrete identifier (delivery address), d) a good-faith statement under penalty of perjury.

4. What we CANNOT do

Generic surveillance orders ("show me the users"), requests without disclosed keys or legal basis, and removal of content from recipients' devices after delivery (we do not control receivers).

5. Transparency

Government requests will be honoured only under applicable law and published in a transparency report where allowed; no official-site key can decrypt user content because the site never held one.

Contact: abuse & reports · This page uses no JavaScript, no external fonts, no cookies and no analytics.