FitRealm Back to site

FitRealm Privacy Policy

Version: 1.0.0 Effective: 29 September 2026

The short version

FitRealm is a fitness app. You log workouts, food, sleep, weight and steps; you earn XP and streaks; and you can follow other athletes, chat, and join gyms, communities and events.

  • We do not sell your data, and nothing you log is ever used to target an ad. Your workouts, food, weight, sleep, steps, photos and messages are never shared with an advertiser. That line does not move.
  • Ads and Pro arrive after launch, and this policy already covers them. The app you install on 29 September 2026 shows no ads and sells nothing; both land in an update in the weeks that follow. From that update the free app shows ads, served by Google using your device's advertising ID — a resettable number that carries no name and no FitRealm account — and never using your fitness data. In Europe we ask your permission before any personalised ad. A Pro subscription removes ads entirely. Everything this policy says about advertising, subscriptions and the companies behind them describes how it works from that point on. See section 2.
  • There is still no product-analytics or behaviour-tracking SDK in the app. Nothing watches what you tap and reports it back. Apart from ads, the third-party code that reports back sends technical data about itself, not what you were doing: the crash reporter tells us how the app broke and whether a session ended in a crash, Google Play's integrity check tells Google about the app, your phone and your Play account so it can confirm this is the genuine FitRealm, and Google's barcode scanner tells Google how the scanner ran — never the camera image or the barcode. See section 5.
  • Your data never leaves for a model. Nothing you log is sent to any machine-learning or generative service, by us or anyone else. Your plans, progression and insights are produced by ordinary algorithms running on our own servers.
  • We ask for your clear yes before we use your health data. Your weight, body measurements, sleep, steps and the food you log are health data under EU law, so before you start we ask for your explicit consent, in its own box that starts empty. FitRealm cannot build your plan without them, so this one is needed to use the app. See section 3.
  • We ask before we store anything about an injury. It is a separate question with its own box, and the box starts empty. Say no and we store none. Your plan is still built — it just cannot leave out the movements that hurt you. You can change your mind at any time.
  • We never store your exact location. Location sharing is off unless you turn it on, and even then our server rounds your position to a roughly 2 km grid before saving it. Your precise coordinates are never written down.
  • You can download your data, or delete your account outright, from Settings, then Account & security. Deletion is immediate and permanent.
  • Health data stays health data. We only ever read your step count from Health Connect — nothing else.

1. Who we are

FitRealm is operated by Ashish Shirish Vayangankar, trading as Vayash Studio, Julius-Leber-Strasse 1a, 67551 Worms-Pfeddersheim, Germany ("we", "us"). For anything in this policy, contact privacy@fit-realm.app.

2. What we collect

We only collect what you give us or what the app needs to work. Nothing here is bought from third parties or inferred from your behaviour outside FitRealm.

Account and profile

Your email address and password (or your Google account, if you sign in with Google); display name, handle, bio, specialty, profile photo, avatar and cosmetic choices; your chosen gym; and the version of these documents you accepted, with the time of acceptance.

Body and training inputs

Sex, age, height, current and target weight; experience level, training style, available equipment, priority muscles, cardio and ab-training preferences, session length, exercises per day and rest days. If you change the sets, reps or rest your plan recommends, or choose how many of your cardio-plan days are lifting days, or tell us which cardio machines you can reach, we store those choices too. We also store your daily calorie and macro targets, and the resting metabolic rate they are worked out from — including your own figure, if you replace our estimate with it. These drive your plan — they are inputs to an algorithm, not a medical record.

Injuries and movement cautions

Only if you say yes. Injuries are data about your health, so we treat them separately from everything above. Before the app asks you anything about an injury, it asks whether you want to share injuries at all. That question has its own box, it is not part of accepting these documents, and it is never ticked for you.

Say no and we do not ask, and we store nothing about an injury. Your plan is built exactly the same way. The one thing it cannot do is leave out the movement patterns that commonly aggravate a problem you have.

Say yes and we store the cautions you pick from our list — such as lower back, knees, shoulders or wrists. We use them for one thing: keeping those movement patterns out of the plan we build for you. They are never shown to another athlete, and they are never used for advertising.

We also keep a record of the answer itself: whether you said yes or no, when you answered, and which version of these documents you answered against. It is how we can show what you chose. We keep one for a no just as we do for a yes, and the record contains no injury.

You can change your answer at any time in Settings, then Training profile. Turning it off deletes every injury we hold for you when you save.

Reminder and workout settings

Your reminder settings (whether reminders are on, which kinds you get, and your quiet hours) and your workout settings (whether rest timers are on, which way your working sets ramp, and what the weight you enter means for any exercise you told us about) are stored with your account, so they follow you to a new phone. Your phone keeps its own copy as well, so they keep working without signal.

