TidyTab Home

Privacy Policy

Last updated 21 August 2026

TidyTab collects nothing. There is no account, no analytics, no telemetry, and no server to send anything to. Everything the extension does happens inside your browser.

What TidyTab stores, and where

Two things are saved, both by Chrome's own storage APIs on your own machine:

WhatWhereWhy
Your settings: which modules are on, your banner strategy, reading preferences, and any per-site on/off choices chrome.storage.sync So TidyTab behaves the way you set it up
A short action log: the site name, which banner type was found, what TidyTab did, and when chrome.storage.local So the popup can tell you what happened on a page. Capped at 500 entries and 30 days, then discarded

Neither is transmitted to us, because there is nowhere for it to go. TidyTab makes no network requests of any kind.

One thing worth being precise about

Settings use chrome.storage.sync. If you are signed into Chrome with sync turned on, Chrome itself copies those settings between your own devices through your Google account. That transfer is between you and Google under Google's terms; TidyTab neither performs it nor receives the data. Turn Chrome sync off and the settings simply stay on the one machine.

You can wipe the action log at any time from Options, under Data.

What TidyTab never does

Permissions, and why each one exists

PermissionReason
storage Save your settings and the local action log described above.
scripting Insert the Reader Mode view into the page when you ask for it, by clicking the toolbar button or pressing Alt+R. Nothing is injected until you do.
Access to all websites Cookie banners appear on any site, and TidyTab cannot know in advance which. It reads the page only to find a consent notice and its buttons. It never reads page content for any other purpose, and nothing it sees leaves your browser.

Children

TidyTab is a general-purpose utility, is not directed at children, and gathers no personal information from anyone.

Changes

If this policy ever changes, the revised version appears here with a new date. Since the extension collects nothing, any change would be about clarity rather than new data use.