Back to Blockade Privacy Policy

Privacy Policy

Last updated: July 2026

Hi there. We built Blockade to help you recapture your focus, not to collect or monetize your personal data. Here is the absolute, no-nonsense truth about how Blockade handles your privacy.

1. Local Browsing Data Rule (Zero Browsing Logs)

Your browsing history is entirely your business. Your manually configured domain blocklists, active bypass timer timestamps, and configuration preferences are processed and stored exclusively inside your browser memory container using chrome.storage.local. Blockade **never** tracks, logs, transfers, or uploads the websites you visit or the domains you choose to block to any external servers.

2. Cloud-Based License Verification

Blockade utilizes a highly secure, cloud-hosted backend infrastructure (via Supabase) solely to verify your account's subscription tier. When the extension starts up or runs its automated background synchronization routine, it sends a localized network handshake containing your distinct, randomized Chrome Extension Runtime ID. This handshake reads your corresponding activation tier (such as FREE_PASS, ANNUAL_PASS, or LIFETIME_PASS) and subscription expiration timestamps. This data is used exclusively for feature access control and is never linked to your local blocklist setups.

3. Extension Permissions Disclosure

To insulate your attention spans cleanly, Blockade leverages sandboxed Manifest V3 APIs to operate efficiently and transparently:

  • declarativeNetRequest: Instructs the browser to drop network connectivity to targeted distractions completely locally, without reading raw page contents or network payloads.
  • tabs: Used exclusively to evaluate if a restricted site is open in an unrefreshed window when updating preferences, allowing instant focus routing.
  • alarms & storage: Scheduled locally to run background cooldown timers and maintain your personal blocklist records across browser restarts.

No third-party behavioral analytics, telemetry frameworks, session eavesdropping scripts, or external data scrapers are present in the source code.