Body measurements

Any measurements you enter yourself (weight, circumferences, body fat percentage or muscle mass in kilograms). We never estimate or infer body composition — if you did not type it in, we do not have it.

Progress photos

Photos you choose to add as progress photos, and the date you give each one. They are private: stored where only your own account can read them, never shown on a profile, feed, leaderboard or post, and used for nothing except showing them back to you. Adding them is a Pro feature; if a subscription ends you keep what you added, and can still view and delete it.

Workouts and progress

Workout plans and sessions, exercises, sets, reps and weights, session duration, cardio sessions, personal records and rep-max records, planned rest days, any weekly splits you save and the names you give them, any workout templates you save for a day, and the exercises you star as favourites.

For a cardio session you time in the app, we also store when you started it and how many steps your phone counted while it ran. When you start the timer, our server also records the time by its own clock. That record decides how many of the session's minutes can earn XP. That step figure is only used to stop the same walking being counted twice in your burn for the day. Sessions you type in yourself have neither, because there is no timed window to record.

Food, water and sleep

Food entries (name, amount and its unit, calories, protein, carbs, fats, fibre, notes), meals you save to log again, water intake, and sleep logs.

Steps and physical activity

Step counts from your phone's motion sensor and, if you allow it, from Health Connect. From Health Connect we ask only to read your steps — including while FitRealm is in the background, where your phone supports that, so your step count stays up to date while the app is closed. No heart rate, no weight, no sleep, nothing else. You can switch Health Connect off at any time in Settings: FitRealm then stops reading it and stops using the totals it already read, and counts your steps with your phone's sensor only. When your phone's sensor and Health Connect have both counted a day, FitRealm shows its own count, because that is the one it can take a bike ride or a drive off. Health Connect fills in a day your phone did not count, and the start of the first day, before FitRealm began counting. To remove FitRealm's access completely, use the link beside that switch, which opens Health Connect.

FitRealm also asks Android what kind of movement your phone is doing, so it can tell cycling and travelling in a vehicle apart from walking. Your phone's step sensor counts a pedal stroke as a step, so a bike ride adds steps you never took. Android tells FitRealm when a ride or a drive starts and stops, and FitRealm can take the steps counted during a measured ride back off your day. Windows shorter than one minute or with 30 or fewer steps per minute leave your count unchanged. Android works this out on your phone. FitRealm receives only the kind of movement and the time it started and stopped — never where you were, never a route, and nothing about the journey itself. Those start and stop times, step-counter readings, and detector registration times and failures are stored on your phone, not sent to us, and the Steps screen shows you what was taken off.

Once you allow Physical activity (see section 6), and unless you switch it off, FitRealm counts your steps continuously — while the app is closed, and again after you restart your phone. Android requires an ongoing notification whenever an app does this, so FitRealm posts one showing your step count for the day. It has its own notification category, separate from workout sessions, so you can hide it in your phone's notification settings without losing the others — steps keep counting either way. You can turn background counting off in Settings, and steps are then only counted while the app is open. The step count is read from your phone's sensor on your device and stored with your account; it is not shared with anyone.

Gamification

XP events (including XP held over to a later day when you pass the daily XP limit), level, streak state, quest progress, which progress celebrations you have already been shown, cosmetics you own, and your position on leaderboards.

Subscription status

From the update that introduces Pro — there is nothing to buy at launch.

Whether your account has an active Pro subscription, which plan it is and when the current period ends. This comes from Google Play when you subscribe, and it is what unlocks the paid features. We never receive your card, bank or payment details — Google takes the payment and keeps that side of it entirely.

Social

Posts, captions, photos, comments, likes; who you follow and who follows you; follow requests you send and receive; direct messages; communities and events you create, join or are invited to; and in-app notifications.

To enforce the weekly limit on new follows, we also record which athletes you started following and when. Each of those records is deleted within nine days.

Location — opt-in and deliberately coarse

  • Presence sharing is off by default. When you turn it on, your phone sends its position and our server immediately rounds it to a roughly 2 km grid before storing it. The exact coordinates are discarded and never written to our database. While sharing stays on, opening Socials can send it again, rounded the same way: the first time after the app starts or you sign in, and after that only when you have moved into a different square of that grid or at least 15 minutes have passed since the last send. You can turn it off at any time.
  • Gym search uses your device location to find gyms near you; the search position is used for the lookup and not stored as your location.
  • Events near you works the same way. Your phone rounds its position to about 11 km before sending it, and the server uses that only to sort the list by distance. It is not stored.
  • Event check-in sends your phone's position once, when you check in to an event you joined. Our server checks that you are within 250 metres of the venue, and that reaching it from the venue of your previous check-in would not have meant travelling faster than 1,000 km/h. The position itself is never written to our database: we keep only that you checked in, and when.
  • Maps in the app are drawn using tiles from OpenFreeMap (see section 5).

