Your journal. Your data. Period.
We built Daylogue for people who take their privacy seriously.
Privacy by design
These aren't afterthoughts. Here are the specific controls, and the specific limits.
We never read emotion off your face or your voice tone
Daylogue does not run emotion recognition on your face or on the tone of your voice. It works from what you choose to share: what you write, what you say, what your week looks like, what your body's doing. Body data sits alongside what you wrote — it might tell you your stress ran higher on the nights you logged under six hours. It will never tell you that you sounded sad.
Daylogue reads your entries. We would rather say so.
Your narrative is written from your words, and your patterns are found by comparing your entries to each other. That work happens on our servers, which means our systems read what you wrote. We would rather tell you that plainly than make a cryptographic promise you could disprove in an afternoon.
What actually guards it
Entries travel over TLS and ordinary account access is restricted with per-user database controls. Daylogue reads synced entries to provide narratives and patterns, so the service is not end-to-end encrypted. Legacy and additional encryption paths remain under coverage and key-custody review.
We sell subscriptions, not you
No ads. No data selling. No third-party trackers. We make money from subscriptions, not your emotional insights. Your data will never be sold to advertisers or anyone else.
Take it all with you
Export supported account data in the available formats. Account deletion begins with a 30-day grace period, then deletion from active product systems begins. Backup, processor, billing, audit, legal, and user-authorized Collab limits are described in the Privacy Policy.
How we protect you
Real commitments, not marketing badges. Here's what we actually do.
No Emotion Recognition
We never run emotion recognition on your face or your voice tone. Only what you choose to share
Logging controls
Controls are designed to reduce the risk that entry text appears in application logs or error reports; complete coverage is still being verified
No certification implied
Controls are described at their verified scope
Daylogue does not currently claim HIPAA compliance or a SOC 2 attestation
No Data Sales
We make money from subscriptions, never your data
Security measures we employ
Your data, your rights
You can use the available export, correction, and deletion controls, subject to the documented formats, timing, and retention limits.
Export
Download supported account data in the formats currently available
Delete Account
A 30-day grace period comes first; active-system deletion begins after it ends, with documented retention limits
Processing Details
See what each feature reads, why it reads it, and which listed processors are involved
Collection Limits
Current collection purposes and categories are described in the Privacy Policy
Your journal, your controls
Per-user access controls on every row. Export the whole archive whenever you want. Delete it for good when you ask.
How AI works with your privacy
AI is core to Daylogue. Here's exactly what happens when you use it.
When you use AI features
- 1Your entry is sent from your device over TLS
- 2Content is sent to AWS Bedrock for processing
- 3The model reads it and returns what it found
- 4The narrative or summary is stored on our servers in readable form
What we commit to
- Daylogue does not train its own models on your content; provider handling follows current written terms
- Logging and diagnostic controls are designed to reduce the risk that entry text appears in application logs or error reports; complete coverage is still being verified
- We never run emotion recognition on your face or the tone of your voice
- AI processing is ephemeral at our providers
- No AI mode stops newly submitted content from reaching our AI and voice services on supported platforms
During AI processing, your content briefly exists as readable text at our AI provider (AWS Bedrock). This is necessary for AI to work. Provider handling follows Daylogue's current service configuration and written terms; current details are in the Privacy Policy and subprocessor list.
Explore privacy topics
Dive deeper into how we protect your data.