Tawn / Legal

Cookies and local storage.

What your browser keeps for Tawn, and how that differs from a tracking cookie.

Updated 9 October 2026

01 / 04

What the app stores locally

The current Tawn web app relies on browser local storage for its theme preference and, after sign-in, the account session token and user details. These items are browser storage entries, not first-party authentication cookies.

The extension uses Chrome extension storage for guest cards and sign-in state. This lets the new-tab page show a collection before you create an account.

02 / 04

Storage you may see

The exact storage keys may change as the product evolves. The current implementation uses the entries below.

  • tawn_theme — your light or dark appearance choice on the website.
  • tawn_token and tawn_user — web sign-in state and account details.
  • tawn_urls — guest page cards in Chrome extension storage.
  • tawn-store — extension interface and collection state in its local browser storage.
03 / 04

Cookies and sign-in providers

The current web sign-in flow sends a bearer token to the Tawn API rather than relying on a first-party authentication cookie. Google or GitHub sign-in may use cookies on the provider’s own site as part of its authentication flow.

Opening a saved third-party site can also result in cookies from that site. Those sites control their own cookies and policies.

04 / 04

Your controls

You can change the Tawn theme from the navigation or dashboard settings. Signing out removes the web session entries. Your browser’s settings can clear local website data, and Chrome’s extension controls can remove extension storage. Clearing local guest data may remove cards that have not been synced to an account.

For questions about Tawn’s browser storage, contact penchal@tawn.dev.

Need a closer look?

Ask us about your data or your account.

We can clarify how Tawn works today and help with a specific request.

Contact Tawn