Focus Lock for Chrome

Privacy with a visible boundary

Focus Lock checks page addresses and applies blocking rules inside Chrome. It does not send extension data to a developer-controlled server.

Policy summary

Local first, with optional Chrome Sync

Full URLs, focus intentions, detailed session events, and live sessions remain in the local Chrome profile. Chrome Sync receives a smaller approved set only after the user confirms setup with sync enabled.

Data boundaries

What stays local and what can sync

This Chrome profile only

Local data

  • Full URLs used for rule matching and blocked-attempt records
  • Focus intentions entered for sessions
  • Detailed session events and gate outcomes
  • Live sessions, active gates, and temporary site unlocks
Optional, after setup confirmation

Chrome Sync data

  • Settings and block or allow lists
  • Site access credit and streaks
  • Per-device daily and monthly session totals and domain-level blocked-attempt counts
Not part of the extension

No developer data service

  • No developer-controlled server
  • No advertising or behavioral profiling
  • No sale of user data
  • No remotely hosted executable code

Your controls

Export, disable, and delete

Export local history

In Settings, open Privacy and data, then choose Export local event log. The JSON export contains the detailed event log from this Chrome profile.

Delete local history

Delete local history removes historical full URLs, focus intentions, and detailed session events from the local event log. In local-only mode, it also removes local aggregate statistics. It does not clear the current live-session runtime, which holds the focus intention and the address of each tab the session is blocking. A session set to run until stopped holds that runtime until you end it. Retention below says what ending a session clears.

Control Chrome Sync separately

Turn off Chrome Sync for Focus Lock to stop future synchronization. Disabling sync does not delete existing remote copies. After sync is off, use Delete remote Sync data to remove Focus Lock data stored through Chrome Sync while keeping local settings and statistics on this device.

Delete everything

The same page can delete all Focus Lock data. In Settings, open Privacy and data, then choose Delete all Focus Lock data. It removes every Focus Lock record from this device and any Focus Lock copies left in Chrome Sync, then returns the extension to setup. It is available while no session is running.

Website access

Why blocking needs broad site access

Focus Lock asks for optional access to HTTP and HTTPS websites during onboarding. The extension needs this access because categories, custom rules, and allow-only sessions can apply to any top-level website.

That access is used to read the current page URL, stop a fresh blocked navigation, add or remove the packaged Focus Lock blocking interface, and mute or restore an affected tab. The blocking interface is extension-provided content. Focus Lock does not inspect or collect page text, images, form fields, passwords, messages, or other website content.

Blocking is enforced by the extension's service worker. If Chrome has not woken the worker when a page starts loading, that page can load before the block applies. Focus Lock does not use declarativeNetRequest rules. A page that loads that way is re-evaluated once the worker answers.

Retention

Data remains until its limit or your action

Detailed local events
The local event log keeps at most 50,000 records. New records replace the oldest records after that limit.
Daily aggregate statistics
Daily records use the retention period selected in Settings. The default is 90 days. Older daily records roll into monthly session totals and domain-level blocked-attempt counts.
The running session
The runtime of a running session holds the focus intention and the address of each tab the session is blocking, and it lasts as long as that session lasts. A timed session ends on its own. A session set to run until stopped has no timer, so it lasts until you end it. Delete local history does not reach this runtime, which is deliberate, because a session cannot keep enforcing if the state it runs on is deleted underneath it. Ending a session clears the session and its intention, and starts a cleanup that sends one clear instruction to each website tab open at the time, whether or not that tab was blocked. Each instruction holds that tab's address while the cleanup runs, and the cleanup removes every stored address when it completes.
Settings and monthly aggregates
Settings remain until the user changes or deletes them. When sync is enabled, Focus Lock can discard the oldest monthly aggregate records if needed to fit Chrome Sync's storage quota. Chrome and Google can also apply their own account and storage rules.
Everything at once
Delete all Focus Lock data, under Privacy and data in Settings, removes every Focus Lock record from this device and any Focus Lock copies left in Chrome Sync, then returns the extension to setup. It is available while no session is running.

Chrome and Google

Chrome Sync is operated by Google

Focus Lock reads, writes, and deletes the disclosed Chrome Sync data through Chrome's extension APIs. The developer does not receive or retain a separate copy. Data handled by Chrome or Google is governed by the Google Privacy Policy and applicable Google Chrome Terms of Service.

Focus Lock's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.