Safety and moderation

Accounts you block, and reports you file (what was reported, the reason and any details you write). Reports filed about you are kept for safety purposes, and so are reports you file — a report has to outlast the moment to be read and acted on. Section 7 explains what happens to both if you delete your account. A report is recorded against whoever created what was reported, so a report about a post you shared, a community you created or an event you host counts as one filed about you.

Moderation records. If a community owner or moderator removes you or one of your posts, we keep which community it was, the date, the rule that was broken, and which moderator did it. The app shows you the community, the date and the rule, and those are in your data download. Which moderator acted is kept for our own records and is not shown to you.

Decisions we take about your account. When FitRealm acts on a report, by removing something you posted or by suspending your account, we record what was decided, when, and the rule behind it, along with a private working note. What was decided and when are in your data download. The working note is not. A suspension stops you signing in for the time we set; nothing in your account is deleted. We tell you which rule was broken and how to ask for a second look.

If you create an event, we also record that you ticked the in-person safety terms, which version you ticked and when. We keep that because hosting an event is the one thing in FitRealm that puts people in the same physical place, and we need to be able to show that the person who arranged it was told what that means.

Feedback and suggestions

If you report a problem or suggest a missing exercise, we store what you wrote, and for a problem report the app version and platform you were on. A problem report can carry up to five screenshots you choose to attach.

If you report a gym that is missing from the map, we store the name you typed, any note you added, and the point you chose for the gym — a pin you dropped on the map or an address you picked — not where you are. Reports are checked by hand before anything appears on the map, and only you and FitRealm's developer can see one. If we confirm the gym exists we may add it to OpenStreetMap, the public map database FitRealm uses; the gym's name and location become public there, but nothing about you does.

If you report that a place on the map isn't a gym, we store which place, the reason you picked and any note you added. Only you and FitRealm's developer can see the report, and nothing is removed from the map until we have checked it.

If you add a packaged product we do not have, we store the barcode, the product name and brand you typed, the nutrition values you read off the label, and three photos you take: the nutrition label, the barcode, and the product itself. You type the numbers; nothing in FitRealm reads them off your photo. The photos are there so a person can check what you typed before the product is added, and that person is FitRealm's developer. Until it is checked, the product is visible to you and to nobody else. Once it is added, the product, its brand and its nutrition values become part of FitRealm's food library for everyone — your name is not attached to it, and the photos are never shown to anyone.

A product we have already added stays in the library if you later delete your account. By then it describes a packaged food, not you, and nothing in it points back to you. The three photos you took are deleted with your account, and so is a product that was still waiting to be checked.

Screenshots are held in private storage. There is no public link to them anywhere, only you and FitRealm's developer can open them, and they are never shown to other users or used for anything except working out what went wrong. A screenshot captures whatever else was on your screen at the time, so attach one only when you are happy for us to see it.

Technical

Your app version and device platform, and short-lived rate-limiting records used to stop abuse of our servers. Once a day the app also tells us, with your account, which platform and app version you use and the country part of your phone's language setting (for example "IN" in English (India)). That is a setting you chose, not your location: it is never taken from GPS or from your IP address.

App integrity checks

At most once a day, the app asks Google Play on your phone to confirm that it is the unmodified FitRealm installed from Google Play, running on a device that passes Google's integrity checks, with a Google Play account licensed for it. Our server has Google decode the answer and keeps only Google's verdict labels, the app version, when the check happened, and a one-way fingerprint of the random single-use number that ties the answer to that check. If the check cannot run on your phone, we keep the error code Google Play gave the app instead. These records are deleted after 30 days, and with your account if you delete it sooner.

Today the check only records the result. It does not block anything or change what you can do in the app.

Advertising

From the update that introduces ads. The launch build carries no advertising code at all, so nothing in this section happens until that update ships.

The free version of FitRealm shows ads, served by Google AdMob. To deliver them, Google receives your device's advertising ID — a resettable identifier Android gives to apps for advertising, which is not your name and not your FitRealm account — together with your IP address, your device model, operating system and app version, and which ads you were shown and whether you interacted with one.

Nothing you log in FitRealm is used to choose an ad. Your workouts, records, body measurements, food, sleep, steps, health inputs, photos, posts and messages are never sent to any advertising system. Health and fitness data is treated as special-category data under EU law, and none of it leaves our database for advertising, ever.

In the EU, the UK and Switzerland we ask you first. Before any personalised advertising, the app shows Google's consent form and you choose. If you decline, ads still appear — they are what pays for the free version — but they are chosen without your advertising ID being used to build a profile of you. You can change that choice at any time from inside the app.

