Legal

Terms for Official Instances

On most Trycord instances, the people you deal with are the people who run that instance. On an official instance, that is the same party everywhere, and these terms describe what is different about that.

Legal review required before publication. This document comes from the Trycord project as a starting point. It is not legal advice, and nobody has reviewed it for the party actually operating the instance. The fields marked OPERATOR are facts only the operator can supply: the legal identity behind the instance, its address, its subprocessors, where data is stored, its retention periods, and where formal notices must be sent. 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 these terms take effect on this instance

1. What an official instance is

An official instance is a hosted Trycord instance operated by the Trycord project, or by a partner the project has appointed and published. Being listed in the app is the whole of the designation: there is no other certification, no badge, and no other instance may present itself as official.

Everything else — a community's own server, a friend's instance, a copy you host — is not official, even if it runs unmodified software.

2. How these terms relate to the main terms

The Terms of Service apply on official instances too, and this page adds to them. Where the two conflict, these terms win. Nothing here removes a right you have under the main terms.

3. Who runs it, and who you can contact

One party operates every official instance: OPERATOR: the legal name of the party that operates the official instances, contactable at the project's Discord, discord.gg/dSF7eqsJuP. Because the same party runs all of them, you do not have to work out who operates the one you joined, and there is one place to raise a problem.

This is the practical difference from a self-hosted instance. On one of those, your only route for anything serious is that instance's operator. Here, you can reach the operator directly.

4. Your data on an official instance

The operator is the data controller. The retention rules are set once and apply across every official instance, so your data is not handled differently depending on which one you happened to join.

  • Retention: OPERATOR: the retention periods that apply on the official instances
  • Backups: OPERATOR: the backup schedule and how long backups are kept
  • Hosting and subprocessors: OPERATOR: the hosting provider and the subprocessors used on the official instances
  • Where data is stored: OPERATOR: the country or region where data on the official instances is stored
  • Your rights: access, correction, export and erasure, as set out in the Privacy Policy

Export is the one the operator holds itself to most firmly. You should always be able to get your data out, in a usable format, without asking a favour. If that is ever hard on an official instance, treat it as a defect and report it as one.

5. Moderation on official instances

Official instances carry platform-wide rules, because one party operates them. Beyond those, communities on an official instance set their own rules and their own moderators enforce them, in the same way as anywhere else.

Because one party operates every official instance, a report about enforcement can be raised centrally rather than only with a community you may already have been removed from. The Support page describes how to appeal.

The rules in section 5 of the Terms of Service apply unchanged, including the prohibition on child sexual abuse material and on asking for, offering or facilitating it. An official instance is no exception, and no appeal route overrides that prohibition.

6. Availability

Official instances are provided free of charge and on an as-available basis. The status page describes an instance at a moment rather than committing to the future. The operator publishes incidents rather than staying quiet about them. There is no uptime guarantee, and no paid tier changes that unless it is written down here.

7. Suspension on official instances

Accounts that break the Terms of Service or the platform-wide rules may be suspended. Because the operator runs the instance, it can see the context of a decision, including whether a community moderator acted correctly, and appeals are reviewed centrally.

Personal data is not sold, and messages are not used to train models. If that ever changes, it will be disclosed in this document and in the Privacy Policy before it happens rather than afterwards.

8. Ending an official instance

If an official instance is closed, the operator publishes notice on the status page, gives a reasonable period to export, and keeps the export available afterwards for OPERATOR: how long an export stays available after an instance closes. Communities that people are still using are not deleted silently.

9. Liability

The limitations in section 15 of the Terms of Service apply here. Nothing in these terms limits liability that cannot lawfully be limited, and where you are a consumer, the protections your local law gives you are unaffected.

10. Notices

Formal notices are sent to the project's Discord, discord.gg/dSF7eqsJuP. For anything that is not a formal notice, start on the Support page.