Last updated: May 2026
This privacy policy describes how the Focus Mode Chrome extension handles your data. We take your privacy seriously.
Focus Mode collects no data whatsoever. The extension does not collect, transmit, or share any personal information, browsing history, or usage statistics. No data is sent to any server — there are no analytics, no telemetry, no ads, and no third-party services of any kind.
All data is stored exclusively on your local machine using Chrome's
chrome.storage.local API. The following pieces of data are
stored locally and never leave your device:
storage — Used to save your blocked-domains
list and session preferences locally so they persist between browser
restarts.
alarms — Used to run a background timer that
counts down the remaining focus-session time. The alarm fires approximately
once per second and never triggers any network activity.
declarativeNetRequest and
declarativeNetRequestWithHostAccess — Used
to redirect (block) the websites you specify during a focus session. The
browser matches navigation requests against the block list directly — no
request data is inspected, logged, or transmitted.
host_permissions (<all_urls>) —
Required so that the extension can redirect requests on any domain you add
to your block list. The extension never reads or modifies page content; it
only intercepts navigation to the specific domains you choose.
web_accessible_resources — The
blocked.html page is served from the extension itself when a
blocked site is visited. This is the page you see instead of the
distracting website. No external resources are loaded.
None. Focus Mode does not use any third-party APIs, CDNs, analytics services, crash reporters, or external fonts. Every resource is bundled with the extension and loaded locally.
The extension never makes network requests of any kind. There is no phone-home mechanism, no update pings, and no background communication with any server.
If this policy is updated, the "Last updated" date at the top of this page will be revised. Your continued use of the extension after changes constitutes acceptance of the updated policy.
If you have questions about this privacy policy, please open an issue on the GitHub repository.