Daybreak Privacy Policy
Daybreak is a local-first baby journal. We do not operate a Daybreak cloud account server that stores your journal. Most data never leaves your device unless you choose a backup or pairing feature.
1. Who we are
Daybreak is published by Luknai (“we”, “us”). This policy describes how the Daybreak mobile and web application (“App”) handles information. Website: https://www.luknai.com/.
2. What Daybreak stores
Depending on how you use the App, it may store on your device:
- Account details you create locally (for example email address, display name, and a password hash — not your plaintext password)
- Child profiles (name, date of birth, sex, birth measurements, diaper preferences, optional portrait photo)
- Care logs (naps, feeds, diapers, growth, photos, milestones, notes, pumping, medications, appointments and visit notes)
- Journal entries and milestone records
- App preferences (units, app lock PIN hash, backup reminders, widget summary labels)
- Technical identifiers needed for sync (for example a device id)
This information often relates to children. You are responsible for using Daybreak as a parent or caregiver and for any consent required in your jurisdiction to keep records about a child.
3. How data is processed
3.1 On-device processing
Core features — logging, timeline, development guidance, milestones, and charts — run on your device using an on-device database. Bundled developmental content is shipped with the App and evaluated locally.
3.2 Encryption
When you are signed in, journal rows and photos may be encrypted at rest on the device with a key derived from your Daybreak password. Encrypted backup files are always encrypted before they leave the device.
3.3 App lock
Optional app lock uses a PIN you set (stored as a hash) and, if you enable it, your device’s biometric unlock. Biometric data is handled by the operating system; Daybreak does not receive fingerprint or face templates.
4. Features that can leave your device
Only if you use them:
- Local / downloaded backups. You can save an encrypted backup file on the phone or download it. Anyone with the file still needs your Daybreak password to open it.
- Google Drive backup (optional). If you connect Google, Daybreak uploads an encrypted backup to
your Google account’s app data folder using Google OAuth and the Drive API (
drive.appdatascope). We do not receive your Google password. Google’s processing is governed by Google’s policies. You can disconnect in the App; you may also remove app data via your Google Account settings. - Device pairing / sync. You may pair another device you control (for example phone ↔ phone or phone ↔ laptop) over a direct connection (Nearby on Android, or WebRTC). Pairing requires explicit Share/Find actions and a mutual pair code. Journal data is exchanged between your devices; it is not uploaded to a Daybreak server.
- Checkup summary export. You may export a readable HTML summary to share with a clinician or caregiver. That file is not encrypted like a backup — only share it with people you trust.
- Home screen widget. A small plaintext snapshot (child first name and relative “last nap/feed/potty” labels) may be written for the widget. It does not include notes, photos, or date of birth.
5. What we do not do
- We do not sell your personal information.
- We do not show third-party advertising in the App.
- We do not operate a Daybreak backend that stores your journal contents.
- We cannot reset a forgotten Daybreak password. Recovery requires a backup you made or a device you already paired.
6. Children’s privacy
Daybreak is intended for parents and caregivers to keep records about babies and young children. It is not directed at children as primary users. Information about a child that you enter is stored under your control on your devices and in destinations you choose (backup/pairing). If you believe a child’s information was entered without appropriate authority, delete it in the App and remove backups you control.
7. Data retention and deletion
Data remains until you delete it in the App, clear the App’s storage, uninstall the App, or delete backup files and paired copies you control. Uninstalling removes on-device data for that installation (subject to your OS). We do not hold a separate cloud copy to delete on request because we do not host your journal.
8. Security
We design Daybreak around on-device storage, password-based encryption for backups, and explicit pairing confirmations. No method of electronic storage is perfectly secure. Protect your device lock screen, Daybreak password, and backup files.
9. International users
Processing primarily occurs on your devices and, if you opt in, on Google’s infrastructure for Drive. If you are in the EEA/UK or another region with privacy rights, those rights may include access, deletion, and objection — exercised through the controls on your device and Google Account, since we do not hold a hosted copy of your journal.
10. Changes
We may update this policy as the App changes. We will revise the effective date above. Continued use after changes means you accept the updated policy.
11. Contact
Privacy questions about Daybreak: contact Luknai via https://www.luknai.com/ (use the site’s contact options) and mention “Daybreak privacy”.