Privacy Policy

Effective date: 2026-05-18  ·  Last updated: 2026-10-05
App: Fernday (com.DeltaPKR.Healthify)  ·  Publisher: DeltaPKR
Contact: deltapkr.developer@gmail.com

This Privacy Policy explains what information the Fernday mobile application ("Fernday", "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).
• Logs you add during the day: glasses of water (with the time logged), meals (meal slot, an optional name you type, a quality tag such as “Healthy” or “Skipped”, and the time), and activities (kind, such as walk or yoga, duration in minutes, and the time).
• Food details (optional): when you log a food you searched for or scanned, the meal also stores its barcode, the amount in grams, and its calories, protein, carbohydrate, fat, fibre, sugar and Nutri-Score. Foods you look up are kept in a local food list so you can log them again; foods you add yourself (a name, calories per 100 g, and optionally a barcode) are kept there too.
• Calorie-counting settings (optional, off by default): whether calorie counting is on, your activity level, your goal (maintain, lose or gain weight), and your own daily calorie target if you set one.
• Workouts (optional): routines you create (a name and the exercises in it with their sets, reps or time, and rest), exercises you add yourself (a name and how you track it), and the workouts you do in the workout player: each set's exercise, reps, weight and time, whether it was a warm-up, any personal record it set, and the workout's length and an estimated calorie burn (shown only if calorie counting is on). The exercise library itself is part of the app and needs no connection.

All of these are stored locally on the device in an SQLite database. A copy is synced to Firebase Firestore under an anonymous identifier. Sync is one-way today: the app sends its records to Firestore but does not yet restore them on a new install or another device.

1.2 Health Connect

With your explicit per-data-type permission, Fernday reads the following record types from Android Health Connect:

These are the only two Health Connect record types Fernday reads. It does not read 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, Fernday 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. Fernday does not export raw Health Connect records to Firestore — only the daily summary (e.g. "12 345 steps today") is synced.

Saving workouts to Health Connect (optional, off by default). If you turn on "Save to Health Connect" in the Move tab's settings, Fernday asks for Health Connect's exercise write permission and then writes each workout you finish and each activity you log as an exercise session: its type, title, start and end time. Sets, weights, notes and calorie estimates are not written. Workouts you logged before turning it on are written too. Editing or deleting a workout in Fernday updates or deletes its copy. Fernday does not read exercise sessions back. Once written, a session is in Health Connect on your device, where apps you allow to read exercise can see it. Turning the setting off stops new writes; sessions already written stay until you delete them in Health Connect.

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.
• Food searches and barcodes. When you search for a food or look up a barcode, the search text or barcode is sent to Open Food Facts (see §4). Fernday keeps no history of your searches beyond the foods you choose to log.

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. Barcode scanning uses Google's code scanner (see §4), which runs in Google Play services: Fernday does not hold the camera permission and never receives camera images, only the barcode number.
• 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:

1. Power core app features (check-ins, daily dashboard, food logging and the optional calorie estimate, weekly insights, streak tracking, reminders).
2. Keep a cloud copy of your records under an anonymous identifier (one-way today; restoring from it is not yet available).
3. Diagnose and fix crashes via Firebase Crashlytics.
4. 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

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 the app's database 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.

Food data shown in the app comes from Open Food Facts and is available under the Open Database License.

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 → Fernday.
• Stop saving workouts to Health Connect — Move tab → settings → Save to Health Connect. Delete saved sessions in the Health Connect app.
• Disable notifications — Android system settings → Apps → Fernday → 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

Fernday 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 "Fernday privacy" in the subject line.