Support
This page is the logged-out support path. It does not require a GitHub account. Prefer it over repository Issues while the product repository remains private.
In the extension (no network)
- Site not working? in the toolbar popup — guided pause/restore for the current site, plus an optional local redacted JSON report download. Nothing is uploaded; hostname and notes are opt-in only.
- Options → About — privacy policy and this support link.
- Protection Center → Activity — deliberately starts a bounded in-memory Filtering Log after ownership is proven. Opening State starts no capture. Leaving the last Activity owner, stopping capture, or restarting the background clears it.
- Advanced mode — reveals the User rules editor and expert Popup/Options shortcuts to Activity and Host Inspector (static rule lookup). Ordinary Protection Center routes remain available.
Privacy
The store-facing privacy policy lives at https://shieldadblock.com/privacy/.
Chrome filter-list capacity (declarativeNetRequest)
On Chrome, Shield is honest when Chrome’s declarativeNetRequest dynamic network-rule limit omits some network rules from enabled filter lists: Settings shows applied vs omitted network rules per list, and how to free capacity (turn off lists you do not need). Firefox uses a different blocking engine and does not show this Chrome-only quota UI.
Bundled core network rules stay within Chrome’s guaranteed 30,000 static rules. Optional bundled extras use Chrome’s shared static pool only when this profile has room; Settings reports an omitted extra while retaining core protection. User rules and downloaded lists use the separate dynamic pool.
Filter scriptlets and embedded pages
A site pause covers network filtering, cosmetic hiding, and Scriptlets for the top page and same-origin embeds. Filter scriptlets do not run in cross-origin embedded pages (including when the parent is active). Open that host as a top-level tab to receive Scriptlet protection there. The global protection switch is broader: it disables protection on every site.
Contact the publisher
Use this channel when something in the policy looks wrong, a site stays broken after guided recovery, or you need a reply from the publisher.
| Channel | When to use |
|---|---|
| Chrome Web Store / AMO support email | Once the extension is listed — the store’s support field is the primary public inbox. |
| This page | Self-help and the durable public URL to paste into store forms (https://shieldadblock.com/support/). |
| support@shieldadblock.com — monitored public contact before and after listing. | |
| GitHub Issues | Contributors with repository access only — not the public support URL. |
Shield does not operate a ticket server or account system. There is no telemetry back-channel.
Publisher email
The monitored public email is support@shieldadblock.com.
Security
Suspected vulnerabilities in Shield AdBlock itself: contact the publisher at support@shieldadblock.com, and do not file them as ordinary “site broken” reports. Do not include browsing history, cookies, or passwords in any report.