Privacy Policy

We collect only what's necessary to provide our service. Here's exactly what we store:

Account Information: Your email address, profile fields, and authentication records. Email and necessary account identifiers are stored in readable form. Password handling is provided through the authentication service; Daylogue does not store a readable copy of your password.

Journal Entries & Check-in Notes: Your journal entries and check-in notes 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.

AI-Generated Summaries & Insights: When you use AI features, Daylogue generates summaries, narratives, and pattern insights from your check-ins. These AI-generated outputs are always stored in readable form, not encrypted, because they power features like your daily narrative, weekly insights, and pattern detection.

Structured Metrics & Metadata: Mood scores, energy levels, stress ratings, sleep data, tags, timestamps, and device identifiers. This structured data powers your dashboards, trends, and AI features. It is protected by per-user access controls and row-level security, and it is stored in readable form.

Legacy and Additional Encryption: Some account and vault paths contain additional encryption components. Coverage and key custody are being re-verified, so Daylogue does not present those components as a user-selectable setting, end-to-end encryption, or protection for every entry. Users should assume synced content is readable by the service.

We use your information to:

• Provide the core journaling and check-in experience
• Generate AI-powered insights and pattern detection
• Send reminders and notifications (with your permission)
• Respond to support requests
• Improve and maintain our services
• Prevent abuse and ensure security

**We never use your data for:** - Advertising or ad targeting - Selling to third parties - Training Daylogue's own models on your personal entries - Uses outside the purposes described in this policy and the choices presented in the product

Your privacy is protected by several concrete controls:

Encryption Scope: Daylogue is not end-to-end encrypted. Some legacy account and vault paths contain additional encryption components, but coverage and key custody are still being re-verified. We do not present them as protection for every entry or as a setting that makes synced content unreadable to Daylogue.

What Our Servers Read: Daylogue reads your entries to write your narratives, detect patterns, and generate summaries. That processing happens on our servers. AI-generated summaries, narratives, and structured metrics are stored in readable form because the features you use depend on them.

No Emotion Inference: Daylogue does not run emotion recognition on your face or on the tone of your voice. It works only from what you choose to share.

Transmission Security: All data in transit is protected by TLS.

Diagnostics: Daylogue uses redaction and production logging controls to reduce the risk that sensitive content reaches application logs and error reports. Coverage is tested, but this is a control rather than a guarantee that no defect or third-party failure can ever expose content.

Standards and Certifications: Daylogue does not currently claim HIPAA compliance, a SOC 2 attestation, NIST alignment, ISO 42001 alignment, or a Business Associate Agreement for general customers. A vendor certification or internal roadmap is not a Daylogue certification.

AI is core to Daylogue's insights. Here's exactly how it works:

How AI Processing Works: 1. When you use AI features, your content is sent to our AI provider (AWS Bedrock) for processing 2. AI generates insights, summaries, and narratives 3. AI-generated summaries are stored server-side to power features like your daily narrative, pattern detection, and insights 4. Your entries and generated outputs remain on Daylogue systems in server-readable form; legacy and additional encryption paths do not change that baseline

Important Disclosures: - During AI processing, your content briefly exists as readable text at AWS Bedrock - Daylogue does not use personal entries to train its own models. Provider handling is governed by the current service configuration, written terms, and subprocessor disclosures - Voice check-ins can use Deepgram for speech-to-text, ElevenLabs for conversational voice, and AWS Bedrock for AI processing; current processing roles are listed on our subprocessor page - AI-generated summaries are stored in readable form, because they are needed server-side for features you use - Daylogue does not run emotion recognition on your face or on the tone of your voice. It works only from what you choose to share

No AI mode: On supported accounts and platforms, No AI mode prevents newly submitted content from being sent to Daylogue's AI and voice services. It is not a local-only or end-to-end-encrypted mode: entries still sync to and are stored by Daylogue on the terms described above. Rules-based patterns require a separate choice, use structured fields and eligible accepted manual tags, and omit sensitive tags. Turning AI features back on applies only to future content; protected content is not backfilled.

Daylogue does not sell personal data. Disclosed service providers process data to operate requested features.

Our Data Trust Promise: - We do not sell personal data - We do not disclose personal entries to advertisers or data brokers for their own advertising - We do not use personal entries for ad targeting - Daylogue does not use your personal entries to train AI models; providers are governed by the current terms and agreements listed on our subprocessor page - Our revenue comes from subscriptions only - You can request account deletion at any time; the phased lifecycle and exceptions are described below

