MVweb Image Blocker — Privacy Policy
MVweb Image Blocker is a browser extension that blocks image downloads to save mobile data. This document explains exactly what data the extension reads, sends, and stores.
What we collect
Nothing. We operate no servers and have no telemetry, analytics, error reporting, or remote logging.
What we store
The extension uses your browser's local extension storage (chrome.storage.local). All stored data lives on your device and is removed when you uninstall the extension. We store a single value:
| Key | What | Lifetime |
|---|---|---|
blockingEnabled | Boolean — whether image blocking is currently on. | Until you change it or uninstall. |
Network requests
The extension makes no network requests of its own. Its entire purpose is to prevent requests — it blocks image downloads to save data.
Content scripts
None. The extension never injects code into web pages. Blocking happens at the network layer via the declarative blocking API (declarativeNetRequest).
Permissions
- storage — to remember whether blocking is on across sessions.
- declarativeNetRequest — to block image requests at the network level.
- host access (<all_urls>) — required only so the block rule can match images on any site. The extension reads no page content and makes no requests to those sites; the permission solely scopes where the block rule applies.
Remote code
None. The extension ships no remote code. There is no eval, no remote <script>, no dynamic import(). The manifest enforces a strict Content Security Policy: script-src 'self'; object-src 'none'; base-uri 'none'.
Privacy by default
Blocking is off until you explicitly turn it on. The extension does nothing until you ask it to.
Contact
Questions about this policy: mvweb.ru