Accept all, or Refuse? Tacet presses neither.

What Tacet clears away.

A consent wall is rarely one thing. Tacet removes each piece the site puts between you and the page.

• The popup

  The dialog that asks you to accept, in the middle of the page, in a corner or along the bottom. Tacet recognises the consent tools sites use most, and finds the others by their shape, their place on the page and their wording, in five languages. In the demo: the white box in the middle.

• The backdrop

  The dark or blurred layer stretched over the whole page, so that nothing behind it answers a click. In the demo: the dark veil over The Morning Ledger.

• The scroll lock

  A rule that stops the page from scrolling, or freezes it in place. Tacet lifts it and brings you back to where you were reading. In the demo: try scrolling before you switch Tacet on.

• The blur

  Some sites blur or disable the article itself until you answer. Tacet clears that too, and leaves alone what a site blurs on purpose, such as the page behind a menu you opened. In the demo: the article text.

It hides the question. It never answers it.

Tacet is the word a musical score uses to tell an instrument to stay silent. That is what the extension does with the consent question.

• It never presses a button.

  No Accept, no Refuse, no Settings. Tacet hides the question; it does not answer it for you.

• It never records a choice.

  The consent tool stays unanswered, so it has no consent to pass on to its partners, and the trackers that wait for it stay off.

• It leaves alone what you opened.

  A login form, a menu, a photo viewer or a newsletter form you clicked on stays where it is, and so does the page behind it.

• It steps aside when you ask for the settings.

  Click a site’s “cookie settings” link and its own dialog comes back, for you to answer as you choose.

Tested on 47 pages with a wall.

On 20 October 2026, Tacet ran in Chromium on 47 article and home pages that greet readers with a consent wall. Every one ended up readable, and scrolling again where the wall had locked it. It also ran on 16 sites without walls, such as Wikipedia, GitHub and Google Maps, to check that it leaves working pages alone.