Sage is built around a simple principle: your focus practice is yours. Sage stores your settings, your focus history, and your blocked-site list locally in your browser. It never reads your task labels, never sees the sites you visit, and never sells or shares your data.
Sage does send a small set of anonymous product analytics so we can understand how many people use Sage and which features matter. These events carry no personally identifying information, no task content, and no browsing data — details below, including how to turn analytics off.
What stays on your device
Everything Sage needs to function is stored in your browser's local storage and never leaves your machine:
- Your timer settings (focus and break durations, sound on/off, etc.)
- Your completed session history (timestamps, durations, task labels you typed yourself, completion status)
- Your blocked-site list (sites you added yourself)
- Your scheduled blocking rules (days and times you configured)
- Sage Premium activation status, if you've activated a license
- Milestones you've reached
- An anonymous install identifier — a random UUID used only as the analytics client ID, never linked to your name or email
What Sage sends to Google Analytics
Analytics is on by default and can be turned off anytime in Sage popup → Settings → Anonymous usage analytics. Once disabled, no events are sent.
When analytics is on, Sage may send the following events to Google Analytics 4:
- extension_installed — sent once, the first time Sage runs after install.
- milestone_reached — sent when you cross a focus-hours milestone (1, 5, 10, 25, or 40 hours), with the milestone number.
- gate_hit — sent when you encounter a premium-gated feature, with the name of the gate (e.g.
session_length). - premium_upgrade_clicked — sent when you click an upgrade link, with the source location.
- premium_activated — sent after a successful Premium activation, with the plan name.
Each event includes the anonymous install ID described above. Analytics never includes your task labels, any URLs you visit, sites you've blocked, the contents of your session log, or any identifying information about you.
What Sage doesn't do
- Sage doesn't read the content of web pages you visit.
- Sage doesn't track which sites you visit. Blocking is purely declarative — rules redirect listed sites without reporting matches anywhere.
- Sage doesn't have access to your browsing history, bookmarks, passwords, or autofill data.
- Sage doesn't sell or share your data with advertisers or third parties (other than the two services described in this policy: Google Analytics for the events listed above, and Lemon Squeezy when you activate a license).
- Sage doesn't ask you to sign in. There are no accounts.
- Sage doesn't show ads.
Why Sage requests Chrome permissions
- storage — saves your settings and focus history locally.
- alarms — fires a reliable timer-end event even if Chrome has suspended Sage's background worker.
- idle — detects when you step away from the computer so Sage can offer to pause the session.
- notifications — alerts you when sessions and breaks end.
- offscreen — plays the session-end chime (Manifest V3 service workers can't play audio directly).
- declarativeNetRequest and declarativeNetRequestWithHostAccess — redirect distracting sites to Sage's calm "blocked" page during focus sessions and scheduled windows.
- <all_urls> host permission — required so blocking rules can match any domain you add to your personal block list. Sage doesn't read page content, inject scripts, or track browsing; the permission is used solely to redirect listed domains to a local page.
Sage Premium & payment processing
Sage Premium uses Lemon Squeezy as the merchant of record for checkout and license delivery. When you subscribe on Lemon Squeezy's site, they collect only the information needed to process the payment (such as your email and billing details) and issue you a license key.
When you enter that license key in Sage and click Activate,
Sage transmits only two things to Lemon Squeezy: the
license key itself, and an auto-generated instance name
(such as Sage Chrome Extension (a1b2c3)) that
helps you track which device you activated on. No focus data,
browsing data, or other Sage data is ever sent.
Lemon Squeezy's own privacy practices are covered in their privacy policy.
Data retention & deletion
Your local Sage data lives in your browser's local storage. Uninstalling Sage deletes everything stored on your machine, including the anonymous install ID.
Analytics events sent to Google are retained according to Google's default GA4 retention policy (currently 14 months). If you'd like your analytics data deleted sooner, email us (see Contact below) and we'll request deletion from Google.
Changes to this policy
If Sage ever changes how it handles data, this policy will be updated and the “Last updated” date below will reflect the change.
Contact
Questions or concerns? Email support@eventsfindermap.com or reach out via the Chrome Web Store listing's support tab.
Last updated: May 17, 2026.