Privacy Policy
Last updated: June 2026
Hi there. We built Blockade to help people recapture their focus, not to collect or monetize your personal data. Here is the absolute, no-nonsense truth about how Blockade handles your privacy.
1. 100% Local Data Rule (Zero Logs)
Blockade is engineered with a strict **zero-server infrastructure**. 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. We do not own, lease, or operate external cloud databases that capture your data, meaning your browsing habits never leave your local machine.
2. Payments & Licensing Status
The current public distribution version of Blockade operates natively as a baseline utility. No payment collection mechanisms, financial data arrays, or external merchant gateways are integrated into the source code of this release. Future implementations of alternative access options (such as Annual or Lifetime Passes) will utilize dedicated, PCI-compliant third-party merchants of record to guarantee financial isolation, and this policy will update explicitly when those modules launch.
3. Extension Permissions Disclosure
To insulate your attention spans cleanly, Blockade leverages standard, sandboxed Manifest V3 APIs to operate 100% offline:
- declarativeNetRequest: Instructs the browser to drop connectivity to targeted distractions completely locally, without reading raw 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 background analytical trackers, telemetry frameworks, session eavesdropping scripts, or external data scrapers are present in the source code.