MiHabit Privacy Policy

Effective date: July 20, 2026
Applies to: MiHabit mobile app, version 1.0.2 (build 19)
Developer / data controller: VSJ TECH LAB
Privacy contact: support@vsjtechlab.com

1. About this policy

MiHabit is a routine, habit, wellness, reminder, and progress-tracking app. This Privacy Policy explains what information MiHabit processes, where it is stored, how it is used, when it is sent to another service, how long it is kept, and the controls available to you.

MiHabit is designed so that the personal content you enter such as your profile name, routines, completion history, goals, book progress, and cached health totals is primarily processed on your device. The app does not require a MiHabit account and does not upload that content to a MiHabit-operated cloud database. If you choose Google Drive backup, MiHabit uses Google sign-in and sends a filtered backup to your Google Drive account as explained below. The app also contains Google services for advertising, analytics, authentication, Drive storage, and subscriptions. Those services process certain account, device, usage, advertising, backup, and transaction information as explained below.

Health and fitness information is treated separately and is not sent by MiHabit to advertising or analytics services.

2. Information you provide and information created through app use

A. Profile and preference information

MiHabit stores the information you provide during onboarding and in Settings, including:

your profile name;
your chosen avatar;
your selected app language;
dark-mode and theme choices;
time format and start-of-week choices; and
notification and health-sync preferences.

Google sign-in is optional and is requested only if you open Google Drive backup and choose to connect. When connected, MiHabit processes the Google account email address, display name, Google identity token, OAuth access token, and Firebase Authentication UID needed to authenticate the session and access MiHabit’s private Drive storage. MiHabit does not receive your Google password. OAuth and identity tokens are handled by the Google and Firebase SDKs and are not written into the MiHabit backup file.

B. Routines, goals, and reminders

When you select a built-in template or create a custom routine, MiHabit may store:

the routine title, description, category, and subcategory;
frequency, repeat pattern, scheduled days, reminder times, priority, duration, difficulty, and rest days;
reminder tone, muted status, and whether reminders are enabled;
numerical targets, measurement units, current progress, and completion counts;
completion, skip, deletion, and rescheduling status;
creation, update, completion, automatic-completion, and health-sync timestamps; and
whether the routine is manually tracked or linked to a supported health metric.

This information is used to display your routines, calculate remaining goals, schedule reminders, show progress, and generate insights.

C. Progress, rewards, and activity history

MiHabit creates and stores records needed to provide its progress and rewards features, including:

routine completion history and daily progress;
Lifestyle Scores and weekly summaries;
completion source, such as manual entry or Health Connect / Apple Health;
XP, levels, streaks, best streaks, achievements, reward claims, unlocked avatars and themes, streak shields, skip tokens, and milestone state;
the number of routines completed and scheduled; and
learning records, including book title, author, total pages, current page, reading goal, and last-read time.

D. Notification and scheduling information

To provide reminders, MiHabit stores local notification schedules and technical records such as notification IDs, routine IDs, recurrence, reminder slot, scheduled time, device time zone, sound choice, muted state, and notification type. It also keeps a rolling local diagnostic log of up to 200 notification operations. That log may include the operation, routine or notification ID, time, success or failure, and an error or stack trace when an operation fails.

Notification content may include a routine name, reminder message, remaining goal, and action buttons. Depending on your device notification settings, this content may be visible on your lock screen or to anyone who can view your notifications.

E. Subscription status

MiHabit offers Free, Premium, and Premium Plus access. The app stores the currently resolved entitlement level on your device. Google Play processes the purchase or subscription itself, including payment method, billing account, purchase status, product ID, price, and transaction records. MiHabit does not receive or store your complete payment-card details.

F. Information we do not request

The current app does not request access to precise or approximate device location, contacts, call logs, text messages, camera, microphone, or photos and videos. Google Drive backup does not give MiHabit access to the rest of your visible Drive files; it requests only the limited Drive application-data scope.

