Effective date: April, 2026
TabLab is a local-first extension. It does not collect, store, or transmit
your personal data to any server operated by TabLab.
What data TabLab accesses
To provide its functionality, TabLab reads the following data directly
from your browser using Chrome extension APIs:
- Bookmarks — titles, URLs, and folder structure
- Open tabs — titles, URLs, and last-accessed timestamps
- Browsing history — visit timestamps for bookmarked URLs only,
used to identify stale or unvisited bookmarks
This data is processed locally and cached in chrome.storage.local
on your device. It is never sent to TabLab's servers (TabLab has none).
AI processing and external providers
TabLab supports several AI backends for AI processing:
-
Browser-local ML, Gemini Nano (built-in) — runs entirely in the browser via
Transformers.js and WEBLLM or Chrome's on-device AI API. No data leaves your device.
-
Local provider (Ollama, LM Studio, or any OpenAI-compatible
local server) — if you configure a custom endpoint in Settings,
tab and bookmark titles/URLs will be sent to that endpoint to perform
inference. TabLab sends the request and returns the result; it does not
log, store, or forward this data itself. The privacy practices of the
local provider are governed solely by that provider. TabLab is not
responsible for how local providers handle your data.
-
Cloud provider (OpenRouter) — if you select this endpoint in Settings,
tab and bookmark titles/URLs will be sent to OpenRouter, which routes requests
to an upstream AI provider (such as OpenAI, Anthropic, Google, or others depending
on the model selected). TabLab sends the request and returns the result; it does not
log, store, or forward this data itself.
Important: cloud providers may log your requests and, depending on
their terms of service, use them to improve or train their models. Both OpenRouter
and the underlying upstream provider have access to the content of your requests.
Review the privacy policies of OpenRouter and your chosen upstream model provider
before use. TabLab is not responsible for how cloud providers handle your data.
By default, TabLab uses Browser-local ML — no data leaves your device.
Cloud and local network providers must be opted into explicitly in the TabLab settings.
No tracking, analytics, or advertising
TabLab contains no analytics SDKs, no crash reporters, no advertising
networks, and no telemetry of any kind.
Data retention
All data stored by TabLab lives in chrome.storage.local on
your device. Uninstalling the extension permanently removes all stored data.
Changes to this policy
If this policy changes, the updated version will be published at this URL
and the effective date above will be updated.
Contact
Questions? Open an issue on
GitHub.
