Privacy Policy

UnblockedBlock blocks access to tools commonly used to get around a network content filter: web proxies, unblocked-game mirrors, remote-desktop and virtual-machine services, and cloud-gaming platforms. That is its only function. It does not block ads, does not act as a VPN, and has no feature outside this single purpose.

To decide whether a page is one of the tools described above, the extension's scripts run on the pages you visit and read a specific, limited set of technical signals:

• the addresses of scripts a page loads, and the text of small inline scripts (capped at 32 KB per script, since the technical markers it looks for always appear near the start of a bootstrap script);
• whether the page registers a service worker, and that worker's address;
• the names of cookies and of localStorage/sessionStorage keys, never their values;
• the page's own title, meta description, headings, and address bar text;
• protocol-level details of the connections a page opens - WebSocket, WebTransport, and WebRTC data channels - for example the first few bytes of a message, or how many binary messages arrive in a short window; and of canvas, keyboard-lock and pointer-lock activity. These are used only to recognize remote-desktop and tunneling behavior, never to log what is typed, drawn, or clicked, and never to read the contents of a call or a conversation;
• whether the page compiles a WebAssembly module, and whether it starts a Web Worker or SharedWorker. Only that these things happened is noted, never what the module or the worker contains or does. Both are ordinary on their own and mean nothing by themselves; they matter only alongside the signals above, because one way to build a proxy is to put its network code where page-level checks cannot see it;
• the structure of SVG documents, to catch a technique where a whole website is hidden inside an image file. This looks only at document structure, never at ordinary image content;
• the same signals inside frames on the page that come from the same site. A page can build a frame that the browser does not run our checks in, and put the tool there instead, so the page's own checks look into those frames. Frames belonging to a different site are not readable this way and are not read.

This happens on your device, in memory, and is not sent anywhere. If none of it matches, nothing is kept. If it does match and the page is blocked, only the hostname, a reason code, and a timestamp are added to the local log described next.

Everything the extension stores lives in chrome.storage.local, on your device, and is never synced to a Google account or any server:

• blockLogThe hostname, reason, and timestamp of each block, capped at the most recent 50 entries. Shown in the popup and options page.
• blockCountA running total, shown in the popup.
• customDomainsHostnames you've chosen to block yourself, entered in the options page (up to 1,000).

No account, device identifier, IP address, or location is stored alongside any of this.

It also removes one specific thing. Some of the tools this extension blocks work by installing a service worker - a small program the browser keeps and runs on that site's behalf, even on later visits - and then serving pages out of that worker's own storage. Content served that way does not pass through the browser's normal request path, so a block rule cannot reach it, and it keeps working until the worker is removed. So when the extension blocks a site for that specific reason, it unregisters the service workers that site has installed and clears the cache storage belonging to that site.

This is deliberately narrow. It only ever affects the site being blocked, never another site. It runs only when a page has already been identified as one of these tools, never on suspicion, and never on an ordinary site that happens to work offline. Nothing that is removed is read, copied, or sent anywhere first - it is deleted in place, on your device.

Separately, the extension periodically checks a server the developer operates for an updated block list - new bypass sites discovered since this version was published, without waiting for a new Chrome Web Store review. About once an hour it requests a single JSON file of hostnames and URL patterns. That file is plain, readable data and nothing else: no code is downloaded or run, and the file can be viewed directly at unblockedblock.pages.dev/rules.json. The request carries no browsing history, no list of sites you have visited, and nothing else identifying you - there is nothing in it to carry, because the update flows one direction only: server to device.

Where this extension is deployed by a school or employer through Chrome Enterprise, an administrator can set two optional lists (hosts to always allow, and extra hosts to always block) through the Google Admin console. This is read from chrome.storage.managed, which is controlled by device policy: the extension only reads it, never writes to it, and a user cannot edit it from inside the browser.

• Send browsing activity to any server
• Sell or share data with anyone
• Use accounts, ads, or trackers
• Sync data across your devices
• Keep or send anywhere what it reads from a page it doesn't block
• Record keystrokes, clicks, or mouse movement
• Read cookie or storage values
• Access passwords or payment details

The options page has a Clear log button that erases the local block history immediately, and a Clear temporary blocks button that lifts any block created by the on-device checks (rather than the built-in list) for the rest of the browser session. Removing the extension deletes everything it has stored.

• declarativeNetRequestBlocks known bypass sites and known bypass infrastructure at the network level, using rule lists that ship inside the extension itself.
• storageHolds the local log, your custom list, and (if managed) an administrator's policy, all described above.
• site accessLets the detection scripts in section 02 run on the pages you visit. This is required because bypass tools can appear on any domain, not a predictable list.
• alarmsSchedules the hourly block-list update described in section 03. Does nothing else.

This extension is often deployed on school networks and used by students. It does not knowingly collect personal information from anyone, of any age. Because it does not collect personal information at all, the same is true for children using it.

If what this extension collects or does ever changes (for example, if a future version adds a server-connected feature), this page will be updated first, the date at the top will change, and the change will be reflected in the extension's Chrome Web Store data-usage disclosure at the same time.