Cookies
Cookie Notice
Effective date 2026-09-06Last updated 2026-09-06
TTX Commander does not set cookies. The facilitator console and the participant app store nothing in your browser — no cookies, no local storage, no session storage. There is no analytics, no tag manager, no advertising pixel, and no third-party tracker on any page of this application. There is nothing to consent to, so there is no cookie banner.
What that means in practice
- Nothing follows you between visits. Close the tab and the application has kept nothing on your device.
- Nothing follows you between sites. No third party is loaded to watch what you do here.
- Fonts are served from us. The two typefaces the interface uses are downloaded when the application is built and served from our own origin, so your browser does not call a font provider while you read this page.
The one credential in the browser
A participant reaches an exercise through a join link — a signed, short-lived token that lives in the page’s address. The participant app holds that token in memory for as long as the page is open and sends it with each request to identify the session and role. It is not written to a cookie or to browser storage. When the tab closes, the app has kept nothing; the link in your history is what lets you return, until it expires.
The facilitator console does not store a credential in your browser either. Note that your identity provider’s own sign-in pages are a separate service with their own cookie behaviour, outside this notice.
If this changes
Two things may change, and they are not the same:
- Strictly necessary cookies. If we add cookies purely to keep you signed in or to protect a form, those are strictly necessary to deliver a service you asked for. They do not require consent under the ePrivacy rules, and we would describe them here rather than ask you to accept them.
- Analytics or anything similar. If we ever add analytics, performance measurement, or any non-essential tracking, that does require consent where the law requires it. We would ask before setting it, offer a way to decline, and list it here first.
Either way the change would appear on this page, with the effective date at the top updated. Nothing described here is set today.
Related
Cookies are not the interesting privacy question for this service — what happens to the text typed during an exercise is. That is covered in the Privacy Policy.
Questions: [email protected]