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.
Decrypt on device
Your encrypted entry is decrypted locally
Send to AWS Bedrock
Content sent securely over HTTPS
AI processes
Claude analyzes and generates response
Re-encrypt result
Response encrypted before storage
Important disclosure
During AI processing, your content briefly exists as readable text at our AI provider (AWS Bedrock). This is necessary for AI to work. It is not stored or logged, but we want you to know it happens.
AI and your privacy
Everything you need to know about how we use AI.
How AI features work
When you use AI features like conversational check-ins or pattern detection, your entry is first decrypted on your device. The content is then sent securely to AWS Bedrock for processing. The AI analyzes your text and returns insights. Finally, those insights are encrypted and stored just like your original entries.
Not used for training
AWS Bedrock, our AI provider, does not use customer inputs to train or improve their models. Your journal entries are processed to generate a response, then discarded. Your reflections remain yours alone.
Why AI is always on
AI is core to how Daylogue works. It powers your conversational check-ins, spots patterns across your entries, and prompts deeper reflection. This is not optional because these features define what Daylogue is. If you want journaling without AI, there are excellent alternatives.
The honest limitations
During AI processing, your content briefly exists as readable text in memory at AWS Bedrock. This is necessary for AI to work. The content is not stored, logged, or persisted, but it does exist in plaintext during processing. We believe you should know this.
What we promise
We are transparent about what AI can and cannot do for your privacy. Here is what we commit to.
AI for reflection
Patterns spotted. Insights generated. Then forgotten.
AI Provider
AWS Bedrock (Claude models)
Input/Output Logging
Disabled - no prompts or responses logged
Data Persistence
Content processed in-memory, not stored
Transit Security
HTTPS (TLS 1.2+) for all AI requests
Training Data
Customer inputs never used for training
End-to-End Encryption
Not possible for AI requests (plaintext required)
Note: True end-to-end encryption for AI requests is not possible because AI models need to read your text to process it. Transit encryption (HTTPS) protects data in transit, but the AI provider must be able to see the plaintext during processing.