Privacy policy

02 What stays on your device

• Your blocklist, schedules, and settings are stored in Chrome’s extension storage (chrome.storage.sync), which Chrome may sync across your own signed-in browsers. This data never touches any server of ours — we do not have servers.
• Blocked-attempt counters (shown in Insights) are stored locally (chrome.storage.local), never leave your device, and are deleted automatically after 90 days.
• Blocking itself runs inside Chrome’s declarativeNetRequest rule engine. BlockMe never reads or modifies the content of the pages you visit.

03 The one network request

If you purchase BlockMe Pro, the extension talks to exactly one host: api.polar.sh — the payment provider (Polar, our merchant of record) — to activate and periodically re-validate your license key. That request contains the license key you entered and a random activation identifier. It never contains browsing data, page contents, or your blocklist.

On the free tier, the extension makes no network requests at all.

Purchases themselves happen on Polar’s checkout pages and are governed by Polar’s privacy policy. BlockMe never sees your payment details; the extension stores only your license key and its validation status.

04 Permissions

BlockMe requests the minimum permissions needed to block sites (declarativeNetRequest, storage, alarms, activeTab). Site access (<all_urls>) is optional, off by default, and used only so Chrome can show BlockMe’s block page in place of a blocked site.

05 Contact

Questions: mt@le-max-app.com

06 Changes

If this policy ever changes, the updated version will be posted on this page with a new “Last updated” date.