Cookie Policy

Travis uses the fewest cookies and storage technologies we can while still delivering a working service. This page lists every one. If you spot something we missed, email privacy@usetravis.com.

The marketing site

The public marketing pages set no cookies by default. We do not run third-party analytics that profile or fingerprint visitors, advertising trackers, or remarketing pixels. If we ever add a privacy-respecting analytics tool, we will list it here first and only enable it with your consent in regions where consent is required.

The Travis account dashboard (web)

When you sign in to your Travis account in the browser, we set:

Strictly necessary

• Sign-in session cookie (travis_session) — an HTTP-only cookie scoped to usetravis.com so you stay signed in across pages. Required to use the dashboard. Cleared on sign-out or after the session expires.
• Sign-in safety token — a short-lived value during the OAuth sign-in flow to protect against impersonation. Held server-side and discarded automatically after 10 minutes.

The Travis desktop app

The desktop app stores your sign-in session token in a permissions-restricted file inside the app's data directory — readable only by your OS user account. The exact location depends on your platform:

• macOS: ~/Library/Application Support/com.myketheguru.travis/cloud_jwt
• Windows: %APPDATA%\com.myketheguru.travis\cloud_jwt
• Linux: ~/.local/share/com.myketheguru.travis/cloud_jwt

On earlier versions (pre-v0.22.5) the session token was stored in the OS keychain. The desktop app migrates it to a file on first launch of v0.22.5 and removes the keychain entry. You may see a one-time keychain prompt as part of that migration; after it, the desktop app does not access the keychain for the session token.

Bring-your-own-key (BYOK) third-party API keys (Claude, OpenAI, etc.) remain in the OS keychain. Those are long-lived credentials where the keychain protection is appropriate.

Third-party cookies

Some pages that embed third-party services may carry their cookies. We try to avoid this, but two exceptions:

• Payment checkout — if you start a paid subscription, you get redirected to Stripe (our payment provider), which sets its own cookies to process the payment. We don't control those.
• Embedded video (if used in marketing) — sets its own cookies when you press play. Embeds load behind a placeholder that requires a click first.

Do Not Track

We honor the Global Privacy Control signal and the legacy Do Not Track header by not enabling any optional analytics for that visit. There is nothing else to honor — we do not track you by default.

Managing cookies

Because we set so little, there is rarely anything to clear. If you want a fresh start, you can:

• Sign out of the dashboard — clears your session cookie.
• Clear your browser's cookies + local storage for usetravis.com.
• Sign out of the desktop app — removes the local session file (and the legacy keychain entry, if any).

Changes to this policy

We will update this page if we add any new cookie or storage mechanism. The "Last updated" date at the top will reflect any change.

Contact

Cookie questions: privacy@usetravis.com.