Privacy Policy
Last updated: 6 November 2026 · Applies to the myHab.Fit Android app (com.myhabfit.app) and this website
In short
- You must be 18 or older to use myHab.Fit.
- Your profile, workouts, body weight, water, fasting, recovery and Health Connect readings are kept on your phone, not on our servers.
- Our servers hold only your account ID, the agreements and choices you made, confirmation that you are 18 or over, your subscription status and the purchase token Google Play issues for it, and a backup key if you use Google Drive backup. They are in India (Mumbai).
- Menstrual-cycle and symptom logs stay on your phone and in your phone's encrypted backup. We can never read them.
- Camera images never leave your phone. No photo or video frame is ever stored or sent anywhere.
- Crash reports and usage statistics are off unless you turn them on.
- We do not sell your data. We do not use it for advertising. We do not collect an advertising identifier.
- You can download your data or delete your account from inside the app, at any time.
myHab.Fit is currently available only in India.
1. Who is responsible for your data
myHab.Fit is operated by SEETALA SRI SAI SRAVANTHI, an individual based in Hyderabad, Telangana, India.
Under the Digital Personal Data Protection Act, 2023 ("the DPDP Act"), that person is the Data Fiduciary for your personal data — meaning they decide what data is collected and why, and are answerable for it.
If myHab.Fit moves to a company we own or control, or to a successor that takes over the app, that company becomes the Data Fiduciary for your data in our place. It will hold your data under the same commitments as this policy, and we will tell you in the app before the change takes effect.
Contact for any question or complaint about your data — Grievance Officer: Seetala Sri Sai Sravanthi, Proprietor
Email: contactus@myhab.fit
Postal: S-404, Poojitha Estates, Model Colony, Sundernagar, Hyderabad, Telangana, India – 500038
We acknowledge every request or complaint about your data within 48 hours and resolve it within one month.
2. Age requirement
myHab.Fit is for adults. You must be 18 or over to create an account or use the app.
Before you sign in, the app asks for your date of birth. If you are under 18 on that date, you cannot sign in, and the app will not ask again for 24 hours; for that wait, the phone stores only the time it ends, never your date of birth. If you are 18 or over, the app keeps only your birth year, on your phone, and our servers record only that you confirmed you are 18 or over. The check relies on what you tell us — we do not verify it, and we would rather say so than imply a check we do not perform.
We do not knowingly collect data from anyone under 18. Under Indian law, anyone under 18 is a child, and processing a child's data requires verifiable parental consent, which this app is not designed to obtain. If we learn that an account belongs to someone under 18, we will delete it.
If you believe a child is using the app, contact us at contactus@myhab.fit.
3. What we collect, and why
Before you start, the app shows a short notice and asks you to agree to two things: the Terms and this policy, and the use of your health and fitness data on your phone as described here. Crash reports and usage statistics are separate, optional switches that start off.
3.1 Your account
When you sign in with Google, your email address, name, profile photo link and an internal account ID are held by Firebase Authentication, the Google sign-in service we use, along with the IP address you signed in from, for security. Our own records use only the account ID. We don't copy your email, name or photo anywhere else.
Sign-in is through your Google account. We never see or store a password. There is no guest mode — an account is required.
3.2 What you tell us when you set up
All of this is kept on your phone (§4).
| What | Why |
|---|---|
| First name | To greet you. |
| Gender | One input to the formula that estimates calories burned. It also chooses which version of an exercise-demonstration video and of the body map is shown, and the default coaching voice, and decides whether the optional cycle feature is offered. |
| Date of birth | Asked once, before sign-in, for the 18 check in §2. Only the year is kept, as one input to the calorie formula and to suggest a daily water goal. |
| Height and weight | The same calorie formula. Weight also starts your body-weight chart and helps suggest a daily water goal. |
| Goal, fitness level, workout days a week | Builds your workout plan and sets your weekly target. |
| Preferred time of day (asked by earlier versions only) | Times your workout reminders, if you turn them on. |
| Equipment you have, gym machines and the weights you own | Limits which exercises can appear in your plan and suggests the weights to use. |
3.3 What the app records as you use it
Workouts you complete (exercises, sets, repetitions, weights, duration, estimated calories), personal bests, your streak and consistency record, per-exercise progression, any injuries you flag, recovery scores calculated from your health data, movement breaks, walks and your daily step goal, water you log and your water goal, fasts you time and your fasting plan, the "Low energy" or "Feeling sick" signals you set for the day, and your reminder settings. All of it is kept on your phone.
Reminders are decided on your phone. Nothing about which reminders you get, or when, is sent to us. To time them, the app can also use signals on your phone: whether you have likely woken up, whether you are likely travelling, and whether you are using the phone (see §11). These stay on your phone.
If you add a myHab.Fit widget to your Home screen, it shows your steps, water, workout and fast there, where anyone who can see your screen can see them. What a widget shows is kept on your phone only and is not included in either backup. Cycle data never appears on a widget.
3.4 Health data from Health Connect (optional, and separately permitted)
If you connect Health Connect and grant permission, we read: steps · sleep sessions and stages · heart-rate variability · resting heart rate · active calories · body weight · workouts recorded by other fitness apps (including the name of the app that recorded them).
This is used to estimate how recovered you are, to adjust the intensity of your sessions, to check your walks and count active days toward your weekly streak, and to show your health trends in the app. If you also allow reading in the background, the app uses it only for two things: to time and word your reminders (for example, not to send a morning reminder before you are awake), and to keep the steps on your Home-screen widgets up to date.
These readings stay on your phone. We don't upload them, and neither is anything built from them, such as your recovery score or your streak.
We also write two things back to Health Connect: the workouts you complete in myHab.Fit, and the calories for them, so your other health apps can see them.
You can grant or revoke each of these permissions at any time in Android's Health Connect settings.
3.5 Menstrual cycle (optional, off by default)
If you turn this on, you can log period days with a flow level, and symptoms from a fixed list, with a severity. There is no free-text box.
It is used to gently reduce workout intensity on days you report certain symptoms, to leave jumping exercises out on days you log a period, to show cycle predictions, and to send a period reminder if you turn one on.
This data stays on your phone and in your phone's encrypted backup. We can never read it. Android's backup includes it only when the backup is encrypted with your phone's screen lock, so neither Google nor we can read it; Android's phone-to-phone transfer can also carry it to a new phone. It is never uploaded to our servers, never included in the Google Drive backup (§3.11), never included in usage statistics, and never sent to anyone else. A period reminder records nothing about itself and hides its text on your lock screen.
Two indirect signals, which we would rather state than have you discover. Although the cycle log itself never reaches us: (a) exercise-demonstration videos come from a delivery network, and the file requested differs by gender — so that network's logs can imply your gender; and (b) if you turn on usage statistics, they record when workouts start and finish, and if you train less during your period, that pattern could show there, as any change in your training would. Neither transmits your cycle log, but we would rather say so.
You can delete all cycle data at any time in Settings → Cycle tracking, separately from the rest of your account.
3.6 Camera (optional, off by default, marked experimental)
If you turn the camera on, it is used to count your repetitions during a set.
No image, video frame, or body-position recording is ever saved or sent anywhere. The analysis runs entirely on your phone, using a model bundled inside the app. Nothing is uploaded for processing. The only thing kept is a small set of numbers describing your joint angles, stored on your phone, which you can reset in Settings.
3.7 Usage statistics (optional, off by default)
If you turn on Share usage statistics, Google Firebase Analytics receives which features you use, whether setup finished, which exercises you watch or look up, how many exercises a workout has, when a workout starts, finishes or stops early (so the times can show how long it lasted), subscription outcomes, and which version of our training-progression logic your app runs. These never include your weights, reps, body measurements, steps, cycle data or any other health reading. They carry a random per-installation identifier generated by Google; your name, email and account ID are never included. Google Analytics also estimates your approximate location (for example, your city or region) from your IP address.
Statistics are sent only while you are signed in. Turning the switch off stops them and clears the identifier on your phone. A copy of the statistics is exported to our own Google Cloud storage (BigQuery) in Mumbai.
3.8 Crash reports (optional, off by default)
If you turn on Send crash reports and the app crashes, a technical report is sent to Google Crashlytics: the error trace, the app's state at the moment of the crash, your device model and Android version, and a random installation identifier used to count how many installations a crash affects. We attach no account identifier. We add two technical labels: where the app was installed from (for example, Google Play) and which version of our training-progression logic is running. Crashes recorded before you turned the switch on are deleted, not sent.
3.9 Exercise videos and spoken guidance
Exercise-demonstration videos and spoken exercise guidance are downloaded or streamed from our delivery network rather than bundled into the app. Each request includes your device's IP address and which file you asked for: the video file differs by gender, and the guidance file differs by coaching voice. No cookies, account identifier or account data are sent. Downloaded files stay on your phone and are removed after 15 days without use; you choose in Settings whether they download on Wi-Fi only, on any network, or never.
Coaching cues are spoken by voices bundled in the app or installed on your phone. No text is sent to an online speech service.
3.10 Subscriptions
Payment is handled by Google Play; we never see your card or bank details. When you buy a subscription, our server (Google Cloud Functions, Mumbai) checks the purchase with Google Play and keeps your subscription status with your account, along with the purchase token Google Play issues for it, so it can recognise later renewals, cancellations and refunds.
To confirm that requests come from the genuine app, the app also sends Google Play Integrity checks through Firebase App Check. On each start it fetches app settings from Firebase Remote Config, which uses a random installation identifier.
3.11 Backups and your own copy
- Android backup. If backup is on in your phone's settings and your phone has a screen lock, Android can include the app's data in your phone's backup, encrypted with your screen lock, so that neither Google nor we can read it. It is used when you reinstall or move to a new phone. Downloaded videos, the subscription record and an unfinished workout are left out. You can turn backup off in your phone's settings.
- Google Drive backup (optional, only when you start it). In Settings → Privacy & data → Back up to Google Drive, the app saves an encrypted file in a hidden app folder of your own Google Drive. The app can see only that folder, not your other Drive files. The encryption key is created on your phone and stored with your account on our server, so you can restore on a new phone. Because we hold that key, cycle logs are never put in this file.
- Download my data. In Settings → Privacy & data → Download my data, the app writes one readable file with what our servers hold for your account and everything stored on your phone, cycle logs included. It is saved where you choose and is not encrypted, so keep it somewhere safe.
4. Where your data is stored
On your phone — never sent to our servers: everything described in §3.2 to §3.6, including your profile, birth year, workout history, personal bests, streak, progression, body-weight log, water and fasting logs, cycle and symptom logs, injury flags, today's energy and sickness signals, recovery scores, movement-break logs, walk state and step goal, camera calibration, the cached list of other apps' workouts, your achievements and your preferences. Android protects it from other apps, and the backups in §3.11 can copy it, encrypted.
Signing out keeps this data on the phone. Signing in on that phone with a different account clears the previous account's data from it.
In our cloud storage (Google Cloud Firestore, Mumbai region, India): your account ID; when your record was created and last updated; which versions of the terms, this policy and the health-data notice you agreed to, and your crash-report and usage-statistics choices, with a dated history of each agreement and change, including your confirmation that you are 18 or over; your subscription record; and your Google Drive backup key, if you use Drive backup. Our server also keeps a record of each purchase (§3.10).
Access is restricted so that only your own signed-in account can read your own records, and only our server can write your subscription record. Everything else is refused by default.
Data leaving India. Your account records are held in India. However, sign-in, usage statistics, crash reports, app settings and integrity checks are operated by Google on its global infrastructure, Android backup and Google Drive are Google services, and our delivery network (Cloudflare) is global, so some data is processed outside India. The DPDP Act permits such transfers subject to conditions set by the Government of India, and we will comply with any conditions applicable to us.
5. Who else receives data
| Who | What they receive |
|---|---|
| Google (Firebase Authentication) | Your sign-in: email address, name, profile photo link, account ID, and the IP address used to sign in (for security) |
| Google (Cloud Firestore and Cloud Functions, Mumbai) | The cloud data listed in §4, and purchase checks as in §3.10 |
| Google (Firebase Analytics and BigQuery) | Usage statistics as in §3.7, only if you turn them on |
| Google (Firebase Crashlytics) | Crash reports as in §3.8, only if you turn them on |
| Google (Firebase Remote Config and App Check) | A random installation identifier, and an integrity check from Google Play |
| Google (Android backup and Google Drive) | Your encrypted backups, if you use them (§3.11) |
| Google Play | Your subscription purchase and status |
| Cloudflare | Video and guidance-audio requests: your IP address and which file you asked for |
We do not share your data with anyone else. We do not sell it, and we do not give or license it to advertisers, data brokers, or any other third party for their own purposes.
Google processes the data it receives under its own terms and its own privacy policy, at policies.google.com/privacy. We do not control what Google does with data under those terms, and we do not claim to.
6. Advertising
We do not use your data for advertising. myHab.Fit shows no ads and runs no advertising campaigns using your data.
We also do not collect an advertising identifier — the device-level ID that advertising networks use to recognise you across apps. The permissions that would allow it have been removed from the app, and Google's own collection setting is switched off.
We state this about what we collect and what we do. As above, data that Google receives is governed by Google's own terms.
7. How long we keep it
On your phone, older records are removed automatically, checked daily:
| Data | Kept for |
|---|---|
| Workout history | 372 days |
| Individual set records | 183 days |
| Body-weight log | 3 years |
| Water and fasting logs | 183 days |
| Cycle and symptom logs | 372 days |
| Other apps' cached workouts | 372 days |
| Movement-break logs | 372 days |
| Recovery scores | Approximately the last 60 |
| Camera calibration | The most recent 50 entries |
| Downloaded videos and guidance audio | 15 days after last use |
| All-time personal bests | Kept indefinitely |
In our cloud storage, your account record, agreement history and subscription record are kept for as long as your account exists, and your Drive backup key until you delete it or your account. They are removed when you delete your account (§8). After deletion we keep only a scrambled form of each purchase token and its status, with no link to you, so that a later notice from Google Play about that purchase is still recognised.
Usage statistics. Our Google Analytics property is configured to retain event-level data for 2 months and user-level data and key-event data for 14 months. New activity resets the retention clock for a user's identifier, so user-level data can be kept for longer while that user remains active. Google removes expired data through its monthly deletion process. The copy exported to BigQuery is deleted after 14 months.
These retention settings do not apply to standard aggregated Analytics reports, which can remain available for longer. See Google's data-retention explanation.
Crash reports. Google states that Crashlytics keeps crash reports and associated identifiers for 90 days; see Firebase's retention information.
8. Deleting your account and your data
In the app: open Settings → Subscription & account → Delete account. This removes:
- your Google Drive backup file, if the app has access to your Drive;
- your entire cloud record — account, agreement history, subscription record and Drive backup key (so any backup file that could not be removed can no longer be opened);
- the raw purchase token our server kept (§7);
- your Google sign-in link to this app;
- every piece of personal data stored on that phone, including your cycle logs.
It cannot be undone.
Please read this before you delete — some things are outside our reach:
- Your phone's encrypted backup is replaced at its next run. Android usually runs it within a day. Keep the app installed until then, or remove the app's backup yourself in your phone's backup settings.
- Workouts we wrote into Health Connect stay there. The workouts and calories we recorded into your phone's Health Connect store are yours and remain in it. They may already have been read by other apps. You can remove them yourself in the Health Connect app. We deliberately do not delete them, because they are part of your own health record and other apps may depend on them.
- Your subscription is not cancelled. Deleting your account does not cancel a Google Play subscription, and a subscription you are still paying for cannot be moved to a new account. Cancel it in Google Play.
- Another phone is not wiped remotely. Opening the app on another device does not guarantee that its local data is erased. Uninstall myHab.Fit or clear its storage in Android settings on every other device to remove those local copies. An email deletion request also cannot remotely clear local data on your devices.
- Files you saved with Download my data stay where you saved them. Delete them yourself.
- Usage statistics and crash reports already sent are not recalled. They carry a random per-installation identifier, not your account.
If you have already uninstalled the app, or cannot sign in, use the account deletion request page or email contactus@myhab.fit. We will verify that the request is yours and complete it within one month.
Deleting only some things. You can delete your cycle data alone, and reset your camera calibration alone, from Settings. Other categories can only be removed by deleting the account, or by asking us.
9. Your rights
Under the DPDP Act you have the right to:
- Know what personal data of yours we hold and what we do with it — this policy sets it out, and Download my data gives you a copy; ask us for anything more.
- Correct or complete it. Most of it is editable in the app in Settings; ask us for the rest.
- Have it erased, as in §8.
- Withdraw consent at any time. Turn crash reports and usage statistics off in Settings → Privacy & data; turn off cycle tracking in Settings; revoke camera or Health Connect permission in Android settings; or delete your account to withdraw entirely. Using the app requires the two agreements in §3, so withdrawing those means deleting your account. Withdrawing consent does not undo processing already carried out lawfully.
- Nominate another person to exercise these rights on your behalf if you die or become unable to. Contact us to do so.
- Complain. Write to our Grievance Officer, Seetala Sri Sai Sravanthi, at contactus@myhab.fit. We acknowledge within 48 hours and resolve within one month. If we do not resolve it, you may complain to the Data Protection Board of India.
Exercising any of these rights costs nothing and will never restrict your use of the app, except where the right you exercise necessarily does (deleting your account ends it).
10. Security
Data on your phone is kept in the app's private storage, which Android protects from other apps. Backups are encrypted as described in §3.11. Your cloud records are held in Google Cloud Firestore with access rules that permit only your own signed-in account to read them. Sign-in is handled by Google; we never hold a password. Data in transit is encrypted.
If a data breach affects your personal data, we will inform you and the Data Protection Board of India without delay, and report the details to the Board as the law requires.
No system is perfectly secure, and we do not claim otherwise.
11. Permissions the app asks for
| Permission | What it is for | Optional? |
|---|---|---|
| Health Connect (individually per data type) | Reading your health data, optionally in the background for reminders and Home-screen widgets, and writing your workouts back | Yes |
| Camera | On-device repetition counting | Yes — off by default |
| Physical activity | Counting steps for walks and movement breaks, and timing reminders: Google Play services on your phone tells the app when you have likely woken up and when you are likely in a moving vehicle or on a bike, so reminders wait. What it learns stays on your phone and is never sent to us. | Yes |
| Notifications | Reminders you have asked for | Yes |
| Google Drive (hidden app folder only) | Saving and restoring your encrypted Drive backup, asked only when you start one | Yes |
Every one can be refused or revoked, and the app continues to work without them, with the related features unavailable.
One thing this table does not show. The above is what myHab.Fit itself asks for. An Android app's installed package also lists permissions added by the software libraries it is built with — in our case Google's — which we never ask for and do not use. Google Play shows you that fuller list.
12. This website
This website is a small set of pages describing the app. It has no account, no sign-in, and no analytics or tracking of any kind. It sets no cookies of its own. Our hosting provider, Cloudflare, may set a strictly necessary security cookie.
If you write to us from it, we hold your message and your email address for as long as it takes to answer you.
13. Changes to this policy
If we change this policy we will update the date at the top and, where the change is significant, tell you in the app before it takes effect.
14. Availability in other languages
This policy is published in English. On request we will provide it in any of the languages listed in the Eighth Schedule to the Constitution of India. Write to contactus@myhab.fit.
15. Contact
Grievance Officer — Seetala Sri Sai Sravanthi, Proprietor — contactus@myhab.fit
S-404, Poojitha Estates, Model Colony, Sundernagar, Hyderabad, Telangana, India – 500038