Cookie policy

After Discord OAuth sign-in, the API sets tdr_member_session. It is HTTP-only, Secure in production, SameSite=Lax and scoped to the portal path. It lets the API recognize the signed-in member and expires no later than the configured session period, currently up to 30 days.

A separate CSRF token protects account-changing requests. These controls are necessary to provide the authenticated service and cannot be disabled while remaining signed in.

Google Analytics is used only on the public website after you select Accept analytics. Rejecting it leaves access unchanged and prevents the Google tag from loading. Advertising features and Google signals are disabled. The member app and backoffice do not load this tag.

The cookies _ga and _ga_* distinguish consenting website visits and sessions for up to 180 days. The choice is stored for 180 days in local storage under tdr.website-analytics-consent.v1. Cookie settings at the bottom of every public page lets you change your choice. Rejecting after acceptance deletes these cookies and reloads the page to stop analytics. Deleting browser storage also resets your preference.

We measure public page visits, validated labels from utm_source, utm_medium, utm_campaign, utm_content and utm_term, and clicks to open the app. After consent, campaign labels may be reused in this tab for up to 30 minutes. Use only public campaign labels. We exclude full URL query strings, fragments, account identifiers, private workspace data and form contents. Google receives ordinary connection and device information when you consent. No advertising cookies are installed.

Optional first-party performance sharing is disabled by default. The footer control enables or disables it without installing third-party analytics cookies. The browser stores this choice in local storage under tdr.performance-consent.v1. Reports contain only performance values and broad device/surface categories; samples expire within seven days. The feature is not advertising or behavioral profiling.

Interface language and the optional performance-sharing choice use local storage. Member-scoped session storage retains filters, working context and recoverable drafts in the current browser tab. Signing out clears that member's tab-scoped state. Explicit account draft snapshots are stored privately on the server, not in a cookie.

The private Founder backoffice stores its API connection details in that browser's local storage. This is separate from the member portal and is used only for the operator's authenticated administration session.

Signing out revokes the server session and clears the session cookie. You can also remove site data through browser settings, which will sign you out.