Privacy policy
Your thoughts are personal. This policy explains what Axo accesses, where information lives, and the choices you have.
The short version
Your step titles, thoughts, reflections and habitat progress are saved on your device. Axo has no account or cloud sync. Basic usage analytics is on by default and can be turned off in Preferences → Privacy & usage → Help improve Axo. Mixpanel processes those usage events; RevenueCat and the app store process purchases and verify Plus access. Axo does not use an advertising SDK. Optional Android focus protection processes other-app usage events locally. Nothing is posted automatically.
This policy applies to the mobile app Axo: ADHD Focus & Habits (Android package com.axo.focus) and this Axo website. The developer’s privacy and support contact is appcraft.dev1@gmail.com. “We” and “our” refer to the developer of Axo.
Information stored on your device
Axo uses local app storage to provide its features and remember your progress. Depending on what you choose to use, this includes:
- Your companion’s name, onboarding choices, app preferences, and tutorial progress.
- Step titles, task plans and actions, routines, completion status, and selected focus durations.
- Focus-session dates, durations, pauses and progress, daily intentions, and reflections you write.
- Earned pebbles, companion progress, owned decorations, and their habitat positions.
- Reminder settings, permission-prompt status, widget/timer state, and optional focus-protection settings.
- Local Plus-preview interaction counts and invitation timing. These are on-device records, not remote analytics or purchase data.
We do not operate a server that receives this app progress. The app does not request your contacts, messages, microphone, camera, precise location, or health records. Device time and timezone support local reminders and session dates. Where used, motion-sensor input animates the habitat on-device and is not sent to us or retained as a motion history.
Local app storage is protected by the operating system’s app-access controls. It is not a separate encrypted vault. Your device’s security, backup settings, and who can access your unlocked device also matter.
Optional Android focus protection
Focus protection is a feature you can choose to enable. Axo displays available launcher apps—their names, package identifiers, and icons—so you can select distractions. Your selected package identifiers are saved locally.
With your explicit consent and Android Usage Access permission, Axo reads recent app foreground/background events during an active protected focus session to detect whether a selected app is open. Android may provide events for other apps within the queried time window; Axo processes these locally to determine the foreground app. It does not upload them, build a retained browsing or app-usage history, or use them for advertising.
With permission to display over other apps, Axo shows a focus shield over a selected distracting app. Axo may request temporary audio focus to encourage that app to pause audio. This is best-effort, not an operating-system app lock, a guaranteed audio blocker, or parental control. It does not read the content inside other apps.
A visible foreground service supports active protection. Monitoring stops when the session ends, is paused, or required access is revoked. You can disable focus protection in Axo’s Preferences and revoke Usage Access or display-over-other-apps permission in Android settings. Core focus sessions work without these permissions. iOS Screen Time protection is not implemented in the current version.
Permissions and why they exist
Usage analytics and purchases
Mixpanel usage analytics
To learn which features help people and where the experience fails, Axo sends a small set of usage events to Mixpanel’s US endpoint. These describe app visits, onboarding progress and completed setup, focus starts and saved durations, step creation/completion, feature use, paywall views and checkout outcomes. They include timestamps, a pseudonymous app identifier, confirmed Plus status and basic app/device information such as app version, OS and device model. Pseudonymous does not mean fully anonymous. We do not attach your email, companion name, step or routine titles, thought or reflection text, selected-app names or package lists, or Android Usage Access history. We do not enable session replay, automatic screen/click capture or advertising identifiers. Mixpanel uses the network IP address to estimate city, region and country for usage analytics. This is approximate, may be affected by VPNs or network routing, and does not use GPS or request device location permission.
Usage analytics is enabled by default, without a consent popup. Turn it off or back on in Preferences → Privacy & usage → Help improve Axo. Turning it off stops new app usage events and requests deletion of unsent SDK events. Previously delivered events and requests already in flight are not recalled. It does not disable billing, affect focus features, or remove your Plus access. We do not upload past local focus history when you enable analytics. Mixpanel stores events according to the project’s retention settings; we do not promise a fixed retention period here. Contact us with privacy or deletion enquiries. See Mixpanel’s privacy policy.
RevenueCat and the app store
For optional Axo Plus purchases, we use RevenueCat and Google Play. RevenueCat processes a pseudonymous purchase identifier, product and transaction information, entitlement status and technical app/device information to provide checkout, verification, refunds and restore. Google Play handles your payment account and payment details; Axo does not receive your card number. These necessary purchase operations remain enabled when usage analytics is off. This version does not configure server-side RevenueCat-to-Mixpanel revenue forwarding. See RevenueCat’s privacy policy and Google’s privacy policy.
This website
The website contains no advertising, analytics scripts, tracking pixels, embedded social feeds, or sign-up form. Its interactive previews use temporary in-memory state; they do not write cookies or browser storage and are not saved or submitted to us. Fonts and artwork are served with the site rather than loaded from a third-party font service.
When hosted on GitHub Pages, GitHub processes technical request information, including visitors’ IP addresses, for hosting and security. See GitHub’s privacy statement. External links and email services have their own policies.
Retention and deletion
App progress remains in local storage until you delete applicable entries, clear the app’s storage through device settings, or remove the app. On Android, open the device’s app settings for Axo and use the storage/data-clear option to erase local app data. Names vary by device. Clearing only the cache does not erase progress. Uninstalling may not remove separately retained operating-system backups or images you exported.
Temporary share images are stored in Axo’s cache. When creating a new share image, Axo attempts to remove its own cached share images older than one day. The operating system may clear the cache earlier. Images saved or shared outside Axo remain under your control or the receiving service’s control.
Support correspondence is retained for as long as reasonably needed to handle the request and fulfil applicable legal or security obligations. Contact us to request deletion of information held in support records. We cannot remotely access or erase app progress that exists only on your device. To remove backed-up copies, use the relevant platform’s backup controls.
Your choices and privacy enquiries
You can edit or delete steps, opt out of reminders, turn off optional focus protection, revoke device permissions, choose what goes in a share card, and clear local app data. There is no Axo account to delete.
Depending on your location, you may have rights to access, correct, delete, restrict, or object to our processing of information you have sent us, and to complain to a relevant data-protection authority. Email appcraft.dev1@gmail.com with your request. We may need proportionate information to confirm that the request relates to you. These choices do not limit rights provided by applicable law.
Children’s privacy
Axo is not designed or marketed for children under 13. We do not knowingly seek personal information from children under 13 through support enquiries. If you believe a child has provided us with such information, contact us so we can investigate and take appropriate action. Local app content is not transmitted to our servers.
Updates and contact
If the app’s features, payments, or data practices change, we will update this policy and its date. Material changes will be communicated where required. This policy describes the current app, not unimplemented features.
Privacy contact for Axo: ADHD Focus & Habits
appcraft.dev1@gmail.com
For help with the app, visit Support. For rules about use, read the terms & conditions.