3. Optional Health Connect and Apple Health processing

Health Sync is optional. MiHabit works without connecting Health Connect or Apple Health. The app requests read access only after you initiate the connection and choose the categories you want to enable.

Depending on your choices and platform availability, MiHabit may read:

steps;
walking and running distance;
exercise or workout duration;
completed workout sessions;
sleep duration;
active energy or calories burned; and
water or hydration intake.

MiHabit uses this information only for user-facing health and wellness features, including updating linked routine progress, determining whether a linked goal has been completed, calculating Lifestyle Score when you enable that option, and presenting progress and wellness insights.

MiHabit reads records from the platform health store and converts them into daily totals. It does not retain every raw health record. A cached daily summary can contain the daily value for each enabled metric, the date and last-sync time, unavailable metrics, and limited source metadata supplied by the platform, such as source name or ID, device ID, and recording method. Cached daily summaries older than 90 days are removed during successful synchronization.

MiHabit does not:

write records to Health Connect or Apple Health;
upload health records or cached health summaries to a MiHabit server;
send health information to Google Mobile Ads or Firebase Analytics;
use health information for advertising, profiling, credit decisions, or data-broker purposes; or
sell health information.

You can disable individual health categories, turn off automatic completion or score inclusion, manage permissions in the platform health settings, disconnect Health Sync, or remove MiHabit’s cached summaries. Disconnecting or removing a cached summary does not delete the original record from Health Connect or Apple Health. You must use the controls provided by Google or Apple to manage the original record.

Health information shown by MiHabit is for routine and wellness tracking, not medical diagnosis, treatment, emergency monitoring, or another medical purpose. Data from a phone, wearable, Health Connect, or Apple Health may be delayed, incomplete, duplicated, or inaccurate.

4. How information is used

MiHabit uses information for the following purposes:

to provide onboarding, profile, avatar, language, theme, and accessibility preferences;
to create, schedule, display, edit, reschedule, skip, delete, and complete routines;
to calculate progress, remaining goals, scores, streaks, XP, achievements, and rewards;
to schedule local notifications, play selected reminder sounds, process notification action buttons, and restore schedules after a reboot, app update, clock change, or time-zone change;
to generate local insights, weekly reports, and readable exports;
to read optional health totals and automate linked routine progress when you enable Health Sync;
to show and restore paid subscription entitlements;
to show interstitial ads to Free users, subject to the app’s action threshold and cooldown;
to understand basic app usage and performance through Firebase Analytics on Android;
to diagnose local notification failures using the on-device audit log;
to authenticate an optional Google account and create, find, update, download, restore, or delete your private MiHabit Google Drive backup when you request those operations; and
to run optional automatic Drive backup after local changes while you remain signed in.

MiHabit does not use the profile name you enter as a Firebase Analytics user ID and does not intentionally attach your routine titles, descriptions, history, book records, or health totals to advertising or analytics requests.

5. Where information is stored

On-device app storage

Profile, preference, routine, progress, reward, book, notification, subscription-entitlement, and cached health-summary data is stored in MiHabit’s private application storage using a local Hive database. The operating system normally prevents other apps from directly opening this storage. MiHabit does not add separate database-level encryption, so protection also depends on your device passcode, operating-system security, and backup settings.

Operating-system backups and device transfer

The current Android release does not opt out of Android Auto Backup or define exclusions for the local database. Depending on your Android version, manufacturer, Google account, and backup settings, Android may copy eligible MiHabit app data to the private backup area of your Google Drive account or transfer it to another device. Similar operating-system backup or device-transfer behavior may apply on Apple devices according to your iCloud and device settings. These platform-managed backups are controlled by Google or Apple, not by MiHabit, and may outlive an app uninstall for a period of time.

Optional Google Drive backup

