Privacy Policy
This Privacy Policy explains what information the Healthify mobile application ("Healthify", "the app", "we") collects, how it is used, where it is stored, and your rights regarding that information.
1. Information we collect
1.1 Information you provide directly
During onboarding and daily check-ins you may enter:
- Profile basics: display name, age, gender, height, weight.
- Health context: existing health conditions, personal wellness goals.
- Wellness goals: daily step goal, water-intake goal, sleep-hours goal.
- Daily check-ins: mood score (0–4), water glasses, food-quality tag, sleep hours, day rating (1–5).
All of these are stored locally on the device in an SQLite database
(healthify.db). A copy is synced to Firebase Firestore under an
anonymous identifier so the same account can be used across devices.
1.2 Information read from Health Connect
With your explicit per-data-type permission, Healthify reads the following record types from Android Health Connect:
| Health Connect record | Used for |
|---|---|
| Steps | Today's step count on the home dashboard, measured against your step goal, and one of the two automatic inputs to your daily wellness score |
| Sleep sessions | Last night's total sleep hours on the home dashboard, and the second automatic input to your daily wellness score |
These are the only two Health Connect record types Healthify requests. It does not request heart rate, distance, active calories, weight, height, blood glucose, oxygen saturation, menstruation, nutrition, exercise sessions, or any other record type. Heart rate, distance and active calories were requested by versions up to 1.0.14 and were removed in 1.0.15.
Granting Health Connect access is optional. If you decline, or revoke it later in the Health Connect app, Healthify keeps working — you enter steps and sleep manually on the check-in screen instead.
Health Connect data is read on demand, summarised, and the summary is stored alongside your check-in record. The app does not write data back to Health Connect and does not export raw Health Connect records to Firestore — only the daily summary (e.g. "12 345 steps today") is synced.
1.3 Information collected automatically
- Anonymous Firebase user identifier (UID). Generated by Firebase Authentication's anonymous sign-in. Random opaque string; not linked to a Google account, email address, phone number, or device identifier.
- Crash diagnostics (release builds only). If the app crashes, Firebase Crashlytics records the stack trace, Android version, device model, and the anonymous UID above. No screen contents and no health data are included.
- Firebase Analytics events. Aggregated, non-PII usage events (e.g. "user completed a check-in"). No free-text inputs are sent.
1.4 Information we do not collect
- We do not request your name, email address, phone number, or any government identifiers.
- We do not request precise location.
- We do not access contacts, microphone, camera, SMS, call logs, or files on external storage.
- We do not share data with advertisers.
- We do not sell personal information.
2. How we use information
We use the data described in §1 to:
- Power core app features (check-ins, daily dashboard, weekly insights, streak tracking, reminders).
- Sync your records across devices so reinstalling the app does not lose your history.
- Diagnose and fix crashes via Firebase Crashlytics.
- Improve the product via aggregated, non-PII analytics.
We do not use your information for advertising, profiling for third-party marketing, or any automated decision making with legal effects.
3. Where data is stored
| Location | What is stored |
|---|---|
On your device (healthify.db, app's private storage) |
Full profile, check-ins, reminders |
| Firebase Firestore (Google Cloud, EU/US multi-region) | Anonymous UID, profile summary, daily check-in summaries (mirror of on-device DB) |
| Firebase Authentication | Anonymous UID + sign-in token |
| Firebase Crashlytics (release builds only) | Crash stack traces + device metadata + anonymous UID |
Health Connect data stays on your device — it is never uploaded to our servers. The summary numbers derived from it (e.g. step count for a given day) are mirrored to Firestore as part of the daily check-in record.
Android cloud backup (Auto Backup) and device-to-device transfer
deliberately exclude healthify.db and Firebase
installation files. Your health data does not roam through Google account backup.
4. Sharing with third parties
We use the following sub-processors. We do not share data with anyone else.
| Sub-processor | Purpose | Data shared |
|---|---|---|
| Google / Firebase | Auth, Firestore, Crashlytics, Analytics | Anonymous UID, check-in summaries, crash reports |
| Android Health Connect | On-device data source | Per-permission read access; data is read only, not written |
All transit uses HTTPS/TLS; cleartext network traffic is disabled at the OS level.
5. Your rights
You can, at any time:
- Revoke Health Connect access — Android system settings → Health Connect → Permissions → Healthify.
- Disable notifications — Android system settings → Apps → Healthify → Notifications.
- Delete your data — Uninstall the app to remove the local database. To delete the synced copy on Firestore, email deltapkr.developer@gmail.com with your anonymous UID (shown in the Profile tab under About → Account ID, tap to copy) and we will erase the corresponding documents within 30 days. The Profile tab also has a one-tap Request data deletion row that opens a pre-filled email.
- Export your data — Email deltapkr.developer@gmail.com and we will return a JSON export of all Firestore documents associated with your UID.
You also have rights under applicable law (GDPR, CCPA) including access, correction, deletion, restriction, portability, and the right to lodge a complaint with your supervisory authority.
6. Children
Healthify is not directed at children under 13. We do not knowingly collect data from children under 13. If you believe a child has provided data to us, contact deltapkr.developer@gmail.com and we will delete it.
7. Security
- All network traffic uses TLS.
- The local database lives in the app's private, Credential-Encrypted storage (sandboxed by Android).
- Release builds are minified and obfuscated via R8, with crash mapping files uploaded only to Firebase.
- We do not log raw health data; only aggregated summaries are persisted.
No system is perfectly secure. If you discover a vulnerability, email deltapkr.developer@gmail.com.
8. Retention
- Local data persists until you uninstall the app or wipe data via Android settings.
- Firestore data persists indefinitely while your anonymous UID exists. Email-based deletion requests are honoured within 30 days.
- Crashlytics retains crash reports for 90 days by default per Firebase policy.
9. Changes to this policy
We may update this Privacy Policy from time to time. Material changes will be reflected in the "Last updated" date above. Continued use of the app after the effective date of any change constitutes acceptance.
10. Contact
Email: deltapkr.developer@gmail.com
Publisher: DeltaPKR
Country of operation: Armenia
For data-protection inquiries please put "Healthify privacy" in the subject line.