Privacy Policy
Last updated: February 8, 2025
Overview
Scrollable Tabs is committed to protecting your privacy. This Privacy Policy explains how we handle information when you use our Chrome extension.
TL;DR: We don't collect, store, or transmit any personal data. All processing happens locally on your device.
Information We Access
To provide the core functionality of the extension, we access the following information locally within your browser:
- Tab information: Titles, URLs, favicons, and tab IDs of your open tabs
- Tab groups: Group names, colors, and which tabs belong to which groups
- Audio status: Whether a tab is currently playing audio
- Pinned status: Whether a tab is pinned
This information is only accessed to display your tabs in the extension popup and is never stored or transmitted.
Information We Do NOT Collect
We do not collect or have access to data that is not related to the extension
To name a few:
- Personal identification information
- Browsing history
- Login credentials or passwords
- Payment information
- Location data
- Device information
- Any data from web pages you visit
Data Storage
The only data stored by this extension is:
- User preferences: Your settings (popup width, toggle options, etc.) are stored locally using Chrome's storage API
This data never leaves your device and is only used to remember your preferences between sessions.
Third-Party Services
We do not use any third-party analytics, tracking, or advertising services. The extension operates entirely within your browser without external communication.
Permissions Explained
Our extension requests the following permissions:
- tabs: To read information about your open tabs (titles, URLs, favicons) and switch between them
- storage: To save your preferences locally
- tabGroups: To display and manage your Chrome tab groups
Changes to This Policy
We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated "Last updated" date.
Contact
If you have any questions about this Privacy Policy, please open an issue on our GitHub repository.