What Fitineary stores, why, who can see it, and how to get rid of it. This one policy covers the Fitineary app and the fitineary.com website.
The short version. Your account is your email address, or your phone number if you sign in with that instead. We also keep a record of how far you got through signing up, and the app tells our own server whether your phone is iOS or Android and which version of the app it runs — and, once your app is updated to the version that sends it, which version of the phone’s system — and, when it registers for notifications, your device’s time zone, so that water reminders, if you turn them on, arrive at your local time. Everything else is what you log — food, training, sleep, mood, weight, photographs — plus, if you choose to connect Apple Health or Health Connect, what your phone and watch recorded, and, if you have a coach, what you send them: messages, photographs and voice messages. It is stored so the app can show it back to you. It is not sold, and it is not used for advertising. A coach sees your diary only while you have connected to one, and only for as long as you stay connected; the messages the two of you sent each other stay with both of you afterwards. You can delete the account, and everything in it, from inside the app; the sign-up record stays, with nothing left on it that says it was yours. If you only joined a list on the website, we hold your email address, the goal or details you gave, and the country you visited from, and nothing else.
Fitineary is operated by 7th Pillar Infotech, which is the Data Fiduciary for your personal data under India’s Digital Personal Data Protection Act, 2023 (the DPDP Act), and the data controller under equivalent laws elsewhere.
| Registered address | 1st Floor, Sree Vilas, Darshan Nagar Rd, near DLF, Kakkanad, Kochi, Kerala 682037, India |
|---|---|
| Company identifier | GSTIN 32AAACZ7635B1ZL |
| Privacy contact | privacy@fitineary.com |
| Grievance Officer | Rashin Pothan — grievance@fitineary.com, +91 98470 32301 |
All of it comes from you. There is no tracking pixel, no advertising identifier and no analytics SDK in the app. We do count how people get through sign-up, with our own server and nothing else: see Sign-up progress below. The same records note whether a challenge card on Today was shown to you and whether you tapped it. Apart from that, nothing measures what you look at, how long you stay or what you tap once you are using the app. There is one third-party SDK, and it reports crashes: when the app fails it sends the programming error and the version of the app and phone it happened on, so that we find out without waiting for somebody to tell us. It carries nothing you logged and nothing that says who you are. It is described in full in section 5.
| Account | Your email address or your phone number, whichever you sign in with, which is the account — there is no password. If you join the feed you also choose a username (your @handle), which people on the feed can see and search for. A display name, language, and your unit preferences (kg/lb, cm/ft). An optional profile photograph. |
|---|---|
| Sign-up progress | The server notes, once each, when a code was requested and entered, each onboarding step reached, onboarding finished and your first log, with the time. The onboarding steps and the first log also carry the app version and whether the phone is iOS or Android; a code being requested or entered carries them once your app is updated to the version that sends them. From that same update, when the app is first opened it creates a random identifier for that installation — generated and kept on the phone, not derived from the phone or from any advertising identifier — and tells our server the app was opened. Until you enter a code, the app being opened is tied only to that identifier. Requesting a code creates an account for the email address or phone number you typed, so from that step on the records are tied to that account, even if you never enter the code; when you do enter it, any earlier record from that installation is attached to the account too. We use these to see where sign-up loses people. On Android, if you installed the app through a link on fitineary.com, that first record also carries what Google Play passes on about the link: the campaign named in it and the random visitor number our website put there (see The visit below), so we can tell which link an installation came from. Once your app is updated to the version that sends it, the server also notes, once for each challenge, the first time a challenge card on Today was on your screen and the first time you tapped it, with the time and whether the phone is iOS or Android; nothing is noted for a challenge you have already joined. These are tied to your account. They are kept for 400 days and are not deleted with the account — see section 6. |
| Last used | Once you have an account, each request the app makes to our server says whether the phone is iOS or Android and which version of the app it is running, and, once your app is updated to the version that sends it, which version of the phone’s operating system. We keep the latest of these against your account, with when you last used the app, so that we know which versions are still in use. It is one record, replaced as it changes rather than added to, and it is deleted with the account. |
| About you | Sex, date of birth, height, your goal and activity level. Used to compute a calorie and protein target and for nothing else. |
| Health & fitness | What you log each day: meals and their portions, water, sleep duration and quality, mood, body weight, exercises, sets, reps and loads, and completed routine sessions. |
| From Apple Health or Health Connect | Only if you connect it, and only what you allow. Steps, active calories, workouts, sleep and weight, read from your phone's health store. Fitineary also writes back to it the water you log, a weight you typed yourself, and each day's food energy and macros. It reads no heart rate. It is stored with your account, and a coach you have connected to sees steps, active calories and workouts from it only while Share with my coach is on. Friends in a friend group see what your watch recorded only if you choose Watch data for that group. See “Your phone’s health store” below. |
| Photographs, video & voice messages | Meal photographs you take or pick, a photograph you add to a workout you logged (it is not sent for analysis; it appears on the picture you choose to share, and a coach sees it only if you let them see your training), a profile picture, demonstration videos a coach attaches to an exercise, and anything you attach to a message in a coach conversation — a photograph, or a voice message you record there. A meal photograph is sent for analysis when you log a meal from a picture, whether you take it or pick one you already had — see “Reading a meal photograph” below. An attachment sent to a coach is not sent for analysis and goes to no AI service at all; it is stored so the two of you can open it, and nothing else — see “Sending a photograph or a voice message to your coach” below. |
| What you describe | If you tell Tinni what you did, or ask her something, instead of filling in a form, the words you typed — or, if you spoke, a recording of what you said — are sent to our server to be read. A recording is turned into words there and is not kept; the words become your message in your conversation with Tinni, kept with your other messages and deleted with your account. Recording starts only when you start it and stops when you stop it — two deliberate actions, one at each end, with nothing captured before the first or after the second, and thirty seconds is the cap whatever you do. The microphone is used in two other places — a voice message you record in a coach conversation, and the sound on a demonstration video if you are a coach filming one — and nowhere else: there is no listening in the background and no wake word. If you describe food, its calorie figure comes back in the same answer. In older versions of the app the food’s name is sent a second time to be given a calorie figure, without being asked for. See “Describing a log in words” below. |
| Coaching | If you connect to a coach: the connection itself, what they coach, the routines they assign you, and the messages between you — including any photograph or voice message either of you attaches to one. If you are a coach, your own coaching profile: your bio, what you coach, your certifications and a phone number, if you choose to publish one — leaving it blank is a complete answer, and the field says at the point of entry that your clients can see it and call you. |
| Tinni’s notes | Tinni, the AI coach in the app, keeps short notes of what you tell her about yourself — that you are vegetarian, say, or training for a 10k — so she does not have to ask again. A note comes only from something you said to her, never from your diary; each is under 200 characters, and she keeps at most 40. When she makes one, it shows under her reply with an Undo. You can see every note and delete it, or all of them at once, in Tinni’s settings. They are in the copy of your data we send when you ask for one (section 7), and are deleted with your account. Coaches cannot see them, and the switches that decide what of your diary Tinni reads do not hide them from her. |
| Device | A push token, and only if you allow notifications. When you sign in, your phone's notification service issues an address for this app on this device; we store that address and whether the device is iOS or Android, so a message from your coach can reach your lock screen. Refuse the permission and nothing is stored. With that address we also store your device’s time zone, so that water reminders, if you turn them on, arrive at your local times, and whether this device has handed its water reminders to our server. The server sends them only once the feature is on for your phone. Signing out deletes all of it. It is not an advertising ID and it identifies no one but this installation. Delivering a notification necessarily hands that address to the push service that issued it — see “Where it lives” below. |
| Subscription | Only if you subscribe. Which plan you are on, whether it is a trial, when it started and when it renews or ends, whether it will renew, and the payment provider’s own reference for your subscription. We never see or store your card number or bank details — you enter those on the payment provider’s page, not ours. See “Paying for a subscription” below. |
| Challenges | Only if you join one. That you joined, when, from which kind of phone, and the boxes you ticked to join (that you are 18 or over, live in India, have read the official rules and, for a gym challenge, are a member there), each recorded with the exact wording you agreed to. A challenge is scored from the diary you already keep, including what you bring in from Apple Health or Health Connect: we keep each day’s result — whether it counted, its points and why — and, to make the scoring fair, when each diary entry reached our server, how a meal was logged (photo, Tinni, search, typed), and whether a workout was recorded by a device or typed in. When you join, the app sends the random identifier of this installation (described under Sign-up progress), so that several accounts entering one challenge from one phone can be reviewed; it is never a hardware or advertising identifier. A nickname, if you choose to appear on the leaderboard, and a separate record if you also choose to appear on the public leaderboard on the website, with the exact wording you agreed to. From prize winners only, when they claim: legal name, UPI ID, PAN where tax law requires it for the amount, and for a gym prize a photograph of the membership card. These are stored encrypted and used only to check and send the prize. Entering a challenge needs a verified mobile number, which is already part of your account (one entry per number). If you leave a challenge, the app first asks why: the reasons you tick and anything you choose to write are kept with your entry, seen only by Fitineary staff, and used to make challenges better. |
We do not collect location, contacts, your device's advertising ID, browsing activity or performance telemetry. The only data we take from another app is what you choose to bring in from Apple Health or Health Connect, described above.
The one exception is a crash, and it is an exception rather than a qualification: when the app fails it sends a report of that failure, carrying the programming error, the version of the app and the model and operating-system version of the phone — and nothing that identifies you or anything you logged. The crash service is sent nothing while the app is working. What the app does send our own server while it is working is described above: how far you have got through sign-up, and the platform and versions you last used. Section 5 says exactly what a crash report holds.
On the website. fitineary.com collects only what you type into its two forms, plus three things about the visit:
| Early access list | Your email address, the goal you chose (“lose weight”, “build muscle” or “general fitness” — a broad interest, not a health record), your confirmation that you are 18 or over, and a record of your consent: which boxes you ticked, when, and the version of this policy in force at that moment. We keep that record because the law requires us to be able to show consent was given. |
|---|---|
| Coach list | Your name, email address and the professional details you enter: what you coach, roughly how many clients you have, years coaching and any certifications you list. |
| The visit | The country your request came from, which our hosting provider derives from your IP address — we store the country, not the address — your browser’s user-agent string, and the page that referred you. Analytics events only if you consent; see section 11. Separately, our own server counts each page you open on fitineary.com and the challenge pages, and when you tap through to the App Store or Google Play: the page, the time, whether the phone is Android or iOS, the kind of browser (for example Chrome, or Instagram’s built-in one), the campaign named in the link if there is one (and whether the link came from a Meta ad, never the ad’s click reference itself), and a random visitor number kept in one first-party cookie so that the same browser is counted once. To tell real visits from automated ones, it also notes the network the visit came through (for example your mobile operator, or a cloud provider), and the country and city our hosting provider places it in. Not your IP address, and nothing about you. The visitor number goes into the Google Play link too, which is how an Android installation is tied to the visit above. These counts are kept for 400 days and are shared with no one. |
Leads from our ads. If you fill in a Fitineary form on Facebook or Instagram, Meta shares with us your phone number, your name or email if the form asked, and your answers. We use them to see whether you joined Fitineary and to contact you about what you asked for. Write to privacy@fitineary.com to have them deleted; we will not import them again.
The website asks for no health information, no phone number, no postal address and no payment details. The challenge pages at challenges.fitineary.com are a different thing: the pages you act on are part of the app, signed in with your Fitineary account, and what they hold is the Challenges row above. A challenge’s public page and its public leaderboard can be read by anyone, signed in or not; what they show is described in section 4. The calculator on its front page runs entirely in your browser; the numbers you type into it never leave your device.
We do not profile you, sell data, share it with advertisers, or use it to train a model.
The legal basis is your consent, given when you create an account or join a list, for everything above; and legitimate use — keeping the service secure and working — for the country, user agent and referrer the website records. You can withdraw consent at any time; see section 8.
You can. Nobody else, with eight exceptions you create yourself:
Access is enforced by the database itself, per row, rather than by the app asking politely — a request for data you may not see returns nothing, not a filtered version.
Our own staff use an admin panel that lists accounts with how far each got through sign-up, the platform and versions it last used and when, and its email address and phone number masked, with most of the characters hidden. The sign-up progress and last-used record are not shown to you in the app; that panel is where they are read. A limited set of staff can reveal a contact. For a challenge, staff also see each entry’s scored days and the checks raised on it (for example, several accounts joining from one phone) so that a result can be confirmed before a prize is paid. When somebody reports a post or a comment, staff see it, who wrote it and why it was reported, and may keep it, remove it (the author is told why) or pause the author’s posting; reports are reviewed within a day. Every action taken in the panel, a reveal included, is written to a staff access log — see section 6.
Records are held in a managed PostgreSQL database run by Supabase in Mumbai, India; photographs, video and the voice messages you send a coach are held as objects in Cloudflare R2, in its Asia-Pacific region. Both are held under 7th Pillar Infotech’s own accounts, and both are encrypted in transit (HTTPS/TLS) and at rest by the provider. An image, a video or a voice message is reached only through a short-lived signed link that is issued after your permission to see it has already been checked — the storage layer never decides who you are.
Six things leave this system by design. All six are described here in full; nothing else about you goes anywhere. Your phone’s health store, described after them, is the other direction: it puts data into this system, and what Fitineary writes back to it stays in your phone’s health store.
A sign-in code. To sign you in we send a one-time code. If you sign in with your email address, the address and the code go to Resend, an email delivery service, which sends the email. If you sign in with your phone number, the number, the code and your display name, if you have set one, go to AiSensy, which delivers the code as a WhatsApp message through Meta’s WhatsApp Business platform. Nothing else about you is included, and the code stops working once it is used, or an hour after it was sent at the latest.
Paying for a subscription. Nobody has to pay to use Fitineary; a subscription is an option. On Android the payment page is run by Dodo Payments, which sells the subscription to you as the merchant of record: you enter your payment details, your email address and your billing address on Dodo’s page, and Dodo handles them under its own privacy policy. We send Dodo only which plan you chose and a random identifier for your account, and Dodo tells us whether the payment succeeded, when the plan renews, and whether it was cancelled. On iPhone you pay Apple through the App Store, and RevenueCat checks the purchase with Apple for us; we give RevenueCat the same random account identifier, never your email address or phone number. Either way, your card number never reaches us, and neither provider is sent anything you logged.
Notifications. To put a message on your lock screen we pass your device's push token, and the notification's own wording, to Expo's push service and from there to Google’s Firebase Cloud Messaging on Android or Apple’s push service on iOS. The message body is written by our server, not copied from the conversation — a coach’s notification says that they sent you a message, and never what it said. If you turn on water reminders and the feature is on for your phone, our server uses your water log, your water target and your device’s time zone to decide when to remind you and what the reminder says, and sends it to your device through Expo’s push service; the wording of a water reminder can therefore reflect how much you have had that day. Nothing else about you is included.
The app asks first. The first time you use any feature below that needs an AI service — reading a photo or a recording, estimating a food, talking to Tinni, or making a plan for you — the app tells you what will be sent and to whom, and asks for your permission. Nothing is sent to an AI service until you allow it, and if you choose Not now nothing is sent and you can log by search and by hand instead. Your answer is kept with your account. You can turn it off at any time in Tinni’s settings, and the app then asks again before it next sends anything. The one exception is the check before posting: posting to the feed, commenting, or setting a profile photograph always sends those words and pictures to Google’s Gemini to be checked, because nothing is shown to your friends unchecked. It is not used for anything else. Older versions of the app, which do not show this question, do not ask: they send what is described below when you use these features, and we stop writing Tinni’s reviews for you until an updated app has asked. The AI services are Google’s Gemini, reached directly or through OpenRouter, a service that routes a request to an AI model; and, only when Google’s service is unavailable, Anthropic’s Claude, reached through OpenRouter.
Making a plan for you. When you ask the app to Make one for me, our server sends a request through OpenRouter to Google’s Gemini, under the same instruction not to retain it. For a workout routine it sends your answers (goal, level, equipment, days a week, session length, the areas to focus on or go easy on, and anything you type in the note about an injury or a limit), your sex, your age in years (worked out from your date of birth; the date itself is not sent), your height, your latest weight, and the names of the exercises it may choose from. For a diet plan it sends your answers (goal, style, cuisine, meals, the foods to avoid and anything you type in that note), your daily calorie and nutrient targets, the foods it may choose from, and which of them you logged in the last sixty days; no age, sex, height or weight. Neither includes your name, phone number, email address or anything else that identifies you. What comes back is a draft, and nothing is saved until you save it.
Reading a meal photograph. When you log a meal from a picture — taken now, or chosen from your photos — that picture is sent through OpenRouter to Google’s Gemini to be read, and what comes back is a guess at what is on the plate and how much of it — a list of foods and gram estimates, which you then correct before anything is saved. The request is routed through our own server, which passes on the picture and a fixed instruction to read it — and nothing else. Not your name, not your email address, not your diary, not your targets, and nothing that identifies you or the account. If you then ask for a different food match, the food’s name and the portion in grams are sent the same way; still nothing about you. Our server instructs OpenRouter not to retain what it is sent — it will only route the request to providers that do not store it — and it is used to answer your request and for no other purpose. The same instruction is set when a recording is turned into words. A message to Tinni is the one exception, and it is described below. Nothing you photograph, type or say is used to train an AI model that answers anybody’s questions, ours included.
You are never obliged to use it. Search for a food and enter the portion instead and no photograph leaves your phone at all. And the estimate is an estimate: it arrives with a match score precisely because it can be wrong, and every gram stays editable before you save it.
Describing a log in words. Instead of filling in a form you can tell Tinni, in her chat, what you did: type it, or say it. The microphone opens a screen that records nothing until you start it, and stops the moment you stop it. Either way what you wrote, or a recording of what you said, goes to our own server. A recording is sent from there to the same AI service to be turned into words, and those words become your message. Our server then sends your message to Google’s Gemini API with what Tinni needs to answer it, and only that: the recent messages in your conversation with her, her notes about you, only the parts of your diary you have switched on for her in Tinni’s settings, and names from your food and exercise library. Not your name, not your email address, and nothing that identifies you or the account. Google keeps what it is sent for up to 55 days, only to detect misuse of its service. It does not use it to train its models, other than the ones that detect that misuse, and it does nothing else with it. If Google’s service is unavailable, the same request goes through OpenRouter, under the same instruction not to retain it, to another Gemini model or to Anthropic’s Claude.
Tinni’s reviews. Once a day or once a week, as you choose in her settings (or never), Tinni writes a short review of your diary into her chat. To write it, our server sends Google’s Gemini the figures for that period from only the parts of your diary you have switched on for her — in the same way, and with the same nothing-that-identifies-you, as a message to her. A review is written only while you have allowed AI services in the app; turn them off and the reviews stop.
What comes back is a card of what was understood, one row per thing, and every row says what it would write before it writes anything. The rows are not tappable. Save on a row writes that row into your diary there and then; Adjust opens the ordinary screen for that kind of log, already filled in, for when you want to change something first. A row you did not mean can be removed, and closing the card without saving puts nothing in your diary. A food or exercise that is not in your library yet is added to it when you save its row, and not before. The rows you have not saved yet are kept on your phone, and only there, so that going back or closing the app does not lose them; they are deleted when you save or discard them, when you sign out, or a day after you last changed them.
A food row’s calorie figure comes in the same answer. Food is the one thing you can describe with no number in it, so a food row arrives with a calorie and macro figure already worked out, from your library or estimated by the AI service, and an estimate says so. Nothing is sent a second time for it. Older versions of the app send it a second time, and nobody asks you first: there, when a food row appears, the food’s name — and only the name — goes back to the same service under a second fixed instruction: give this a calorie and macro figure. That happens once per food row, without being requested, because the figure is what the row has to show you before Save can mean anything. It travels the same way as everything else here, with nothing about you attached, and it is what Save writes.
A recording made to describe a log is never kept on our servers. On your phone the file is temporary, and lives only for as long as it takes to read it. There is no step in between: stopping the recording is what sends it, and Fitineary deletes the file as soon as it has been read, before it is sent. It is also deleted if you cancel, or leave the screen while a recording is still running, and a recording shorter than a second or with nothing louder than silence in it is deleted and sent nowhere. Our server passes the recording on to be turned into words and does not store it. There are two cases we cannot cover for you: force-quitting the app while a recording is in progress or waiting to be read, and an operating system that refuses the deletion — Fitineary asks it to delete the file and cannot compel it. In either case the temporary file is the operating system’s to clear, and we have no way to know it is still there. No copy of the sound is stored in your account and it is not attached to anything you log. What is kept is the words it was heard as: they are your message in your conversation with Tinni, kept with your other messages and deleted with your account.
The sound outlives the file by a little, in the app’s memory and nowhere else. The file has to be read before it can be sent, and what was read is kept in the app’s memory while Tinni’s chat stays open — so that if the reading fails, trying again does not mean saying the whole thing over. It is never written back to storage, never uploaded a second time on its own, and never attached to your account. It goes when you send your next message, typed or spoken, when Tinni answers, or when it is refused in a way that trying again cannot fix, and it goes when you close the chat. Recording never starts on its own. It begins when you start it and ends when you stop it, and it is always capped at thirty seconds.
What we do keep, for this and for a meal photograph alike, is a short record of what the model understood, and for a recording the words it was heard as — kept with your account so we can see how often it reads people correctly, deleted with the account, and not used to train anyone’s model. For a photograph we also record whether you corrected the reading. For a description we do not: what you do with the card afterwards is not written back against the record, and it is stored saying exactly that.
You are never obliged to use this either. Every screen it can take you to is one you can reach by tapping, and refusing the microphone leaves everything except this, a voice message to a coach, and the sound on a demonstration video exactly as it was — the app says so plainly and offers you the typed box instead.
Sending a photograph or a voice message to your coach. This one is here for the opposite reason to the ones above: nothing about it leaves our system, and what makes it worth its own section is that it is kept. Attach a photograph to a message, or record a voice message in the conversation, and the file is stored the way a meal photograph's bytes are stored — a row in the database and an object in Cloudflare R2, reachable only through a short-lived signed link issued after your permission to see it has been checked. It is not sent to the AI service, or to anyone else. Nothing is read out of it, nothing is guessed from it, and it is not used to train anything. It is stored so that you and your coach can open it, and for nothing else.
Nothing is recorded until you deliberately start a recording, and nothing leaves your phone until you press Send: a recording waits in the conversation where you can play it back and throw it away, and a photograph you have attached can be removed before you send it. Once you do send it, Fitineary deletes the temporary recording from your phone; the copy that remains is the stored one. A sent message cannot be taken back — there is no delete for a single message, on either side, and saying otherwise would be describing a control that does not exist. It goes when the account goes.
A crash report. When the app fails — a screen that stops drawing, or the whole app closing on its own — a report of that failure is sent to Firebase Crashlytics, Google's crash-reporting service. It contains the programming error and the line of our own code it happened on, the version of Fitineary you are running, the model and operating-system version of the phone, and whether the app was in the foreground. It is sent because a crash you do not report is a crash we never learn about, and until this existed the only way we heard about one was somebody describing the screen to us.
What a crash report does not contain, and this is enforced in the code rather than promised here. No email address, no phone number, no name and no account identifier — the report is not tied to you, and we could not look up who sent one. Nothing you logged: no meal, no photograph, no weight, no message to a coach. Nothing you typed or said. The service records no list of what you tapped, and Fitineary writes no notes of its own into a report, which is what keeps that true. This is crash reporting and not analytics: nothing is sent to it while the app is working, Google Analytics for Firebase is switched off and is not even installed, and the crash service collects no measurement of your use of the app. The sign-up progress and the last-used record described in section 2 go only to our own server.
One identifier does exist, and it is not you. Crashlytics gives each installation a random identifier of its own so that two crashes from the same phone can be seen as the same phone. It is generated on the device, it is not the advertising identifier, it is not your account, and uninstalling the app ends it. We never send anything alongside it that would say whose phone it is.
Your phone’s health store. This one is here because it is the other way round: nothing about it leaves our system, but it brings data in. If you connect Apple Health on an iPhone or Health Connect on Android, Fitineary asks your phone for permission to read your steps, active calories, workouts, sleep and weight, and to write back the water you log, a weight you typed yourself, and each day’s food energy and macros. It does not read heart rate. A run, walk, ride or swim brings its distance with it. You choose what to allow on your phone’s own permission screen and can change it there at any time. Nothing is read until you connect, and it is read while the app is open, not in the background.
What is read is stored with your account in the same database as the rest of it (Mumbai, section 5), and it goes when the account goes. It is never sent to the AI service, and never used for advertising. A coach you have connected to sees your steps, active calories and workouts from your watch only while Share with my coach is on, which it is until you turn it off; with it off they see none of those. Sleep and weight are the exception: they are part of your daily diary row, which a coach you are connected to already sees when you type them. Friends in a friend group see none of it — not the workouts, sleep or weight your watch recorded — unless you choose Watch data for that group, and then only within the categories you share with it. If you type a sleep or weight yourself, your value is kept and an import never replaces it, and a workout you edit or delete stays as you left it. A workout you delete from your phone’s health store, and never edited here, is removed from Fitineary at the next sync. The connection is remembered for your account on that phone; another account on the same phone starts disconnected.
The website’s lists. The website is hosted by Cloudflare, which also stores what you submit to either list. A working copy of the lists is kept in Google Sheets: your email, goal and consent record, or a coach’s details. If you tick the analytics box on the sign-up form, PostHog receives analytics events about your visit; the website never sends it your email address, and without that tick it receives nothing. These three process data on our instructions only.
Leaving India. Your account and everything you log are stored in India. Some of the providers named in this section operate outside India, including in the United States, so what this section says each of them receives is transferred and processed outside India. The DPDP Act permits such transfers except to countries the Central Government restricts, and we use providers that make contractual data-protection commitments. We may also disclose personal data where the law requires us to, or to establish or defend a legal claim.
Until you delete it. Individual entries go when you delete them. The whole account goes when you delete the account — see below — and that removes your profile, your logs, your photographs, your messages, your coaching connections, your posts, comments, cheers and friends, and the record of the app you last used. A post you delete goes from every feed at once; a post staff remove after a report is kept, hidden, with the reports about it, until the account is deleted, so a repeated problem can be recognised. Sign-up progress records (section 2) are not deleted with the account: each one that named it loses the account and the installation identifier and is given a new random label of its own, so it no longer says whose it was. What it keeps is the step, the time, and the platform and app version where it has them, which is what lets us count, and it is deleted 400 days after it was made.
The staff access log also outlives the account. When a member of our staff uses the admin panel, it records who did it, what they did, what they searched for — which can be a name, email address or phone number they typed — and which account it concerned. It is kept so that staff access to accounts can be checked, and the database is set up to refuse edits to and deletions of its entries. Beyond the sign-up progress records above, we keep no copy of an account for analytics.
When a coaching relationship ends, the routines that coach assigned you leave your library along with their access — they belong to the coach, who keeps them. Reconnecting is not an undo; they assign again. What stays is anything you built yourself.
A disconnected conversation keeps its words and loses its attachments, and that is a decision rather than a side-effect. The messages you exchanged stay readable to both of you. The photographs and voice messages do not: from the moment the connection ends, each of you can still open what you sent yourself, and neither of you can open what the other sent. Nothing is deleted — the files are still there, and reconnecting makes them open again — but while you are disconnected they are simply not yours to see, for the same reason the rest of the diary is not. The app says so on the bubble rather than showing a broken picture.
Challenges. Deleting the account removes your consents, your scored days, your nickname and your place on every leaderboard, and anything you wrote about why you left a challenge; the reasons you ticked stay, with nothing that names you. A result already published keeps its place and amount with nothing that names you, so the other places stay correct. Until that challenge’s results close, a one-way fingerprint of your mobile number is kept, linked to no account, so the same number cannot enter the same challenge twice; it is then deleted. A prize claim’s name, UPI ID and PAN are kept, encrypted, for the period tax law requires after the prize was paid, then erased; if you delete the account after being paid, the UPI ID is erased at once and the name and PAN stay only for that period, because the tax return names the person paid. A claim that was never paid is erased 90 days after it closed. A membership photograph is deleted as soon as the claim is checked.
The website’s lists are kept until twelve months after the app’s launch in August 2026, or until you ask us to erase your entry, whichever comes first; after that an entry is deleted without you having to ask. A consent record is kept for as long as the entry it belongs to, plus the period in which a claim could be brought.
Under the DPDP Act you have the right to:
Write to privacy@fitineary.com and we will answer within 30 days; we may ask you to confirm the request comes from the email address or phone number we hold. If you are unhappy with how we have handled your data, contact our Grievance Officer (section 1) first. If you are not satisfied with the answer, you have the right to complain to the Data Protection Board of India.
Fitineary is not for anyone under 18. The website asks you to confirm your age before you join a list. We do not knowingly collect personal data from a child, we do not track children, and we do not serve them behavioural advertising. If you believe a child has created an account or joined a list, email privacy@fitineary.com and we will delete it.
Data is encrypted in transit and at rest. In the app, the database’s own rules decide who can read what (section 4). Our staff see accounts only through an admin panel that named staff alone can sign in to, and every action in it is written to the staff access log (sections 4 and 6). Access to the website’s lists is restricted to the people who need it. No system is perfectly secure, and we do not claim otherwise; if a breach affects your personal data we will tell you and the Data Protection Board, as the DPDP Act requires.
Neither the app nor the website sets an advertising cookie or a third-party tracking cookie.
The website sets one first-party cookie, fx_vid: a random number, kept for a year,
used only so that our own count of pages opened and taps through to a store (section 2,
The visit) counts a browser once. It holds nothing about you and is never shared. Our own
staff’s browsers carry one more, fx_team, set only when they sign in to our admin
panel, so that our own visits are not counted. Apart from these, the analytics tool on the website loads switched off, keeps anything it holds in memory only,
sets no cookie and no lasting identifier, and records nothing — not even a page view
— unless you tick the consent box on a sign-up form. If you consent and later change your
mind, tell us and we will delete the events.
If this policy changes, the date at the top changes. If a change materially affects what we collect or who receives it, we also say so in the app’s release notes on the App Store and Google Play, and email the people it affects; where the law requires it, we ask for your consent again. We will not quietly widen what is collected.
15 October 2026: we added the sign-up progress and the last-used record described in section 2, and rewrote the sentences that said nothing of the kind was counted. It is collected by our own server only, and nothing is sold or shared with advertisers.
Questions, corrections, or a data request: privacy@fitineary.com. We answer data requests within 30 days. Complaints go to the Grievance Officer named in section 1.