Privacy policy

Last updated 6 October 2026

Who is responsible

Invisible Shapes, Waterlei 248, 7325 GL Apeldoorn, the Netherlands (KvK 70894884) is responsible for the data described here. Questions or requests: hello@cookiechomper.com.

What stays on your device

The extension stores these in your browser and never sends them anywhere: your settings and the sites where you answer banners yourself; how each site's banner was refused, so the next visit needs no work, and on which sites a “no” was already given, so cookie settings you open yourself are left alone; and a short log of recent activity, shown on the extension's settings page. Removing the extension deletes all of it.

When banner text leaves your browser

The most common cookie banners are recognised on your device, using an open-source list that comes with the extension. The extension sends the following for any other banner, for a recognised banner whose rejection on your device doesn't finish or isn't clear to have worked, and for anything offering a choice that is still on screen, or appears, after a rejection:

• the page language, and whether the banner is on the page itself or inside an embedded frame;
• the text and the labels of the buttons, links and switches of the part of the page read as the banner, with email addresses and long numbers (phone, order or account numbers) replaced by placeholders before they leave your browser.

The amount is limited: at most five parts of the page, about 1,200 characters of text each, and the labels of at most 254 buttons, links and switches. Where a banner ends can't always be told exactly, so a little nearby text sometimes comes along. What's still on screen after a rejection is not always a cookie notice; it can be a site's menu or a newsletter pop-up. Text already shown on the page, such as a message you sent in a chat, counts as page text and is treated the same way.

It never sends the web address (not even the site's name), what you type into forms and text boxes, or your cookies. Names and other personal details are not blanked out, so if one sits in the text read as the banner, it goes along. This goes to our server, which passes it to TypeSafe's AI model to decide which button refuses tracking, and returns the answer. Our server doesn't store it. TypeSafe processes it on our behalf, only to produce that answer.

Your trial and subscription

When you install the extension, our server creates a random install ID. It stores that ID, when it was created (for the 14-day trial), and, once you subscribe, which Paddle subscription belongs to it, its status, and when it started, was cancelled or was refunded. The install ID is not linked to your name, email address or browsing.

Using your subscription on another browser

If you ask to restore your subscription, the extension sends the email address you enter to our server. We use it once: to ask Paddle whether that address has a Cookie Chomper subscription, and if it does, to email you a one-time code through our email provider, Resend. We don't store the address. We keep only a scrambled (hashed) copy of the code, which works only in the browser that asked and stops working after 30 minutes or its first use.

Payments

You subscribe on Paddle's checkout. Paddle is the merchant of record: it collects your payment details, email address and billing country, and handles VAT and invoices under its own privacy notice. We receive the subscription's status and a Paddle customer ID, never your card details.

This website and our server

This website sets no cookies and uses no analytics. It and our server run on Cloudflare, which keeps technical request logs (time, route, response code and the connecting IP address) for a few days, to operate and protect the service. We don't log banner text or site names.

Who processes data for us

Where your data goes

Our database is in Western Europe. Cloudflare runs this website and our server on computers around the world, so a request may be handled outside the EU, including in the United States. TypeSafe, which runs the AI model that reads the banner text described above, and Resend, which sends restore codes, are US companies and handle that data in the United States. Our agreement with each of them includes the European Commission's standard contract terms for this, and Cloudflare and Resend are also certified under the EU–US Data Privacy Framework. Paddle, based in the United Kingdom, handles payments under its own privacy notice, as a separate company responsible for its own data. We have a data processing agreement with Cloudflare, TypeSafe and Resend.

Legal basis

Sending banner text so that the banner can be rejected is necessary to provide the service you installed (GDPR Article 6(1)(b)). Subscription records are needed for the contract and for tax law (Article 6(1)(b) and (c)). Server logs are kept for our legitimate interest in running a secure service (Article 6(1)(f)).

How long we keep it

• Banner contents: not stored by us.
• Install ID and subscription status: while the trial or subscription is current, and deleted 12 months after it ended.
• Paddle keeps billing records for as long as tax law requires.

Your rights

You can ask for access to, correction or deletion of your data, object to its processing, or ask for a copy. Because we don't know who you are, include the email address you used with Paddle when you write to us. You can also complain to your data protection authority; in the Netherlands, that's the Autoriteit Persoonsgegevens.

Changes

When this policy changes we update this page and the date above, and mention material changes in the extension's release notes.