Wherever you are, Android gives you its own control over this: in your phone's settings you can reset your advertising ID, or delete it entirely so that apps receive none.

Crash diagnostics

When the app crashes, it sends a technical report so we can fix the fault: the error and the line of code it came from, your app version, your device model and operating system version, and a random identifier created for this installation of the app.

The report carries no name and no account — not your user ID, not your email — so a crash cannot be traced back to you by account. It contains no screenshot and no copy of what was on screen, and none of your logged data. Section 5 names who receives it.

FitRealm builds most crash reports itself. Before one of those leaves your phone, the app automatically strips email addresses, access tokens and record identifiers out of the error text, and shortens anything overlong so a stray piece of your data cannot ride along inside an error message.

A few faults happen underneath the app. Android shuts the app down, or the app stops responding and Android records that. Android builds those reports, so the app cannot rewrite their text before they are sent. They carry the fault, the place in the code it came from, and what the app was doing at the time. They do not carry anything you have logged in FitRealm, because the crash reporter is never given it.

The crash reporter also sends a small session signal each time the app is opened and closed: that a session started, how long it lasted, whether it ended normally or in a crash, your app version, and a random identifier created for this installation of the app. It lets us see what share of sessions run without crashing, so we can tell whether an update is safe. Like a crash report, it carries no account identity and none of your logged data.

You can switch this off. Go to Settings, then Privacy & safety, and turn off Crash reports. Switching it off shuts the crash reporter down rather than muting it — it stops running, stops sending, and stops keeping anything on your phone. The setting belongs to the device, so it survives signing out, and you can turn it back on in the same place at any time.

3. Why we use it, and the legal basis

Where EU law (GDPR) applies, every use of your data rests on one of three bases: our contract with you, your consent, or our legitimate interest. We apply the same standard to all users worldwide.

Health data needs more than that, and it gets it. EU law calls data about your health special-category data, and Article 9 bars us from using it at all unless one of a short list of conditions is met. Being necessary for our contract with you is not on that list. So your health data rests on your explicit permission, asked as its own question before you start — see the two bullets below.

  • Running your account and keeping your reminder and workout settings with it, building your plan, showing your progress, records, XP, quests and leaderboards, providing the social features you use, and unlocking the paid features on a subscribed account — necessary to perform our contract with you (GDPR Art. 6(1)(b)).
  • Your weight, body measurements and body composition, sleep, steps and the food you log — your explicit consent (Art. 9(2)(a)), on top of the contract above. We ask for it before you start, with its own box that starts empty, separate from accepting these documents. FitRealm cannot build your plan or show your progress without this data, so it is needed to use the app. To withdraw it, delete your account in Settings; that deletes this data with it. Nothing gets past that question without your tick, and we keep the date and document version you accepted, so that we can show it was given, which Art. 7(1) requires of us.
  • Presence sharing, reminders and notifications, Health Connect step access — your consent (Art. 6(1)(a)), and each can be switched off where you switched it on.
  • Injuries and movement cautions — your explicit consent (Art. 9(2)(a)). This one is asked as its own question, with its own box, and the box starts empty. It is separate from accepting these documents, and refusing it costs you nothing but the movement filtering it pays for. You can withdraw it at any time in Settings, then Training profile; withdrawing deletes the injuries we hold. We keep a record of your answer so that we can show it was given, which Art. 7(1) requires of us.
  • Safety, moderation, rate limiting and abuse prevention — our legitimate interest in keeping FitRealm safe and working (Art. 6(1)(f)).
  • App integrity checks — our legitimate interest in keeping XP, leaderboards and challenges fair by spotting modified copies of the app (Art. 6(1)(f)). For now the result is only recorded, and nothing is blocked because of it.
  • Crash diagnostics — our legitimate interest in finding and fixing the faults that break the app (Art. 6(1)(f)). Reports carry no name and no account, so this stays a fair trade: we learn that something crashed, not who you are. You can object to this at any time by turning off Crash reports in Settings, then Privacy & safety.
  • Personalised advertising, once ads arrive in an update after launch — your consent (Art. 6(1)(a)), asked through Google's consent form before the first personalised ad and withdrawable at any time. Consent is not the price of using FitRealm: decline it and the app works exactly as before, with ads that are not personalised.
  • Feedback, suggestions and any screenshots you attach — our legitimate interest in fixing what is broken and deciding what to build next (Art. 6(1)(f)). You chose to send it, and we cannot fix a problem we cannot see.
  • Missing-gym reports — our legitimate interest in having a gym map that matches the real world (Art. 6(1)(f)). The map point you send describes a gym, not you, and you choose when to send one.
  • Reports that a place isn't a gym — the same legitimate interest (Art. 6(1)(f)). The report is about a public place, and you choose when to send one.
  • Usage statistics — our legitimate interest in knowing whether FitRealm works and what to improve (Art. 6(1)(f)). We count, in totals, how many people sign up, finish onboarding, train, use each part of the app and come back. The counts are made inside our database from what the app already stores: workouts, cardio, water logs, social activity, the date you joined, and, to compare groups, your platform, your phone's region setting, your home gym's city and country, your workout style, experience level, sex and age group. Nothing extra is collected for them beyond the platform and region described in section 2. They never use your weight, body measurements, sleep, steps, food or photos. Only totals and percentages leave the database. A group smaller than 5 people is never shown, a comparison is only shown when it covers at least 20 people, and only FitRealm's developer sees them.

