Tostada
Try Tostada Join Slack

Privacy

Tostada runs locally. The promise behind that one sentence:

What stays in your browser

  • Your library — every token, principle, rule, and component override — lives in localStorage under the key tostada-library.
  • Your API key — if you've set one — lives in localStorage under tostada-ai-key.
  • Your undo/redo stack and change history — never leave the browser.

That's it. There's no Tostada server, no account system, no sync layer.

What leaves your browser

Only one thing, only when you ask for it:

  • When you click an Ask AI button (today: Ask AI for tokens), Tostada makes a direct call from your browser to api.anthropic.com. The call includes your prompt and your API key. The response includes the proposed token patch. That's the entire round-trip — Anthropic is the other end.

We don't proxy, log, or inspect the call. The Anthropic SDK is the same one any Anthropic-API project uses; we run it in browser mode (anthropic-dangerous-direct-browser-access).

What we don't do

  • No analytics. No Plausible, no Mixpanel, no Google Tag Manager, no PostHog. Open devtools → Network and confirm.
  • No telemetry. Tostada doesn't phone home about which buttons you click, which tokens you edit, or what your library looks like.
  • No accounts. There's nothing to sign up for; nothing to authenticate against.
  • No fonts that track you. Google Fonts is used on the marketing site (tostada.dev/) but not inside the app — the app uses system fonts and bundled Inter.

When this changes

The roadmap calls for accounts, multi-user, and library sync (see REBUILD_PLAN.md). When those land, this page will document:

  • Exactly which data is synced server-side
  • What identifier ties you to your library
  • How to delete your data
  • Whether telemetry is opt-in (yes) or opt-out (no — we won't ship opt-out telemetry)

Until then: your library data lives in your browser. Your AI key lives in your browser. Your prompts go straight to Anthropic.

Backing up

Since the only persistence layer is localStorage, browsers can lose your data:

  • Incognito mode wipes everything on close
  • "Clear site data" wipes everything
  • Browser sync can clobber localStorage across machines

Export your library JSON regularly until the import/export UI ships — see re-importing a library.