Privacy
Privacy policy
Operational details for how DayKept handles local-first writing, limited telemetry and optional support contact.
Effective date: April 4, 2026
DayKept is a local-first personal archive. This policy explains what stays on your device, what limited operational signals may be measured, and what DayKept is designed not to collect.
1. Writing and search stay on-device first
Entries, titles, journals, tags, search and attachments stay on your device unless you explicitly create a backup bundle, use full archive export, share something out, or contact support.
2. Telemetry is designed not to collect archive content
DayKept is designed not to send journal content, full search text, snippets from entries or attachment names in app telemetry.
3. Limited operational analytics
The app may collect limited operational signals such as app version, locale, outcome buckets and coarse counts around search, backup, restore, export and purchase recovery.
4. Optional automatic backup copies on Android
If you enable Automatic backup copies on Android, DayKept uploads backup bundle copies to a visible folder in your own Google Drive. This is optional and does not sync your live archive across devices.
5. Website analytics
The public website may measure aggregate page views and CTA clicks for install, support and plan-comparison surfaces. The website does not receive journal content from the app by default.
6. Support contact
If you contact support, billing or privacy email addresses, DayKept receives the information you choose to send so the issue can be reviewed. Please do not send journal content unless support explicitly asks for it.
7. Your choices
You can keep, move, export or delete your archive using the tools available on your device and in the app.
8. Policy updates
If this policy changes in a material way, the updated version will be published on this page with a new effective date.
9. Contact
For privacy questions, contact [email protected].