This policy explains what the FIVE Android app (com.fivepresence.app) does with your information. FIVE is provided by Solarist ("we").
Your challenges stay on your phone
FIVE helps you set and enforce time away from distracting apps. To do that, it stores these on your phone:
- your challenge settings, and the challenge that is running, with the records FIVE needs to resume it after a restart
- the apps you chose as Essential Apps
- your challenge history and progress
- your permission and settings choices
- your answers to the setup questions
FIVE does not send any of this to us by itself. We do not run a server that receives your challenges, history, app choices or setup answers. Some of it reaches us only if you choose to email us a bug report (see Support log and bug reports below).
How FIVE uses Android permissions
Accessibility. FIVE uses Android's Accessibility Service to see which app is in front, so that it can block distracting apps during a challenge, and, from version 1.0.8, whether a call is ringing, so that it can step aside for the call. It sees which app is in front and whether a call is ringing, not your messages, what you type or what your notifications say. It notes which app and window is in front, including window titles, but does not read the text inside other apps. From version 1.0.9, it reads each window's app when the window list changes, and reads its title only for FIVE, a captured essential app during a challenge, or a system app. To tell whether a call is ringing, it checks only whether a notification from your phone app or another calling app announces an incoming call, and it records nothing of that notification. What it notices stays on your phone unless you choose to send it to us in a bug report (see Support log and bug reports below).
Notification access and usage access. FIVE does not ask for Android's notification access or usage access. It does not read your app usage or what your notifications say.
Other permissions. FIVE also asks to show its block screen over other apps, to be exempt from battery optimization so that it keeps running in the background while a challenge is on, to restart its protection after your phone reboots, and to show notifications. If you choose FIVE's stronger protection, it also asks to be a device administrator, so that turning FIVE off or uninstalling it takes one extra step; this gives FIVE no other control over your phone. To start a scheduled challenge on time, it asks for Android's Alarms & reminders permission. You choose whether to grant each permission. FIVE cannot enforce a challenge without the Accessibility Service and showing over other apps, and its stronger protection also needs the battery optimization exemption and device administrator.
Signing in is optional
You can use FIVE as a guest. A guest needs no account, and FIVE only remembers on your phone that you chose guest mode.
When FIVE starts, including in guest mode, it connects to Clerk. Clerk receives a random identifier that FIVE's sign-in software creates for this installation, along with your IP address. If you sign in, Clerk also records the approximate area (city and country) of each sign-in, worked out from your IP address. Clerk uses this to run and secure sign-in. In versions of FIVE up to and including 1.0.6, when FIVE showed its sign-in screen, Clerk's sign-in software could also send Clerk usage information about that screen: which screen was shown, the software version and FIVE's public Clerk key. It carried none of your challenge data, and, like any connection, it showed your IP address to the server that received it. Later versions switch this off.
If you sign in with Google or with your email address, our sign-in provider, Clerk, handles the sign-in and keeps you signed in. FIVE then receives your Clerk user ID, name, email address and profile picture link, and keeps a copy of them on your phone. Clerk holds your account. Its privacy policy explains how Clerk handles this information.
No analytics or crash-reporting service
FIVE contains no ads, no analytics and no crash-reporting service, and it never sends usage or crash data to us by itself. Versions up to and including 1.0.6 had one exception, in the sign-in software, described under "Signing in is optional"; later versions do not. Android and your phone's software may also keep their own system logs.
Support log and bug reports
FIVE keeps a private log on your phone, in every version of the app, so that when something goes wrong we can find out what happened. The log records:
- which app is in front and when, and the list of windows on screen with each window's app and title (a title can name a chat, a contact or a web page). From version 1.0.9, new log entries keep a window's title only for FIVE, apps chosen as essential for that challenge, and system apps. Other apps keep their package name and times without a title
- when FIVE's block screen covered the screen or stepped aside, and why
- changes to FIVE's challenge, service and permissions, FIVE's own screens opening and closing, and the screen turning on and off and the phone being unlocked
- from version 1.0.9, each time you open Sign in: the window opening and closing, FIVE leaving for the browser or Google's account sheet and coming back, the sign-in method (Google One Tap, browser or other), the status words and error codes Clerk reports, and whether the attempt ended with a session, an error or no session (never your email address, name, account id or sign-in tokens)
- from version 1.0.9, what FIVE's schedules did: each schedule added, changed, switched on or off, skipped or deleted, each alarm set, canceled or delivered, whether a reminder was passed to Android, and whether a scheduled challenge started
- from version 1.0.9, whether FIVE thinks a call is ringing, from Android's audio mode and from which phone app announced a call (never who is calling or the number)
- from version 1.0.9, when FIVE stopped responding for several seconds (with where its main thread was in FIVE's code), when Android did not let FIVE run, and when the phone slept
- FIVE's crashes, and how Android says FIVE's earlier runs ended (Android 11 and later)
It does not record what you type in other apps, the text inside other apps' windows, message or notification contents, or screenshots. Text you type into FIVE itself can be part of a bug report, as listed below.
The log is kept in FIVE's private app storage, which Android backup excludes. It holds at most about 4 MB: when it is full, the oldest part is deleted, so it covers the most recent hours of phone use rather than a fixed period. Beside it, a smaller decisions log keeps only the lines about FIVE's decisions, the app in front, challenge, service and permission changes, and crashes, without the window lists; it keeps about a week (at most about 2 MB). From version 1.0.9, it also keeps sign-in attempts. From version 1.0.9, it also keeps FIVE's screens, what its schedules did, whether a call was ringing, when FIVE stopped responding or did not run, and when the phone slept. Both are deleted when you uninstall FIVE or clear its data.
Older support-log entries stored on the phone from before the title limit may still contain other apps' window titles until those entries age out. From version 1.0.9, FIVE removes every window title from those older entries in any report it builds or shares, without changing the stored log or an older saved report. If an older window entry is ambiguous because a title resembles another window, its report copy keeps only the clear text before the first title and marks the rest as redacted.
The log never leaves your phone by itself. It leaves only if you choose Settings > Report a bug (Settings is not available during a challenge), write a short comment and send the email. FIVE then builds one text report and attaches it to an email. The email itself holds your comment, FIVE's version, your Android version and your phone's maker and model. The attached report holds the following.
From version 1.0.9, a summary at the top is made from the parts below: FIVE's build and your phone's model, each challenge in the log with its times and how it ended, protection changes, crashes and freezes, and FIVE's latest decisions.
What you wrote.
- your comment
- when the report was made, and whether you started it from Settings or FIVE offered it after it stopped unexpectedly
FIVE's settings and schedules.
- your choices in FIVE: breaks, haptics, the early-exit toll, hiding the notification panel, the protection level, which suggested Essential Apps you turned off, and your calculator app
- the first name from your account, if you are signed in
- how many challenges you have completed and ended early, and the time you have reclaimed
- the times and lengths of the current or most recent challenge and its cooldown, and the length of the last challenge you completed
- about the last challenge you ended early: when it started and was due to end, how long it ran, the reason and comment you typed, and that payment's Google Play order ID (or, if Google Play gave none, a scrambled code made from the purchase)
- a random ID FIVE creates for this installation, which it uses to notice when its data has been restored from a backup
- your schedules: when each one runs, on which days, for how long and in which time zone, any dates you skipped, and a record of past scheduled challenges and whether each started
- a second random ID for this installation, which FIVE's schedules use for the same purpose
Your phone.
- its maker, brand, model and hardware names, the Android version and security patch date, and the phone software's build name and full build fingerprint
- your language, time zone and mobile network code (which names your mobile carrier and its country)
- screen size and density, text size setting and screen orientation
- how much memory Android gives FIVE and whether it is a low-memory phone, whether battery saver is on, whether FIVE is exempt from battery optimization, and how long since the phone was last restarted
- from version 1.0.9, whether the phone is dozing, whether Android lets FIVE set exact alarms, restricts it in the background, and which standby bucket it is in
- whether the phone looks rooted (FIVE checks whether a common rooting tool's file exists) and whether it is an emulator
- FIVE's version and build, when FIVE was installed and last updated, and which app installed it (such as Google Play)
FIVE's log.
- the whole log described above, oldest first, and the decisions log
FIVE's system log, crashes and exit records.
- up to the last 3,000 lines of FIVE's own Android system log (messages FIVE and the libraries inside it write; Android does not let FIVE read other apps' messages)
- FIVE's past crashes, with the technical details of where in FIVE's code each one happened
- up to 16 records Android keeps of how FIVE's earlier runs ended (Android 11 and later): when, why, and how much memory FIVE was using, and, if FIVE froze, Android's technical snapshot of what FIVE was doing
Technical state.
- which Android permissions FIVE has, and whether FIVE's accessibility and block-screen services are running
- the state of FIVE's challenge engine, and, if a challenge is running, its internal ID, whether you or a schedule started it, its Essential Apps, and which Essential App is open, if any
- how large FIVE's log is
- a technical snapshot of what each part of FIVE was doing when the report was made (a "thread dump")
FIVE opens your email app with the report attached to an email to support@fivepresence.com. The email is sent only if you press Send in your email app. If FIVE stopped unexpectedly, it may offer to send this report the next time you open it outside a challenge. It never sends a report automatically, and you can decline. Before the report is attached, FIVE removes sign-in tokens and keys, and passwords in web addresses, from every line of it. We use a report only to investigate and fix the problem it describes.
Sending a report is your choice. Nothing in FIVE needs it, and FIVE works the same if you never send one. If you do, the report reaches us by email at support@fivepresence.com, in FIVE's support mailbox, which is hosted by Zoho (see Contacting support below). It is data you chose to send us, and we use it only to find and fix problems. We do not sell it, and we do not share it with anyone else.
Payments
FIVE lets you end a challenge early by paying an early-exit toll. Google Play processes these payments with the payment method in your Google account. FIVE never sees your card number or other payment details. FIVE tells Google Play which toll you are buying, and attaches its own reference for that early exit so the payment can be matched to it. From version 1.0.8, each early-exit payment also carries a scrambled code that FIVE makes at random for this installation, so that Google Play can match the payment to this installation of FIVE. The code is made on your phone and is not linked to your name, email address or account. FIVE keeps it on your phone and leaves it out of Android backups.
When Google Play confirms a payment, FIVE checks Google Play's signature on the purchase receipt, on your phone, to make sure the payment is genuine and is for your challenge's toll. FIVE then ends the challenge. It keeps a record of the purchase on your phone, including Google Play's order ID, so that it applies each payment only once and so that refunds can be handled. FIVE does not store the receipt itself.
Refunds are handled manually through support: email support@fivepresence.com. Google's privacy policy covers how Google Play handles your payment.
Earlier website sign-ups
This section is about the website, not the app. The website no longer has a sign-up form. If you joined the waitlist on it earlier, we still hold the email address you entered and the time you submitted it. We use them to email you about the FIVE test and the app's release. You can ask to be removed at any time by emailing support@fivepresence.com. To add you to the test, we enter your email address into Google Play Console, which Google runs.
They are stored on our own server in Mumbai, India, and are not sold or shared for any other purpose. We keep them until six months after FIVE is released, or until you ask us to delete them. To ask, email support@fivepresence.com and we will delete them within 7 days.
Backups
Android can back up app data to your Google account and copy it to a new phone, depending on your phone's backup settings. FIVE never includes the records of running challenges and payments, or your setup answers, in these backups or transfers. Your other FIVE settings and the copy of your sign-in profile may be included.
If you used FIVE's earlier version (com.aistudio.five.detox), its data stays with that app. Installing the current app does not move it across.
Signing out, deleting your account, and uninstalling
- Signing out ends your session with Clerk and removes the copy of your profile from your phone. It does not delete your account or your challenge history.
- Deleting your account in the app deletes your Clerk account and signs you out. Your challenge history and settings stay on your phone. See Delete your FIVE account for the steps, and for how to ask us if you no longer have the app.
- Uninstalling FIVE removes FIVE's data from your phone, apart from anything Android has backed up. It does not delete your Clerk account.
Contacting support
If you email support@fivepresence.com, your message goes to FIVE's support mailbox, which is hosted by Zoho. We keep support emails only as long as we need them to answer you and to handle any refund, and never longer than 12 months. We delete them sooner if you ask us to.
Children
FIVE, the app, is for ages 13 and up, and works fully without an account as a guest. Creating an account is for people 18 or over, or a parent can do it for a teen. We do not knowingly collect personal data from anyone under 18 unless a parent is doing it for them.
Changes to this policy
If we change this policy, we will update this page and its effective date.
Contact
FIVE is provided by Solarist. We can be contacted by email only. For privacy questions or requests, email support@fivepresence.com.