If you connect Google Drive backup, MiHabit creates one private application-data file in the Google Drive account you select. The file can contain your profile name and avatar, routines and reminder configuration, manual completion history, goals, scores, XP and reward state, app preferences, and book progress. It is used to back up and restore MiHabit data across devices. Automatic backup is off by default and can be enabled or disabled on the Cloud Backup screen.

Before upload, MiHabit removes Health Connect and Apple Health measurements, cached daily health summaries, health-sync timestamps, source-specific health completion records, and the current measured value and completion state of health-linked routines. The configuration that says a routine is linked to a particular health metric can remain so that the routine can be reconnected on another device. General aggregate XP or rewards already earned in the app may remain without the underlying health measurement. The separate local Health Sync cache is never added to the Drive file.

The backup is stored in Google Drive’s hidden appDataFolder. Google states that this area is accessible only by the app that created it, is not visible in the normal Drive interface, and cannot be shared like an ordinary Drive file. MiHabit requests only the drive.appdata OAuth scope and cannot use that scope to read your other Drive documents. You can restore, replace, or delete the backup in MiHabit and can remove the app’s Drive data through your Google account controls. MiHabit does not operate a separate server database holding the backup.

6. Information collected or processed by third parties

A. Google Mobile Ads / AdMob

MiHabit initializes the Google Mobile Ads SDK and requests interstitial ads for Free users. Google states that its Mobile Ads SDK automatically collects and shares data for advertising, analytics, and fraud prevention, including:

IP address, which may be used to estimate general location;
app launches, taps, ad interactions, and video views;
diagnostic and performance information, such as launch time, hang rate, and energy usage; and
device and account identifiers, including the Android advertising ID, app set ID, and applicable identifiers related to accounts on the device.

The Android release currently declares advertising-ID and Android Privacy Sandbox advertising permissions. You can reset or delete the advertising ID and manage ad privacy controls in Android Settings. Google and participating ad-technology providers process advertising data under their own terms and privacy notices. See Google Mobile Ads data disclosure, Google’s Privacy Policy, and My Ad Center.

MiHabit does not provide routine content or Health Connect / Apple Health data to the Mobile Ads SDK.

B. Firebase Analytics on Android

The Android version includes Google Analytics for Firebase. It starts automatically in the current release; MiHabit has not added a separate in-app Analytics opt-out control. Google states that the default Firebase Analytics implementation may collect:

an app-instance identifier for the installation;
Android advertising ID when available;
masked IP address used to derive coarse location;
device, operating-system, app-version, language, screen, session, and app-lifecycle information;
basic app engagement; and
in-app purchase and subscription events, including product ID, product name, and price.

MiHabit does not set a Firebase user ID to your profile name and does not log custom health records or routine content to Firebase Analytics. Google encrypts Firebase Analytics data in transit and retains or uses it according to the Firebase property’s configuration and Google’s terms. See Firebase Analytics data collection, Firebase privacy information, and Google’s Privacy Policy.

C. Firebase Authentication and Google Drive

When you voluntarily connect cloud backup, Google sign-in authenticates the Google account and Firebase Authentication creates or resolves a corresponding Firebase user identity. Google and Firebase may process the account email address, display name, account identifier, authentication tokens, IP address, device and security information, sign-in time, and Firebase UID to provide authentication, protect accounts, and prevent abuse.

MiHabit then uses the Google Drive API with the limited drive.appdata scope to store and retrieve the filtered backup described in Section 5. Google processes the backup file, file identifier, size, modification time, access requests, and related service logs as the Drive provider. MiHabit does not request access to ordinary Drive files and does not share the backup with advertisers. See Firebase privacy and security, Google Drive application data, and Google’s Privacy Policy.

D. Google Play and Google Play Billing

Google Play distributes the Android app and processes purchases, subscriptions, license tests, entitlement restoration, and store availability. Google may process your Google account, payment, transaction, device, and fraud-prevention information. MiHabit receives store product information and purchase status needed to unlock or restore the appropriate plan. Google Play’s handling of this information is governed by Google’s Privacy Policy and Google Play Terms of Service.

