What Daylogue reads, and what it never collects
No vague tiers. No marketing language. Here is the full inventory, item by item, including the parts that are less flattering to us.
The full picture, item by item
On the left, what Daylogue never collects. On the right, everything it reads. No exceptions on either side.
What you write is stored on our servers in readable form, protected in transit by TLS and by per-user access controls in the database, and entry text is kept out of Daylogue's application logs and error reports. Daylogue reads it to write your narratives. That is how the product works, and we would rather say so than imply otherwise.
What Daylogue never collects
Not a setting. Not a plan tier. It does not exist in the product.
How your face looks
Daylogue never analyzes your face or your expression to guess what you are feeling
How your voice sounds
Voice check-ins are transcribed into your words. The tone, pitch, and pace of your voice are never scored
Your location beyond weather conditions
Daylogue does not build a map of where you have been
Your contacts, camera roll, or other apps
Daylogue reads what you put into Daylogue. Nothing else on your device
A score of you as a person
There is no wellness grade, no composite person-score, no verdict on how you are doing overall
Anything sold to a data broker or advertiser
Daylogue makes money from subscriptions. Your entries are not the product
This means: there is no toggle to hunt for and no upgrade to buy. These things are not collected, so there is no version of Daylogue where a breach, a subpoena, or a change of ownership could expose them. Daylogue works only from what you choose to share.
What Daylogue reads
Stored server-side in readable form. This is what writes your narrative.
Your journal entries
The actual words you wrote, stored in readable form on our servers
Your check-in notes
What you typed or dictated during a check-in, including gratitude, wins, and challenges
Your voice conversation transcripts
What you said out loud in a voice check-in, transcribed into text
Your goal descriptions, habit notes, and focus area observations
The reflections you write about what you are noticing
Your mood, energy, stress, and sleep numbers
The scores and hours you reported
Your tags and themes
Labels like "work", "family", "stress", "gratitude"
AI-generated summaries and your daily narrative
Written from your words and stored in readable form, because the app has to show them back to you
Health metrics from a device you connect
Heart-rate variability and sleep quality are stored, and they are compared against the themes in your writing, so a theme can be flagged as landing on the days your body dipped
Pattern insights
Like your stress running higher on the nights you logged under six hours
Your chromascape color and soundtrack choices
The palette and song tied to each day
Weather data and check-in times
The conditions at your location when you checked in, and when each check-in happened
Your account email and subscription status
So you can log in and we can manage billing
Why does Daylogue need to see that second column?
Your daily narrative is written from your own words. There is no way to write it back to you without reading what you wrote.
Pattern detection compares your entries to each other over time. That is how it notices your stress running higher on the nights you logged under six hours.
Your chromascape maps mood and energy to color palettes. That mapping happens on our servers.
In short: everything in the right column exists because a specific feature you use depends on it. We do not collect data we do not use. We never sell it. We never share it with advertisers or third parties. We never use it to train AI models.
What one entry actually becomes
Say you write this in a check-in:
Your entry, as we store it
Your own words, kept on our servers in readable form
Exactly what you typed. Protected in transit by TLS and by per-user access controls in the database, and entry text is kept out of Daylogue's application logs and error reports, but readable to the systems that write your narrative.
AI-generated summary
What powers your narrative and insights
Condensed by AI. No specific names, no exact quotes, no private details.
Structured metrics
The numbers and tags extracted from your check-in
Numbers and categories. No context about who, what, or why.
One entry, three stored forms, all readable server-side. Nothing here was inferred from your face or from the tone of your voice. It all came from what you chose to write.
What happens if our database is breached?
Here is the honest answer, not the reassuring one. This is what an attacker would get:
No emotion scores read off your face or your voice tone
Daylogue never generates that data, so there is nothing there to take. Health metrics you connect are a separate matter: those are stored, and they are covered by the rest of this page.
Your entries, notes, transcripts, summaries, mood scores, tags, and narratives
Readable. An attacker who got into the database could read the words you wrote, not just a summary of them. Journal vault entries on accounts that have an encryption key are the exception: those are stored as ciphertext.
Your email address and subscription status
Readable. Same as any other service you have an account with.
The bottom line: your words are stored in readable form and a serious breach would expose them. What stands between an attacker and your entries is per-user access controls, row-level security, TLS, and the fact that entry text is kept out of Daylogue's application logs and error reports. Those are real protections, and they are not the same thing as a cryptographic guarantee. We would rather you knew the difference before you decided how much to write. We never sell your data to third parties. We never share it with advertisers. We never use it to train third-party AI models. Our only revenue is subscriptions.
You still own everything
Export your data anytime. Delete everything with a single request. Your data, your call.
Export anytime
Download all your data in JSON format with one click
Delete within 30 days
Request deletion and we remove everything
No shadow copies
When deleted, your data is gone from our systems
No surprises
We tell you exactly what we can see before you sign up
Your data lives here
On our servers, protected by TLS in transit and by per-user access controls. Yours to export or delete at any time.