Privacy Policy

Last updated: 2026-06-15

Tabby is built around one principle: your tab history is yours, and nobody else's.

No Data Collection

Tabby does not collect, store, or transmit personal data. There are no servers, no analytics, no telemetry, no crash reporters, and no third-party SDKs of any kind.

Local Storage Only

Sessions, the closed-window archive, and settings are persisted via Chrome's chrome.storage.local API on your device. Uninstalling Tabby permanently deletes this data.

No Host Permissions

Tabby does not request access to any website (no <all_urls>, no *://*/*). It cannot read or modify the content of any web page.

Permissions We Use

• tabs — read tab title, URL, favicon URL, and pinned/active state to build sessions and power tab search.
• storage — persist sessions and settings to chrome.storage.local.
• sessions — surface Chrome's recently-closed tabs/windows for restore.
• alarms — schedule the optional periodic auto-snapshot.
• windows — create or focus browser windows when restoring sessions.

No Network Calls

Tabby makes no HTTP requests. Favicon images are served by Chrome's built-in chrome://favicon resource, which does not involve any third-party network call.

Export & Import

When you click Export, Tabby writes a JSON file to a location your browser chooses. You decide whether to share or back it up. Import reads such a JSON file from a location you pick — Tabby never accesses your filesystem otherwise.

Open Source

Every line of code that runs in your browser is published in the public repository at github.com/visionion/tabby. We do not bundle, minify, or obfuscate the extension code shipped to the Chrome Web Store.

Children

Tabby is not directed at children and does not knowingly collect any information from children (or anyone — see above).

Contact

Questions or concerns: info@visionion.dev.