E. Health Connect and Apple Health

Health Connect and Apple Health act as user-controlled health data stores. MiHabit accesses only the categories you authorize. Google or Apple may process information as the platform provider under their own notices. See Health Connect and Apple Health and privacy.

MiHabit uses operating-system services to schedule and display notifications. The operating system receives the notification content needed to show it.

If you choose Export JSON, MiHabit creates a copy of the app-state data and places it on the system clipboard. Other apps or people with access to the device may be able to read clipboard content subject to operating-system protections.

If you choose Export PDF, MiHabit creates the report on the device and opens the system share or printing interface. The PDF can include your name, plan, Lifestyle Score, weekly progress, routines, streaks, XP, hydration summary, recent activity, and recommendations. MiHabit does not choose the recipient. Any app, cloud drive, printer, email service, or person you select will receive the report and handle it under its own terms.

Operating-system backup and device-transfer services may also process eligible local app data as described in Section 5.

7. When information is disclosed

MiHabit discloses information only in the following circumstances:

Service providers and platforms: account, authentication, backup, device, usage, advertising, analytics, and purchase data is processed by the third parties described in Section 6 to provide their services.
At your direction: information is sent to a destination you choose when you connect Google Drive backup, copy a JSON export, share or print a PDF, manage platform health data, or use an operating-system backup or transfer feature.
Legal and safety reasons: the developer may disclose information actually available to the developer when reasonably required by law, legal process, or to protect rights, safety, and security.
Business transfer: if the app or its developer is involved in a merger, acquisition, financing, reorganization, or sale of assets, relevant information may be transferred subject to applicable law and continued protection.

The developer does not sell the profile, routine, book, progress, or health content stored by MiHabit. Advertising providers may collect and share advertising identifiers and interaction information as described above. Depending on the law where you live, personalized advertising or cross-context behavioral advertising can be legally defined as a “sale” or “sharing.” MiHabit must provide any consent or opt-out mechanism required in your region before using those forms of advertising.

Health Connect and Apple Health information is never disclosed for advertising, data-broker, creditworthiness, or similar purposes.

8. Retention and deletion

Different information has different retention periods:

Profile, routines, completion history, scores, XP, rewards, achievements, preferences, and book progress remain on the device until you edit or delete the relevant item, use the in-app reset, clear MiHabit’s app storage, or uninstall the app.
Health daily summaries older than 90 days are removed during successful health synchronization. You may also remove all imported summaries from Health & Activity settings.
A Google Drive backup remains in the connected account until it is replaced, you delete it from MiHabit or your Google account controls, or Google deletes it under its policies. Signing out stops MiHabit from accessing the backup but does not delete the Drive copy. The Cloud Backup screen provides a separate permanent-delete control.
Firebase Authentication account and sign-in records are retained by Google/Firebase according to the Firebase project configuration and Google’s policies. Signing out removes the active local session but does not necessarily delete the Firebase Authentication user record.
The local notification diagnostic log keeps the most recent 200 operations.
Notification schedules remain until they fire, are cancelled, are replaced, or you reset or clear the app.
Reset app user signs out of Google/Firebase locally and clears Cloud Backup settings, Health Sync settings and cached summaries, notification schedules, diagnostics and action claims, advertising cadence, other technical keys, and the main user state. It does not delete an existing Drive backup or Firebase Authentication user record. MiHabit retains only a valid paid-plan entitlement cache so resetting a profile does not remove Premium access that was purchased through Google Play. To delete the Drive copy first, use Delete cloud backup before resetting. To remove the remaining local entitlement cache as well, use the operating system’s Clear storage / Clear data control or uninstall the app; the underlying purchase record will still remain with Google Play.
Android or Apple backups may retain an older copy until the platform replaces or deletes that backup under your device and account settings.
Purchase and subscription records remain with Google Play according to Google’s legal and accounting obligations and cannot be deleted by MiHabit’s local reset.
Advertising and analytics data is retained by Google according to the applicable product configuration, user controls, and Google policies.

