GoodDay Privacy Policy

1. Overview

GoodDay is a calm wellness and habit companion published by Fenixlab Games. It helps you build better days through gentle tracking of everyday wellness categories such as movement, water, sleep, nutrition, Me Time, and Digital Balance, along with a Day Score, insights, challenges, and optional local reminders.

GoodDay is a general wellness application. It does not diagnose, treat, cure, or prevent disease, and it is not a medical device.

GoodDay currently does not require you to create an account or sign in. There is no GoodDay server-side user profile or GoodDay account database.

2. Information You Provide

When you use GoodDay, you may enter or generate wellness information on your device, such as:

• daily habit entries and progress
• Day Score and related history
• wellness plan / goals
• challenge progress
• reminder preferences
• language and appearance preferences
• onboarding choices

You choose what to log. Manual logging works even if you never connect health permissions.

3. Health and Fitness Data

If you choose to connect a health source, GoodDay may request permission to read:

• steps
• sleep information

Purpose: populate relevant GoodDay wellness categories, reduce manual logging, and support in-app wellness progress features (including Day Score).

Access: read-only.

GoodDay does not:

• write data to Health Connect or Apple Health / HealthKit
• sell health data
• use health data for advertising
• intentionally send raw health values through GoodDay’s custom Firebase analytics events

Health access is optional. You can deny permission and continue with manual logging. You can revoke permission later in your device’s health or privacy settings (for example, Health Connect on Android or Apple Health / HealthKit settings on iOS).

4. Information Processed Automatically

When Firebase Analytics and Firebase Crashlytics are active (in release and profile builds), Google Firebase may process technical information needed for analytics and crash reporting. Depending on the SDK and project configuration, this may include categories such as:

• app and session usage
• app version
• device and operating-system technical information
• diagnostics
• crash and error information
• Firebase-generated technical identifiers

GoodDay does not invent or list exact field-level inventories beyond what can be verified from the product’s design and privacy guards. Retention for Firebase/Google-processed data follows Google Firebase practices and the project’s Firebase configuration.

Advertising ID collection is disabled in GoodDay’s Android configuration.

5. Firebase Analytics

GoodDay uses Firebase Analytics to understand product usage and improve the app.

GoodDay’s custom analytics events are privacy-filtered. They are designed not to intentionally include:

• raw steps or sleep duration
• raw health values
• water, nutrition, Me Time, or Digital Balance quantities
• exact Day Score values
• exact targets
• notification title or body
• share-card content
• free-form user text
• a custom Firebase user ID set by GoodDay

This is not a claim that Firebase collects “no data.” Firebase may still process technical information as described in Section 4 and in Google’s privacy documentation for Firebase / Google Analytics.

6. Firebase Crashlytics

GoodDay uses Firebase Crashlytics to collect crash and stability reports so we can improve reliability.

Crash reports may include technical diagnostics such as stack traces and device/app metadata provided by the SDK. GoodDay’s error-reporting safeguards are designed not to intentionally attach raw health values, notification content, share content, or similar sensitive free-form content to custom crash keys.

7. How We Use Information

We use information to:

• provide GoodDay’s wellness features on your device
• calculate in-app progress such as Day Score
• schedule local reminders you enable
• understand feature usage through Firebase Analytics
• diagnose crashes and improve stability through Firebase Crashlytics
• support optional health import after you grant permission

We do not use health data for advertising.

8. Data Sharing

• GoodDay does not sell your health data.
• GoodDay does not use health data for advertising.
• Wellness records you create in GoodDay are stored on your device and are not uploaded to a GoodDay account backend (GoodDay has no such account backend today).
• Technical analytics and crash information may be processed by Google Firebase as described above.
• If you share a wellness card, the destination you choose (for example, a messaging or social app) receives what you share and is governed by that destination’s own privacy policy.

9. Local Storage

Most GoodDay wellness and preference data is stored locally on your device using the platform’s ordinary app storage mechanisms (for example, app preferences storage). Examples include:

• wellness / daily records
• plan and goals
• challenge progress
• reminder settings
• selected language and appearance
• onboarding state
• health-connection preference flags used by the app

GoodDay may also create temporary image files on device when you export a share card.

This policy does not claim a special GoodDay-implemented encryption-at-rest layer beyond ordinary platform app storage.

10. Data Retention and Deletion

Local GoodDay data

• Local wellness and preference data generally remains while GoodDay’s app data remains on your device.
• Uninstalling GoodDay, or clearing GoodDay’s application data in your device settings, removes local GoodDay records stored in the app.
• Health permissions can be revoked separately in system health / privacy settings without uninstalling.
• Reminder permissions and reminder settings can be changed in the app and in system notification settings.

GoodDay does not currently provide a production in-app “Delete all data” control. (Developer QA reset tools may exist only in debug builds and are not part of the production experience.)

No GoodDay account

Because GoodDay does not create a GoodDay account profile, there is no GoodDay account profile that requires separate account deletion.

Firebase technical data

Analytics and crash information processed by Google Firebase is retained according to Google Firebase / Google practices and the Firebase project configuration. This policy does not promise instant deletion from Google’s systems.

11. Health Permissions

Health access is requested only after you choose to connect. Current production read types are steps and sleep. Access is read-only. You may revoke access at any time in system settings. Manual logging continues to work without health permissions.

12. Notifications

If you enable reminders, GoodDay schedules local notifications on your device. You control notification permission and reminder settings.

GoodDay does not currently use remote Firebase Cloud Messaging for marketing or remote push campaigns.

13. Sharing Features

GoodDay can generate wellness share cards on your device. Sharing happens only after you take an explicit action. GoodDay uses the Android / iOS system share sheet. GoodDay does not require its own social upload server for this feature. Any app you select as a share destination has its own privacy practices.

14. Security

We take reasonable steps appropriate for a local-first consumer wellness app, including transmitting Firebase network traffic over HTTPS and applying privacy filters to custom analytics and crash metadata.

No method of electronic storage or transmission is completely secure. This policy does not claim that GoodDay is “100% secure.”

15. Third-Party Services

GoodDay uses Google Firebase (including Analytics and Crashlytics). Depending on your platform and choices, health platforms such as Android Health Connect and Apple Health / HealthKit may also be involved when you grant permission.

Useful privacy resources:

• Google Privacy Policy
• Firebase / Google Analytics data use
• Android Health Connect
• Apple Privacy Policy

16. Children / Audience

GoodDay is intended as a general consumer wellness app and is not directed at children. Age targeting and content-rating answers for Google Play are completed separately in Play Console and are not redefined by this policy.

17. Changes to This Policy

We may update this Privacy Policy from time to time. The hosted version will show the current effective date. Continued use of GoodDay after an update means you should review the latest hosted policy.

18. Contact

Developer: Fenixlab Games

App: GoodDay

Email: fenixlabgames.support@gmail.com

For privacy questions about GoodDay, contact Fenixlab Games at the email above.