Privacy Policy

Information DayIn uses

Account information. If you create or use an account, DayIn uses your email address, account identifier, and display name. You can authenticate with email or Sign in with Apple when available. Apple supplies only the information you authorize it to share.

Account emails. Resend processes confirmation and password-recovery email addresses, message content, and delivery records. Its email-tracking features can also record opens and link clicks when enabled. Account emails support account access and recovery; they are not marketing messages.

Habit and readiness information. DayIn stores the habits you create, schedules, targets, reminders, goals, completion or progress records, and notes you enter. Readiness check-ins can include sleep quality, body state, mental load, and context tags.

Apple Health information. With your permission, DayIn reads the Health and activity types needed for features you enable, including sleep, heart-rate variability, resting heart rate, steps, and active energy. Requests depend on the habit or feature you choose. Raw daily Health summaries stay on your device. Health-derived habit records and readiness information can be included in cloud backup if you enable it. DayIn does not write to Apple Health.

Profile photo. A profile photo you choose is stored on your device in the current version.

Support email. If you contact support, DayIn and its email provider process your email address, message, attachments you choose to send, and email-delivery information. Please do not send passwords, reset links, access tokens, or detailed Health records.

Website connection information. The DayIn website does not currently contain account forms, advertising, or analytics scripts. Its hosting provider still processes ordinary connection and delivery information such as IP address, approximate location derived from IP, browser/request details, and service logs.

Website theme preference. The website stores your chosen light or dark theme in your browser so it stays selected between pages and visits. This preference stays in your browser and does not send personal information to DayIn.

How DayIn uses information

DayIn uses this information to authenticate accounts, provide habit tracking and readiness features, deliver reminders, provide optional cloud backup, respond to support requests, protect and operate the service, and comply with applicable obligations. DayIn does not sell personal information and does not use Health information for advertising or marketing. The current app does not use advertising or cross-app tracking SDKs.

Guest use and cloud backup

You can use DayIn as a guest without an account or time limit. Guest habit and readiness records stay on that device and are not enrolled in cloud backup. They can be lost if DayIn's local data is removed.

If you later sign in or create an account, DayIn transfers that installation's guest history into the account on the device. Password recovery alone does not transfer guest history. Cloud backup remains a separate choice.

Cloud backup follows the account's saved setting and is off by default for a newly encountered account. You can enable or disable it in Profile → Cloud backup. Enabling it sends the account's supported habit and readiness records to DayIn's backend. Disabling it stops future synchronization; it does not delete records already stored remotely. Account authentication still uses the network when cloud backup is off.

Service providers and processing locations

DayIn uses:

• Supabase for account authentication and optional cloud backup. DayIn's core database, Auth service, and backups are currently hosted in Supabase's selected eu-west-1 region in Ireland. Supabase documents that limited support, operational, and log processing can occur outside the selected region.
• Resend to deliver account confirmation and password-recovery emails. DayIn's sending region is configured as Ireland. Resend states that the sending region does not determine stored-data location and that stored data is held in the United States.
• Zoho Mail to receive and send messages at support@getdayin.app.
• Vercel to host the static DayIn website.
• Apple for Apple Health access and Sign in with Apple when available and when you choose those features.

DayIn requires service providers that receive personal information to give it the same or equal protection as described in this policy, under their applicable privacy and data-protection obligations.

Your choices

• Use DayIn locally as a guest without creating an account.
• Grant or decline Apple Health access, and change Health permissions in Apple Health or device settings. Manual habit tracking remains available without Health access.
• Turn future cloud synchronization on or off in Profile → Cloud backup.
• Export supported DayIn data from Profile → Export.
• Clear tracking history while keeping the account through Profile → Reset account. For a guest, Reset local history clears that installation's guest history.
• Delete an authenticated account through Profile → Delete account and confirm the request.
• Contact support@getdayin.app with a privacy request or question.

Retention and deletion

Local DayIn records remain on the device until you use the relevant reset or deletion control, delete DayIn and its local data, or erase the device. DayIn's protected local application storage is excluded from device backup. DayIn cannot remotely erase local-only guest data.

DayIn keeps an active account and records you choose to sync while the account exists. Confirmed account deletion removes the active authentication identity and associated DayIn cloud profile, habits, habit logs, goals, reminders, and readiness records. DayIn then removes that account's local records and queued synchronization operations. If local cleanup is interrupted, the app keeps a marker and retries. If a network interruption leaves the remote result uncertain, DayIn preserves local records and shows guidance rather than claiming deletion succeeded.

Reset account/history removes DayIn tracking records while preserving account access. Deleting a DayIn account does not delete original records stored by Apple Health; manage those through Apple Health and device settings.

Service providers can retain limited backup copies and operational, security, or delivery records under their applicable service and plan schedules. These periods can differ from removal of DayIn's active account records. Resend currently documents 30-day retention for email and log data and seven-day backup retention. Supabase backup and platform-log periods vary by plan. Vercel does not publish one fixed period for all operational records. Zoho Mail keeps active mailbox messages until they are deleted and can retain deleted or archived messages under the mailbox plan and administrator settings.

DayIn keeps support correspondence while needed to answer the request, maintain a useful support record, protect the service, or meet applicable obligations. You may ask DayIn to delete support correspondence by emailing support@getdayin.app; limited provider recovery copies or logs can remain for their applicable retention periods.

Changes and contact

DayIn may update this policy as the app, providers, or practices change. A revised policy will show a new effective date.

Privacy and support contact: support@getdayin.app

DayIn