Cookie policy

What we set

This is a documentation site for a developer platform, so the cookie footprint is deliberately small. There are no advertising cookies, no cross-site trackers, no social embeds and no third-party pixels. The only categories in use are strictly necessary cookies and, if you accept them, first-party analytics.

A cookie is a small text file a site stores in your browser. The same rules we describe here apply to equivalent technologies such as local storage, which the console uses to remember interface preferences.

Strictly necessary

These are set without consent because the site cannot function without them, and they carry no information about you beyond what is needed for the request in front of it.

• tr_session - keeps you signed in to the console for the length of the session. Session cookie, deleted when the browser closes.
• tr_csrf - a per-form token that stops a third-party site submitting on your behalf. Session cookie.
• tr_consent - records the cookie choice you made, so we do not ask again on every page. Twelve months.

Analytics

If you accept analytics, we set a first-party cookie that tells us which documentation pages are read, which guides get abandoned halfway, and which error codes are looked up most. That is genuinely what we use it for - the reference gets rewritten based on it.

• tr_an_id - a random identifier for one browser, not linked to an account or an email address. Six months.
• tr_an_ses - groups page views into a single visit. Thirty minutes.

The analytics data stays with us. IP addresses are truncated before storage and nothing is shared with an advertising network. Declining costs you nothing and changes nothing about how the site behaves.

The console

Signed-in areas use browser local storage to remember interface state: which language tab you last used on a code sample, whether a sidebar is collapsed, and your preferred environment. This never leaves your browser and is cleared when you clear site data.

Controlling cookies

You can change or withdraw consent at any time from the cookie link in the footer, and the change applies immediately. Every browser also lets you block or delete cookies from its settings, though blocking the strictly necessary ones will stop the console signing you in.

Changes

If we add a cookie or change what one is for, this page is updated and the consent prompt is shown again rather than assuming an old choice still covers it. Questions go to developers@textreach.online.