Privacy Policy

Last updated: October 30, 2026

This privacy policy describes how DayOne ("we", "our", or "us") collects, uses, and protects information when you use our mobile application and how the DayOne website integrates audience measurement. We are committed to protecting your privacy and ensuring the security of your personal information.

Information we collect

Game lists, settings, Pro entitlement state, guided-tour status, and up to 1,000 recent action records are stored locally as JSON in AsyncStorage. This local data is not encrypted by the application. The server notification service synchronizes game lists and, when available, the backend receives your Firebase anonymous UID, push token, platform, locale, UTC offset, tracked and backlog game IDs, per-game reminder delays, status and timestamps, and manual removals. Firebase authentication requires no email or password, but its UID links server records and is not a guarantee of anonymity. The optional Google Drive sign-in is separate: it uses your Google email and access token for Drive and stores lists, game metadata, per-game reminder delays, and device sync metadata; language, theme, platform and genre filters, and global notification preferences remain local.

Permissions we request

The app may request notification permission and, where supported, exact-alarm access to deliver game reminders. Optional Google Drive access is limited to the private appDataFolder used for backups. Adding a game to a calendar opens the system event editor; older iOS versions (before iOS 17) may request calendar permission, while Android does not request calendar read/write permission. Haptics and keeping the screen awake support interface behavior. Store purchase access is used for DayOne Pro. Pro widgets share selected game titles, covers, dates and Pro status locally with the widget extension and can display them on the home screen.

How we use your information

Local state is stored as AsyncStorage JSON, without application-level encryption. Optional Google Drive backups are compressed and reversibly obfuscated with XOR using a SHA-256 value derived from your Google account email and a fixed salt; this is not strong or end-to-end encryption, and private appDataFolder access is not cryptographic exclusivity. We use backend data to schedule notifications, synchronize relevant game state, and validate Pro purchases through Firebase Cloud Functions.

Data sharing

We do not sell your information or share it for advertising. IGDB and the DayOne API provide game information. For server notifications and synchronization, our backend receives device details and tracked/backlog game data associated with a Firebase UID. Optional Drive backup sends backup and device-index data to Google Drive. Purchase validation sends a signed iOS transaction, or Android purchase token and product ID, together with the Firebase UID to Firebase Cloud Functions. The iOS function verifies and decodes the Apple-signed transaction; Android validation queries Google Play. Purchase records and technical validation logs are stored in Firestore.

Data security

Local JSON stored in AsyncStorage is not encrypted by the application. Google Drive backups are compressed and reversibly obfuscated with XOR using a SHA-256 value derived from your Google account email and a fixed salt; this is not strong or end-to-end encryption and private appDataFolder access is not cryptographic exclusivity. Network communications use HTTPS/TLS. Firebase Cloud Functions verify Apple signed transactions or validate Android purchases with Google Play; purchase and validation-log records are stored in Firestore. Deleting an individual game updates local data and, when synchronization or a new Drive backup runs, its removal can propagate to backend lists and Drive sync data. Uninstalling removes local app data only. Deleting Drive backups in Settings removes only the managed Drive backups. Neither action by itself deletes the Firebase identity or backend device, notification, purchase, or validation-log records.

Your rights

You can delete individual games and local app data, and you can delete Google Drive backups separately in Settings. Uninstalling removes local data only. To request access to or deletion of data associated with your Firebase UID on our backend, contact [email protected].

Purchase information

When you purchase DayOne Pro, purchase-related data includes the signed iOS transaction or the Android purchase token and product ID, your Firebase UID, validation status and entitlement information. Apple or Google processes the payment; local entitlement state is also stored in AsyncStorage.

Payment processing

All payment processing is handled securely by the app store (App Store or Google Play). We do not collect, store, or have access to your payment method details such as credit card numbers, billing addresses, or other financial information. Payment transactions are processed according to Apple's or Google's privacy policies and terms of service.

How we use purchase information

Purchase data is used to validate and maintain Pro entitlement and prevent invalid access. The app sends validation data and the Firebase UID to Firebase Cloud Functions; validation results, purchase records and validation logs are stored in Firestore, while entitlement state is also stored locally in AsyncStorage.

Purchase data sharing

Apple or Google processes the payment and receives the store transaction. For validation, purchase data and the Firebase UID are sent to our Firebase Cloud Functions. The iOS function verifies and decodes the Apple-signed transaction; the Android function validates the purchase with Google Play. We do not receive your card number or other payment-method details and do not sell purchase data.

Purchase data security

Purchase validation uses HTTPS to send the signed iOS transaction or Android purchase token, product ID, and Firebase UID to Firebase Cloud Functions. The iOS function verifies and decodes the Apple-signed transaction; the Android function validates with Google Play. Purchase records and technical validation logs are stored remotely, and entitlement state is stored locally in AsyncStorage without application-level encryption. Reinstalling does not reset a store purchase or erase remote records; eligible purchases can be restored through the same store mechanism.

Refunds and cancellations

DayOne Pro is a one-time lifetime purchase with no recurring subscriptions. Refund requests must be made directly through the App Store or Google Play Store according to their refund policies. We do not process refunds directly. If a store issues a refund, your Pro features may be disabled after purchase validation; immediate revocation is not guaranteed.

Third-party services

We use IGDB for public game information; the DayOne API for game data, notification scheduling and relevant game-state synchronization; Firebase for anonymous authentication, purchase validation and related records; Google Drive, when enabled, for private appDataFolder backups and device sync metadata; Expo for push delivery; Apple App Store or Google Play for payments; and YouTube for embedded trailers. Firebase verifies the Apple-signed iOS transaction, while Android validation queries Google Play. A Firebase anonymous UID links backend records and should not be understood as a guarantee of anonymity. Please consult each provider’s privacy terms.

Google sign-in and Drive backup

Signing in with Google is optional and enables Google Drive backup. It provides DayOne with the information needed for this feature, including your email address, Google identifier and access tokens. The profile provided may also include your name. Google processes technical information to handle authentication, prevent fraud and analyse how its service operates. These processing activities are described in Google’s Privacy Policy.

Google Privacy Policy

Technical analytics and logs

DayOne does not use Firebase Analytics. The server and Firebase retain technical logs needed to operate the service and validate purchases. Google’s sign-in service carries out its own technical processing and analytics, as described in its privacy policy. The app’s debug logs remain local unless you choose to share them with support. The website uses Vercel Analytics to measure its audience.

Data retention

Local lists and settings remain until you delete them or uninstall the app; local action history is limited to 1,000 records. During creation of a new Drive backup, deletion markers older than 30 days are filtered out; this does not guarantee timed deletion of older remote backup copies. Drive backups remain until removed through Settings or Google Drive. Uninstalling does not erase Firebase identity, backend device, notification, purchase or validation-log records. Contact [email protected] for access or deletion requests concerning backend-linked data.

Changes to this policy

We may update this privacy policy from time to time. Any changes will be reflected in the app with an updated "Last updated" date. Continued use of the app after changes constitutes acceptance of the updated policy.

Contact us

If you have any questions about this privacy policy or our data practices, please contact us at [email protected] or through the app store where you downloaded this application.