Trycord
Create account Open the app

Help

Support and community

Trycord is software you run yourself, so the person who can fix most problems is the operator of the instance you are on. This page explains which problem belongs to whom, and where the rest of the community talks.

Legal review required before publication. This document comes from the Trycord project as a starting point for an instance. It is not legal advice, and nobody has reviewed it for the instance serving it. The fields marked OPERATOR are facts only the operator can supply: the address for support, the address for privacy requests, the address for formal notices, and any response times the operator commits to. Fill them in, and have a qualified lawyer read the result, before presenting this document as binding. The contact points in these documents are the project's own. If you run your own instance, replace them with yours before you publish them.

Version: 1.0 · Template last revised: 2026-09-20 · Effective on this instance: OPERATOR: the date this support policy takes effect on this instance

1. Start here: which instance are you on?

This decides who can actually fix your problem.

  • An official instance, run by the project or by a partner and listed in the app. One party operates all of them, so you can escalate straight to that party. See the official instance terms.
  • Your own, or a community's, run by whoever set it up. They are the operator, they control the data, and they are the only people who can change anything.

If you are not sure, the instance's name and owner are shown in the application, and self-hosted instances usually publish an admin contact of their own.

2. An account, community or content problem

A ban, a timeout, a deleted message, a role you think you should have, a channel you cannot see: this is moderation, and it belongs to the instance operator or the community moderators, not to the project. They can undo what they did. The project cannot, because it does not run your instance.

Report it in the application where you can, or contact the operator at the project's Discord, discord.gg/dSF7eqsJuP.

3. Appealing a decision

If an account, a community or a message was actioned, you can appeal. Start at the appeal form.

  • You need the action ID from the enforcement notice.
  • You do not need to be signed in. Being banned should not stop you appealing.
  • Signed-in users can review past decisions under My appeals.
  • On an official instance, appeals are reviewed centrally, so a community you were removed from cannot refuse to hear you.
  • Appeals are read by a person. Expect a real answer, not an autoresponder.

Where the action was taken because content was illegal, or because a law required it, there may be no appeal, and the operator may not be able to explain the decision in full. The Trust and Safety page says more about that.

4. Reporting abuse, and anything involving a child

Abuse of a person, of a community, or of the service is reported to the operator at the project's Discord, discord.gg/dSF7eqsJuP. The rules that apply are in the acceptable use rules.

Anything involving the sexual exploitation of a child is treated as urgent and goes to a named person: the project's Discord, discord.gg/dSF7eqsJuP. Report it to the operator and, where the law requires it, to the authority in the country where it happened. Do not forward or keep copies of the material.

The Trust and Safety page describes what the operator does with a report, and what happens to the account and to any bot or integration involved.

5. Your data, or a legal request

Access, export, correction and deletion are handled by the operator of your instance, because they are the data controller. If you are self-hosting, that is you. The Privacy Policy says what is held, for how long, and what the process is.

A privacy request goes to the project's Discord, discord.gg/dSF7eqsJuP. A formal legal notice goes to the project's Discord, discord.gg/dSF7eqsJuP.

6. Something is broken

Work down this list; it finds the cause most of the time.

  1. Check the status page. If the instance is degraded, nothing you do locally will help.
  2. Reload, and try a private window. A stale cached build or a stuck service worker causes a surprising share of "the app is broken" reports.
  3. If the desktop app misbehaves, update it. It does not auto-update mid-session, so an old build against a new server is a common cause of odd failures.
  4. Still stuck? Report it on GitHub. Include the instance URL, what you expected, what happened, and your app version, from Settings, Updates.

7. Talking to other people

For questions, ideas, and the kind of help that is easier as a conversation, the project runs a Discord server: discord.gg/dSF7eqsJuP. It is the same community the issues and the roadmap come from, and it is a good place to ask before you file something.

The Discord is not the support route for an instance, and it is not a place to report abuse, child safety concerns or legal requests. Those go to the operator, as above.

8. Something wrong on this website

If a page here says something the product does not do, or a self-hosting step does not work, that is worth reporting too. The documentation ships with the code, so an issue is the right place.

9. What to put in a report

A report that says what happened, where, when, and who was involved is usually enough to act on. Where you can, add the message ID, the channel, the account, and a screenshot. Do not include material that is itself illegal to hold, and do not send it to a public issue tracker.

Response times on this instance: OPERATOR: the response times this instance commits to, or a statement that it does not commit to any.