Privacy Policy

Effective date: July 11, 2026

🔒

Your data stays on your device. Always.

FocusSpark is built on a local-first, privacy-by-design architecture. We do not operate servers, we do not transmit your data anywhere, and we do not use product analytics or tracking of any kind. Everything happens inside your browser.

No Servers No Analytics No Tracking No Outbound Connections 100% Local

1 Data We Collect

FocusSpark operates entirely on your local device. We do not operate backend servers. The only data we access is:

Session settings and preferences — timers, blocklists, schedules, themes, sounds, health settings, and extension preferences stored locally via chrome.storage.local or browser.storage.local.
Focus activity and statistics — completed sessions, abandoned sessions, blocked-attempt counts, per-domain local usage totals, achievements, session notes, and optional distraction-journal entries. This data is used only inside FocusSpark.
Current or active tab URL — when you click "Add current tab to blocklist," use the block-current-site shortcut, enable the FocusSpark new-tab page, or when FocusSpark tracks active-tab time locally, the extension reads active tab metadata via the declared tabs permission and the existing <all_urls> host permission scope. This data stays on your device.
Browsing history — only if you explicitly enable Smart Suggestions. When enabled, the extension scans the most recent 7 days and up to 1,000 history entries locally on your device to suggest frequently visited sites. This analysis never leaves your computer and is never transmitted to any server.

2 How We Use Data

All data is used locally to provide the extension's core functionality:

Tracking focus sessions and daily statistics.
Blocking distracting websites during active sessions, wind-down hours, and configured soft-cap limits.
Showing FocusSpark UI such as the popup, floating timer, blocked-page overlay, and optional new-tab page.
Suggesting frequently visited sites to block (optional, local analysis only).
Generating local exports such as JSON, CSV, printable reports, and streak images.

When you add a site to your blocklist, Chrome transforms it into a browser-managed declarativeNetRequest rule. Firefox applies equivalent blocking through browser.webRequest. No traffic data or browsing behavior is sent externally.

3 Data Sharing

We do not sell, share, rent, upload, or transmit your data to third parties. Everything stays on your computer. There are no FocusSpark API calls, no cloud sync endpoints, no advertising identifiers, and no telemetry beacons in this extension.

4 Data Export & Deletion

You can export your data to JSON, CSV, printable reports, or shareable images from the Settings or Analytics panels. You can also clear all stored data instantly using the Reset all data button. Resetting data removes FocusSpark's locally stored state from your browser.

5 Permissions

FocusSpark requests only the browser permissions needed for its local functionality:

Storage — save your settings, sessions, stats, and blocklists locally.
Tabs and host access — read active tab URLs for blocklist actions, local usage tracking, the floating timer, and the optional new-tab redirect.
Blocking APIs — block configured sites inside the browser using Chrome declarativeNetRequest or Firefox webRequest.
Notifications, alarms, and idle detection — run timers, reminders, health nudges, and auto-pause behavior.
History — optional, requested only if you enable Smart Suggestions.

6 Changes to This Policy

We may update this policy as the extension evolves. Changes will be reflected in the extension's store listing and within the extension itself.

7 Contact

If you have questions about this Privacy Policy, please reach out through the support channel on the Chrome Web Store or Firefox Add-ons listing for FocusSpark.