Common questions about privacy

Quick answers to the things people ask most.

Click any question to see the answer. If you have a question not covered here, reach out to us.

Your entries are stored on our servers in readable form, protected in transit by TLS and by per-user access controls in the database. Daylogue reads them to write your narratives and surface your patterns. That is how the product works, and we would rather say so than imply otherwise. Staff do not have routine access to individual entries, and entry text is kept out of Daylogue's application logs and error reports. Where an account has an encryption key, journal vault entries on that account are additionally stored as AES-256-GCM ciphertext. Treat that as protection against storage-layer exposure, not as a guarantee that no one here could ever read your writing. Daylogue is not end-to-end encrypted, and your narratives, summaries and extracted metrics are stored in readable form regardless.

The short version

Daylogue never runs emotion recognition on your face or on the tone of your voice. Your entries are protected in transit by TLS and by per-user access controls, and entry text is kept out of Daylogue's application logs and error reports. Daylogue does read your entries to write your narratives, and we would rather say so. We do not sell your data. You can export or delete everything anytime.

Still have questions? We are happy to answer them.

Ready to journal privately?

Start today, knowing exactly what happens to what you write. No guessing at your face or at the tone of your voice.