privacy policy.

dayCday is a local-first decision-tracking app. The app is designed so your decision content stays on your device: decision titles, options, answers, notes, close reasons, settings, reminder schedules, and profile name are stored locally in the app.

The current mobile builds may include limited product analytics and crash/performance diagnostics so we can understand whether onboarding, reminders, and check-ins are working and what needs to be fixed before wider release.

The app stores the following information on your device:

• decision titles, options, answers, notes, and close reasons;
• your check-in cadence, reminder state, deadlines, and notification preferences;
• local onboarding and app settings, including the profile name you enter.

We do not operate account login, cloud sync, remote backup, payment, advertising, AI-processing, or remote push-notification services for this version.

The mobile apps may send limited telemetry for product analytics, crash reporting, performance diagnostics, and release quality monitoring.

Product analytics are used to understand broad app usage and improve the release. For example, this can include app opens, onboarding completion, that a decision was saved, whether a decision reaches a second check-in, or whether a local notification led to a check-in.

Current diagnostics may include crash reports, error context, performance traces, app version, build number, platform, release environment, and technical device or app information needed to diagnose failures.

Your decisions remain private. We do not intentionally send decision titles, option text, notes, custom prompt copy, profile name, close reason text, check-in answer content, or free-form decision content through these analytics or diagnostics events.

If you choose to share, export, screenshot, back up, or otherwise move information out of the app, the destination app, operating system, or backup provider may handle that information under its own terms and privacy policy. dayCday does not control those destinations.

dayCday uses local notifications for decision check-ins. This version does not use remote push notifications and does not register a remote push token with a dayCday server.

If future versions add accounts, sync, cloud services, AI features, payments, advertising, new telemetry, or other remote services, we will update this policy and any required store disclosures.

For privacy questions or requests, email [email protected].