Service Providers: We use subprocessors to deliver the service. The current list describes each provider, its role, the data categories it can receive, and when it is used. See [/subprocessors](/subprocessors).

Legal Requirements: We may disclose information if legally required (e.g., court order). Journal entries and check-in notes are stored in readable form and can be provided in response to valid legal process, like any other data we hold. Where an account has an encryption key, you should not assume that vault storage puts that content beyond legal process; encryption is not a guarantee of immunity from it. AI-generated summaries and structured metrics are always stored in readable form and can be provided if legally compelled.

Business Transfers: In an acquisition, merger, financing, reorganization, bankruptcy, or sale of assets, information may transfer as part of the transaction subject to applicable law and the notices and choices then required.

Not disclosed for third-party advertising: Daylogue does not disclose journal content, AI outputs, or personal reflections to advertisers or data brokers for their own advertising. This does not prevent disclosed service-provider processing, a transfer you direct, legal process, or a business transfer described in this policy.

Social Sharing (Insight Cards): When you choose to share an insight card, Daylogue generates a static image containing a visual summary of your data (e.g., color palettes, mood gradients, wellness labels). These images never contain raw journal text, specific dates, or personally identifiable information. Share images include subtle Daylogue branding. Once you share an image outside Daylogue (via social media, messaging, etc.), that content is outside our control and subject to the receiving platform's policies. We log share events (card type, aspect ratio, platform) to improve the feature. No third-party tracking SDKs are used for sharing.

Daylogue offers optional organization and team features for workplaces, sports teams, and other groups. Here is how your data is handled in those contexts.

Aggregate Data Access: Employer-context administrators can view eligible aggregate self-reported trends, subject to contributor thresholds and suppression rules. The general floor is five eligible contributors; averages and intersections require ten, and protected populations or organization settings may require more. These controls reduce reidentification risk but do not make reidentification impossible. Employer-context administrators are not given access to journal entry text, transcripts, individual scores, or individual participation histories through the aggregate dashboard. Other roles, including a person a member separately authorizes through Collab, have different access rules disclosed at the point of consent.

Individual Score Sharing: Members who join an organization can optionally choose to share their individual wellness scores (mood, energy, stress) with organization leaders. This sharing is: - Entirely voluntary and opt-in - Controllable per metric (you can share mood but not stress, for example) - Revocable at any time through your settings - Limited to the past 7 days of scores (leaders cannot see historical data, written reflections, or voice entries) - In a Collab solo practice, the same controls also cover theme words drawn from a fixed vocabulary we maintain, and a count of check-ins since your last session. A provider never receives a check-in date or time, and never your own wording.

API Access: Enterprise organizations may access aggregate data and, where members have opted in, individual scores through authenticated API endpoints. All API access is: - Authenticated via organization-specific API keys - Rate-limited and monitored for abuse - Logged for compliance auditing - Scoped to specific data types (an API key cannot access more than what was granted)

Webhook Data Transfers: Organizations may configure webhooks to receive automated notifications about organizational events (such as wellness alerts or weekly report availability). Webhook data: - Contains aggregate information only (no individual data is sent via webhooks) - Is signed with HMAC-SHA256 so the receiving server can verify authenticity - May be delivered to URLs specified by the organization administrator - Delivery is logged for audit purposes

API Request Logging: We log API request metadata including client IP addresses, user agent strings, and request timestamps for security monitoring, abuse prevention, and compliance auditing. These logs are retained for 90 days.

Peer Feedback (Appreciation, Constructive, Concern): Workplace organizations may enable peer feedback, which lets members send feedback to one another in three lanes. Each lane has a different visibility model: - **Appreciation** is private to the recipient by default. Designated reviewers and organization administrators are notified that a note was sent and can see the sender, recipient, lane, and date — but not the body. Senders can optionally choose at submission time to share an appreciation note with team admins, in which case admins can also read the body in their reviewer dashboard. - **Constructive feedback** is visible to the recipient and to designated reviewers (which typically includes organization owners, admins, and coaches). The body of the message is visible to those reviewers as part of the moderation flow. - **Concern reports** are visible to designated reviewers. The body is not shown to the recipient.

For all lanes, designated reviewers can read message bodies they are authorized to see, update case status, and (for constructive and concern) participate in a moderated thread with the sender. Anonymous submissions are supported where the lane allows it; anonymous senders are not linked to a user account in the submission record. Submissions are retained per lane for the period configured by the organization (defaults: appreciation 365 days, constructive 730 days, concern up to 7 years for compliance retention).

