Privacy policy

Last updated: 18 November 2026

This notice covers the Shield AdBlock extension for Chrome, Microsoft Edge and Firefox, and visits to shieldadblock.com. This English version lets you read this notice in English. It is updated whenever the notice changes. The original is the German text. If the versions differ, the German version prevails.

The controller, called “the publisher” in this notice, is Amr Makram, c/o COCENTER GmbH, Koppoldstr. 1, 86551 Aichach, Germany. Privacy questions go to privacy@shieldadblock.com. No data protection officer is appointed. The legal notice repeats the address.

The short version

Shield AdBlock does not send browsing history or request data to its publisher. There is no analytics, no telemetry, no crash reporting, no Shield account, and no Shield-generated tracking identifier. There is no publisher service receiving this data.

Visiting this website

You can browse this site without creating an account. The site has no sign-up form. Fonts, images, and site assets are served from this domain. To reach the publisher, the legal notice lists an email address and a WhatsApp link. The site does not load a WhatsApp script or button.

Cloudflare, Inc. delivers and protects this website and processes connection information, including your IP address and the pages you request. The legal basis is Article 6(1)(f) of Regulation (EU) 2016/679 (General Data Protection Regulation, GDPR), the legitimate interest in delivering and securing the site. Cloudflare acts as the publisher’s processor (Article 28 GDPR). Cloudflare keeps connection data only as far as delivery and security require. The publisher cannot access the raw logs and keeps no visit log of its own. See Cloudflare’s privacy policy.

If you install the extension from the Chrome Web Store, Google processes that installation as an independent controller under its own terms. If you install it from Firefox Add-ons, Mozilla does the same.

Email and WhatsApp

If you email us, we receive your email address, message, and any attachments you include. We use this information to respond to and follow up on your inquiry. Emails to shieldadblock.com addresses are first received by Cloudflare, Inc. (Cloudflare Email Routing), acting as the publisher’s processor, and forwarded to the Google mailbox. The mailbox is a free account at Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). Google also processes the messages under its own privacy policy: https://policies.google.com/privacy. We keep the correspondence until the inquiry and any follow-up are finished, then delete it.

The legal notice also links to WhatsApp. Clicking that link loads a WhatsApp page in your browser. WhatsApp then receives connection data, including your IP address, even if you send no message. Opening the link can also start a chat at WhatsApp. WhatsApp Ireland Limited receives your phone number, your WhatsApp profile name, and the message, and delivers the chat to the publisher. According to WhatsApp, it may process the chat outside the European Union, including in the United States, under the EU-U.S. Data Privacy Framework where that decision covers the recipient, with standard contractual clauses as the fallback. The publisher uses the chat only to answer and follow up, then deletes it. WhatsApp keeps its own copy under its policy.

The legal basis for email and WhatsApp inquiries is Article 6(1)(f) GDPR: the legitimate interest in answering people who contact us. Sending a message is voluntary. You can use the website and the extension without contacting us.

Share only what is needed for your question. Please leave out passwords, cookies, and browsing history.

Chrome Web Store Limited Use

Shield AdBlock’s handling of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Shield uses data only to provide the protection and local controls described in this policy. The publisher does not sell user data or use it for advertising, profiling, or credit decisions.

The extension

Bundled protection, ad hiding and the cookie-consent engine run on your device. They do not download blocking sources or consent rules while you browse. Ordinary website traffic continues.

What stays on your device

Durable settings, lists, rules, caches and aggregate counters use the browser’s local extension storage. Session records use the browser’s session storage for the browser session and can survive a background-worker restart. Chrome and Edge also clear them when the extension is reloaded or updated. Shield does not upload this state to its publisher, and it does not sync it to a Google, Microsoft or Mozilla account.

StoredWhat it is
SettingsProtection toggles, the cookie-consent choice, and other local preferences.
Paused sitesHostnames you chose to pause Shield on, or to pause page fixes on, such as example.com. Sites you only visit are not added.
Blocking sourcesWhich lists you enabled, and any custom list URLs you added.
Added-source cacheSupported rules downloaded from lists you enabled, kept so they work offline.
Your rulesFilter text you typed or confirmed. The selection tool (Hide an item) is unavailable in this release; older confirmed rules can still be edited.
Blocking countsAggregate blocked-request totals only. They do not list sites you visited. Production Chrome and Edge do not show these counts.

If you turn on automatic local backups and grant the downloads permission, Shield keeps two rotating JSON files in your Downloads folder. They contain settings, custom rules, site exceptions and list choices. They do not contain request logs or blocking counts. They remain after uninstall until you delete them. Anyone with access to the files can read them. Export creates a local file; sharing it is your choice. Shield does not upload these files.

Activity, a request log, is unavailable in this release on Chrome, Edge and Firefox.

Cookie consent

Cookie consent defaults to Always reject. On supported websites Shield uses that site’s own consent controls. Those controls may save cookies and send website requests even when the choice is reject. Always accept permits the cookies and tracking the website requests. Shield’s blocking stays on. Choosing Off stops later automatic consent actions and does not undo a choice the website already saved. Shield stores the mode you chose and keeps no per-site consent log. The consent engine is packaged with Shield and is not downloaded while you browse. Shield sends no consent data to its publisher.

Network requests

The default lists, including EasyList and EasyPrivacy, are static files compiled into the package. Using them does not contact their authors.

If you turn on a blocking source you added, the extension downloads it from the URL shown for that source. The request carries no Shield identifier, settings or browsing history. The list operator receives ordinary connection details, including your IP address and the time of the download. A locale suggestion does not download anything until you add and enable that list. The suggested lists are served by easylist.to, easylist-downloads.adblockplus.org and raw.githubusercontent.com. An address you enter goes to that address’s operator. Those operators are separate controllers. The publisher has no contract with them. The legal basis is Article 6(1)(f) GDPR, and the list is downloaded only after you add and enable it.

