Privacy Policy
The short version
MyFocusLogy keeps your focus history on your phone. There is no account, no sign-in and no server holding what you record: your sessions, the activities and tasks you name, and everything the app learns from them stay on the device and are never uploaded.
Two things can leave your phone, and only if you switch them on yourself — anonymous usage events that show whether the app is working, and crash reports. Both are off when you install it, both can be switched off again at any moment, and the app is complete without either. Neither one carries what you wrote, what you called anything, or anything that identifies you.
The rest of this document explains exactly what is stored, what those two switches do, and what happens when you delete the app.
What the app stores on your device
All of it lives in the app's private storage, which other apps cannot read.
About your focus sessions
- when a session started and ended, how long it was planned for and how much of it was actually focused time;
- pauses and their total length, and how many times you paused;
- how the session ended, and whether it was recovered after the phone restarted;
- the time zone your phone was in when the session started, so that a session is attributed to the right day if you travel;
- anything you chose to tell the app about the session afterwards: how focused you felt, your energy and interest, and the reason if something interrupted you;
- moments when your attention slipped, if you marked them, and your breaks.
About what you work on
- the activities and categories you create, under the names you type;
- your tasks: the title you write, an optional estimate, the day you planned them for, and when you completed them.
Learned from the above
- calibration and training profiles the app builds from your own history to suggest session lengths. These are derived from your sessions and never leave the device either.
Settings
- your theme, default focus mode and custom duration, whether you finished onboarding, whether notifications are on, and the activity you selected last.
If you connect another MyLogy app
- identifiers linking a session or task to a goal in that app. These are internal identifiers, not content.
What the app does not do
- It does not upload what you record. Your sessions, the names you gave your activities and tasks, your ratings and the profiles the app builds from them stay on this phone. No switch in the app sends any of it anywhere.
- There is no account and no sign-in. We never learn who you are.
- There is no advertising, and no profile is built about you. No advertising identifier is collected, no ad-personalisation signal is sent, what the app measures is never linked to any advertising product, and the app gives you and your phone no identifier of its own.
- Your data is never sold, shared with advertisers, or used to build a profile about you for any purpose outside the app itself.
- No health or clinical conclusions are drawn. The app does not diagnose, label or infer conditions such as ADHD, depression or burnout, and stores no such labels.
- It asks for no other permissions. No location, contacts, files, photos, camera or microphone.
Analytics and crash reports
Two switches in Settings → Privacy, separate from each other and both off when you install the app. Until you turn one on, nothing described here happens.
Help improve the app sends anonymous events about how the app is used: that a session was started or finished, in which mode, whether a recommendation was shown or followed, whether onboarding was completed. Lengths and counts are sent as ranges — "26–40 min", "2–3 pauses" — never as exact figures, because an exact figure plus a language plus an app version is a much smaller crowd to stand in than a range is.
Send crash reports sends what is needed to fix a crash: where the app stopped, which screen phase it was in, which mode was running, the app and algorithm version. It also sends a small set of timing measurements — how long the app took to become usable, how long the database took to open.
Neither switch ever sends, and the app is built so that it cannot send: the names of your activities, categories or tasks · any text you typed · the identifiers of sessions, activities or tasks · the exact time a session started or ended · when during a session your attention slipped · the contents of a file you exported · file names · your personal comfortable session lengths · any identifier for you or your phone.
No account is created, no advertising identifier is collected, and no score is calculated about your attention, your productivity or your concentration — not on the phone and not anywhere else.
Saying no costs you nothing. Every feature works identically with both switches off, and nothing in the app asks twice. You can change either answer whenever you like; turning one off stops the sending immediately. When you turn off crash reports, the app offers to delete any report still waiting on your phone. To have what was already sent deleted, write to the address at the end of this policy.
Permissions
The app declares four permissions. Exactly one of them is ever asked of you, and neither gives the app access to anything about you.
Notifications (POST_NOTIFICATIONS) — the one you are asked
for. It is used for two things, both about the session you started: a notification that stays
while a session is running, and one telling you when a session has finished. You may refuse
it, and the app works fully without it — the session still ends correctly and the result is
still recorded; you simply are not notified. You can change your mind at any time in Android
Settings.
Internet (INTERNET) — granted when the app is installed and never shown as a prompt. It exists for one reason: so that the two switches above can send anything at all. While both are off, no event and no report leaves the phone, and the permission by itself starts no transfer. Everything the app is for — starting, running and recording a session, building your history, suggesting a length — works with no network at all.
Network state (ACCESS_NETWORK_STATE) — granted when the app is installed and never shown as a prompt. It answers one question, "is there a network at the moment", so that the app does not throw a crash report at a dead radio. It reads nothing about you, and it opens nothing.
Start after reboot (RECEIVE_BOOT_COMPLETED) — granted when
the app is installed, never shown as a prompt, because there is nothing to consent to: it
grants no access to any data on your phone. It lets the app be told that the phone has
finished starting, so that a session which was still running when you restarted is closed and
written down honestly instead of being left open for ever. It reads nothing and sends
nothing.
The home-screen widget needs no permission at all.
What the app shows outside itself
Two things put what you recorded on the screen while the app is closed. Neither sends anything anywhere — both are drawn on your device — but both can be read by someone looking at your phone.
- While a session runs, a notification shows the time remaining and the name of the activity you chose, exactly as you typed it. Android treats it as private content, so on a locked screen it is hidden if you have asked Android to hide sensitive notifications. It disappears when the session ends.
- The home-screen widget, if you add one, shows how long you focused today, or the countdown of a running session. Anyone who can see your home screen can see it.
Neither reveals anything you have not already put into the app. It is still worth knowing before you give an activity a name you would not want read over your shoulder.
Sharing with another app on the same phone
MyFocusLogy can make a single day's focus total available to another app from the same family, so that a habit like "focus time" can fill itself in instead of being marked by hand.
What can be read is deliberately narrow: a date, the number of minutes focused that day, and how many sessions that took. Nothing about your activities, tasks, ratings, notes, interruptions or breaks is ever exposed, and nothing can be written back — the channel is read-only and one-way.
Two things guard it. The reading app must be on a list built into MyFocusLogy, and it must be signed with the exact certificate that list expects, so an app that merely copies the right name is refused. In the current release that list is empty, which means no application can read anything at all.
This never involves the internet: the exchange happens between two apps on your device.
Backups and moving to a new phone
Automatic backup is switched off. Your focus history is not copied to Google Drive, not included in your Google account backup, and not transferred when you set up a new phone.
The trade-off is deliberate and worth stating plainly: nothing moves to a new device by itself, and uninstalling the app erases everything the app holds. We chose that over having a copy of your attention history sit in cloud storage. Moving your history is something you do yourself, with a file — see below.
How long data is kept, and how to remove it
Data stays until you remove it. There is no expiry and nothing is uploaded, so "deleting" means deleting from your phone:
- a single session — delete it in the app;
- the focus history, keeping your settings — Settings → Data → Delete focus history;
- what the app has learned from it — Settings → Data → Reset learning; the sessions stay;
- everything — uninstall MyFocusLogy, or use Android Settings → Apps → MyFocusLogy → Storage → Clear storage. Both erase everything the app holds, immediately and completely, because there is no copy anywhere else.
One thing outlives both, and only because you made it: a file you exported yourself. It sits in your storage, not inside the app, so removing the app does not touch it. Deleting that file is yours to do, wherever you put it.
None of these can be undone, because there is no backup to undo them from — unless you exported a file first.
Taking your data with you
Settings → Carry your history → Export writes everything the app holds into a JSON file you choose, through Android's own file picker. Import reads one back — on this phone or another one — replacing the history that is there.
The file is plain, readable JSON and it is not encrypted. It goes exactly where you put it and nowhere else; once it leaves the app, keeping it safe is up to you. We cannot read it, recover it, or delete it for you.
Diagnostic files
If something behaves wrongly, Settings → Diagnostics → Create a diagnostic file writes a small JSON file describing how the app is behaving — never what you are focusing on.
You are shown exactly what would be in it before the file exists. It holds the app and Android versions, the phone model, the settings that change how a timer behaves (including whether the app is exempt from battery optimisation), how many activities, sessions, tasks and breaks you have as plain numbers, the shape of your twenty most recent sessions — including how long ago each of them was, but never the date or the time of day — and the durations the app has learned. It holds no activity names, no task titles, no text you typed and no identifiers — not for you, not for the phone, and not for individual sessions.
The app does not upload this file, and neither switch in Settings can: the crash reporter sends its own reports and has no way to read a file you saved. The file goes where you put it through Android's file picker; if you then choose to email it to us, that is your action and your decision.
Children
MyFocusLogy is not directed at children and does not knowingly collect anything from anyone. Since the app collects no data at all and requires no account, it holds no information that could identify a child or anyone else.
Changes to this policy
If the app ever begins to do something this document does not describe — send anything over a network, add analytics, or store a new kind of data — this policy will be updated before that version is released, and the version and date at the top will change. Past versions remain in the project's history.
Version 1.3 — a correction, not a change of behaviour. Earlier versions
said the app requests exactly one permission. It requests one and declares two:
RECEIVE_BOOT_COMPLETED is granted at install so that a session interrupted by a
restart can be closed and written down honestly. It gives access to nothing, and it has been in
every build this policy has ever described — but the policy did not name it, and a document
whose central claim is “count the permissions yourself” has to be countable. The permissions
section now lists both.
Version 1.2 — a correction, not a change of behaviour. Earlier versions said that uninstalling erases everything and that no copy exists anywhere else. That is true of what the app holds; it was never true of a file you exported yourself, which is written into your own storage through Android's file picker and outlives the app. The sections on backups and on deletion now say so, and the Settings screen says it before you save.
Version 1.1 — the app gained a notification that stays while a session runs and an optional home-screen widget. Neither collects or sends anything new, but both display what you recorded outside the app, so "What the app shows outside itself" was added and the permissions section was corrected: notifications are no longer only about a finished session. The same version added the diagnostic file described above: it is written only when you ask for it, its contents are described to you before it exists, and it carries nothing you typed.
Contact
Questions about this policy or about the app's handling of your data: lunicoworld@gmail.com
Nothing we receive identifies you: no account, no identifier of ours, nothing you typed. That is what makes it safe, and it is also why we cannot look up, export or delete "your" data on request — there is nothing in it that points back to you. Everything that is about you is on the phone and under your control, and switching either option in Settings → Privacy off stops collection at once.