Nothing you log in FitRealm is used for advertising or marketing profiling — not your training, food, weight, sleep, steps, health inputs, photos or messages. The advertising described in section 2 runs on your device's advertising ID, entirely separately from all of it. We make no automated decisions about you that produce legal effects.

4. Who can see your data

  • You choose a public or a private account, in Settings, then Privacy. On a public account, any athlete can follow you and see your posts, your followers and who you follow. On a private account, a follow is a request you confirm or delete, and only the followers you confirmed see those. Either way, other athletes can see your profile card — display name, handle, avatar, bio, gym, level, streak, and how many followers, follows and posts you have — so they can find you, ask to follow you, or block you. Posts you share in a community are seen by its members, whichever you choose.
  • A profile photo you upload is an image at a web address. Anyone who has that address can open the image, which is how the app shows it to other athletes, but nobody can browse or list other athletes' profile photos.
  • Friends are athletes who follow each other. Only friends see what you share as friends-only, and your approximate area if you turn on presence sharing. Privacy also lets you choose who can start a chat with you: anyone, only athletes you follow, or only friends.
  • Blocking hides you and the blocked person from each other across the whole app. Their comments and likes on your posts are removed. Notifications between the two accounts are removed too.
  • Reported content is read by a person at FitRealm. When something is reported — a post, a comment, a private message, a community or an event — a moderator can open that specific item in order to decide what to do about it, whoever reported it and whatever your visibility settings say. Nothing else in your account is opened, and the review is limited to the thing that was reported. We record what was decided and when. You can see what came of anything you reported yourself under Settings, then Privacy, then Your reports.
  • Leaderboards share your display name, your username, your avatar — your profile photo if you added one, otherwise the character you wear or its initials and colour — your level, your streak and the XP you earned in the period being ranked with other athletes in the same scope — the athletes at your gym, in your city, or in your country. Tapping a row opens that athlete's profile card, the same card described above.
  • A leaderboard can be grouped by your weight class, by your workout style, or by both.
  • A grouped board lists only the athletes in that group. So if someone sees you on it, they know you are in that group.
  • A leaderboard row shows nothing new. Your weight, your sex and your workout style are never printed on one.
  • A leaderboard only ever groups by your own weight class and your own workout style. There is no way to ask for someone else's.
  • If you have not logged a weight, you are not placed in a weight class and do not appear on a weight-class board.
  • Events. When you join an event, the host and the other people who joined can see your profile card, described above, and whether you have checked in at the venue. Nobody else can. Anyone else who opens the event sees only how many people are going.
  • Challenge Week boards show more, and only if you take part. These monthly boards are ranked by strength, so alongside your username they show your training experience level and your weight class — a bracket such as "70–80 kg", never the weight you logged. They also show the figure that ranked you, which may be an estimated one-rep max, a percentage change, or the total weight you lifted that week. If you do not record a Challenge Week result, you do not appear on them at all.
  • Men and women are ranked on separate boards, on the leaderboards and on the Challenge Week boards alike. There is also a board with everybody on it. Your sex is never printed on a row, but the board you appear on shows which answer you gave. If you chose "Other", or did not answer, you appear only on the board with everybody on it.
  • Content you post is visible according to the audience you chose for it.
  • Progress photos are visible only to you. They never appear anywhere another person can see them, whatever your visibility setting.
  • Photos you take to add a product are visible only to you and FitRealm's developer. They are held in private storage with no public link, they are used only to check the nutrition values you typed, and they are never shown to other athletes. The product that results carries no link back to you.
  • We do not sell or rent your data, and nothing you log in FitRealm is shared for advertising. The one thing that does reach an advertising company is your device's advertising ID, described in section 2 — it carries no name, no account and none of your records. Some US state privacy laws call that "sharing" for targeted advertising; declining personalisation, or deleting your advertising ID in your Android settings, stops it.

5. Third parties

