Comparison
Privacy is a data-flow question, not a badge.
“Private” can mean local storage, no account, encryption, or simply a good marketing page. The useful questions are concrete: where does the data live, who can access it, what leaves the device, and can you take it with you?
Read the data flow, not the slogan.
A privacy label is only useful if it tells you what is stored, what is sent, and what you can delete. This page gives you the questions to ask any app — including ours.
| Question | Why it matters | What good looks like |
|---|---|---|
| Where is the data stored? | On your device, the vendor’s cloud, or both. | The answer is specific, not just “secure.” |
| Is an account required? | An account creates an identity and a server-side record. | You can use the core app without an account, if that matters to you. |
| What leaves the device? | Ads, analytics, crash reports, integrations, or backups. | The policy names the categories and the purpose. |
| Is health data used for ads? | Health data is sensitive and often regulated. | The answer is a clear “no”; ads use device-level metadata only. |
| Can you export everything? | Portability is part of privacy. | CSV/JSON export and a local backup are available. |
| Can you delete everything? | Deletion should be real, not just hidden. | There is a clear delete path, including local data. |
| What happens if you lose the phone? | Local-first means you need a backup. | The app explains backup/export and transfer steps. |
| Is Health Connect optional? | Platform integrations can read/write health data. | You choose whether to connect, and what to sync. |
General product-privacy checklist as of November 9, 2026. It is not legal advice. Read each app’s privacy policy and data safety disclosure.
Three models
There is no free privacy lunch.
Each model has a tradeoff. The right one depends on what you need.
Local-first
Records live on your device. No account is required. You control exports and backups. Tradeoff: device loss and manual transfer are your responsibility.
Cloud account
Records sync through a vendor account. Convenient across devices. Tradeoff: the vendor and its subprocessors can access the data; read the policy and export options.
Ad-supported free
The app is free because ads or analytics support it. Tradeoff: data may be shared with ad/analytics partners. Health data should never be used for ad targeting.
Where ours fits
Local-first, no account, explicit sharing.
This is what Weight Track Assistant does — and what it does not do.
- Health records are stored on your device; no online account is required.
- Ads receive device-level metadata only, never your health records.
- CSV/JSON export, local backup, and a delete-all-data path.
- Health Connect integration is optional; you choose what to read or write.
- Cloud sync is not part of 4.2; moving phones is manual export/import.
Local-first means you own the backup.
No account also means no automatic cloud copy. If you lose your phone without a backup, the data is gone. The app provides export and local backup; using them is your choice. That is the tradeoff for keeping the data off our servers.
Limits
What this guide does not do.
A short list, so the scope is clear.
- It does not rank every app’s security.
- It does not provide legal advice or a compliance certification.
- It does not claim that local-first is right for everyone.
- It does not replace each app’s privacy policy and data safety disclosure.
Privacy questions.
What does “local-first” mean?
Is a cloud app automatically less private?
Does Weight Track Assistant require an account?
Does the app show ads?
What should I ask before trusting a health app?
Is this medical advice?
The local-first option
Keep the record on your phone.
Weight, GLP-1, measurements, nutrition, and export — without an online account.
- 1M+ installs since 2013
- Current version 4.2
- No account required
- Free on Android