Last updated: October 3, 2026
DayFlux is built on a local-first principle. Core timing calculations and normal app use happen on your device. On Apple devices, DayFlux may also keep an encrypted private iCloud/CloudKit backup so your durable DayFlux data can move to a new iPhone.
DayFlux uses profile information you enter, including:
This information is stored locally for normal use. On Apple devices, durable app data may also be stored in an encrypted field in your private iCloud/CloudKit database for device migration. DayFlux does not maintain a separate account database containing that backup.
DayFlux timing calculations, chart analysis, compatibility reads, and personalized timing reads are generated on your device. Your birth, chart, People, score, and personalized timing-read data are not sent to a DayFlux insight server or an external content-generation service. DayFlux does not require a DayFlux username, password, or account login.
Payments for DayFlux Premium are handled by Apple's App Store on Apple devices and Google Play on Android devices. We never see, store, or process your full payment-card information.
Subscription status and purchase entitlements are managed through RevenueCat, which uses a pseudonymous app-user identifier for entitlement verification and subscription lifecycle management. RevenueCat's privacy practices are documented at revenuecat.com/privacy.
DayFlux can send you one local notification per day, scheduled entirely on your device. These notifications do not involve our servers. You can disable notifications at any time in Settings.
DayFlux may send a limited set of pseudonymous product events to a privacy-focused analytics provider so we can understand activation, retention, subscription conversion, and sharing. Examples include app opens, onboarding completion, paywall views, plan taps, purchase outcomes, and share actions.
These events use a random install-scoped identifier generated by DayFlux. They do not include your name, birth date, birth time, birthplace, location, chart data, saved people, relationship labels, DayFlux score or tier, headlines, or insight text. When product analytics is enabled, the same random identifier may also be provided to RevenueCat and TelemetryDeck solely to associate subscription lifecycle events with product-usage events. DayFlux may also share Apple's privacy-preserving AdServices attribution token with RevenueCat so we can tell which Apple Ads campaigns lead to subscriptions. This uses Apple's AdServices framework, not the advertising identifier (IDFA), and does not track you across other companies' apps or websites.
DayFlux does not use advertising trackers and does not sell personal data.
DayFlux uses Expo's app-update service to check for and deliver app updates. When the app checks for an update, Expo may receive technical information such as your device's operating system, the app's version, and a random identifier created for this installation of the app. This information is used solely to deliver and manage app updates. It does not include your birth data, profile, chart data, saved people, or insight content.
DayFlux is not directed to children under 13. We do not knowingly collect information from children.
Deleting DayFlux removes the local app copy from that device. A private iCloud/CloudKit backup may remain associated with your Apple account for device migration and is subject to Apple's applicable controls.
Subscription records and pseudonymous analytics events may also persist with RevenueCat and TelemetryDeck according to their applicable retention and privacy practices. Store purchase records are also subject to Apple App Store or Google Play retention practices, depending on the platform. For privacy questions or requests, email us.
If we ever change this policy, we'll update the date at the top and post the new version at this URL. We will never change the policy to start collecting personal data without giving you the option to opt out.
Privacy questions: [email protected]
Support: [email protected]