OPERATOR is a
fact only the operator can supply: the address for questions about
storage and consent on this instance. Fill it 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 document takes effect on this instance
1. No cookies are set
The server sets no cookies at all, and the application never reads one. There is no advertising cookie, no tracking cookie, no third-party cookie, and no cookie that follows you to another site. If a cookie appears in your browser for this instance, it was put there by something else.
2. What the browser stores instead
A few things are kept in your browser's local storage, which is part of the browser rather than part of the site. They stay on your device and are not sent anywhere until the application needs them.
- Your session token. When you sign in, the server issues a signed token and the browser keeps it under a key that includes the instance's own address, so a token from one instance is never handed to another. It is sent back on each request as an authorisation header. Clearing it signs you out; it is not a cookie and it is not readable by another site.
- Your theme and your preferences. The light or dark choice, any custom palette, the motion setting, and the layout of your workspace are stored so they survive a reload.
- The API address you are using. If you point the client at a different instance, that address is remembered, along with the token for that instance, under that instance's own key.
- The demo's state. The demo keeps which community you were looking at and which sample you had joined in the tab's session storage, and forgets it when the tab closes.
- This site's theme choice. The website keeps it under its own key, separately from the application's, so a theme picked here never changes how the app looks.
3. Why each one is there
The token is the session: without it the server cannot tell who you are, and you cannot post, read private channels, or send a direct message. The preferences are convenience. The API address is what lets one browser hold a session on more than one instance at once, which is the point of self-hosting.
None of them is used to build a profile of you, to count visits, or to measure an advertising campaign, because there is no such campaign.
4. Other sites
A page on this site can embed an image or a link from somewhere else, and a browser will tell that other place your address when it does. The website itself embeds nothing from another origin. The application connects only to the instance it is talking to, and the demo connects only to the instance whose public community list it is reading.
5. Clearing it
You can clear site data in your browser's settings at any time. Doing so signs you out, resets the stored preferences, and forgets the instance you were pointed at. Nothing on the server is affected: your account, your messages and your settings are still there when you sign in again.
Clearing a single item is usually possible as well: the browser's storage viewer lists each key, and removing the session token signs you out on that instance only.
6. Consent
Some jurisdictions require consent before non-essential storage is used. Trycord stores nothing that is not needed for the service to work, and asks for nothing, but the operator of an instance is the one who has to answer that question for their users: OPERATOR: how consent is handled on this instance, if the law where it operates requires it.
7. Changes
If the software starts storing something new, this page changes with it, and the version and the date at the top of the page tell you when.