blockx privacy policy

Effective 24 August 2026

The controller for the blockx browser extension and the blockx.work website is:

iconic.one GmbH
Scanbox #09285, Ehrenbergstr. 16a
10245 Berlin
Germany

Represented by Alexander Gutjahr. Privacy contact: hello@iconic.one.

The extension and website are separate surfaces with different data practices. Fathom Analytics is loaded only by blockx.work; it is not included in or contacted by the extension. The source code for both is public in the blockx repository.

The blockx browser extension

The Chrome Web Store privacy-policy link points directly to this section. The extension works locally and does not contain analytics, advertising, user accounts, behavioural tracking, or remotely hosted code. It makes no network requests and does not send data to the developer or any third party.

Data the extension handles

• Your blocklist. Domain names, enabled state, and subdomain preferences are stored in chrome.storage.local on your device. They are not synced by blockx.
• Navigation URLs. Chrome delivers navigation event URLs to blockx through the webNavigation permission. blockx checks them locally against your blocklist and immediately discards them. It does not save browsing history. When a navigation is blocked, only its hostname—not its path, query, fragment, or credentials—is passed to blockx’s internal blocked page.
• Theme preference. A light or dark theme choice is stored in the extension’s local browser storage.

blockx does not collect identifiers, page content, form data, authentication information, advertising data, telemetry, or error reports.

Permissions

• storage stores the blocklist locally.
• declarativeNetRequest lets Chrome enforce the local blocking rules.
• webNavigation lets blockx catch navigations served from a site’s service-worker cache and replace Chrome’s raw blocking error with its own local page.

blockx has no host permissions, content scripts, or access to page contents. If you allow the extension in Incognito, the same local blocklist is used there; blockx still does not retain navigation URLs.

Control and deletion

You can edit or remove every stored blocklist entry from blockx. Removing the extension or clearing its extension data removes blockx’s local data. Chrome controls any browser data outside the extension’s storage.

The blockx.work website

blockx.work is a static product and documentation site. It has no user accounts, advertising, embedded social media, or forms, and it does not set cookies. Its fonts and other visual assets are served from blockx.work itself. The website uses Fathom Analytics for aggregate usage statistics and is hosted by Vercel.

Fathom Analytics

We use Fathom Analytics to understand aggregate page views and referrers so we can evaluate and improve the website. Fathom is provided by Conva Ventures Inc., 26 Bastion Square, Third Floor, Burnes House, Victoria, British Columbia, V8W 1H9, Canada, acting as a processor on our behalf.

When you visit blockx.work, your browser loads a deferred script from cdn.usefathom.com and sends a page-view request to Fathom. That request includes the page and referring page and, as part of a normal web request, your IP address and user-agent information. Fathom uses those details transiently to count visits and derives aggregate information such as country, browser, and device type. It does not use cookies and does not store raw IP addresses or user agents alongside browsing activity. Daily salted visitor hashes are deleted at midnight. Fathom may retain IP-based request counts for up to 24 hours, and may retain an address longer if needed to block a serious attack.

Fathom routes visitors in the EU through its EU Isolation infrastructure, where their IP addresses are processed and stripped before anonymous analytics data is sent to its US-hosted reporting infrastructure. We configure the script to honour your browser’s Do Not Track setting. If Do Not Track is enabled, Fathom does not record the visit.

This processing rests on Art. 6(1)(f) GDPR: our legitimate interest in understanding whether the site is useful and which pages need improvement while using a data-minimising analytics service. We keep the aggregated reports while they remain useful for those purposes and delete them when they are no longer needed. You may object to this processing using the privacy contact above.

More information is available in Fathom’s privacy notice, data-processing agreement, and data journey.

Hosting with Vercel

Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA, hosts blockx.work and acts as a processor on our behalf. Vercel receives standard connection data such as an IP address, request time, requested path, referrer, and browser information so it can transmit the site and protect its infrastructure. That processing rests on Art. 6(1)(f) GDPR: our legitimate interest in delivering the site reliably and securely.

Any server-side execution is configured for Vercel’s Frankfurt region; the static files themselves are delivered from whichever edge location is nearest the visitor. International transfers are protected by the safeguards described in Vercel’s Data Processing Addendum. Vercel’s Privacy Notice provides more information about its processing and retention.

Your rights

Where personal data is processed, you may request access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), portability (Art. 20), and you may object to processing based on legitimate interests (Art. 21). Write to hello@iconic.one.

You may also complain to a supervisory authority (Art. 77 GDPR). For this controller that is the Berlin Commissioner for Data Protection and Freedom of Information.

Neither the extension nor the website uses automated decision-making or profiling.

Changes and contact

Material policy changes will be published here and noted in the project changelog. General questions can be raised through the repository’s GitHub issues. Issues are public, so do not put anything private in one; use the email address above instead.