Your habits work offline and synchronize through your private iCloud account. RevenueCat sees purchase status, not lifestyle answers. There are no ads or cross-app tracking. This website is separate and counts visits without cookies: see This website below.
miniHabits requires an iCloud account so your habits can be backed up and synchronized across your Apple devices. The app works offline and keeps a local copy on each signed-in device.
The app has no advertising, cross-app tracking or product analytics. It uses Apple CloudKit for private app data and RevenueCat to manage Apple purchase entitlements.
Sign-in uses your Apple iCloud account. miniHabits does not ask for or receive your name, email address or Apple Account password.
A random, immutable UUID is created in your private CloudKit database. That UUID links your synchronized data to your RevenueCat entitlement; it is never an email address and is not used for advertising.
Habit names, schedules, tracking modes, logs, routines, break periods, themes and sync revisions are stored locally and in the app’s private CloudKit container so your devices can merge offline changes deterministically.
CloudKit is operated by Apple and stores the synchronized copy in your iCloud account. miniHabits does not put this content in a developer-operated database, public database or shared feed.
Your onboarding answers and uncommitted starter plan stay in a temporary local draft. They are not sent to RevenueCat or CloudKit. Only the plan you confirm is written as normal habit and routine data after account creation and a successful purchase or restore.
Annual and lifetime purchases are sold and charged by Apple. miniHabits never receives your card number, billing address or Apple Account credentials.
RevenueCat receives the random miniHabits user UUID, Apple purchase and receipt information, entitlement status, product identifiers and technical information needed to operate and secure the purchase service. It does not receive your habit names, logs, routines or onboarding answers.
The purchase stays associated with its original miniHabits UUID. RevenueCat does not silently transfer it to a different miniHabits account.
RevenueCat is a service provider for entitlement management. Its privacy policy is available at revenuecat.com/privacy.
Signing out removes the local habit document, temporary onboarding draft, sync queue, CloudKit cursor and cached access state from that device. The private iCloud copy remains available for session recovery and a later sign-in.
Deleting your miniHabits account from Settings deletes the app’s private CloudKit data and all local copies on that device. It does not cancel an annual App Store subscription or erase Apple’s transaction record; subscriptions are managed separately in your Apple Account.
In-app account deletion does not delete the RevenueCat customer record used for purchase entitlements. Contact [email protected] if you also want that provider record erased. Erasing it does not cancel an App Store subscription. Because purchases stay with the original miniHabits UUID, a newly created account does not automatically inherit them.
If you only delete the app, the synchronized iCloud copy remains. Reinstalling and signing into the same iCloud account can restore it.
No advertising, ad identifier, data broker, cross-app tracking, social feed or marketing profile. The app does not include product analytics or send lifestyle answers to the purchase provider.
miniHabits does not read Apple Health, request Health permission or contain HealthKit code. A habit you manually name after a health-related activity is synchronized as user-entered habit content; it is not read from the Health app.
The submitted app declares Purchases and User ID for RevenueCat entitlement management, plus Other User Content for CloudKit backup and synchronization. All three are linked to the miniHabits account and used only for app functionality. None is used for tracking.
Apple’s own collection through iCloud and the App Store is governed by Apple’s privacy policy. The label must also include any later service or SDK before that build is submitted.
miniHabits is not directed at children. Account, synchronized content and purchase data are handled in the same way for every user.
Everything above is about the app. The website is separate and counts its visitors.
Every page of minihabits.co loads a visit counter from umami.fberrez.co. Umami is self-hosted on our own machine rather than rented from an analytics vendor, so the traffic data never becomes a third party's asset. It is cookieless: it stores nothing on your device, sets no identifier, cannot recognise you on a second visit and cannot follow you to another site. What it records is the page, the referrer that sent you, and a coarse country, browser and device type, all worked out from the request itself and never from anything left on your machine.
There is no cookie banner because there is nothing to consent to. If your browser sends Do Not Track, the counter switches itself off and records nothing at all. You can also turn it off yourself, on any browser, by setting umami.disabled to 1 in this site’s local storage.
The free tools are unaffected in the way that matters. The page view is counted like any other; the data you paste into them is not. The heatmap generator, the 75 Hard tracker, the morning routine planner and the theme builder all run entirely in your browser and keep what you enter in your own browser storage, which is why none of them asks for an email.
The website does not receive habit data from the app and does not provide account or billing services.
If a future release ever collects anything, this page will say so before that release ships, and the App Store privacy labels will be updated with it.
Questions about this policy: [email protected].