AI-Generated Content: Team narrative summaries provided through the API are generated by AI from anonymized aggregate data. They are not clinical assessments and should not be treated as medical, psychological, or diagnostic information.

When you leave an organization (voluntarily, via admin removal, or via SCIM offboarding), your personal check-in history and account remain intact. Your past contributions to team aggregates are frozen in the historical windows they belonged to — they are not removed retroactively, to preserve the statistical integrity of those aggregates for the remaining team members. Going forward, your data no longer contributes to team averages. You can export your data at any time from Settings → Privacy → Export.

If you are a California resident, the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA) give you specific rights regarding your personal information.

Right to Know: You have the right to request disclosure of what personal information we collect, use, disclose, and sell about you.

Right to Delete: You have the right to request deletion of personal information we have collected from you, subject to certain exceptions.

Right to Opt Out of Sale or Sharing: We do not sell or share your personal information for cross-context behavioral advertising. You can still record an opt-out through the "Do Not Sell or Share My Personal Information" footer link, which disables marketing tracking. We honor Global Privacy Control (GPC) signals as a valid opt-out request.

Right to Correct: You have the right to correct inaccurate personal information we hold about you.

Right to Limit the Use and Disclosure of Sensitive Personal Information: Under CPRA, you have the right to limit our use of sensitive personal information (SPI) to what is necessary to perform the service. Daylogue collects the following categories of SPI: (1) voice audio and transcripts from voice check-ins; (2) self-reported wellness data (mood, energy, stress, sleep) and AI-generated inferences derived from your check-ins, which may reveal information about your mental or physical condition; and (3) precise geolocation when used for weather and context personalization. We use this SPI solely to provide the service you signed up for. We do not use SPI to infer characteristics about you for any other purpose, and we do not sell or share SPI. To exercise the right to limit, email privacy@daylogue.com with "Limit Sensitive Personal Information" in the subject line, or use the "Limit the Use of My Sensitive Personal Information" link in our footer.

Right to Non-Discrimination: We will not discriminate against you for exercising any of your CCPA/CPRA rights.

Rights of Minors (Ages 13–16): For California residents between the ages of 13 and 16, we do not sell or share your personal information without your opt-in consent. We do not knowingly collect personal information from users under 13 under any circumstances.

Data Retention: We retain personal information for service delivery and for documented security, billing, audit, legal, and operational needs. A deletion request has a 30-day grace period; after that period Daylogue begins deletion from active product systems. Limited copies may remain temporarily in backups or with processors, and records subject to billing, security, audit, legal, or separately authorized Collab custody may follow different retention duties. Voice providers process audio under the current terms and configuration listed on our subprocessor page.

CA AB 2013 AI Transparency: Daylogue does not use your data to train Daylogue models. External inference is governed by the current provider terms and configuration listed on our subprocessor page.

How to Submit a Request: Use our privacy request form at /privacy/request, or email privacy@daylogue.com with "California Privacy Request" in the subject line. We will respond within 45 days.

Users in Washington State, Nevada, and Connecticut have additional rights under state consumer health data laws.

Applicable laws: Washington My Health MY Data Act (WMHDA, RCW 19.373), Nevada SB 370 (NRS Chapter 629), Connecticut SB 3.

Information we treat as potentially covered: For this policy and rights process, Daylogue treats self-reported check-in scores, some voice transcripts, some AI-generated narratives, and derived pattern data as potentially covered consumer health data. Whether a particular record has that legal classification depends on the information, how it is used, your location, statutory definitions, and applicable exceptions.

Potential state rights: Depending on your residence, the data involved, and whether a law applies to Daylogue, you may have rights to access, delete, correct, obtain a copy of, or withdraw consent for covered consumer health data, and to appeal certain decisions. Definitions, exceptions, verification requirements, and response periods vary by jurisdiction. This section is being reviewed with outside counsel and does not narrow any right provided by applicable law.

How we use potentially covered data: We use it to provide requested features, maintain security, comply with legal obligations, and support the other purposes disclosed in this policy. We do not sell personal data or use personal entries for advertising. Employer-context dashboards are designed not to display individually identifiable entries, transcripts, scores, or participation histories; separately authorized sharing and other institutional roles follow their own disclosed access rules. If you decline health-data collection in-app, mood, energy, stress, and sleep scores will not be collected during check-ins, and voice check-ins will be unavailable while that preference is active. Your choice is remembered across sessions and can be changed at any time in Settings > Privacy & Security. Crisis resources remain available regardless of your consent state.

