dayily

Dayily

Privacy Policy

This policy explains what the Dayily mobile app currently stores, reads, sends, and writes. It is written for the current implementation and may be updated as the app changes.

Last updated: 2 October 2026

1. Data we handle

Dayily is designed to work locally first. Depending on the features you use, the app may handle:

  • workout sessions, exercises, sets, repetitions, load type and load, timing, titles, notes, templates, favorites, and a body-weight snapshot associated with a workout;
  • local profile and preference data, such as language, units, workout settings, and whether health integration is enabled;
  • account data related to signing in, such as an account identifier, email address, verification state, and limited profile information supplied by your sign-in provider;
  • health and activity records made available by your device after you grant permission;
  • technical information needed to operate sign-in, cloud sync, crash reporting, and in-app feedback.

Dayily does not store passwords or other authentication secrets in its own local preferences.

2. Health and activity data

With your permission, Dayily reads data from Apple Health on iOS or Health Connect on Android. Depending on your device and permissions, Dayily may read categories such as workouts, active energy, distance, heart rate, heart-rate variability, steps, sleep, respiratory rate, oxygen saturation, and body weight. Apple devices may also provide electrocardiogram summaries and wrist temperature when the device supports them. The exact data depends on your device, platform, permissions, and what your watch or band records.

Dayily uses these records on the device to build reports, show activities from other apps or devices, and look for a time-matched activity that can be shown with a Dayily workout. Health records are not used for advertising or marketing.

Dayily can also request separate permission to write a Dayily workout to Apple Health or Health Connect. That write is optional and is controlled by the platform permission you grant. Records already held by Apple Health, Health Connect, another app, or your device are managed by those services; Dayily does not claim ownership of or universal deletion control over them.

At present, health measurements read from Apple Health or Health Connect are used for local reports. The cloud sync is for Dayily workout and related journal data; it is not a general upload of your health database.

3. Accounts and cloud sync

You can use Dayily without an account. If you sign in and enable cloud sync, Dayily sends the account and journal data needed for that feature to its cloud service providers so your journal can sync across devices.

Cloud data can include workout sessions, exercise and set details, timestamps, notes, templates, favorites, and a body-weight snapshot associated with a workout. Your local history stays on your device and does not depend on network access. Free and Premium rules may limit cloud retention or sync, but they do not charge you for keeping your local workout history.

Deleting a Dayily account requests deletion of Dayily cloud data, the account used for Dayily sign-in, and the local profile and workouts. Re-authentication may be required. Data held independently by Apple Health, Health Connect, app stores, or other services must be managed there.

4. Diagnostics and support

Dayily uses service providers for crash reports, technical diagnostics, limited product analytics, and in-app feedback. They may receive information needed for those purposes, such as device, app, network, error, account, or feedback details. Feedback and screenshots are sent only when you choose to submit them.

Diagnostic and analytics events are designed not to include workout or health content, search strings, or passwords. Dayily does not use workout or health data for advertising or marketing. The public website does not add analytics, advertising SDKs, cookies, or tracking scripts.

5. Sharing and third parties

Dayily can create a local image of a workout or progress card and open the operating system’s share sheet when you choose to share it. The receiving app or service then handles the copy you send.

Dayily uses third-party providers for account sign-in, cloud sync, diagnostics, feedback, and limited analytics, including Firebase, Cloudflare, and Sentry. Apple Health and Google Health Connect provide the platform health data you authorize. Their own terms and privacy policies also apply. Dayily does not sell health or workout data or disclose it for advertising or marketing.

6. Your choices

  • You can use the core local journal without signing in.
  • You can grant, refuse, or later change Apple Health or Health Connect permissions in the platform settings.
  • You can turn off cloud sync by signing out; the local history remains on the device.
  • You can request account deletion from the account settings in the app.
  • You can send a privacy question to dayily.review@gmail.com.
  • For reproducible app bugs or feature requests, you can open a public issue at github.com/Preeternal/dayily-site/issues. Please do not include health data, passwords, or other sensitive personal information in a public issue.

Account deletion instructions: Delete your Dayily account.

We will update this page when the data practices materially change. The stable privacy URL is preeternal.github.io/dayily-site/privacy/.