What Tacet reads, and what it keeps.

Where it runs

Tacet runs on the web pages you open over http or https, in the page itself rather than in frames embedded in it, from the moment the page starts loading. It does not run on the browser’s own pages, on extension stores, or on files opened from your computer. All of its code is in the installed package; it loads nothing from the internet.

What it reads and why

• The layout of the page: which elements sit on top of the others, their size and position, and the styles that lock scrolling or blur the content. This is how Tacet tells a wall from the rest of the page.
• The visible text and the names (identifiers, classes, labels) of those elements, to recognise consent, subscription, newsletter and ad-blocker wording in five languages.
• The button or link you click or press (its text, name and address), to leave alone what you open yourself, such as a login form or a site’s own cookie settings.

All of this happens inside the page, in memory, and is forgotten when you leave it. Tacet does not read what you type into forms, your cookies, your passwords or your browsing history.

What it keeps

• In the browser’s extension storage, on this device only (it does not sync): the list of sites where you switched Tacet off, whether it hides cookie banners that do not block the page, and whether debug logging is on.
• The list of what Tacet changed on a page stays in that page’s memory, so that its popup can show it. It disappears when you leave or reload the page.
• With debug logging on, Tacet also writes that list into the page, as an attribute of its root element, and into the page’s console, where the page’s own scripts could read it. Debug logging is off by default.

What it sends

Nothing. Tacet makes no network requests: no analytics, no telemetry, no crash reports. Updates come through your browser’s extension store.

Permissions

• storage, to keep the three settings described above.
• Access to all websites. Tacet has to run on every page to find its walls; Chrome shows this as “Read and change all your data on all websites”, Firefox as “Access your data for all websites”. Tacet uses it only to hide walls and restore the page as described on this page.
• On Firefox, Tacet declares that it collects no data.

Your choices

From Tacet’s popup, you can switch it off for a site, undo its changes on the current page, or stop it from hiding cookie banners that do not block the page. Removing the extension deletes its settings. Nothing about you is kept anywhere else.

This website

This website uses no analytics and sets no cookies. It is hosted on GitHub Pages; GitHub may log visitors’ IP addresses for security purposes under the GitHub Privacy Statement. The demo on the homepage runs Tacet’s code on a made-up page; its made-up consent wall records nothing.

Questions

Ask on the project’s GitHub issues. Issues are public, so do not include personal information. The support page has answers to common questions.