No AI mode and consumer health data: No AI mode is separate from collection consent. On supported accounts and platforms it prevents new content from being sent to Daylogue's AI and voice services, but it does not keep entries only on your device. Entries and structured fields still sync to and are stored by Daylogue. Rules-based patterns require a separate choice and omit sensitive manual tags. Turning AI back on does not backfill content protected while No AI mode was active.

To exercise these rights: Email privacy@daylogue.com with "Consumer Health Data Request" and your state of residence in the subject line.

Full policy: Consumer Health Data Privacy Policy (available at security@daylogue.com on request).

If you are located in the European Economic Area, the United Kingdom, or Switzerland, the General Data Protection Regulation (GDPR) and applicable national law govern our processing of your personal data.

Legal basis for processing: We process your personal data on the basis of: - Your explicit consent (Article 6(1)(a)) for check-in data, AI processing, and optional features - Contract performance (Article 6(1)(b)) for account management and service delivery

Article 9 special-category data: Self-reported check-in scores and wellness narratives may qualify as data concerning health under GDPR Article 9. We process this data only with your explicit consent, which you give at the time you complete a check-in. You may withdraw this consent at any time in Settings > Privacy & Security.

AI interaction disclosure: Daylogue identifies AI conversations as interactions with an AI system rather than a human. The exact jurisdictional disclosure language remains subject to outside-counsel review.

Your GDPR rights: Right to access, right to rectification, right to erasure ("right to be forgotten"), right to restriction of processing, right to data portability, right to object, right not to be subject to solely automated decision-making.

How to exercise your rights: Email privacy@daylogue.com with "GDPR Data Request" in the subject line. We will respond within 30 days.

Data transfers: Daylogue and its processors may process data in the United States and other locations identified in current provider documentation. Transfer mechanisms and contractual coverage are being verified by provider and processing path; contact privacy@daylogue.com for the current scoped answer.

You have access to the following account controls, subject to the formats, timing, and limits described here:

Export: Download the account data and formats currently supported by the export tool from account settings.

Delete: Request account deletion at any time. A 30-day grace period follows, during which you can cancel. After that period, Daylogue begins deletion from active product systems. Limited copies may remain temporarily in backups or with processors, and billing, security, audit, legal, or records held by a separately authorized Collab recipient may follow different retention duties. The current lifecycle and exceptions are described in our deletion documentation and in the product before confirmation.

Access: Request a copy of all data we hold about you.

Correction: Update your account information at any time.

Opt-Out: Unsubscribe from marketing emails anytime. Essential service communications (security alerts, account issues) cannot be opted out of while your account is active.

To exercise these rights, email privacy@daylogue.com or use the in-app settings.

Program Name: Daylogue SMS Check-ins

What It Is: When you opt in through the Daylogue app, we send text message check-in prompts to your phone number. You reply with how you're feeling, and your response is processed as a check-in. You can also opt in to SMS notifications (reminders, weekly summaries, and gentle nudges).

Message Frequency: Up to 5 messages per day (1 outbound prompt plus up to 4 conversational follow-ups per session). Notification texts are sent based on your chosen schedule.

Message and Data Rates: Standard message and data rates may apply depending on your mobile carrier plan.

Opt-In: You opt in to SMS check-ins exclusively through the Daylogue app settings by entering your phone number, verifying it with a one-time code, and toggling on SMS check-ins. SMS is off by default. No messages are sent until you explicitly opt in. There is no web form, keyword, or checkout-based enrollment.

Opt-Out: You can stop receiving messages at any time by replying **STOP** to any message, or by toggling off SMS check-ins in your Daylogue app settings.

Help: Reply **HELP** to any message for support information, or contact us at hello@daylogue.io.

Your Phone Number and Mobile Information: We store your phone number solely for delivering SMS check-ins. No mobile information, including phone numbers, SMS consent records, and opt-in/opt-out data, will be shared with or sold to third parties or affiliates for marketing or promotional purposes. Your number is stored securely and used only to deliver the messages you requested.

AI-Personalized Messages: Some SMS check-in messages are personalized using AI. When this occurs, eligible context from recent check-ins may be sent to the AI provider to generate an opening message. Provider storage, retention, and training handling follow the current service configuration, written terms, and subprocessor disclosures. Other messages use standard templates without AI personalization.

