Privacy Policy
EyeTime is local-first. It has no account, no ads and no remote code. It has no analytics either, unless you switch on the one optional thing described under Anonymous usage below: off by default, and you can read every report before it is sent.
What is stored (on your device only, in chrome.storage.local)
- Domain names and seconds per hour, e.g.
github.com — 340 s at 10:00. Never full URLs, page titles, page content or keystrokes. - Your settings, tasks, notes, habits and quick links.
- A short local log of the last 20 errors (message and code location only, no page addresses). It is never sent anywhere; you can read it in Settings → About → Report a problem and clear it there.
- If you import a calendar file (.ics): the times and titles of the next 14 days' events, kept locally and never uploaded; remove them any time in Settings → Data & privacy.
- Nothing else: the shareable "My week" card is drawn locally and contains totals only.
- Optionally (if you enable the desktop companion): seconds per desktop application name.
What is sent anywhere
Nothing. The extension makes no network requests of its own. The exceptions are all entirely opt-in (plus one feature that stays on your computer, described among them):
- Desktop companion — if you switch it on in Settings → Tracking, the extension reads
http://127.0.0.1:8765/v1/todayon your own computer using a pairing token. Nothing is sent to it.
- Calendar subscription — if you paste your calendar's secret iCal address (up to three calendars) in Settings → Data & privacy, the extension downloads each file from the address you gave, once an hour, directly from your browser (a plain request without cookies, no third party involved). Only the events of the next 14 days are kept, on your device. The optional meeting warning and quiet mode work from those stored events; nothing is sent anywhere. The address is secret, so it is stored locally only: never synced and never included in a backup. Unsubscribe deletes it and withdraws the browser permission.
- Settings sync — off by default. If you switch it on in Settings → Data & privacy, your settings only (look, focus modes, preferences) are stored in your browser's own sync storage (
chrome.storage.sync) and travel through your browser account like bookmarks do. Tasks (unless you switch on task sync below), notes, habits, links and browsing statistics are never included. With Encrypt synced data with a passphrase (below the sync switches) the copy is sealed on your device first: the cloud holds only ciphertext, a salt and a time. - Weather — off by default. If you switch it on (Settings → General → Weather) and pick a city, the browser asks you for access to
api.open-meteo.comandgeocoding-api.open-meteo.com. Searching for a city sends the text you typed to Open-Meteo's geocoding service; the forecast request carries only the city's coordinates rounded to about a kilometre (never your IP-based location, name or any identifier; no cookies, no referrer). Open-Meteo is a free service without accounts or keys. The answer is kept on your device for half an hour. Turning the weather off withdraws the permission.
- Unknown sites (experimental) — off by default (Settings → General). If you switch it on in a recent desktop Chrome, EyeTime asks the language model that Chrome itself runs on your computer (Gemini Nano) to sort sites that are in none of your lists, using only the site address and the title of an open tab. The page content is never read, nothing is sent to EyeTime or anyone else, and the answers (distracting / productive) are kept on your device, shape only your reports (marked with a spark) and never block anything. EyeTime never starts the model download by itself: if Chrome still needs to download the model, you press a button first. Forget the guesses deletes them. Not available in other browsers.
- Task sync — off by default and a separate switch (Settings → Data & privacy → Sync tasks too), because task text is personal. If you switch it on, your open tasks and the ones finished in the last three days are stored in your browser's own sync storage (
chrome.storage.sync) and travel to your other browsers signed in to the same account, governed by that browser's sync policy. Habits, notes, history and the calendar never sync. With the sync passphrase on, the task list is sealed on your device before it is uploaded, like the settings. Nothing goes to EyeTime or any third party. To remove the cloud copy, turn the switch off on all your devices and clear sync data in the browser's sync settings. - The dock — off by default. If you turn it on in Settings → General → Dock, the browser asks you to allow EyeTime to access websites. EyeTime then draws a small black tab on the edge of web pages and, when you open it, a panel from EyeTime's own pages inside the page. It does not read, copy or send page content. The only things taken from a page are its address and title, and only when you press Save (or use Save to EyeTime topic in the right-click menu): they are stored on your device in your topics list, with tracking parameters removed. The numbers on the tab's rings come from EyeTime's own local data. Topics are included in the backup file and never synced or sent anywhere. You can hide the dock on chosen sites (for example your bank), and turning the dock off withdraws the access.
- Connected services — off until you connect one (Settings → Data & privacy → Connected services). Todoist, Notion and CalDAV (iCloud, Fastmail, Nextcloud…) can be kept in step with your tasks and calendar. (Google and Microsoft are prepared but not offered in this version.) When you connect one, the browser asks for access to that service's own address only (for example
api.todoist.com), and EyeTime talks to it directly from your browser: there is no EyeTime server in between and no third party. What is sent is what a sync is: the text, due date, done state, priority and estimate of your tasks, and, for a calendar, the planned focus blocks you chose to put there (title and time). What is read is the tasks of the list you chose and the busy times of the calendar you chose (kept on your device, for 14 days). Tokens, passwords and sign-in tokens are kept in local storage only: never synced, never in a backup, never in the usage report; you paste an access token or an app-specific password yourself, never your main password. Disconnect deletes the credentials, the pairing records and the calendar events brought in, and withdraws the browser permission; nothing is deleted on either side. If you switch off Delete in both places, deletions are never copied; and a sync that would delete a large part of your tasks stops and asks first.
- Anonymous usage — off by default. If you switch on Share anonymous usage numbers (Settings → Data & privacy; EyeTime also asks, after you have finished a focus session and come back on another day, at a calm moment, never while you work: up to three times in all, at least three weeks apart, and only after you answered Maybe later, each time with other words; Don't ask again (or No, thanks on the third time) ends it for good), EyeTime sends one small report a week to its own collector, over HTTPS, without cookies. Its purpose is to find out whether new people reach a first session, whether they come back, and which features nobody uses, so that EyeTime can be made simpler and better. The report is numbers and names from a fixed list; Show what would be sent in the same place shows the exact next report, built by the same code that sends it. It is described here field by field:
| Field | What it holds |
|---|---|
| v | the version of the report format |
| id | a random identifier made when you switch sharing on (128 random bits, not derived from anything on your device or in your browser). It is replaced when you press New anonymous ID, and deleted when you switch sharing off |
| app | the EyeTime version, e.g. 3.8.0 |
| br, os | the browser family (Chrome, Edge, Firefox) and the operating-system family (Mac, Windows, Linux, ChromeOS): nothing finer, no version, no model |
| lang, look, layout, mode | your interface language, the look and the arrangement of Home you chose, and light / dark / automatic |
| age | whole days since you installed EyeTime |
| act | the days (counted as days since the install, never as dates or times) on which you opened or used EyeTime, for the last 60 days |
| first | for each feature in the list below, how many days after the install you first used it |
| ft | for each feature, how many times you used it since the last report |
| fl | which optional parts of EyeTime are switched on, from the fixed list below (a list of names, nothing you typed), plus how many tasks, habits and own sites you have in coarse steps (none, 1–5, 6–20, more) |
| pr | only the Windows app sends it, as win; the browser extension sends nothing here. It says which product the report is from |
| x | only while an experiment is running (one is: the voice of the question about sharing, ask-copy:personal or ask-copy:practical): which arm of it this device is in. The arm is chosen on your device by a random number that stays there and is never sent; the list of experiments is fixed in the code and a report naming any other is refused |
The features that are counted, and nothing else: newtab_view, popup_open, insights_view, settings_view, focus_start, focus_done, focus_stop, focus_pause, eye_break_done, eye_break_skip, block_page, block_continue, task_add, task_done, habit_check, shutdown_done, plan_done, ritual_plan, ritual_skip, connection_add, palette_open, drawer_open, editor_open, starter_apply, wall_next, standby_open, tour_open, onboarding_done, fl_u15, fl_u25, fl_u35, fl_u50, fl_u75, fl_75p, fl_early_stop, bp_always, bp_focus, bp_schedule, bp_limit, bp_budget, bp_friction, nt_u100, nt_u250, nt_u500, nt_u1000, nt_slow, err_worker, err_page, err_blocker, err_sync, err_other, fb_shown, fb_answered, fb_dismissed, fb_written. Besides plain uses they cover how sessions go (fl_u15 … fl_75p: finished sessions by length, fl_early_stop: stopped in the first five minutes), which mechanism stopped a page (bp_), how fast the new tab was ready (nt_: under 100, 250, 500, 1000 milliseconds, or slower) and how many errors happened, by place (err_: a count; the text of an error never leaves your device), and how often a small question was shown, answered or closed and how many messages were written (fb_: counts only; what anyone wrote is never in the report).
The things that can be reported as switched on (fl), and nothing else: ritual, dock, weather, calendar, tasks_sync, settings_sync, sync_encrypted, instant_block, smart_sites, connections, schedule, limits, budget, friction, eye_notify, bedtime, standby, custom_css, companion, daily_goal, focus_sound, review, tasks_0, tasks_1_5, tasks_6_20, tasks_21p, habits_0, habits_1_2, habits_3p, sites_0, sites_1_5, sites_6p.
The counters are kept on your device whether or not you share (that is how Show what would be sent can show you your own numbers, and how sharing, once switched on, reports the real days since the install rather than only the future); they are never sent unless you switch sharing on. The collector (its code is in this repository, server/usage/) accepts exactly these fields and refuses anything else, keeps at most one report per install per six hours, and does not store or log your IP address, headers, cookies or user agent. Stopping: switching sharing off sends one request that asks the collector to delete everything it holds for your id, then deletes the id here; Delete all my data in Settings does the same. The counters and the id are never part of a backup file and are never synced. The page after removal: when a collector is set up, EyeTime asks the browser to open one page of the project after it is removed (the extension makes no request itself). The page asks one question with seven answers; a click sends one answer from that fixed list to the collector, which counts it per day: no identifier, no cookie, and nothing at all is sent without a click. After the click the page offers a second, optional step: a few words and, only if you want an answer, an email address. That is a message to the maker and is treated as one (see Messages to the maker: kept until deleted, the address erased once answered or after 90 days); it is empty by default and goes only when you press Send. What the collector counts about itself: per day, how many reports it accepted and how many it refused and why, with nothing that names an install, so that a faulty version can be noticed; it keeps no log. How long: the rows of an install that has not reported for 400 days are deleted. In Firefox the browser asks for its own technical and interaction data permission when you switch sharing on, and you can withdraw it in the add-on's permissions.
Fonts and icons are bundled inside the extension; no content is loaded from the internet.
Anonymous usage: who is responsible, on what basis, for how long, and your rights
This is the fuller notice for the optional anonymous numbers (the browser extension and the Windows app). It is what the Privacy details link on the question opens.
- Who is responsible. The developer of EyeTime (GitHub:
maxbzd, https://github.com/maxbzd/eyetime). To write to them privately, use the contact in SECURITY.md (GitHub's private report, or the e-mail and Telegram listed there); say "privacy" in the subject. Please do not put your anonymous ID in a public issue. - Why, and the legal basis. To find out whether new people reach a first session, whether they come back, which features nobody uses, how fast and how stable EyeTime is, so that it can be made simpler and better. Nothing else. The basis is your consent (GDPR Article 6(1)(a), and the equivalent in other countries). It is a separate, single-purpose question; EyeTime works exactly the same if you say no, and nothing is taken away, delayed or made harder. The question is a plain choice: no box is ticked for you, and every answer is one click.
- After you say yes. EyeTime sends the numbers on its own, once a week; nothing has to be confirmed each time. You can stop whenever you like in Settings, and the numbers sent so far are deleted when you do.
- Is it personal data? The random ID (made on your device when you say yes, derived from nothing about you) together with the counters is treated as personal data (a pseudonymous identifier), although nobody can tell who you are from it: there is no name, account, address, IP address, site, task, note, title or time of day in it, and the collector does not store or log your IP address, headers, cookies or user agent. (The network provider that carries the connection, Cloudflare, necessarily sees the connection's address while it answers; EyeTime does not keep it and has switched the provider's logs and analytics for the collector off.)
- Who receives it. Only the collector, run by the developer on Cloudflare (Workers and D1), which acts as the hosting provider (processor) under its standard data processing terms. Nothing is sold, rented, shared with anyone else, or used for advertising, profiling that affects you, or any decision about you. Totals may be published (for example "N installs"), never one install's numbers.
- Where. The collector's servers can be in another country than yours, including outside the EU, the UK and Switzerland. The provider transfers data under its data processing terms (standard contractual clauses and, where it applies, the EU–US Data Privacy Framework).
- How long. An install's weekly numbers are kept while you share and are deleted at once when you switch sharing off (the request to forget goes out then; the Windows app repeats it until the collector has confirmed). An install that has not reported for 400 days is deleted. Counts that carry no ID (how many reports came in on a day, why people removed EyeTime) are kept as totals.
- Your rights. You can see exactly what is sent (Show what would be sent), before and after. You can withdraw consent at any time, as easily as you gave it: the switch in Settings (the question's thank-you message says where it is), with no effect on anything else, and it erases what is held for your ID. Because the collector cannot tell who an ID belongs to, a request about your data is answered by these controls; if you still need something from the developer, send your ID with your message. You can complain to your data protection authority (in the EU, the one of your country of residence, work or where you believe the law was broken). There is no automated decision-making.
- Children. EyeTime is not directed at children. The question is meant for adults and for young people old enough to consent in their country (13–16 in the EU depending on the country; 18 in some countries). If you are younger, please say no and ask a parent; nothing is lost.
- If what is sent ever changes (a new field, a new purpose, a new recipient), a new version of this consent is made and nothing is sent until you have agreed to it again; the question comes back for that.
- California and similar laws. EyeTime does not sell or share personal information, and does not use it for targeted advertising. The categories collected, if you agree: a random identifier and counts of how EyeTime is used (internet activity within the product), and the setup choices listed above. Purposes and retention are as above. You may ask to know, to delete and to correct, as above, and will not be treated differently for saying no.
- Chrome Web Store. The use of information received from the browser's APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. The numbers are used only for the purposes above, are not sold, not transferred for other purposes, and not used for advertising or credit decisions.
Messages to the maker: what you write, and the answer
This is the notice for the form "Write to the maker" (the command palette, the toolbar popup, Settings) and for the small questions EyeTime may ask at a good moment (a rating after a session, how you would feel if EyeTime were gone, the mood of the week). It is what the Privacy details link on the form opens. It applies only to a build that has a message server; a build without one sends nothing and the form opens a draft on GitHub instead (public there, and it says so).
- What is sent, and only when you click. The words you typed, the kind (idea, problem, kind word, or the answer to a small question), optional chips from a fixed list, an optional rating, and, if you leave Attach version and system on, the EyeTime version, browser family, system family, language and how long you have used it in four coarse steps (the page shows exactly what). Nothing is sent before you press Send or tap an answer. No anonymous-usage ID, no IP address, no address of any page, no account. The server does not log requests.
- Free text can be personal. What you write is yours to choose: please do not write anything personal. If you do, it is processed to read and answer you and to improve EyeTime, nothing else. The basis is your request (you sent it; GDPR Art. 6(1)(b)/(f)) and, for the optional reply address, your consent (the field you filled).
- How long. A message is kept until you or the developer delete it: you can delete your own messages from the list on the form page at any time (see below), and the developer deletes a message on request. The optional reply address is erased as soon as the message is answered, and in any case after 90 days. The developer's answers are erased 14 days after they reached your device (180 days if they never did).
- Getting an answer. If you tick Show the author's answer here, in EyeTime, your device makes a random ticket (16 random bytes, derived from nothing about you) and sends it with that message. The server keeps only a hash of it. Once in a while (at most every six hours, and only while you have messages with a ticket less than six months old) EyeTime asks the server whether there is an answer, sending the tickets and nothing else; the server does not store who asked or from where. The ticket is a pseudonymous identifier, so it is covered by this notice; it is never combined with the anonymous-usage ID. If you would rather be answered by email, give an address instead (or as well); it is used once. If you do neither, no answer can reach you.
- Deleting. Delete this message on the form page tells the server to delete the message and its answers (it proves the message is yours with the ticket), then removes it from the list. If you did not ask for an answer there is no ticket, so there is nothing to prove ownership with: write to the contact above and quote the words.
- The small questions. One tap, with an optional line. They are rare (at most one in 30 days of any kind, never in the first week, never during a focus session), the consent question counts toward that, "Not now" silences them for 60 days and Don't ask for ratings turns them off for good. The answers are stored like any message (coarse context, no ID). How often they were shown, answered or closed is counted as four numbers in the weekly anonymous usage report, if you share it (
fb_shown,fb_answered,fb_dismissed,fb_written: counts only). - Who receives it. Only the collector run by the developer on Cloudflare (hosting provider under its data processing terms; the servers can be outside your country). Nothing is sold, shared or used for advertising. The messages are kept in a database apart from the anonymous numbers.
- Your rights. Access, correction and deletion: through the controls above or by writing to the contact. You can stop at any moment by not writing; nothing about EyeTime depends on it.
EyeTime for Windows (the desktop app)
The app is a separate download from this extension and is described in desktop/README.md. What it sends, and what it does not:
- Always, and only this: the update check. The service asks GitHub's public release list for a newer version, and downloads it from the project's own release page when you allow it (a file the project did not sign is thrown away). No identifier is sent with it.
- Nothing else, unless you switch it on. Settings → Anonymous numbers → Share is off by default. The app asks in plain words after you have used it for a few days, at a calm moment (right after a finished session, never during one): up to three times in all, three weeks apart, only after Maybe later; never again after Don't ask again or a No, thanks on the third time. Nothing can be sent from a build that has no collector address in it.
- If you switch it on, once a week it sends the same kind of report as the extension (
v,id,pr=win,app,lang,age,act,first,ft,fl, described above), from its own, shorter lists of names. There is no browser, look, layout or mode in it. The identifier is random, made when you switch sharing on, and not derived from the computer, the account or anything else; turning sharing off asks the collector to forget it. - Counters, and nothing else:
blk_rule,blk_session,blk_limit,blk_cool,ch_shown,ch_done,ch_wrong,ch_expired,ch_hold,ch_wait,ch_type,ch_math,ch_pin,ch_friend,ch_for_end,ch_for_break,ch_for_unblock,ch_for_edit,ch_for_emergency,ses_start,ses_done,ses_stop,ui_open,svc_start,svc_unclean,upd_found,upd_applied,upd_failed. They count kinds of events: a program or a page was closed by a rule, a session, a limit or a cool-down, a challenge was shown and how it ended, a session started, finished or stopped, the window was opened, the service started, or did not stop cleanly (a crash or a power cut), an update was found, installed or failed. No program name, site, path, window title, rule name, PIN, code, text you typed or time of day is ever in it, and a unit test builds the heaviest possible report and checks that. - Setup flags:
pin,partner_pin,auto_update,browser_ext,locked_rules,limits,schedule,sessions_used,strict,w10,w11(a list of names; for example that a PIN is set, not the PIN). - You can read the exact next report in the app before it is sent, and stop at any time.
Permissions — why each one
| Permission | Why |
|---|---|
storage | Save settings and statistics on this device |
tabs | Read the address of the active tab to know which site you're on |
webNavigation | Stop a paused site before it loads |
idle | Detect when you're away so idle time isn't counted |
alarms | Wake the extension for timers and reminders without a background loop |
contextMenus | Right-click menu to classify or block the current site |
notifications | Eye-break and session-complete reminders |
offscreen | Play the soft session start/end sound |
favicon | Show site icons from the browser's own cache (nothing is downloaded) |
declarativeNetRequestWithHostAccess | Instant blocking (off by default): lets the browser itself send a distracting site to the pause page before a request is made. It does nothing until you switch that setting on and allow access to websites; it cannot read pages or requests, and the browser shows no warning for it. Chrome only |
scripting | Lets the dock's page script be registered on demand, and only after you have granted access to websites (it does nothing on its own; the browser shows no warning for it) |
| Sites: youtube.com, instagram.com, tiktok.com, vk.com, vkvideo.ru | Only to limit short-video scrolling and hide YouTube feeds |
Optional: 127.0.0.1:8765 | Only when you enable the desktop companion |
Optional: websites (http:///, https:///) | Asked only when you turn on the dock (Settings → General → Dock); withdrawn when you turn it off. See below. |
Optional: api.open-meteo.com, geocoding-api.open-meteo.com | Asked only when you turn on the weather; withdrawn when you turn it off |
| Optional (Firefox): technical and interaction data | Asked only when you switch on Share anonymous usage numbers (see above); nothing is sent without it. Chrome has no such permission: the switch is the consent |
Optional: the address of one service (api.todoist.com, api.notion.com, or your CalDAV server, for iCloud *.icloud.com) | Asked only when you connect that service in Settings → Data & privacy → Connected services; withdrawn when you disconnect it |
Optional: one https:// site | Asked only when you subscribe to a calendar link, and only for the site that hosts your calendar (for example calendar.google.com); withdrawn when you unsubscribe, reset or restore a backup |
Your control
- Incognito windows are not tracked unless you switch it on.
- Pause tracking from the popup; exclude sites in Settings → Tracking.
- Export everything as JSON, or delete it all, in Settings → Data & privacy. Removing the extension also removes the data.
Changes
Any change to this policy ships with a version bump and is listed in the release notes.
Questions: open an issue at https://github.com/maxbzd/eyetime/issues, write to <maxbzd1600@gmail.com> or to Telegram @maxbzd.