What do you need?

The email we sent says what the decision was, which rule it was about, and carries a reference code. Actions here are not issued automatically - each one is reviewed against the report that prompted it.

You can appeal it once. Quote the reference and tell us what you think we misread.

Appeal a decision →

Appeals are read in the order they arrive, oldest first. You get the decision by email at the address you filed under.

One appeal per decision. A declined appeal is final - filing again does not move you up a queue, it just adds to it. If your circumstances genuinely change later, write to support instead.

If an appeal is accepted, the restriction is lifted by a moderator as a second step, so expect a short gap between the two emails.

Every report is reviewed. Reports about physical safety - threats, self-harm, anything involving a minor - go to the front of the queue regardless of when they came in.

You can see the status of anything you reported in the app, under your account settings. We do not tell you what specifically was decided about the other account: in a harassment case, that would be a channel straight back to the person you reported.

Block them in the app first - that stops them reaching you immediately, without waiting on us. Then report them, so we can act on the account rather than just on your view of it.

If you cannot get into the app, write to us and pick Safety or harassment. Those go to the top of the support queue.

If you are in immediate danger, contact your local emergency services. We are not one.

Write to us →

It depends on the conversation, and the honest answer is: usually yes, technically.

By default, conversations are not end-to-end encrypted. The message text is stored on the server, which means staff can read it - in practice only when reviewing a report, and every time they open one is recorded. We do not read messages for any other reason, but nothing in the storage itself stops us, and you should know that rather than assume otherwise.

End-to-end encryption is available and you turn it on per conversation. Once it is on, the server holds only ciphertext and has no key for it, so nobody here can read that conversation - moderators included.

That changes what a report can show us. For an encrypted conversation the only thing a moderator sees is the copy your own app attaches, so they are looking at what you say you saw. For an unencrypted one we hold the message itself.

Use Forgot password on the sign-in screen. It sends a code to your address; support cannot reset a password for you.

A password reset does not touch your messages, but it does invalidate the copy of your encryption key that was sealed under the old password. Your recovery code is what opens it afterwards - so have that to hand before you reset.

Your encrypted history cannot be recovered. Not by support, not by anyone - the key was never held here in a form the server can open, which is the same property that stops us reading your messages.

You can still regain the account itself through a password reset, and use it going forward. What is gone is the ability to decrypt what came before.

Both are in the app, under privacy settings: request a copy of your data, or start deletion. Deletion runs after a grace period and is cancellable until it starts.

If you cannot get into the account - or you never had one and want to know what we hold about you - write to us and pick Privacy or my data. We handle those on a statutory clock.

Write to us →

This page belongs to the instance you reached it on, and so does its moderation team. If your account is on a different server, its operators are the ones who can help - this queue cannot see accounts it does not host.

For running the software itself, the API reference and the deployment guide are the place to start.