Privacy policy
AttentionPro is a focus tool, not an advertising business. Detection runs on your device, and the only things that reach our servers are the ones listed here.
Last updated 6 September 2026.
Using AttentionPro without an account
Both clients work fully offline. Tasks, timers, daily history, your wall list and every setting live in local storage on that device. In this mode we receive nothing at all, because the clients make no network calls to us.
What the clients look at on your device
To count attention rather than presence, the clients have to observe a few things locally. None of this is transmitted.
| What | Why | Where it goes |
|---|---|---|
| The site or app in the foreground | To credit time to the right task and to know when to show the wall | Stays on the device |
| Whether you are idle | So time only counts while you are really there | Stays on the device |
| Tabs and tab groups (extension) | To group the tabs that belong to a task, and to reopen them later | Stays on the device unless you turn on backup |
| Your browser history (extension) | To rank suggestions when you search from the new tab page | Stays on the device, always |
| App usage and screen state (Android) | To count foreground time and drift time | Stays on the device unless you turn on backup |
| Notifications from apps you walled (Android) | To hold them so they wait for you instead of interrupting you | Stays on the device |
About the history permission
The Chrome extension asks for permission to read your browsing history, and we would rather explain that here than have you find it in a permission list. When you search from the new tab page, the extension reads Chrome's own history so it can suggest pages you already use, ranked by how often you visit them and boosted when they match the task you are working on. That reading happens entirely on your machine, the results are shown only to you, and nothing about your history is ever sent to us or to anyone else. We do not build a history log of our own.
What the intelligence in the product does
The guardwall changes what it says based on what it notices: a long unbroken feed session, an app you close and reopen a minute later, use after you had wound down for the night, a task that has stopped moving while your usage climbs, a budget you set and then passed. All of that is logic running on your own device, over data that never leaves it. There is no model in a data centre reading your activity, because nothing about your activity is sent anywhere to be read.
If you create an account
Sign-in is an email one-time code. There is no password field on any surface. We store your email address and an account identifier so we can tell you which subscription is yours.
If you turn on cloud backup
Signing in on a client is the opt-in for backup. From then on that device uploads a snapshot of its own state, at most once an hour, and only when something changed. A snapshot contains:
- Your settings, including your wall list
- Your saved templates and bookmarks, which include the web addresses you saved
- Your tasks, including task names, notes, and any tab addresses saved with a shelved task
- Your daily history and your resistance events
Please read that list literally. Cloud backup is what makes a reinstall recoverable, and to do that it carries the addresses you deliberately saved into a task or a bookmark. It does not carry a record of pages you merely visited.
A snapshot does not include the dock, the on-page display, notification mode, wallpaper images, or other device-only preferences.
Snapshots are stored per device. We do not merge them on the server, and we do not read them: to us a snapshot is opaque data attached to your account.
What our servers record
Our logs hold operational metadata only: which route was called, your account identifier, sizes, timings, request identifiers, and error codes. They never contain task names, notes, or addresses. We keep them so we can tell whether the service is working.
Who else is involved
- Amazon Web Services hosts the account system, the API and the database, in the United States.
- Paddle (Paddle.com Market Ltd) is the merchant of record for purchases made on this website and through the browser extension. Paddle is the seller on that transaction, so it collects your name, email and billing address, takes the card details on its own hosted page, and issues the receipt. None of that reaches our servers or either client: what we receive back is that an account is paid, until when, and which plan. Paddle is an independent controller of the data you give it, under Paddle's privacy notice.
- Google Play is the seller for subscriptions bought inside the Android app, and handles those payments under Google's own terms. We receive the purchase result, not the payment details.
There are no advertising networks, no analytics services, and no data brokers. The fonts and every other asset on this website are served from our own domain, so visiting these pages does not tell a third party that you were here. We do not sell or share your data.
Artificial intelligence
The detection and counseling described above run on your device, offline and free. Nothing you do is sent to a language model or any other external service. If we later add an optional conversation feature that needs a server, it will be opt-in, it will send aggregates and task names only, and this policy will say so before it ships.
Your control over the data
- Delete one device's backup, or every backup on the account, from your account page.
- Removing a device also deletes that device's snapshot. The two are one action on purpose, so a freed seat never leaves an unreachable copy behind.
- Download a copy of any snapshot from the account page.
- Delete the entire account, including the email address, the subscription record and every snapshot, from account deletion.
- Deleting cloud data never touches the copy on your device, and uninstalling is never blocked or delayed.
How long we keep things
A device's snapshot is kept until you replace it, delete it, or delete the account. Account and subscription records are kept while the account exists. Operational logs are kept for a short retention window and then expire.
Children
AttentionPro is not directed at children under 13, and we do not knowingly collect their data.
Changes
If this policy changes in a way that affects what we collect, we will update the date at the top and say what changed before the change takes effect.
Contact
Questions or a data request: support@attentionpro.app.