Last updated 20 November 2026
Arogyam is a self-hosted health tracker. This policy describes the installation
running at arogyam.getplutus.xyz, which is operated privately by its
owner rather than by a company. It is written to describe what the software
actually does — if something is not listed here, the app does not do it.
Everything you enter, on the server running this installation:
| Category | Examples |
|---|---|
| Account | Your Google account's email address, name, profile picture URL and Google user ID |
| Profile | Name, date of birth, sex at birth, height, weight, activity level, dietary preference, health conditions you choose to record |
| Food | Meals logged, quantities, times, and any photographs you take to estimate a meal |
| Body & activity | Weight, body fat, waist/neck/hip measurements, steps, sleep, workouts, mood and energy notes |
| Body read | Only if you use it: the findings — body shape, a body-fat range, posture flags and which areas look behind the rest. The photographs themselves are not stored; they are sent for analysis and dropped. |
| Clinical | Blood pressure readings and any lab results you enter (TSH, HbA1c, vitamin D, lipids) |
| Device data | Readings sent by a watch or phone you connect, such as steps, resting heart rate and sleep |
There is no advertising, no cross-site tracking, and nothing is sold or shared for marketing. Usage analytics are collected by this server; they are additionally forwarded to Google Firebase only for accounts that switch that on themselves, and it is off until you do — see Usage analytics below. Five outside services are contacted, and only for the purpose described:
| Service | What is sent | When |
|---|---|---|
| Google Sign-In | Standard sign-in exchange; Google tells the app your email, name and picture | Every sign-in |
| OpenRouter | The photograph of your meal, so an AI model can estimate its calories. For a body read, the one to three photographs of your body you choose to take, together with your sex at birth, age, height and weight so the read can be calibrated. No name, email or account identifier is attached. | Only when you use the camera to log food, or run a body read |
| Open Food Facts | The barcode number you scanned | Only when you scan a barcode |
| Fitbit, Strava or Oura | Standard OAuth exchange, to pull your own readings in | Only if you connect one |
| Google Firebase / Google Analytics | Usage events only — which screen, which control, whether a request worked — under a random identifier. No meals, measurements, lab values or free text. Sent by this server, so Google does not receive your IP address or set anything on your device. | Only if you switch on Share with Firebase |
Terms of use · Delete your account
The app records how it is used, so whoever runs it can see which screens get opened, where people get stuck in a flow, and what fails. This is first-party: the events are written to the same database as the rest of your data, on this server. No analytics SDK is embedded in the app, and nothing is sent from your device to a third party. The only way these events can reach anyone else is the opt-in described under Sharing with Google Firebase below, which is off unless you switch it on.
What an event can contain is fixed by the database columns, and there is no free-text or catch-all field:
| Recorded | Example |
|---|---|
| What happened, from a fixed list | log_meal, screen_view, api_error |
| Which screen or control | today, fab-add, provider |
| When, and which visit | A timestamp, the local date, and a random id for one app-open |
| How the app was opened | apk, pwa or browser, and the build |
| Whether a request worked, and how long it took | ok, 420 ms |
The owner of this installation may connect it to Google Firebase (Google Analytics 4). This is off for your account unless you turn it on under Me → App → Share with Firebase. Agreeing that this server may count your screens is not the same as agreeing that Google may receive those counts, so it is asked separately.
If you switch it on:
Declining changes nothing else: the app works identically, and the first-party analytics on this server continue unless you switch those off too.
Who can see what: the person who runs this installation can see aggregate figures — counts of accounts and events, screens, funnel steps, failures. No account can see another account's events, in aggregate or otherwise, and the aggregate view is limited to the owner and anyone the owner has named as an administrator.
Your choices:
On the server hosting this installation, in a database that is not shared with other services. Every query the server runs is limited to the signed-in account, and that is checked by automated tests, so one account cannot read another's data. Connected-service tokens are encrypted at rest with AES-256-GCM. Data is kept until you delete it.
If you cannot reach the app, email anil@vitwit.com with the address you signed in with and the account will be deleted.
Arogyam records what you tell it and does arithmetic on it. It is not a medical device, it does not diagnose, and nothing it shows is medical advice. Targets follow published reference values (ICMR-NIN 2020 for nutrients, WHO for sodium and blood pressure bands). Talk to a doctor about anything that matters.
Not intended for anyone under 13, and no account should be created for one.
If this policy changes, the date at the top changes with it.