We use a small number of service providers, each for one job:

  • Supabase hosts our database, authentication and file storage. Everything in section 2 is processed there on our behalf, in the EU (Frankfurt, Germany).
  • Sentry receives the crash reports and session signals described in section 2, and nothing else. We use Sentry's EU region, so the reports are stored in the European Union; the app will not send crash reports to any other region. Your IP address reaches Sentry because it must in order to deliver the report, but it is not attached to the report or stored with it. Sentry never receives your account, your workouts, your food logs, your messages or anything else you have entered.
  • Google Play sells and charges any subscription. Google receives and holds everything to do with the payment — your Google account, your payment method and your billing details. We never see them, and Google tells us only that the subscription exists and when it runs to. Occasionally, after something you have achieved in the app, we ask the Play Store to show its own rating prompt. The prompt is Google's, not ours: we send it nothing about you, we are not told whether it appeared or what you did with it, and anything you choose to write becomes a public review on our store listing. The app remembers only, on your own device, that it asked, so it does not ask again for months.
  • RevenueCat, once Pro goes on sale after launch, checks with Google that a subscription is genuine and tells our servers whether an account is entitled to the paid features. It receives a FitRealm account identifier and the purchase details from Google Play, and nothing you have logged in the app. It processes this outside the EU under its own safeguards.
  • Google AdMob, once ads arrive after launch, serves them in the free version. It receives your advertising ID, your IP address, your device and app information, and what you did with the ads themselves. It receives nothing you have entered or logged in FitRealm. Google decides for itself how it uses that advertising data, under its own privacy policy, and may process it outside the EU under its own safeguards.
  • Google Sign-In receives your Google account identity only if you choose "Sign in with Google". This is separate from AdMob and the two are not joined up by us.
  • Google Play Integrity confirms that the app is the genuine FitRealm, as described in section 2. When the app asks, Google Play services on your phone sends Google information about the app, your device and your Google Play account so that Google can produce its verdict, and our server then sends Google the sealed answer to decode. The request carries no FitRealm account identifier and nothing you have entered or logged — only a one-way fingerprint that our server alone can match to the check. Google processes this under its own privacy policy and may process it outside the EU under its own safeguards.
  • OpenFreeMap (tiles.openfreemap.org) receives your IP address and which map area you are viewing, in order to draw maps. It is a free, open-source basemap service; we send it no account identifier, and it needs no key or registration. It is delivered over Cloudflare's global network, so it may be served from outside the EU.
  • OpenStreetMap Nominatim (nominatim.openstreetmap.org) turns a place name or an address into a point on the map. It is used in two places: when you search the map for a city, area or street, and when you type an address while reporting a missing gym. It receives the text you typed, your IP address, and a rough box around the part of the map you are looking at, which is used to prefer nearby results over identically-named places elsewhere in the world. We send it no account identifier, and we do not keep a record of what you searched for. It runs only when you press search — never while you are typing, and never when you move the map. It is operated by the OpenStreetMap Foundation and may be processed outside the EU under its own safeguards.
  • Open Food Facts receives the barcode or search text you enter when looking up a food.
  • Google ML Kit is the barcode scanner. It reads the barcode entirely on your phone: the camera image and the barcode it reads are never sent to Google. ML Kit does send Google technical data about itself: your device's make, model and operating system version, the app's package name and version, an identifier for this installation of the app that is not meant to identify you or your phone, and how the scanner ran, such as how long a scan took, the image format and size it worked on, which scanner version ran and any error codes. From time to time it may also fetch fixes, updated models or compatibility information from Google. Your IP address reaches Google because it must in order to make those connections. Google uses this data to measure, maintain and improve ML Kit and to detect misuse, under its own privacy policy, and may process it outside the EU under its own safeguards. We never receive it.
  • USDA FoodData Central receives the food search text you enter. The request is made by our server, not by your phone, so USDA never sees your IP address.
  • Health Connect runs on your device; we read your step count from it and nothing about you is sent to it.

We also build the gym map from two public datasets, on our servers and never from your phone: OpenStreetMap's Overpass service (and, when it is unavailable, one of its public mirrors), and Overture Maps. Neither request contains any information about you — we are downloading a public list of gyms, not telling anyone where you are. Gym data is © OpenStreetMap contributors (ODbL) and © Overture Maps Foundation contributors.

