Last updated: 18 August 2026
Applies to: Habitmo for Android (com.habitmo.habitmo), version 1.0.0 and later
Habitmo does not collect your data. There is no account, no sign-in, and no server that belongs to us. Everything you track stays in an encrypted database on your own device.
We cannot see your habits, because they never reach us.
Habitmo is developed and published by Oxymai LLC.
For privacy enquiries, contact us at oxymaillc@gmail.com or visit oxymai.com.
Nothing.
Habitmo contains no analytics SDK, no advertising SDK, no crash reporting service, and no telemetry of any kind. The app makes no network requests to any server operated by us, because no such server exists.
This is verifiable rather than a promise: the app requests only the Android permissions necessary for its functionality, none of which grant internet access for data collection, and the complete list of third-party components is disclosed in Section 6.
All of the following is stored only on your device and never transmitted:
Data
Where it is stored
Habit names, descriptions, icons, colours
Encrypted local database
Daily completion records, rest days, notes
Encrypted local database
Measurable habit values and targets
Encrypted local database
Reminder times
Encrypted local database
Your display name, if you enter one
Encrypted local database
Purchase record (that you bought Pro)
Encrypted local database
Theme, font, language, view preferences
Android app preferences
Database encryption key
Android Keystore
The habit database is encrypted at rest with SQLCipher (AES-256). The encryption key is generated on your device on first launch and stored in the Android Keystore, which is backed by hardware security on most modern devices. The key never leaves your device and is never included in exports or backups.
A practical consequence worth understanding: if you factory-reset your device, uninstall the app, or clear its app data, the Keystore entry is destroyed and the encrypted database becomes permanently unreadable. We cannot recover it for you — we have neither your data nor your key. Use the export feature (Section 5) if you want a copy you control.
Habitmo requests Android permissions required for its functionality. Each is used for exactly one thing:
Permission
Why
POST_NOTIFICATIONS
To show the habit reminders you schedule. Without it, reminders cannot appear at all.
SCHEDULE_EXACT_ALARM / USE_EXACT_ALARM
So a reminder set for 07:00 arrives at 07:00 rather than whenever Android's battery saver permits.
RECEIVE_BOOT_COMPLETED
To re-register your reminders after a restart. Android discards pending alarms on reboot, so without this your reminders would stop permanently the first time you restarted your phone.
VIBRATE
For the haptic feedback when you complete a habit.
Habitmo does not request internet, location, contacts, camera, microphone, storage, or any identifier permission.
Reminders are composed and delivered entirely on your device. Their contents — including your habit names — are never sent anywhere.
Habitmo can export your habits and history as a CSV or JSON file. This is entirely under your control:
The export is generated on your device.
It is handed to Android's standard share sheet, where you choose the destination — email, cloud drive, messaging app, or a local file.
Once you send the file somewhere, that destination's own privacy policy applies to it. We have no visibility into or control over that step.
Exported files are not encrypted. They are plain CSV/JSON so you can actually read and use them. Store them somewhere you consider safe.
Your database encryption key is never included in an export.
The restore feature reads a backup file you select and replaces the app's current contents. The file is read locally and nothing is uploaded.
Habitmo integrates with exactly two third parties. Neither receives your habit data.
Used only to sell and verify the one-time Habitmo Pro unlock. Google processes the payment; we never see or store your payment details — no card number, no billing address, no name. Habitmo receives only a confirmation that the purchase exists, and stores a signed record of that fact locally.
Google's handling of the transaction is governed by the Google Privacy Policy.
To verify a purchase and to check whether the app was installed from Play, Habitmo queries the Play Store app installed on your device. This is a local query to Android and sends nothing to us.
Habitmo offers 18 typefaces. The font files are downloaded from Google's font service the first time a typeface is used, then cached on your device. This request contains only the name of the font being fetched. It does not include your habits, your identity, or any app data.
Google's font service is covered by the Google Privacy Policy. If you never change the default typeface beyond the fonts already cached, this request may not occur at all.
There is nothing else. No Firebase, no Google Analytics, no Facebook SDK, no attribution or ad network, no crash reporter.
Habitmo is not directed at children under 13, and we do not knowingly collect personal information from anyone — including children — because the app collects no personal information at all. Since nothing is transmitted or stored remotely, there is no children's data for us to hold or delete.
Most data-protection rights — access, correction, deletion, portability, objection to processing — describe things you ask a company to do with data it holds about you. We hold no data about you, so there is nothing for us to disclose, correct, or erase.
In practice you already have direct and complete control:
Access and portability — Export your data as CSV or JSON at any time (Settings → Data).
Correction — Edit or delete any habit or day directly in the app.
Erasure — "Delete all habits" in Settings clears your habit data. Uninstalling the app removes the encrypted database and its Keystore key, which destroys the data irreversibly.
This holds regardless of where you live. Because no personal data is processed or transferred, applicable data-protection laws may provide limited or no basis for a data-subject request process concerning data we do not possess.
Your purchase is a separate matter and is held by Google, not us. Refunds and purchase records are handled through Google Play.
Your habit data is retained on your device for as long as you keep the app installed, and is deleted when you delete it or uninstall Habitmo. We retain nothing, because we receive nothing.
If this policy changes, the "Last updated" date above will change with it. If a future version of Habitmo ever introduces a feature that transmits data — for example an optional cloud sync — that feature will be opt-in, clearly described in the app before you enable it, and documented here before release. We will not quietly start collecting data under an unchanged policy.
For privacy questions about Habitmo:
Oxymai LLC
Email: oxymaillc@gmail.com
Website: oxymai.com
For completeness, the answers that correspond to this policy in the Play Console Data Safety form:
Question
Answer
Does your app collect or share any of the required user data types?
No
Is all user data encrypted in transit?
Not applicable — no user data is transmitted
Do you provide a way for users to request data deletion?
Yes — in-app deletion and uninstall
Data types collected
None
Data types shared with third parties
None
Purchase history
Handled by Google Play; not collected by the app