The in-app Reset app user action signs out of cloud backup locally, attempts to disconnect platform health access, cancels scheduled notifications, and deletes the local profile, routines, history, XP, streaks, achievements, book progress, imported health summaries, advertising cadence, notification diagnostics, and related technical state before restarting onboarding. Some platforms may require you to revoke health permission manually in device settings. Reset is not a request to delete records held by Google Drive, Firebase Authentication, Google Play, Google advertising or analytics services, Health Connect, Apple Health, or an operating-system backup provider.

9. Your choices and rights

You can:

edit your profile name and preferences;
create, edit, complete, skip, reschedule, or delete routines;
deny or revoke notification and exact-alarm permissions in device settings;
hide notification content through lock-screen settings;
choose reminder sounds or mute individual reminder slots;
decline Health Sync, disable individual health categories, turn off automatic completion or score inclusion, revoke health permissions, disconnect, or remove cached summaries;
manage or delete original health records in Health Connect or Apple Health;
reset your advertising ID and manage ad personalization in device and Google settings;
manage or cancel subscriptions through Google Play;
connect or sign out of Google Drive backup, enable or disable automatic backup, create or restore a backup, and permanently delete the Drive copy;
export your data in JSON or readable PDF when that feature is available under your plan; and
use Reset app user, clear app storage, or uninstall the app.

Depending on your location, you may also have rights to request access, correction, deletion, restriction, portability, withdrawal of consent, or objection to certain processing, and to complain to a data-protection authority. Because most MiHabit content stays only on your device, the developer may not possess a server-side copy to retrieve or delete. For information processed by Google or Apple, use their privacy controls or contact the relevant provider. For requests concerning information controlled by the MiHabit developer, contact support@vsjtechlab.com.

10. Security

MiHabit limits requested device permissions and keeps personal routine and health-summary content in private app storage rather than sending it to a MiHabit server. Optional Drive backups are transferred over HTTPS to Google’s private application-data storage using OAuth authorization. MiHabit checks backup structure and size before restoring and does not automatically overwrite a cloud copy that changed on another device. The Drive backup is not separately encrypted by MiHabit before upload; it relies on Google account security and Google Drive’s transport and storage protections. Data sent to Google Mobile Ads, Firebase services, Google Play, Drive, and platform services is protected in transit by the security measures those services provide, including TLS where documented.

No storage or transmission method is completely secure. Protect your device with an up-to-date operating system, a strong screen lock, and appropriate lock-screen notification settings. Take particular care when copying JSON to the clipboard or sharing a PDF because MiHabit cannot control the destination after you choose it.

11. International processing

Google, Apple, and any recipient you choose for an export may process information in countries other than the country where you live. This includes Google account authentication and optional Drive backup storage. Their international-transfer safeguards and data-center practices are described in their own privacy notices. MiHabit does not transfer your data to a MiHabit-operated international server.

12. Children

MiHabit is not directed to children under 13. The app requests a local profile name and includes advertising and analytics SDKs. Optional Drive backup also permits Google account sign-in and therefore may process an email address and account identity. A parent or guardian who allows a minor to use the app should supervise the minor’s use, review device privacy and advertising settings, avoid entering identifying information in routine titles or exports, and control whether Google Drive backup is connected. If you believe the developer has received personal information from a child in violation of applicable law, contact support@vsjtechlab.com.

13. Changes to this policy

This policy may be updated when MiHabit’s features, SDKs, legal obligations, or data practices change. The effective date at the top will be revised. Material changes should be communicated through the app, store listing, or another appropriate notice before they take effect where required.

14. Contact

Questions, requests, or complaints about this policy may be sent to:

VSJ TECH LAB
support@vsjtechlab.com