Privacy Policy

Summary

SupafastBlock does not collect any personal data. It sends a small number of anonymous, aggregate usage events (for example, "the popup was opened" or "blocking was toggled") to our own self-hosted analytics server, so we can see which features are actually used. These events never include the pages you visit, page content, or anything that identifies you personally. Everything else the extension writes stays on your device and within your own Chrome profile.

Data We Do Not Collect

SupafastBlock does not collect, transmit, sell, or share any of the following:

• Browsing history or visited URLs
• Page content
• Personal information of any kind (name, email, account identifiers)
• Crash reports
• Any device or account identifiers

Anonymous Product Analytics

To understand which features are used (for example: opening the popup, turning blocking on or off, adding a site to the allowlist, changing a setting), SupafastBlock sends anonymous event names to our own self-hosted PostHog instance at posthog.supafast.tech. Each event is tied only to a random ID generated on your device (not your Google account, IP, or any other identifier we control) and includes at most:

• The event name (e.g. blocking_toggled, popup_opened)
• Whether a toggle was turned on or off
• The extension version
• An aggregate daily count of blocked requests, broken down only by coarse category (ads, trackers, annoyances) - a set of numbers only, never which requests or which sites

We never send the URL, domain, or content of the page you are on. As with any network request, the destination server incidentally sees the IP address the request came from (standard for any web request) - we do not use it to identify you. This analytics data is not sold or shared with third parties and is used only to improve the extension. If you uninstall the extension, Chrome may open a short, optional survey page on supafast.tech asking why - answering it is entirely optional and only sends the single reason you pick, tied to the same random on-device ID.

Data Stored Locally on Your Device

The extension stores the following data exclusively in your browser using chrome.storage.sync and chrome.storage.local:

• Global toggle state - whether ad blocking is enabled or disabled
• Per-site allowlist - domains where you have disabled blocking
• Annoyances toggle state - whether cookie banner blocking is enabled
• Element zapper rules - CSS selectors for elements you have chosen to hide per hostname
• Statistics - aggregated counts of blocked requests and hidden elements, stored as daily buckets
• Anonymous analytics ID - a randomly generated identifier (not tied to your identity), used only to group your own anonymous analytics events together

chrome.storage.sync data is synced by Chrome across your own signed-in Chrome instances using your Google account. This sync is managed entirely by Chrome and Google - SupafastBlock has no access to or control over this sync channel. chrome.storage.local data stays on the local device only.

Remote Servers

Filter rules are bundled inside the extension package and are updated only when you update the extension through the Chrome Web Store - they are never fetched at runtime. The only network requests SupafastBlock makes on its own are the anonymous analytics events described above, sent to our self-hosted server at posthog.supafast.tech.

Third-Party Services

SupafastBlock uses PostHog (self-hosted by us, not PostHog Cloud) for anonymous product analytics, as described above. No other third-party SDKs, analytics libraries, or remote APIs are used.

Contact

For questions about this privacy policy, contact: adblock@supafast.tech. Developer: Supafast Tech. Website: https://supafast.tech