Last updated: July 12, 2026

What data the extension accesses

To block ads and trackers, Adwipe inspects network requests and page content entirely on your device:

• Network requests — matched against a local blocklist. Chrome's declarativeNetRequest engine does this locally; the extension never sees a log of your browsing.
• Element picker — when you click “Block an element”, a script is added to that tab so you can point at what you want hidden. It records only the CSS selector of what you clicked, on your device. It is not injected at any other time.
• Page content — content scripts hide leftover ad elements and skip YouTube video ads. This runs in the page and sends nothing anywhere.

What data the extension stores

Saved locally via storage.local, never leaving your device:

• Whether protection is on or off
• Your per-site allowlist
• A count of ads blocked, and a 30-day per-day tally
• Any filters you write yourself
• Any elements you hide with the picker, and which site they belong to
• Your chosen theme and per-site blocking level

Remove the extension to erase all of it.

What the extension does NOT do

• No personal data collection
• No browsing history collection
• No tracking or analytics
• No telemetry
• No data sent to any server
• No data sold or shared
• No account or sign-up

Permissions explained

Permission	Why it is needed
declarativeNetRequest	Block ad and tracker requests locally
declarativeNetRequestFeedback	Count how many requests were blocked
storage	Remember your settings and allowlist
tabs	Show the correct blocked count for the active tab
alarms	Periodically refresh the blocked-count total
scripting	Injects the element picker into the current tab, and only when you click “Block an element”. Never injected automatically.
host_permissions (<all_urls>)	Apply ad blocking on sites you visit

Where settings are kept

Settings — your allowlist, per-site levels, your own filters, hidden elements and theme — are stored with Chrome’s storage.sync, so they follow your Chrome account to your other computers if you have sync switched on. That transfer is handled by Chrome, not by Adwipe, and the developer has no access to it. Counters stay on the device.

Third parties

Adwipe uses no third-party services, SDKs, or analytics.

Contact

Questions: somshrestha3669@gmail.com