Privacy policy for Tab Suspender, Memory Saver & Ad Blocker
Tab Suspender, Memory Saver & Ad Blocker by SuperchargeBrowser
Privacy policy for Tab Suspender, Memory Saver & Ad Blocker
Privacy Policy
Last updated: October 29, 2026
- Our Core Privacy Commitment
Privacy is not an afterthought — it is a core principle of every SuperchargeBrowser extension. We believe your browsing data belongs to you. All our extensions are engineered so your data never reaches our servers.
We do not collect, store, sell, or share your browsing history, searches, or website content on our own servers or with third parties.
- Data We Collect (and Why)
We limit data collection to the absolute minimum required to operate our website and services.
A. Extensions: Your Browsing Data (None Sent to Us)
Our extensions do not transmit your browsing history, open tabs, page content, or any browsing activity to our servers or any third-party analytics service. All extension logic — including content blocking, tab management, and interface features — runs locally on your machine.
The following behaviors cause requests to our website:
The welcome page. After you install some of our extensions, including SuperchargeFocus, the extension opens a welcome page on our website, but on Firefox only if you allow its optional technical and interaction data permission. That is an ordinary visit to our website, covered by the website analytics described in Section 4. The SuperchargeFocus welcome page also reports through those analytics whether it detected Focus, how far setup got, which of its buttons you clicked and how long the page stayed open.
The in-page sidebar on restricted pages. On pages Firefox reserves for itself, such as about: pages, the Firefox Add-ons site and PDF files, no extension can run in the page. When you open SuperchargeNavigation's in-page sidebar on one of those, it opens a tab on our website to host the sidebar there instead. That is an ordinary visit to our website, covered by the anonymous, cookie-free analytics described in Section 4 — the extension still sends none of your browsing data to us, and it never reports which page you were on. SuperchargeFocus does the same with its panel and opens our Focus page; when your browser reports that it is offline, it opens a page inside the extension instead.
Uninstalling. When you remove one of our extensions, your browser may open a short feedback page on our website. This is a standard browser feature (runtime.setUninstallURL). On Firefox our extensions enable it only while you allow their optional technical and interaction data permission; the page may then open automatically when you uninstall. The request tells us only which extension was removed, plus the ordinary information any web request carries — it contains no browsing data, no settings, and nothing that identifies you. Answering the survey on that page is entirely optional; if you close the tab we keep nothing beyond the anonymous page visit described in Section 4.
B. Extension Settings
Your preferences and extension data (such as feature toggles, saved workspaces, or whitelisted domains) are stored locally in your browser's storage (browser.storage.local). They are never sent to our servers.
SuperchargeInspect. SuperchargeInspect works on a single element you pick. It reads the style of that element only on the tab where you start it, using activeTab. It remembers your last picked element per tab and page in browser.storage.session, and the browser clears that when it closes. It saves your panel theme choice, Auto, Light or Dark, in browser.storage.local. It also saves, in browser.storage.local, the date you first used it, a count of your successful copies, whether you rated it or closed the rating request, and which product tips you closed. These are used only to time the rating request and the tips. They stay on your device and are never sent anywhere. It makes no network requests. It has no account and no sign-in. Nothing is sent to SuperchargeBrowser or anyone else. Copied text and screenshots go only to your own clipboard.
SuperchargeFocus. SuperchargeFocus saves its settings and records in browser.storage.local on your device. That covers your focus rules, sessions, schedules and daily allowances, your page appearance settings, and any location you type in yourself to schedule themes by sunrise and sunset. It never asks your browser for your location. When you pick a page element to hide, it may save the page address, a short label and text from that element so it can find the element again. To run daily allowances, it records how long each website is in use per day, by host name only (such as www.youtube.com), whether or not Activity history is on. It counts the site in the active tab, stops after two minutes without activity unless that tab is playing sound, and also counts other tabs playing sound if you turn that option on. It keeps these counts for the 32 most recent days on which it counted anything. A short-lived sample of the sites being counted is held in browser.storage.session, which the browser clears when it closes.
Activity history in SuperchargeFocus is off by default. If you turn it on, it saves the host name and time of the pages you view. Only if you tick each option does it also save the page address (up to 2,000 characters), the page title (up to 300 characters) and up to 2,000 characters of the page's visible text. Text capture skips form fields and editable areas, but text a site shows elsewhere on the page can still be saved. You choose to keep history for 7, 30 or 90 days, older entries are removed at the next cleanup, and it keeps at most 2,000 entries. In the panel you can exclude sites, pause history for 24 hours, search it, or delete all of it. Deleting history does not delete the daily time counts. Exporting your setup saves a file to your computer with your rules, schedules and page changes, including any saved page addresses and element text. The export never includes Activity history or its settings.
SuperchargeFocus makes a few requests of its own. To show a page in the theme you picked, it may download again the stylesheets and images that page links to, without cookies. Those requests go to the sites that host the files, may follow redirects, and carry the ordinary information any web request carries. When its panel loads, it sends a message inside your browser to other SuperchargeBrowser extensions to check whether they are installed, so it does not suggest one you already have. On our website it marks the page to show that Focus is installed and whether setup is finished, so the site can open the panel for you; the welcome page reports setup progress with the website analytics described in Section 2.A and Section 4. It also saves when you first opened the panel, on how many days you opened it, whether you opened the rating page or closed the rating request, and which tips you closed. These are used only to time those prompts. SuperchargeFocus has no account and no sign-in, and it does not upload your rules, time counts, page changes or Activity history to SuperchargeBrowser or anyone else.
C. Cross-Device Sync (SuperchargeNavigation only)
SuperchargeNavigation stores your workspaces on your device. It can also sync them through your browser's built-in sync, using browser.storage.sync: your Mozilla account on Firefox. Workspace sync is on by default. The extension does not upload your workspaces until first-time setup is resolved. If your browser sync already holds workspace data from another device, the extension can resolve setup on its own. Otherwise it asks you a setup question. Choosing Skip leaves sync on. The extension saves its sync on/off setting in sync storage before setup is resolved. Your browser account decides whether sync storage moves between devices. If browser sync is off, the data stays in your browser and can sync later when you turn browser sync on.
What syncs: workspace names and icons, tab URLs, page titles (up to 200 characters), which tabs are pinned, tab group identifiers and membership, group names and colors, the name of the active workspace, a device identifier and device name, the sync on/off setting, and technical data (a timestamp, format version, chunk count and checksum). What does not sync: the time-travel snapshots and tab favicons. Automatic Saved Tabs backups do not sync while they keep their generated "Saved Tabs" name. If you rename a backup, its contents can sync. A backup's name can sync while it is your active workspace.
Workspace sync uses your browser provider's sync service. It does not send your workspace data to SuperchargeBrowser servers. You can turn workspace sync off on each device. This stops new automatic uploads from that device. An upload already in progress can still finish, and a first-time setup check that is still pending can still import workspaces from sync. Turning sync off does not delete your local workspaces or the copy already in browser sync. The settings option that replaces the synced copy with this device's workspaces does not delete the synced copy either.
To delete synced data, use your Mozilla account settings for Firefox Sync. These controls also affect your other synced browser data. Uninstalling the extension does not by itself guarantee that the cloud copy is deleted. No other SuperchargeBrowser extension uses browser.storage.sync.
D. Website: Communication
What: When you visit our website and provide your email address, we collect it.
Why: To notify you about product launches, updates, and offers.
Storage: This data is stored securely with our email service provider. You may unsubscribe at any time.
E. External Links
Links within our extensions and website may include URL parameters (UTM tags) to identify the referral source. These parameters are standard web analytics identifiers — they do not contain personal data and are not collected or stored by the extension.
F. Website: Browser Local Storage
Our website stores a small number of values in your browser's localStorage and sessionStorage. They render UI consistently between page visits, stop us from counting a one-time event twice, and connect an extension install to a recent click on a store link. Some of these values are sent with our website analytics, as described below. We do not assign a browser identifier to any of them. Page paths are kept without query strings or fragments. How you reached our site is kept as a short label, such as a search engine, a campaign tag or the referring site's name. You can clear these values at any time through your browser's site-data settings.
changelog_review_dismissed_v1: Timestamp recording when you dismissed the changelog feedback prompt, so we don't show it again for ~7 days.
sb.ext.perf.seen / sb.ext.nav.seen: Timestamps recording the most recent visit you arrived from a SuperchargePerformance or SuperchargeNavigation in-extension link (identified by the UTM tag described in section E). Used to render the right "Get Extension" call-to-action — for example, if we already detected you arrived from SuperchargePerformance, the website offers SuperchargeNavigation instead. Entries expire automatically after 90 days. For these SuperchargeNavigation and SuperchargePerformance flags, detection uses only the referral parameter on links you click. SuperchargeFocus also shows our website whether it is installed and whether setup is finished, as described in Section 2.B.
scb_src / scb_land (sessionStorage): How you reached our site, and the first page you opened on it in this browser tab together with how you reached it. They last for that tab's session. The source is sent with our page-interaction events. The landing page is sent with most of them, but not with the time-on-page event. Both are copied into a store-click record when you click a store link.
sb.recent-store-click.<extension>: When you click a link to one of our extensions in a browser store, the website saves the landing page and source from scb_land, which extension and store the link was for, and the time of the click. It keeps at most one record per extension, and a newer click replaces the older one. When that extension opens its welcome page in this browser for the first time, the website deletes the record. If the click was less than 24 hours earlier, the welcome page sends the record's values once with the install count. A record older than 24 hours is never sent. It stays in your browser until this check removes it, a newer click replaces it, or you clear site data. We do not assign a browser identifier to the record.
sb.install.<extension>: One flag for each of our six extensions, written the first time an extension opens its welcome page on this browser, so that one install is counted once rather than again on every reload or return visit. The value is the character 1 — no timestamp, no identifier, and nothing that distinguishes your browser from anyone else's.
G. Website: Feedback & Surveys
What: Your answer, plus your browser and version, operating system and preferred language, read from ordinary request headers. We never ask who you are — there is no name field, no email field, and no account.
Why: To find out what we broke and fix it. Under GDPR our basis is legitimate interests: improving a product you chose to install.
Storage: On Cloudflare, with nothing linking one answer to another or to you. Please leave personal details out of the free-text box — we have no use for them, and we would rather not hold them.
Retention: 24 months, then deleted. Ask us sooner and we will remove your answer.
H. PRO Accounts (Future Feature)
What: If you choose to upgrade to a PRO plan in the future, we will process account identifiers (such as an email or license key) to verify your subscription.
Why: Strictly to unlock PRO features.
Storage: Payments and subscriptions are handled by our third-party Merchant of Record. We do not store credit card details.
- Browser Permissions Explained
Our extensions request only the permissions necessary for their features. Not every extension uses every permission listed below. These permissions support the features and data handling described below.
host_permissions (<all_urls>): Allows our extensions to run their features across all websites you visit, including injecting content scripts for performance optimization, tab navigation overlays, inline page previews, audio volume and equalizer processing, and focus pause screens and page themes. All processing happens locally. We do not transmit page content. SuperchargeFocus reads page content to change how pages look and to find elements you chose to hide, and stores page text only for page changes you save and, if you turn it on, Activity history (see Section 2.B). SuperchargeCapture does not require this permission at install time — see the Capture section below.
tabs: Used to manage your browser tabs — detecting active and inactive tabs, switching between tabs, and providing tab search functionality. Tab metadata is processed locally. SuperchargeNavigation can sync tab URLs and titles through your browser's own sync. Workspace sync is on by default and can be turned off, as described in Section 2.C. SuperchargeFocus keeps the local time counts and optional Activity history described in Section 2.B.
tabGroups: Used to organize tabs into groups, manage group colors and names, and support workspace features. All group data stays in your browser.
sidebar_action: Used to display an in-browser sidebar for tab management and navigation. The panel runs locally with no external communication.
storage / unlimitedStorage: Used to save your preferences, workspaces, and extension state locally on your device via browser.storage.local. SuperchargeNavigation also uses browser.storage.sync when you enable cross-device sync — data flows through your own browser account's built-in sync, not our servers. All other extensions use local storage only.
storage (SuperchargeInspect): Used to save your panel theme choice, Auto, Light or Dark, in browser.storage.local, and to remember your last picked element per tab and page in browser.storage.session, which the browser clears when it closes. It also saves the date you first used SuperchargeInspect, a count of your successful copies, whether you rated it or closed the rating request, and which product tips you closed in browser.storage.local. These values are used only to time the rating request and the tips. All these values stay on your device and are never sent anywhere.
clipboardWrite (SuperchargeInspect only): Used to copy CSS values, notes, style references, and element screenshots to your clipboard when you click a copy button or press the shortcut. It never reads your clipboard and nothing is sent anywhere.
webRequest / webRequestBlocking (SuperchargePerformance only): Used to block ads and trackers. Firefox passes each request to the extension, which checks the address against the blocklist on your device and cancels a match. Requests are never logged, stored, or transmitted.
declarativeNetRequestWithHostAccess (SuperchargeFocus only): When you force Light or Dark for all sites or for one site, SuperchargeFocus adds rules that set the Sec-CH-Prefers-Color-Scheme request header on page and frame loads, so sites that honor the header can send the matching version. When a site is set back to Auto, an allow rule keeps a forced global theme from applying there. These rules set no other header and block or redirect nothing, and the browser applies them without the extension reading your traffic.
idle (SuperchargeFocus only): Uses the idle state your browser reports to pause time counting when you step away: after two minutes without activity, unless the active tab is playing sound. The idle state is checked locally and is not stored.
scripting / activeTab: Used to inject lightweight content scripts that power features like content blocking, page overlays, mouse gestures, and visual indicators. These scripts run locally on the page and do not report data back to us. SuperchargeFocus also registers its own packaged theme scripts to run as a page starts loading, to reduce flashes of the original theme.
alarms: Used to manage internal timers for scheduled tasks such as tab suspension timeouts, periodic data snapshots, focus time counting and Activity history cleanup. Timers run locally.
optional host_permissions (SuperchargeCapture only): SuperchargeCapture declares <all_urls> as an optional permission — not required at install time, so installing it triggers no host-access warning. By default the recording overlay (camera bubble and cursor effects) works only on the current page, because a cross-origin navigation mid-recording revokes the extension's access. Enabling the "Keep going on other sites" toggle in the recording interface prompts Firefox to grant this permission so the overlay can follow you across domains. Be aware that this is a broad grant: while the toggle is on, Capture holds access to every site you visit, which is precisely what lets the overlay survive navigation. That breadth is used solely to keep the recording overlay running — everything is still processed locally on your device, and no page content is read, stored, or transmitted. You stay in control: it is off by default, requested only when you opt in, and revocable from Firefox's add-on settings (about:addons) at any time, which immediately removes the access.
- Third-Party Services
We use trusted third-party providers to operate our business — not the extensions' logic.
Payment Processing: A specialized Merchant of Record handles all payments, tax compliance, and billing.
Email Services: Industry-standard email providers manage our mailing list.
Website Analytics: We use privacy-focused, cookie-free analytics on our website to understand traffic trends and page interactions (such as scroll depth and navigation patterns). Each page interaction is recorded as its own row, together with the country it came from and whether the device was desktop or mobile. We do not store IP addresses and we set no identifiers. Most events from our shared page tracker also include the first page of that browser tab's session and how you reached it. The time-on-page event includes how you reached the site, but not that first page. An install row can also include a recent store-link click from the same browser: its landing page, source, extension, store and time, together with the extension and version that opened the welcome page. This can connect a store click to an install across pages and across separate visits within 24 hours (see Section 2.F). We do not use a lasting browser identifier for this.
Website Analytics: Automated Visitors and Failed Visits: We also run a second measurement tool of our own. Its script and data endpoint come from edge.sightwake.com on Cloudflare’s network. It runs on our website only, never inside the extensions. It tells people apart from automated visitors such as AI agents, crawlers and scripted browsers, and finds pages where a visit fails.
It records how fast and how regular your pointer, scroll, click and keyboard activity is, never which keys you press, what you type, or page content. It also records how long the page was open, how far it was scrolled, how the page loaded, which region of the page and which kind of control got the most clicks, whether the visit failed or reached a goal, and counts describing the page’s structure. From the request it keeps a browser family such as Chrome or headless Chrome, whether you came from inside or outside our site, the network operator number, and whether your IP address sits in a range an AI company publishes for its own agents. It also records clicks on store links, naming the extension and store, and installs, naming the extension. These events can be grouped with the visit's other interactions. They do not include the click time, landing page or source that our website saves.
It also records which page a visit happened on, as a path only, never a query string, fragment or hostname, taken from the address your browser sends when it requests our script. Page names and numbers are stored as they appear. Anything that looks like a credential is masked first: an email becomes :email, long codes become :token, a code after a word such as confirm or password is replaced, and so is everything after a word such as reset or invite. The path is cut to 128 bytes and kept as long as this tool’s other records. See Section 5.
It sets no cookies, writes nothing to your device’s storage, reads no device properties and stores no IP address. It does group one visit’s interactions together, with a key built from a daily rotating value, your IP address and your user-agent. That value is replaced each day and deleted soon after, and the raw IP address and user-agent are never stored. So visits cannot be linked across days, and stored records cannot be matched to you or to an IP address. Our basis is legitimate interests under GDPR Article 6(1)(f). Processing happens on Cloudflare’s global network, which may be outside the EU.
- Data Retention
Browsing Data: We do not receive the browsing data our extensions keep on your device, so there is nothing for us to retain. The time counts and optional Activity history SuperchargeFocus keeps on your device follow the limits in Section 2.B.
Email Data: We retain your email until you unsubscribe or request deletion.
Feedback & Survey Data: Retained for 24 months from submission, then deleted (see Section 2G).
Website Analytics: Anonymous interaction records are retained for 24 months, then deleted.
Automated-Visitor Measurement: Raw records are held for three months, a period fixed by the storage platform that we cannot shorten. Aggregated hourly and daily counts are kept for up to 13 months.
Subscription Data: License status is retained for the duration of an active subscription.
- Children's Privacy
SuperchargeBrowser extensions are not intended for use by anyone under the age of 13. We do not knowingly collect personal information from children.
- Changes to This Policy
We may update this policy to reflect changes in our products or legal requirements. Significant changes will be communicated via our extensions or website.
- Contact Us
If you have any questions about this Privacy Policy, contact us at support@superchargebrowser.com.
See also: Security · Open Source Attributions