Focus Anchor — Privacy Policy

_Last updated: 2026-05-15_

## TL;DR

Focus Anchor stores your task list **on your own device only**. It does not transmit your tasks, browsing data, page contents, or any other information to the developer or to any third party.

## What data the extension handles

- **Task text you type.** The current queue of tasks and the archive of recently-completed tasks (max 50), stored via the Chrome `storage` API.

- **A small amount of UI state.** Whether the bar is currently shown or hidden (`isPaused`), and which task in the queue the bar is currently pointing at (`cursorId`).

- **Settings.** Theme preference (`auto` / `dark` / `light` / `warning`) and a few internal flags (whether the brief done-confetti is enabled, whether the bar pushes page content down, whether cross-device sync is enabled). All stored via the Chrome `storage` API.

Focus Anchor never reads the content of the web pages you visit. The persistent task bar is rendered by the extension into an isolated Shadow DOM; the extension does not parse or transmit anything from the underlying page.

## Optional cross-device sync

If cross-device sync is enabled, your task list is stored in `chrome.storage.sync`, which is provided by Google Chrome and synced via your Google account. The developer of Focus Anchor has no access to this data. You can review and clear Chrome's sync data at any time at https://chrome.google.com/sync.

## Third parties

None. Focus Anchor contains no analytics, no telemetry, no error reporting, no advertising SDKs, and makes no network requests.

## Permissions and why they exist

- `storage` — to save your task list and settings between browser sessions and across tabs.

- **Content-script match pattern (`http://*/*`, `https://*/*`)** — required to render the persistent task bar on top of every web page (the core feature of the extension). The extension does **not** read page content; it only injects its own UI into an isolated Shadow DOM. No `host_permissions` are declared in the manifest; access is granted exclusively through the content-script `matches` pattern above, which is narrower than `<all_urls>` (it excludes `file://`, `ftp://`, and `chrome-extension://` schemes).

## Contact

Questions or requests: zabroevg@gmail.com

## Changes to this policy

If the policy ever changes, this document will be updated and the change date above will be incremented. Users will see the new policy linked from the extension's Chrome Web Store listing.