Data stored in your browser
In short: your settings, sessions, stats and notes live in this browser, under seven keys. You can clear them from Settings or your browser.
at.v1.settings- Theme, accent, default duration, sound, notifications, end behaviour, battery, ambient, language, telemetry and keyboard preferences.
at.v1.session- The current or last session so a reload can offer to resume it.
at.v1.stats- Local-date minute totals, session count and streak data retained for up to 365 days.
at.v1.license- An offline-verifiable Pro token, plan, features, validation time and random device identifier.
at.v1.meta- Install date, completed-session count, rating-prompt choice and last seen version.
at.v1.onboarding- Dismissed tips, including language suggestions.
at.v1.notes- Your notes (IndexedDB, not localStorage): text, titles, pins and edit times, plus whether you read the voice typing notice. Never uploaded.
This data stays in browser storage unless a feature explicitly contacts the first-party API. You can clear it from
Settings or your browser. BroadcastChannel('awaketab') coordinates open tabs without sending that state to a
server.
Voice typing in the notepad uses your browser's own speech recognition. In Chrome and Edge the browser sends your voice
to its speech service (Google or Microsoft) to be transcribed, and Safari uses Apple's, under that company's terms.
AwakeTab receives neither the audio nor the text; only the words you keep are saved, in at.v1.notes on
this device. The microphone is used only while the mic button shows it is listening.
First-party telemetry
In short: telemetry is on by default and anonymous: AwakeTab sends events to its own server, with no user id, no fingerprint and no persistent identifier. One switch in Settings turns it off everywhere.
While telemetry is on, AwakeTab may send: page_view, session_start, session_end, lock_state, lock_denied, fallback_used, resume_shown, resume_accepted, pwa_install, pip_open, share_click, pro_view, pro_checkout_click, pro_activated, rating_prompt, extension_click, ad_slot_loaded, sponsor_view, sponsor_click, session_extend, affiliate_click, rating_submitted and sampled client_error events.
Common fields are timestamp, path without query parameters, locale, coarse browser/OS and viewport classes, application version and a random per-tab session id held only in memory. AwakeTab does not collect a user id, exact user agent, fingerprint, full referrer or persistent analytics identifier.
AwakeTab for Chrome (browser extension)
In short: the extension keeps the same records on your computer, asks for power, storage and alarms (anything else is optional), and sends no usage data unless you turn it on.
The extension keeps the same records as the site, in chrome.storage.local on your computer:
at.v1.settings, at.v1.session, at.v1.stats, at.v1.license (only after you
activate Pro), at.v1.ext (Screen or System level, schedules and auto-start sites) and at.v1.device (a
random device id created once per browser profile, used only to count Pro activations).
If Chrome sync is on, your settings, schedules and auto-start sites are also copied through chrome.storage.sync
to your other Chrome profiles. The licence token and the device id never sync.
The extension asks for power, storage and alarms. Notifications and access to a website are
optional and requested only when you turn on end-of-timer notifications or add an auto-start site; the site permission
covers that one site, and the extension never reads page content. Which sites you add is never sent anywhere.
Anonymous usage statistics are off by default in the extension. If you turn them on in its settings, it sends at most
session_start, session_end, pro_activated and client_error events to
awaketab.com/api/e with source: ext and the common fields above, never a URL, tab title or site name.
Activating Pro sends the licence key, the random device id and the label “AwakeTab for Chrome · your operating system” to
/api/license/activate. The extension shows no ads, loads no remote code and never simulates keyboard or mouse
input.
Data kept on our servers
In short: three kinds of records, each with an end date: usage events for 90 days, ratings for up to 2 years, and a licence record until the licence expires plus one year.
AwakeTab runs on Cloudflare. It keeps three kinds of records there, and nothing else:
- Anonymous usage events
-
The telemetry events above, and content-security-policy reports your browser may send to
/api/csp(only the page path is kept). They are stored in Cloudflare Workers Analytics Engine and deleted automatically after 90 days. They carry no IP address and no identifier beyond the per-tab random session id, so they cannot be traced back to you. Turn telemetry off in Settings to stop sending them. - Ratings
- If you rate AwakeTab, we store the stars, any text you choose to write (up to 280 characters), the page language, the app version and the time, for up to 2 years. No name, email, IP address or device id is attached. Only the aggregate (average and count) is published.
- Licence record
- If you buy Pro or a Business licence, we keep a record to fulfil the purchase, handle refunds and stop abuse: the plan and its status, your licence key (encrypted), the Polar order and customer ids, and for each activated device a hash of its random device id, its label and when it was last seen. It is kept until the licence expires plus one year, then deleted. Your name, email and payment details stay with Polar, the merchant of record, whose privacy terms apply.
Deleting your licence data. Email [email protected] from any address with your licence key or Polar receipt, and ask us to delete your licence data. We delete the licence record and its device list within 7 days and confirm by reply. Deleting it ends Pro on every device, and it does not refund the purchase (a refund within 14 days does that, see the terms). Usage events and ratings carry no identity, so no one, including us, can pick out yours; they expire on the schedule above.
Network and payment data
In short: your IP address is used briefly, as a salted hash, for rate limiting and is never stored as analytics. Polar handles payment.
API rate limiting uses a salted hash of the source IP transiently; neither the IP nor its hash is stored as analytics. Pro purchases are processed by Polar, whose checkout privacy terms apply. Licence endpoints receive only the licence key or token, a random device id and a user-visible device label.
Advertising (not yet active)
In short: no page shows ads today. If article ads start, they will never appear on the awake screen, in Picture-in-Picture, in embeds or in the extension.
No page shows ads today. This section describes what will apply once advertising starts on the articles; the effective date above will change when it does.
AwakeTab's tool pages load no third-party scripts and show no ads. Our articles (pages under /for, /on, /vs, /guides and /learn) will show advertisements from Google AdSense. Ad vendors may set cookies and process your IP address and browsing information to show and measure ads. If you are in the EEA, the UK or Switzerland we will ask for your consent first through a certified consent management platform, and you will be able to change your choice any time via “Manage consent” in the footer. AwakeTab Pro removes ads on all pages. We never show ads on the awake screen, in Picture-in-Picture, in embeds or in the browser extension.
Contact
In short: one address for every question about this policy or your data.
Questions about this policy or your data: [email protected].
Questions: [email protected] · Terms