Tawn / Legal

Privacy, without the guesswork.

A clear account of the page details Tawn keeps, where they go, and the choices you have today.

Updated 9 October 2026

01 / 06

What Tawn keeps

Tawn is built to help you return to useful pages. When the extension captures an HTTP or HTTPS page, it can keep the URL, title, domain, preview image, visit count, time visited, and the section or subsection where the page belongs.

If you create an account, Tawn also keeps the information needed for sign-in, such as your name and email address. Passwords for email sign-in are stored as hashes rather than plaintext. Google and GitHub sign-in may provide account details such as an email address and avatar.

  • Guest page cards are kept in your browser’s extension storage.
  • Signed-in page cards are sent to the Tawn API and associated with your account.
  • The web app keeps your theme preference and sign-in token in browser storage.
02 / 06

How the information is used

Tawn uses page details to build visual cards, group related pages, power search, remember your placement choices, and sync your collection when you sign in. A known-site catalog recognizes some apps directly; unfamiliar pages may be classified through the configured Gemini service.

The current app has no advertising integration. We do not need the text you type into other websites to organize a page.

03 / 06

Previews and connected services

To show a useful card, the extension or API may request page metadata and an Open Graph image from the visited site. When server-side classification is used, URL and page details may be sent to the configured AI provider.

Google and GitHub authentication are optional sign-in routes. Planned integrations with mail, chat, and work apps are not active in the current product.

04 / 06

Your choices

You can organize, move, favorite, and delete cards from your collection. Signed-in cards can be moved to trash and restored; the available trash controls are shown in the dashboard. You can use the extension as a guest before creating an account.

For a question about your account or a data request that is not available in the interface, contact penchal@tawn.dev.

05 / 06

Where data lives

Guest cards are stored locally through browser extension storage. Signed-in cards and account records are stored by the Tawn API in its configured MongoDB database. Your browser also stores the web session and theme preference locally.

The extension and website communicate with the API using bearer tokens. Protect access to your device and browser profile, especially if you remain signed in.

06 / 06

Changes and questions

As Tawn develops, product behaviour and this notice may change. We will update this page when the way the product handles data changes materially.

For privacy questions, write to penchal@tawn.dev. You can also use the Contact page to prepare an email.

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