Last Updated: September 2026

1. Information We Collect

TabSmart does not require an account and does not collect personal information to operate. Specifically, we do not collect your name, email address, or password to use the extension, and we do not store your tab titles, URLs, or page content on any TabSmart server.

1.1 Data That Stays on Your Device

To provide tab grouping and search, TabSmart reads and processes the following locally, in your browser:

• Tab titles and URLs — used to group and search your open tabs
• Page content — extracted from tabs you have open, used to improve grouping and search relevance
• Your grouping preferences and custom instructions — stored locally using Chrome's storage API

This data is processed by an on-device AI model running inside your browser (via WebAssembly) and is never transmitted anywhere by default.

1.2 Data Sent to a Third Party — Only If You Opt In (BYOK)

If you choose to supply your own API key for an external AI provider (OpenAI, Anthropic, or Google), the tab data needed for that specific request is sent directly from your browser to that provider, using your key. TabSmart's servers are not in this path and never see this data. Your API key is stored locally in your browser and is never sent to TabSmart.

1.3 Diagnostic Information

TabSmart does not run third-party analytics or tracking inside the extension. Standard, non-identifying error information may be logged locally in your browser's console to help you troubleshoot issues; this is not transmitted to us.

2. How We Use Information

Because tab data is processed on-device (or sent directly to your own AI provider under BYOK), TabSmart itself has no server-side use of your tab content. The on-device model uses your tab titles, URLs, and content solely to:

• Group related tabs together
• Power in-popup search across your open tabs
• Apply any custom grouping instructions you've configured

None of this processing leaves your browser unless you have explicitly enabled BYOK with your own key.

3. Data Storage and Security

• No server-side tab storage — TabSmart does not operate a database of user tab content, titles, or URLs.
• Local storage only — Your settings, custom instructions, and (if provided) your own API key are stored locally in your browser via Chrome's storage API.
• On-device AI model — The AI model and its runtime are bundled with the extension; model weights are fetched once from our CDN (Hugging Face / Cloudflare R2) and cached locally. This transfer contains no user or tab data — only the model files themselves.

4. Data Sharing and Third Parties

4.1 AI Providers (BYOK — Optional)

Only if you enable BYOK and supply your own key, tab data for that request is sent directly from your browser to your chosen provider:

• OpenAI (GPT models)
• Anthropic (Claude models)
• Google (Gemini models)

This is governed by that provider's own privacy policy and terms. TabSmart does not store, log, or have access to this data at any point.

4.2 Infrastructure

• Cloudflare R2 / Hugging Face — host the on-device model weight files served to the extension. No user or tab data is transmitted in this exchange.
• Render — hosts this website (tabsmart.app). Standard web server logs (e.g., IP address, request time) may be recorded for security and uptime purposes, unrelated to the extension's tab data.

4.3 No Data Sales

We never sell, rent, or trade your information to third parties for marketing purposes.

5. Data Retention

Because TabSmart does not collect or store your tab data on our servers, there is nothing server-side to retain or delete. Locally stored settings and preferences remain in your browser until you clear extension storage or uninstall TabSmart, at which point Chrome removes them automatically.

6. Your Rights and Choices

• No account to manage — there is nothing to sign up for, update, or delete on our end.
• Uninstall anytime — removing the extension deletes all locally stored settings, preferences, and any BYOK key you entered.
• Choose your AI mode — use the default on-device model, or opt into BYOK with your own key, at any time from the extension settings.
• Custom instructions — control how tabs are grouped via your own grouping instructions.

7. Chrome Extension Permissions

TabSmart requests the following permissions, each used only for the extension's core tab-organization and search functionality:

• tabs — read open tab titles and URLs to group and search them
• tabGroups — create and manage Chrome's native tab groups
• scripting — extract page content from tabs you have open, for grouping/search relevance
• activeTab — access the current tab when you interact with the extension
• webNavigation — detect when new tabs finish loading, to keep grouping/search up to date
• storage — save your preferences and custom instructions locally
• unlimitedStorage — allow the on-device AI model files to be cached locally without Chrome's default storage limit
• offscreen — run the on-device AI model in a background document so it doesn't block the browser UI
• Host permission (all sites) — needed so tab grouping and search work across whatever sites you have open; this permission is used to read tab content locally and is not used to inject ads, track browsing, or send data to a server

8. Children's Privacy

TabSmart is not intended for children under 13. We do not knowingly collect personal information from children under 13.

9. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last Updated" date above and, where appropriate, noted in the Chrome extension's release notes.

10. Contact Us

11. Compliance

This Privacy Policy is written to comply with:

• Chrome Web Store Developer Program Policies
• General Data Protection Regulation (GDPR)
• California Consumer Privacy Act (CCPA)

---