Your data is stored in the European Union. When you use FitRealm from outside the EU, your data still lives in the EU; the third parties above receive only the pieces described, some of which (AdMob, RevenueCat, the barcode scanner's technical data, app integrity checks, map tiles, map search, food lookups) may be processed outside the EU under their own safeguards.

6. Permissions the app asks for

Everything you are asked to grant is optional, and the rest of the app keeps working if you decline it.

  • Notifications — showing your step count while FitRealm counts steps in the background, your workout or cardio session while it runs, and reminders and step milestones. Reminders start off. FitRealm asks once whether to turn them on, and you can change that in Settings. FitRealm explains this before Android asks, and only asks while you are using the app.
  • Physical activity — counting your steps with your phone's motion sensor, and asking Android whether you are walking, cycling or in a vehicle so that cycling and driving do not get counted as steps (section 2). Android also requires it before FitRealm can keep step counting and your workout notification running in the background (the foreground service below). Without it FitRealm cannot count steps itself, though it can still read them from Health Connect if you allow that. The app declares this permission under two names, android.permission.ACTIVITY_RECOGNITION and com.google.android.gms.permission.ACTIVITY_RECOGNITION. They are the same permission: older Android versions check the second name. Together they grant one thing, and you are asked once.
  • Health Connect — reading your step count, including in the background where your phone supports that. Health Connect asks for this on its own screen, and nothing else is requested from it.
  • Location — finding gyms near you, checking you in to an event you joined, and presence sharing if you opt in.
  • Camera — scanning food barcodes, taking a progress photo, and taking the three photos of a packaged product you add to the food library.
  • Foreground service — counting your steps while the app is closed, and keeping your workout timer running during a session. It posts an ongoing notification the whole time it is active, under a separate category for each of the two, and you can switch background step counting off in Settings.
  • Run at startup — restarting step counting after you reboot your phone, so the steps you take before you next open the app still count.

Choosing a photo, whether a profile photo, a progress photo or a screenshot for a problem report, needs no permission at all: the app opens your phone's own picker, and only the photo you choose reaches FitRealm.

One more permission works differently, so we spell it out: the advertising ID permission (AD_ID). It is not in the list above because the launch build does not declare it. From the update that introduces ads, the app declares it so that ads can be served in the free version. Android never prompts you for it — it is granted by installing an app that declares it. Your controls over it are the consent choice in section 2 and your phone's own advertising settings, where the ID can be reset or deleted.

7. How long we keep it

  • Your data is kept for as long as your account exists.
  • When you delete your account, every file you uploaded — your avatar, post photos, progress photos, product photos and feedback screenshots — is removed first, and the account itself is deleted only once none is left. It then takes everything else in section 2 with it, erased from our live systems immediately. If a file cannot be removed, the deletion stops there: your account stays, the app tells you whether any photos were already removed, and you can try again. Our hosting provider may hold short-lived disaster-recovery copies for a limited period before they roll off; we keep no long-term backups of deleted accounts.
  • Deleting your account does not delete other people's things. The messages you sent are deleted. The people you talked to keep the messages they sent, and your name in those chats becomes "Deleted athlete". A community you created carries on without you — it passes to one of its moderators, or to its longest-standing member, and it closes only if nobody is left in it. Posts, comments and events other athletes created are untouched, including ones inside a community you started. An event you are hosting stays for the people who joined it, with your name removed. If nobody else had joined it, it is deleted.
  • Reports filed about you are unlinked from your identity the moment your account is deleted. Reports you filed are unlinked from you in the same way, so that what you reported can still be read and acted on. Either way the anonymised record is deleted at most 12 months later.
  • Your answer to the injuries question — yes or no, when you answered, and which version of these documents you answered against — is kept for as long as your account exists and is deleted with it. It is the record of a permission, so it holds no injury in it.
  • Feedback, exercise suggestions and any screenshots attached to them go when your account does, screenshots included. We may keep an anonymised note of what was reported so a fix does not get lost, but it is no longer linked to you.
  • A product you added and we approved stays in the food library when your account goes, with nothing on it that points back to you. The photos you took for it are deleted with your account, and so is a product that was still waiting to be checked.
  • Missing-gym reports go when your account does. A gym we already confirmed and put on the map stays — it is a public place, not information about you, and by then it is part of OpenStreetMap rather than something we hold.
  • Reports that a place isn't a gym go when your account does. A place we already took off the map because of one stays off it — that decision is about the place, not about you.
  • Records of decisions we took about your account, such as a suspension, are kept while the account exists and are deleted with it.
  • The platform, app version and region setting your app reports are kept while your account exists, overwritten each day, and deleted with it.
  • Rate-limiting records expire on their own within days. The record of which athletes you started following, kept for the weekly follow limit, is deleted within nine.
  • App integrity check records are deleted automatically after 30 days, and go with your account if you delete it sooner. What Google Play itself keeps about a check is held under Google's own rules, not ours.
  • Crash reports are deleted automatically after 90 days. They carry no account identity, so they are not linked to you and deleting your account neither reaches them nor needs to.
  • Advertising data is held by Google under its own retention rules, not ours. We keep no copy of it, and there is nothing on our side to delete.
  • Subscription records — that an account is or was subscribed, and when — are kept while the account exists, and go with it when you delete it. Payment records belong to Google Play and are kept under Google's own rules; we never hold your payment details.
  • On your phone. So you can open the app and train without signal, it keeps a copy of your profile and your current plan, and any workout or cardio session that has not reached our servers yet, in storage only FitRealm can read. It also keeps your step history there: your daily step totals, today's steps by hour, and which of each day's step milestones you have reached. It remembers your answer to the injuries question and the date you gave it, so the app knows whether to ask you even without a connection; the answer is kept against your account, so a second account on the same phone has its own. The record we hold of that answer is the one described above, not this copy. None of it goes into your phone's backups. Signing out removes the profile and plan copies and the step history, including any step totals that had not reached your account yet. Your injuries answer stays, because it is the record of a permission you gave and signing out does not withdraw it. A workout or cardio session that has not synced waits on the phone until it does, and signing out does not remove it. If our servers refuse it for good, it stays unfinished on the phone longer than it can still be saved, or more is waiting than the phone can hold, the phone keeps only a short note of it instead: what it was, which day, and why. It keeps the same kind of note when a workout syncs too late to earn XP. A note stays until you dismiss it or twenty newer ones replace it. Deleting your account or uninstalling the app removes all of it. The step records Health Connect keeps are its own, not a copy FitRealm holds, and they stay in Health Connect.

8. Your rights

Built into the app today, under Settings, then Account & security:

  • Download your data — a JSON export of everything you have logged and shared: every workout down to each set's reps and weight, your plans, logs, saved meals and workout templates, your reminder and workout settings, your posts, comments and the messages you sent, your follows and follow requests in both directions, everything you sent us, and any decision we took about your account. Nothing is cut off, however long your history. Each progress photo comes with a download link that stays valid for one hour. The export leaves out what belongs to other people: messages they sent you, whether anyone blocked or reported you, and their follow history beyond who follows you now.
  • Delete your account — permanent and immediate; it takes your profile, workouts, logs, posts, messages, photos and social connections with it. There is no recovery. You confirm it is you first: with your password, or — if you sign in with Google and have not signed in within the last ten minutes — by choosing your Google account again.

You can correct your profile at any time from Settings, and control who sees you from Settings, then Privacy.

If you are in the EU or UK you additionally have the rights of access, rectification, erasure, restriction, portability and objection, and the right to complain to a data protection authority — ours is the Landesbeauftragte für den Datenschutz und die Informationsfreiheit Rheinland-Pfalz. We honour equivalent rights for users elsewhere on request to privacy@fit-realm.app.

9. Children

FitRealm is not for children under 16, or under the higher minimum your country's law sets for services like this. We do not knowingly collect data from children below that age. If you believe a child is using FitRealm, contact us and we will remove the account.

10. Security

Access to your data is enforced at the database level: every table is protected by row-level security, so other people's records are unreachable even from a tampered client. Passwords are handled by our authentication provider and are never visible to us. All traffic is encrypted in transit. No system is perfectly secure — if a breach affects your data, we will tell you promptly.

11. Changes

If we change how we use your data in a way that matters, we will raise the version of this policy and the app will ask you to accept it again before you continue. The English version of this policy is the binding one.

12. Contact

privacy@fit-realm.app — Ashish Shirish Vayangankar, Vayash Studio, Julius-Leber-Strasse 1a, 67551 Worms-Pfeddersheim, Germany.

13. The website fit-realm.app

This section is about the website, which is a separate thing from the app and needs no account.

The site has no contact form, no sign-up, no newsletter and no comments. It asks you for nothing. It sets no cookies of any kind and stores nothing on your device, which is why you are not being shown a consent banner — there is nothing to consent to.

Two things still happen automatically the moment any website is opened, and both involve your IP address:

  • Hosting. The site is served by Cloudflare Pages. To send you a page at all, Cloudflare receives your IP address, the page you asked for, your browser's user-agent string and the time of the request, and keeps short-lived security and operations logs of that.
  • Visitor statistics. We use Cloudflare Web Analytics to count page views and see which pages get read. It uses no cookies, stores nothing on your device, and does not fingerprint or follow individual visitors across sites or over time. Your IP address reaches Cloudflare because it must in order to make the request, but no per-visitor profile is built from it.

Both rest on our legitimate interest in running a secure website and knowing, in aggregate, whether anyone is reading it (GDPR Art. 6(1)(f)). We do not use any of it to identify you — nothing on the website ties a visit to a person.

Cloudflare, Inc. acts as our processor under a data processing agreement. Where data reaches the United States, that transfer rests on the European Commission's Standard Contractual Clauses and on Cloudflare's certification under the EU-U.S. Data Privacy Framework.

Your rights in section 8 apply here too. Write to privacy@fit-realm.app.

This policy is also published at fit-realm.app/privacy.