Each download omits cookies and HTTP authentication credentials and rejects redirects. For a refresh of a current list, the browser may revalidate its HTTP cache: it may send conditional headers and provide a cached body after successful validation. Shield stores no HTTP validators and constructs no conditional headers itself. A first download or a filter-grammar upgrade bypasses the browser cache.

After you remove Shield in Chrome or Edge, the browser opens https://shieldadblock.com/uninstall/. That address contains no settings, backup names or profile identifiers.

Permissions

The extension asks for broad website access, storage, and the browser’s blocking interfaces so it can hide and block on the sites you visit. Those permissions are not used to send browsing history to the publisher. Shield processes the address of the page being visited, and related popup, opener, and frame addresses, on the device, to close unwanted popups, look up the top frame during breakage recovery, and find the page’s frames when removing ad-hiding styles. On Firefox, Shield also reads page-navigation updates to decide which page a request belongs to. These reads stay in memory. Shield does not keep a browsing log of pages, titles, or visit times, and it does not send those addresses to the publisher. On Chrome and Edge the browser matches network rules itself. Popup protection inspects a newly opened tab’s address and the page that opened it, in memory only, to decide whether to close an unwanted popup. A temporary count of those closes stays in memory for that tab, ends when the tab closes or the background worker restarts, and is not saved or sent. On Firefox, Shield inspects requests in memory to decide what to block and does not store or transmit those requests. Shield AdBlock 1.0.2 packages omit added-list and user-rule scriptlets. Bundled Page Fixes remain a separate setting. Bundled scriptlets are ten fixed functions packaged with Shield. A list cannot supply a function body.

Packaged scripts in the page’s JavaScript world

The Chrome, Edge and Firefox packages include two fixed helpers that run in the page’s own JavaScript context (the MAIN world), where the browser allows that injection.

With Shield protection and Block YouTube Ads on, both of which are the defaults, Shield injects a packaged helper on youtube.com, youtube-nocookie.com and their subdomains. It hooks player data, JSON.parse and selected fetch and XMLHttpRequest response reads to remove known ad metadata fields locally. Early registration targets top-level YouTube documents at document start; a document-targeted catch-up can also run in eligible YouTube frames. Whole-site pauses and whole-page filter exceptions limit eligibility. This control is separate and does not depend on Ad Hiding or Page Fixes being enabled.

With Shield protection and Ad Hiding on, both of which are the defaults, Shield registers a packaged helper at document start for eligible frames. Only the top-level document and frames that can access its origin install the wrapper. It signals newly created open shadow roots so hiding can apply inside them. It does not expose closed shadow roots. Whole-site pauses, ad-hiding pauses and whole-page filter exceptions limit eligibility. An exception that cannot be represented in the early registration still allows a document-targeted catch-up on eligible documents.

These helpers ship inside Shield and send no data to its publisher. Their code is packaged, not supplied by a page or a list. Turning a registration off prevents future injections and does not undo a wrapper already installed in a document. Reload the page after turning one of these features off, or after pausing it on a site, so that choice applies to those wrappers.

Facebook

On Chrome and Edge, Block Facebook Ads is off by default. If you turn it on, the extension clicks Facebook’s own Hide post control in your browser. The extension sends no data to Facebook or to the publisher. Facebook (Meta Platforms Ireland Limited) may store that action under its own terms and link it to your Facebook account: https://www.facebook.com/privacy/policy. The legal basis for triggering the click is your consent by turning the setting on (Article 6(1)(a) GDPR). You can turn the setting off at any time. Withdrawal does not affect the lawfulness of processing before the withdrawal. Actions Facebook has already stored can remain there. Firefox does not include this setting.

Third parties

The publisher does not receive your browsing history or request data. Website consent handlers may send website requests when Shield selects consent, including the default rejection. Cloudflare, Inc. is the publisher’s processor for delivery of this website and forwarding of emails. Google, for the free mailbox, and WhatsApp Ireland Limited, if you use the link, are independent controllers. A remote list’s operator receives the connection metadata described above and is an independent controller. Meta Platforms Ireland Limited is an independent controller of a Hide post action only if you turn Block Facebook Ads on. Where the EU-U.S. Data Privacy Framework decision covers the recipient, a transfer to the United States relies on Article 45 GDPR. Otherwise, according to that provider, standard contractual clauses under Article 46(2)(c) GDPR are the fallback.

Children

The same policy applies at every age. Shield requires no Shield account and uses no publisher analytics or advertising profiles.

Your choices

Your rights

You can request access, rectification, erasure and restriction, and you have the right to data portability under Article 20 GDPR. Where consent is the basis, you can withdraw it. Withdrawal does not affect the lawfulness of processing before the withdrawal. A message to privacy@shieldadblock.com is enough.

Right to object. Where processing is based on Article 6(1)(f) GDPR (the website, contact messages and filter lists), you can object at any time on grounds relating to your particular situation. A message to privacy@shieldadblock.com is enough.

You can also lodge a complaint with a data protection supervisory authority, in particular in the member state of your habitual residence, your place of work, or the place of the alleged infringement (Article 77 GDPR).

There is no automated decision-making and no profiling under Article 22 GDPR. You are not required to provide data.

Questions and updates

Material changes will be shown here with a new date. For privacy questions, or to request deletion of correspondence, email privacy@shieldadblock.com. Support is at shieldadblock.com/support/.