Daylogue shows leaders what is affecting the work, never who is struggling. Aggregate themes and participation only. Never a person, never below five people, never used for employment decisions. This page explains the boundary in plain language.
What leaders see
- Qualifying work-context themes across the team.
- Participation rates. How many people checked in, not who.
- Whether a qualifying theme is new or recurring.
- Group summaries with no person-level drill-down.
What stays private
- Your individual check-in content. Every word.
- Journal entries and personal reflections.
- Voice transcripts from voice check-ins.
- Individual mood, energy, stress, or personality results.
- Your personal narrative and chromascape.
- Which channel you use to check in (app, voice, or SMS).
- Your participation mode choice.
k-Anonymity
We require at least five eligible contributors before showing aggregate themes or participation. If the group is too small, leaders see nothing rather than risk identifying a person. No exceptions.
Encryption
Your check-in content is protected in transit by TLS and by strict per-user access controls, and entry text is kept out of Daylogue's application logs and error reports. Your leader never sees it. Daylogue is not end-to-end encrypted: our servers read check-in content in order to write narratives and surface patterns.
Your control
You choose your participation mode. You can change it anytime. You can delete your account and all data at any time. No questions, no waiting period.
AI processing choices
An organization can prohibit AI processing for organization-scoped activity. It cannot turn AI on for an individual or see an individual’s personal No AI setting. Personal activity outside the workspace follows the individual’s own setting. Content protected by either boundary is never backfilled later.
Daylogue is built around a simple privacy principle: how someone feels is not a management data stream. Enterprise features exist to help teams thrive, not to monitor individuals. If that ever changes, Daylogue has failed.