Crisis resource handling: Daylogue uses automated language matching to decide when to display crisis, personal-safety, or harm-to-others resources. Matching can miss language or display resources when they are not needed. It does not diagnose depression, assess suicide or violence risk, predict behavior, determine that a person is in crisis, or investigate a disclosure.

Detection of crisis content is automated using rules-based matching and, when AI processing is enabled, AI-assisted review. No human routinely reviews message content as part of that automated flow; authorized support, security, legal-process, or incident-response access is governed separately.

When the automated system identifies covered language, it is designed to show official resources and end the ordinary check-in flow. Daylogue does not automatically notify an employer, school, organization, trusted contact, crisis service, law enforcement, or emergency service, and it does not submit a workplace or school concern on your behalf. The automated match does not create a routine human-review queue. Legally valid compulsory requests are handled separately under applicable process.

On supported authenticated web and iPhone check-ins, the triggering words are not saved as a normal check-in by default. You may review the exact words and choose to keep them in a separate private note. Private excluded notes do not enter patterns, Your Story, Reads, mood trends, summaries, reminders, exports, organization reporting, concern reports, or future AI context. Daylogue stores a separate content-free safety event—such as resource mode, platform, detector version, and resource interaction—for no more than 90 days. It does not contain the triggering words, names, calendar information, organization ID, pattern IDs, model reasoning, or an inferred diagnosis. Organization-facing member, coach, and administrator views omit safety events and private excluded notes. Separately authorized Daylogue support, security, incident-response, and legal-process access follows the scoped controls and disclosures described in this policy; a person may also choose a separate sharing path where the product offers one.

Daylogue does not send crisis-triggered follow-up email, SMS, or push messages. SMS and email content remains subject to the separately disclosed transport-provider and delivery-system processing needed to receive and respond to a message.

Service Provider: SMS messages are delivered through Twilio, our messaging infrastructure provider. Twilio processes your phone number and message content only as necessary to deliver the service.

Delivery: Carrier and destination support varies. Messages can be delayed or undelivered.

We use minimal, necessary cookies and disclose every tracking tool we run:

Essential Cookies: Keep you logged in, remember your preferences, and protect against CSRF and other security threats. These cannot be disabled without breaking core functionality.

Analytics — Google Analytics 4 (public site only): On public marketing, paid landing, and signup pages, we use Google Tag Manager to govern Google Analytics 4 (measurement ID G-0QB3RW6GN5), operated by Google Ireland Limited for EU/UK visitors and Google LLC for other visitors. All Google analytics and advertising storage starts denied. Before you choose, Google may receive limited cookieless measurement signals under Advanced Consent Mode, but Google Analytics cookies are not set. If you grant analytics consent, GA4 may set cookies named `_ga` and `_ga_*` to measure broad traffic, referral sources, and page performance. Ads storage and advertising-personalization signals remain denied unless you separately grant marketing consent. We have configured ads-data redaction and disabled Google Signals. Data retention is set to the minimum (2 months).

GTM and GA4 do **not** run on authenticated Daylogue product routes. They do not receive journal entries, check-in text, mood, voice content, health information, names, email addresses, or account identifiers. You can change or revoke consent at any time from our [cookie policy](/cookies) page; we immediately return the affected storage signals to denied and expire the related Google cookies. If your browser sends Global Privacy Control or you enable Do Not Sell or Share, we suppress GTM entirely and stop marketing attribution.

What We Don't Use: - Third-party advertising cookies - Cross-site tracking pixels - Social media tracking pixels - Fingerprinting techniques - Any analytics inside the authenticated product

You can also control cookies through your browser settings.

Daylogue is not intended for children under 13. We do not knowingly collect personal information from children under 13. If you believe we have inadvertently collected such information, please contact us immediately at privacy@daylogue.com and we will delete it.

We may update this policy to reflect changes in our practices or for legal reasons. When we make material changes:

• We'll post the updated policy here with a new "Last updated" date
• We'll notify you via email for significant changes
• Continued use after changes constitutes acceptance

We encourage you to review this policy periodically.

Questions about privacy? We're here to help.

Email: privacy@daylogue.com

Response Time: We aim to respond within 48 hours.

Data Protection: For data protection inquiries or to exercise your rights, email privacy@daylogue.com with "Data Request" in the subject line.

Address: Daylogue LLC Los Angeles, CA United States