1. Introduction
Hoot Focus Timer is a focus timer and to-do list for Chrome. It records how long you focus, organises that time by project and task, and shows which websites the time went to.
This policy covers three things: what information Hoot Focus Timer handles, when it handles it, and what control you have over it.
It is built by Aryan Baki, an independent developer. Google sign-in and account backup are optional. You can use the timer without signing in.
2. Information Hoot Focus Timer processes
Information you create
- Project names, descriptions, colours and icons
- Task names, notes, colours, icons, cumulative time goals and optional per-session planned durations
- Session dates, start and end times, and duration
- Paused time within a session
- Manually recorded focus time
- Notes you write, including rich text and any images you insert
- Completion status for projects and tasks
- Your settings — website dark-mode preference, idle threshold and automatic pause, retention period, view preferences, timer configuration and website blocklist
Browsing information processed during an active focus session
- Website hostname, for example
wikipedia.org - Page URL and path, after the redaction described below
- Page title
- Search terms taken from a URL's query string, such as the
q=value on a search results page - Time spent on each website, and the timestamps needed to build your reports
- Whether you were idle, or had Chrome in the background
Derived work progress and completion notifications
Hoot Focus Timer derives XP and time milestones locally from automatically recorded work, including work outside Chrome. Pauses, breaks, manual entries, sample data and known distraction intervals do not earn XP. Configured website rules identify known distractions; browser metadata cannot determine mental attention. This calculation preserves your focus totals and uses no additional page collection.
Local derived metadata includes credited work amounts keyed by session ID, an exclusion flag on activity intervals, completed timer rounds, task queues, pending completion choices and notification delivery status. Reward credits remain after activity-detail retention or deletion so retries cannot award the same work again. Clear all data resets them. These fields are included in JSON backups and your existing optional account backup when you enable sync.
Work and break notifications use Chrome's notification API and are enabled by default. You can disable them in settings. Browser notifications are silent and show generic phase text without task names, website details or page content. A notification click opens Hoot Focus Timer; it does not start work or mark a task complete. Your completion choices remain saved when Chrome or the operating system blocks notification delivery.
Start reminders and local timer sound
Start reminders are enabled by default. They can appear after opening Chrome or returning after 30 minutes of observed idle, locked or outside-Chrome absence. This observation runs independently of session tracking and automatic pause. It stores only local scheduling timestamps, a local date for Skip today, and opaque occurrence/tab/document claims. It does not save webpage addresses, titles, body text or input, and this device state is excluded from backups. Running work and breaks are not interrupted; paused sessions can offer Resume. You can dismiss, skip today or turn reminders off.
Project and task choices and new-task text stay inside an extension-origin frame, separated from the website. The page receives only a public dialog identifier and generic labels, not your catalog or typed task names. Temporary document/navigation identity and private dialog credentials live in Chrome session storage, excluded from backups and cleared on browser restart. Web Navigation permission detects real document and single-page navigation changes so an old dialog cannot change a newer session. It does not add browsing-history collection.
Work and break boundaries can play a short tone generated entirely inside an extension offscreen document. No sound file is downloaded, no microphone is used, and no audio leaves the device. Mute alerts persists in settings and is separate from browser notifications. Boundary and delivery status are saved before delivery so alert failures cannot lose your recorded time or completion choices.
Website appearance outside a focus session
Website appearance runs on supported webpages even when no session is running. It reads page styles and computed colours locally to generate Dark or Light colors and apply brightness, contrast, sepia, and grayscale, or uses supported native dark styling with the default dark filters. The bundled engine may request a page's linked stylesheets with credentials omitted. AO3's native Reversi stylesheet is also requested from AO3 with credentials omitted; this does not change your AO3 account settings or page URL. These styling reads are not saved as browsing activity and are not sent to Hoot Focus Timer's backend. The Website appearance panel controls styling and a host-only site list. Hosts include subdomains; pasted page URLs save only the host, without paths, queries, or credentials. These preferences are included in local backups and in cloud backups when you opt in. Styling does not start session tracking. Chrome and extension pages and the Chrome Web Store are unsupported. The moon button opens the panel; Hoot Focus Timer's own interface remains dark.
Redaction applied before focus records are stored
Before a web address is written to a durable focus record, Hoot Focus Timer removes:
- any username or password embedded in the address;
- the fragment — everything after
#; - any query parameter whose name looks credential-bearing, including
token,access,auth,authorization,bearer,code,credential,jwt,key,oauth,password,refresh,secret,session,signatureandsigned.
Only http and https pages are recorded. Chrome's own internal pages and other address schemes are never recorded.
Keyword blocking. If you add words to a block list, Hoot Focus Timer compares the address and the tab title of a page you open with those words while that list is on, whether or not a timer is running. The check happens in memory on your computer. It is not added to your focus records, and the page itself is still never read. What matched, and any page you let through with “Ignore this one”, are kept only in Chrome’s temporary session storage and are gone when Chrome closes. Limits that count how often you open a site store a number per day, not addresses.
3. When information is processed
Browsing information is recorded only during a running focus phase of a tracked focus session. Specifically:
- While focus is running — website activity is recorded.
- During a Pomodoro break — no website activity is recorded, and break time is excluded from focus totals.
- While a session is paused — no website activity is recorded. Paused time is also excluded from your focus totals.
- After a session is stopped — no website activity is recorded.
- When no session exists — no website activity is recorded. Installing Hoot Focus Timer and never pressing start records nothing about your browsing.
- Manual time entry — records only the project, task, date, duration and any note you type. No browsing information is attached, and none is invented.
4. How information is used
Information is used only to operate the features of the extension:
- To run the focus timer and keep its elapsed time accurate
- To connect recorded time to your projects and tasks
- To build your session history
- To show which websites your focus time went to
- To calculate the totals and charts on your dashboard
- To recover a session that was interrupted by a browser restart
- To save your settings and preferences
- To support the export, import and deletion features
Your information is not used for advertising, profiling, credit decisions, or sale to data brokers.
5. Local storage and data transmission
- Hoot Focus Timer stores your information locally, using Chrome's extension storage on your own device.
- If you choose Google sign-in, Google and Supabase process your name, email address, basic profile information and account identifier to authenticate you. Hoot Focus Timer does not request Gmail access.
- Your data stays local until you click Sign in with Google beside the cloud-backup explanation. That click authorizes automatic backup and restore after Google verifies your account, without a separate enable-sync step. Sync sends projects, tasks, notes, completed sessions, the session-ID XP ledger, retained redacted website activity and preferences, including your blocklist, to the Hoot Focus Timer Supabase backend. Active sessions stay on their original device; linking waits until the timer ends.
- Session tracking makes no backend requests while you are signed out. If you have a Hoot Pro license key, Hoot sends only that key to
hoot-focus-timer.vercel.appto check that your plan is active; no task, timer or browsing information is sent with it. Website styling can request linked stylesheets from their existing hosts. Sign-in and enabled sync make requests to Google and Supabase. Images, icons and animations are bundled inside it — including the small icons beside website names, which come from icons bundled with the extension or from Chrome's own local icon cache rather than from an outside favicon service, because requesting one would itself reveal to a third party which sites you had visited. - You may deliberately export a backup file. Once exported, that file is an ordinary file on your computer and you control where it is stored or shared.
Hoot Focus Timer uses chrome.storage.local, not Chrome's synchronised storage. Your working record remains in this Chrome profile. With account sync enabled, a server backup can restore completed focus data after a reinstall or on another device. Account credentials are stored in extension-origin IndexedDB, separate from focus records.
6. Chrome permissions
Chrome shows a list of permissions when you install any extension. Here is what each one lets Hoot Focus Timer do, and why it is needed.
| Permission | What it allows, and why |
|---|---|
| Access to all websites | Hoot Focus Timer records addresses and titles during running focus to attribute focus time. People work across many different sites, such as documentation, dashboards and web apps, so those sites cannot be specified in advance. Access also lets Hoot Focus Timer show its floating timer and redirect sites you explicitly add to an enabled focus blocklist. |
| Tabs | To see which tab is currently active and read its address and title, so time is attributed to the right website. Also to check a page’s address and title against words you chose to block, and to count how often you open a site that has an opens limit. |
| Scripting | To show the floating timer and an eligible start reminder on pages that were already open. |
| Web Navigation | To validate the current document and invalidate stale dialogs after document or single-page navigation. Raw navigation addresses are kept only in temporary Chrome session storage for eligibility, never added to focus records by this feature. |
| Idle | To pause focus automatically after your configured inactivity threshold or device lock, and resume on activity. You can disable automatic pause; idle time then remains a separate activity category. Independent reminder scheduling observes idle/locked absence without saving page metadata. |
| Alarms | To checkpoint a running session periodically, so its elapsed time survives the browser closing or restarting; also to schedule start reminders, phase boundaries and local absence checks. |
| Notifications | To display silent work/break notifications and open your saved completion choices. This permission adds no page collection or network transfer. |
| Offscreen | To generate a short local work/break tone in an extension document when tabs or the popup are closed. No microphone, external audio or additional page collection is used. |
| Identity | To open the optional Google sign-in flow and return its result to this extension. |
| Storage | To save your projects, tasks, sessions, notes and settings on your device. Unlimited Storage keeps the working record and account merge base without Chrome’s 10 MB local-storage cap. |
| Favicon | To show the icon of a website next to its name in the Blocks and Dark mode lists, read from Chrome's local icon cache. No request is made to the website or to any icon service. |
| History (optional) | Asked for only if you turn on History in the Blocks page; Hoot works without it. To show your Chrome browsing history by day and hour, search it, export the range you are looking at to a file on your device, and delete the visits, hours or days you choose. Your history is read from Chrome while that page is open. It is not copied into Hoot's storage, not included in your backup, and not sent anywhere. If you add a site to “Do not record”, Hoot deletes that site's pages from your Chrome history as Chrome records them; only the list of site names is saved, on your device. |
| Sessions (optional) | Asked for together with History. To list the tabs open on your other signed-in Chrome devices, as Chrome reports them, in the same page. The list is shown and not saved or sent anywhere. |
| Declarative Net Request | To redirect top-level navigation to domains and subdomains in your enabled blocklist during running focus. Matching open tabs also redirect when blocking begins. Rules release on breaks, pauses and completion; embedded resources stay available. Your blocklist is stored locally and included in your backup when you enable account sync. |
8. Hoot Pro and payments
Hoot Focus Timer is free to use. Hoot Pro is an optional paid plan (monthly, yearly or a one-time lifetime purchase) that adds extras such as unlimited tasks, unlimited blocked sites and every background scene. The timer works without it.
- Choosing "Get Pro" opens a checkout page hosted by Stripe in a new browser tab.
- Stripe processes your payment and billing information under Stripe's own privacy policy.
- Hoot Focus Timer does not receive or store your full card details.
- After checkout you receive a license key that starts with
HOOT-. The extension keeps it on your device and sends only that key tohoot-focus-timer.vercel.app, to check whether your plan is active and to open Stripe's page for managing or cancelling it. The reply contains your plan's status and dates. - Your focus records and browsing information are never sent to Stripe, and never sent with the license check.
9. Data retention, export and deletion
Your information stays on your device until you change or remove it.
- Automatic retention — detailed website-activity records are kept for a period you control in Settings. The default is 90 days, adjustable from 1 day to 10 years. Older detail is removed automatically.
- Delete individual records — any session, project, task or note can be deleted from the dashboard.
- Delete website detail only — Settings can erase all retained page and domain information while keeping your session durations and totals.
- Delete everything — Settings includes a "clear all local data" action.
- Export — you can save your sessions or website activity as CSV, or take a complete JSON backup that can be restored later.
- Uninstall — removing the extension from Chrome removes its locally stored data with it.
Signing out pauses sync and keeps local data. A verified sign-in during an active timer keeps a pending linking choice in private extension storage and completes it automatically when the timer ends. Cancelling a later chooser, signing out, revoked account access or requesting cloud deletion clears that choice. Account switching and conflict resolution retain local recovery copies. Account metadata and these copies remain until the extension is uninstalled; clearing the current focus record does not remove them. Uninstalling removes local data and credentials but keeps an enabled account backup for restoration. Account controls let you export or delete the cloud backup; deletion also disables automatic sync on that device. The server keeps a deletion revision, and the extension asks you to choose before recreating a deleted backup. Clearing local data while linked updates your cloud backup at the next sync. Supabase infrastructure backups have separate provider-managed retention. Contact the developer below to request deletion of your account identity.
10. Data security
Local tracking uses Chrome’s extension storage. Optional cloud backups use HTTPS and database access rules that restrict each signed-in user to their own backup. Server administrators retain administrative access.
Beyond that, Hoot Focus Timer limits data handling to what its features actually require, and it redacts web addresses before storing them, as described in section 2. It relies on the isolation and storage protections Chrome gives extensions.
No software can promise perfect security, and this policy does not. Your device, your Chrome profile and any backup file you export are ultimately in your hands.
11. Children's privacy
Hoot Focus Timer is intended for adults, including students in higher, professional and continuing education. It is not designed for or directed at young children, and optional Google sign-in processes the consenting user’s name, email address and account identifier.
12. Changes to this policy
This policy may be updated when Hoot Focus Timer's features or data practices change. The "Last updated" date at the top of this page identifies the current version, and material changes will also be noted in the extension's release notes.
13. Contact
Questions about this policy, or about how Hoot Focus Timer handles information:
- Developer: Aryan Baki
- Email: aryanbaki [dot]dev [at] gmail.com
Please do not include browsing history, screenshots of private pages, or other sensitive information when asking for support. It is never needed to answer a question about Hoot Focus Timer.