Camote Add to Chrome

Esta política solo está disponible en inglés.

Privacy Policy for Camote // Sweet Potato Ad Blocker

Author: Alejandro Navarro Ayala
Version: 1.0.9
Last updated: November 5, 2026

Camote // Sweet Potato Ad Blocker ("the extension") blocks ads and trackers and answers cookie banners in your browser. This policy states which data the extension uses, where it keeps the data, and what it sends.


About this website

camote.app uses no cookies, no analytics and no third-party content. Vercel, which hosts this website, processes technical request data, such as IP addresses, to deliver the pages.

1. No data collection

The extension does not collect, sell or send your personal data, your browsing history or other personally identifiable information (PII) to the developer or to any other party.

  • The extension contains no analytics scripts and no tracking pixels.
  • The extension does not contact a server of the developer or any other remote server.
  • All decisions (filter rules, cookie banner answers, hidden page elements) occur on your device, in the browser.

2. Data on your device

The extension uses the Chrome chrome.storage.local area on your device only. It keeps:

  • your settings (ad blocking, tracker blocking, the cookie banner mode, the main switch);
  • your list of allowed sites (allowlist);
  • local counters, for example the number of blocked ads and answered banners. Only the popup shows them.

Only the extension itself (its background service worker and its popup) can read or change this storage. The scripts that the extension runs in web pages cannot read it. They get from the service worker only the settings that they need, and only the allowlist entries of the current site. The extension requires Chrome 140 or later: Chrome 140 is the first version that can close this storage to the scripts in web pages.

This data does not leave your computer. Chrome deletes it when you remove the extension.

3. Cookie banners and consent cookies

The cookie banner function is on by default. You can switch it off or change its mode in the popup.

  • "Reject cookies" (default): the extension clicks the reject control of a cookie banner. It never clicks an accept control. It does not click a refusal that names a price or a subscription in the 6 languages of the labels. Before the banner loads, it can save the refusal values of Klaro, OneTrust and Cookiebot in the storage of the web site (cookies or local storage), in the top frame only, and never over a value that the site already saved.
  • "Accept cookies": the extension clicks the accept control of a cookie banner.
  • "Answer cookie banners" off: the extension does not answer cookie banners.
  • A page with no IAB TCF consent API 3 seconds after the page load ("Reject cookies" only): if the time zone of your device is in the EEA or the UK, the extension then answers the IAB TCF consent queries of page scripts with "no consent". It gives no other consent answer. Effect on a consent tool of the site that installs its TCF API later: if this tool first looks for an existing TCF API, it finds the answer of the extension and does not start. Then the site shows no dialog of this tool, and its partners get "no consent". The US opt-out signal is Global Privacy Control (section 4).

When the extension answers a banner, the web site keeps the answer, usually in a cookie. Your browser sends these cookies to that web site, the same as after your own click. The extension does not send this data to the developer or to any other party.

4. Privacy signals

When the extension and its tracker blocking are on (default), the extension adds the request headers Sec-GPC: 1 (Global Privacy Control) and DNT: 1 (Do Not Track), removes the request header X-Client-Data, and sets navigator.globalPrivacyControl to true in web pages. These signals tell web sites that you do not agree to the sale or the sharing of your data.

5. Permissions and their use

  • declarativeNetRequest: blocks ad and tracker requests and changes the privacy headers inside the network engine of Chrome. The extension does not read or log the content of your traffic.
  • storage: keeps your settings, your allowlist and the local counters (section 2).
  • scripting: registers the scripts that the extension runs in web pages, and removes them on allowed sites and when you switch the extension off.
  • activeTab: when you click the extension icon, Chrome gives the extension temporary access to the current tab. The popup uses it only to show the number of ads and trackers that the extension blocked on this page.
  • Host permissions http://*/* and https://*/*: run the page scripts on web sites (cookie banners, hidden ad placeholders, protection against anti-adblock scripts) and add the privacy headers.

6. No sharing with third parties

The extension has no partner ad networks, no "acceptable ads" program, no affiliate redirects and no data brokers.

7. Changes and contact

A new version of this policy comes with the extension update that changes the data use. If you have questions about this policy, contact the developer through the Chrome Web Store page of the extension.