Privacy & data

Trace is local-first by design. Understanding exactly what stays on your device and what doesn't makes the rest of the app's behavior predictable.

What stays local by default

Your page index, personal memory, knowledge graph, and history all live on your own device by default, whether you're on Free, Plus, or Pro. If you're using Ollama as your AI provider, AI processing happens on your machine too, so nothing about your browsing or your facts ever reaches Breadcromb's servers.

What leaves your device, and when

If you've configured a cloud AI provider (Self hosted, OpenAI, Anthropic, Gemini, or OpenRouter), the content needed to answer a given request is sent to that provider to process it, the same as using that provider directly. See AI providers for the PII redaction toggle available on every cloud provider.

Two features are opt-in and off by default specifically because they go beyond simple indexing: "Learn how you use each site" and "Personalized suggestions." Neither is active unless you turn it on yourself in Data & privacy settings.

Trending's anonymous signal

The one feature that shares anything by default is Trending, and what it shares is deliberately minimal: a truncated hash of the page's URL, its domain, its title, and the entity names extracted from it. No user ID, no account, no raw URL. There's no way to trace a Trending signal back to a specific person.

Cloud backup on Pro

The Pro plan adds encrypted, Supabase-hosted backup of your full local index, plus cross-device sync. This is opt-in by virtue of being a paid feature you choose to enable, and you can also bring your own Supabase project instead of using Breadcromb's if you want full control over where that backup lives.

Next steps