Privacy Policy
Effective date: July 19, 2026
Summary: Focus Field stores your settings on your device. Site blocking uses Chrome’s declarativeNetRequest on hosts you list. Optional webcam timelapse never uploads video. There is no Focus Field account or backend for your data.
Data on your device
- Blocklist — hostnames you choose to block
- Timer settings — focus/break minutes, always-on flag, phase, session counts
- Timelapse prefs — whether recording is enabled, frame interval, window id
Stored via chrome.storage.local.
Site blocking
While a focus session is active or always-on is enabled, Focus Field installs dynamic declarativeNetRequest rules that redirect matching navigations to an in-extension blocked page. Rules are derived only from your list. When idle (and always-on is off), those rules are removed.
Webcam timelapse (optional)
- Runs only if you enable it and start a focus session
- Camera permission is requested in the timelapse window you open
- Frames are processed in that page in memory; export is a local WebM download
- Closing the window stops the camera
Permissions
- storage — settings
- alarms — timer ticks
- tabs / windows — badge and timelapse window
- declarativeNetRequest (+ host access) — block user-listed sites on any host the user may add
What we don’t do
- No Focus Field cloud for blocklists or video
- No selling data
- No ad SDKs in the extension
Website
Static marketing pages may be hosted on GitHub Pages; the host may log standard HTTP requests. That is separate from extension storage.
Changes
Policy updates will change the effective date above.