AI that helps you reflect, not one that learns from you

Daylogue uses AI to spot patterns and prompt deeper thinking. Here's exactly how that works.

How AI processing works

A step-by-step look at what happens when you use AI features.

You write or speak

Your entry starts on your device, in your own words

Send to AWS Bedrock

Content sent securely over HTTPS

AI processes

Claude analyzes and generates response

The result is stored

Your narrative and insights are stored in readable form, so the app can show them back to you

Important disclosure

During AI processing, your content exists as readable text at our listed provider because the model has to read it. Provider handling follows Daylogue's current service configuration and written terms; see the Privacy Policy and subprocessor list for current details.

AI and your privacy

Everything you need to know about how we use AI.

01

How AI features work

When you use conversational check-ins or pattern detection, your content is sent over TLS to AWS Bedrock for processing. It reads your text and generates summaries, narratives, and insights. Those outputs are stored server-side in readable form, because your daily narrative and your pattern detection need them to be. Your entries themselves are also stored in readable form on our servers. Daylogue reads your entries to write your narratives. That is how the product works, and we would rather say so than imply otherwise. Journal mode, quick check-ins, QuickPulse, vision boards, and connections all work without any AI conversation at all.

02

Provider terms

Daylogue does not use personal entries to train AI models. Listed providers process the content needed for a requested feature under Daylogue's current configuration and written agreements. Current retention and training terms are maintained in the Privacy Policy and subprocessor list.

03

You choose how much AI you use

Daylogue works however you want it to. Write freely in journal mode. Log a quick mood with sliders or a single emoji tap. Use the vision board, track connections, build habits. None of that involves AI conversation. When you do want it, conversational check-ins, pattern detection, and your daily narrative are there. You can also set your conversation style to "Private journal" to turn off conversational AI entirely. Nothing that makes Daylogue useful is locked behind AI interaction.

04

What runs in the background

Here is what happens automatically: some lightweight processing runs when you check in, like suggesting tags for your entries. This helps organize your journal over time. You never have to accept those suggestions, and features like your narrative and "Between the Lines" insights are always optional to read. Nothing is forced on you. If you skip it, it just sits there quietly.

05

The honest limitations

During AI processing, your content exists as readable text at the provider. This is necessary for AI to work. Provider handling follows Daylogue's current service configuration and written terms; current details are maintained in the Privacy Policy and subprocessor list.

Our Commitments

What we promise

AI has real privacy tradeoffs. Here is what we commit to.

Daylogue does not use your content to train its own models; provider handling follows current written terms and subprocessor disclosures
Entry text is kept out of Daylogue's application logs and error reports
Provider retention and deletion follow the current service configuration, written terms, and subprocessor disclosures
We never run emotion recognition on your face or on the tone of your voice
AI outputs are stored on our servers in readable form, protected by TLS in transit and by per-user access controls, because your daily narrative needs them to be readable
You can export all AI-generated insights
You choose how much AI you engage with

AI for reflection

Patterns spotted. Insights generated. Then forgotten.

Process
Respond
Forget

AI Provider

AWS Bedrock (Claude) + ElevenLabs Conversational AI (voice)

Input/Output Logging

Entry text is kept out of Daylogue's application logs and error reports

Provider Handling

Governed by the current service configuration, written terms, and subprocessor policy

Transit Security

HTTPS (TLS) for all AI requests

Training Data

Governed by current provider terms and subprocessor disclosures

Emotion Inference

No emotion recognition from faces or voice tone

Storage of AI Output

Narratives, summaries, and insights stored in readable form

Note: A model has to read your text to work with it, so your words exist as readable text at our AI provider during processing, and they are stored in readable form on our servers afterward. HTTPS protects them in transit and per-user access controls separate them at rest, but no amount of encryption changes the fact that Daylogue reads what you wrote.

AI-powered, privacy-conscious

Reflection that understands you, without learning from you.