TabGuard Privacy Policy
Last updated: 2026-10-21 · Applies to TabGuard Chrome Extension v0.2.2 and later
Summary. TabGuard stores your tab sessions locally on your device. It does not contact any server, collect any analytics, or transmit any data outside your browser. No accounts, no payments, no third-party services.
1. What TabGuard stores locally
All session data is stored in IndexedDB (tabguard_db) on your device:
- Tab URLs, titles, pinned status, window index — only for sessions YOU explicitly save
- Session labels you type
- A SHA-256 checksum used to verify integrity on restore
- Timestamps and your local preferences
This local data never leaves your device.
2. No third-party services
TabGuard does not contact ExtensionPay or any other third-party service. The extension makes zero network requests. All data stays in your browser's local storage on your device.
3. What TabGuard does NOT do
- No analytics, telemetry, or crash reporting
- No advertising or ad networks
- No reading of page content — only tab metadata (URL, title, pinned flag)
- No selling or sharing of any data
- No account system of its own
- No cookies
4. Permissions and why they are used
| Permission | Why |
|---|
tabs | Read tab URL/title to save the sessions you request |
storage | Save preferences and session data |
unlimitedStorage | IndexedDB quota for many saved sessions |
alarms | Schedule the 30-minute auto-backup |
5. Data deletion
- Delete any individual session from the popup (Delete button).
- Remove all local data by uninstalling TabGuard, or via Chrome → Settings → Privacy → Clear browsing data → IndexedDB for chrome-extension.
6. Children's privacy
TabGuard is not directed at children under 13. No personal data is collected by TabGuard itself.
7. Changes
If this policy changes materially, the updated version will ship with the extension release and be posted at this URL.
8. Contact
Email: tuyentn23@gmail.com
Source: github.com/tuyentn23-dot/tabguard-extension
Landing: tuyentn23-dot.github.io/tabguard-landing