Cookie Policy
Last updated: August 10, 2026
This page lists every cookie and browser-storage key Transcodely uses, what each one does, and how long it lasts. The short version: we use strictly necessary, first-party cookies for signing you in — nothing else. We set no advertising cookies, no cross-site tracking cookies, and no third-party cookies, and our website analytics is cookieless. That is why you do not see a cookie consent banner on this site: everything we set is either strictly necessary for the service you asked for, or a local preference that never leaves your browser.
Cookies we set
All cookies below are first-party (set by transcodely.com for
transcodely.com only), marked Secure and SameSite=Lax, and — except where noted — inaccessible
to JavaScript (HttpOnly). They are set only when you
sign in; visitors who never sign in get no cookies from us at
all.
| Cookie | Purpose | Lifetime |
|---|---|---|
tc_session | Your dashboard session: a tamper-protected (signed) token holding your user ID, name, email, and current organization | 30 days, renewed while you use the dashboard |
tc_access | Short-lived access token used to authenticate your dashboard’s requests to the Transcodely API | Minutes; refreshed automatically |
tc_refresh | Single-use token that renews your session without making you sign in again; rotated on every use | 30 days |
tc_workos_sid | Identifier of your session at our sign-in provider (WorkOS), used only to sign you out there when you log out here | 30 days |
tc_refresh_attempt | Short-lived technical marker (a hash fingerprint, no secret) that prevents a session-renewal race from logging you out incorrectly | 10 minutes |
tc_auth_hint | A simple “1” telling our public pages to
show “Dashboard” instead of “Log
in”. Readable by page scripts (not HttpOnly) because that is its job;
contains nothing else | 30 days |
All of these are deleted when you log out. Because every cookie above exists solely to provide the signed-in service you requested, they fall under the “strictly necessary” exemption of the EU ePrivacy rules and do not require consent.
Local storage
We also keep a few preferences in your browser’s localStorage. These never leave your device, are not
sent to our servers, and are not used to track you or build a
profile:
| Key | What it stores |
|---|---|
transcodely:current-org | Which of your organizations the dashboard last showed |
transcodely:app-context | Your last-selected app filter in the dashboard |
transcodely:docs-language | Your preferred code-example language in the docs |
transcodely:billing-nudge-dismissed:<orgId> | That you chose “Not now” on the dashboard prompt to add a payment method, so we stop showing it. Stored once per organization (the key ends in that organization’s ID) and kept until you clear your browser storage |
tc_hacker_mode | Whether the advanced upload options panel is open |
transcodely-player / transcodely:player | Video player preferences: volume, mute, playback speed, caption language, quality. Used by the dashboard player and the embeddable player. Never your watch history or playback position |
The embedded player
If you watch a video embedded on a customer’s website through the Transcodely player: the embed sets no cookies at all. It saves the player preferences listed above to local storage where your browser allows it, and if your browser blocks third-party storage, the player simply runs without saving preferences. Playback telemetry is described in the Privacy Policy, Section 5.
Analytics without cookies
We use Vercel Analytics and Vercel Speed Insights for aggregate website statistics (page views, performance). These are designed to be cookieless: they set no cookies and build no cross-site profile. Our error-monitoring service (Sentry) likewise sets no cookies on this site.
Managing cookies
Since our cookies exist only to keep you signed in, the way to remove them is to log out — or clear cookies for transcodely.com in your browser settings, which simply signs you out. Blocking cookies entirely will prevent the dashboard from working, but the public site and docs work fine without any cookies.
Changes & contact
If we ever add a cookie or storage key, we will list it here before it ships and update the date at the top. Questions: admin@transcodely.com.