Privacy Policy
Last updated: July 13, 2026
Daybrief turns your own calendar, email, and notes into a private morning audio briefing. That only works if we handle your data carefully, so here is exactly what we collect, what we do with it, and what we will never do with it — in plain language.
We will never collect your data to sell it, and we will never sell, rent, or trade your personal data to any third party. Not to advertisers, not to data brokers, not to anyone. Your data exists in Daybrief for one purpose: producing your own briefing, for you alone.
What we collect
- Account basics. When you sign in with Microsoft or Google, we receive your name and email address to create your account.
- Calendar and email (read-only). With your permission, Daybrief reads your calendar events and email so it can identify commitments, deadlines, and follow-ups. We request read-only access — Daybrief cannot send, modify, or delete anything in your accounts.
- Task creation (optional, the one write permission). If you choose Microsoft To Do as your checksheet destination, Daybrief asks for permission to create tasks — that's the only thing it writes, into a "Daybrief" list, only when you tap send. It never modifies or deletes your other tasks.
- Meeting transcripts (optional, read-only). If you enable Meeting insights, Daybrief also reads transcripts of your own Microsoft Teams meetings to brief you on decisions and commitments. This is off by default, requires a separate consent, and can be revoked the same way as everything else.
- What you tell it. Your preferences, goals, evening check-ins, calibration answers, and optional voice notes.
- Generated content. The briefing scripts and audio episodes Daybrief produces for you.
How we use it
- To generate your personal daily briefing — identifying action items, tracking what's slipping, and writing and voicing your episode.
- To improve your own briefings over time, using your feedback and check-ins. Your data is never used to build profiles of you for any other purpose, and never used to train general-purpose AI models.
Who processes it
Daybrief runs on servers hosted by Fly.io in Toronto, Canada. To analyze your items and produce audio, relevant content is processed by Google's Gemini API under its paid-tier terms, which do not permit Google to use that data to train its models. These providers act only as processors on our behalf — they are not given your data for their own use. No humans read your email or listen to your notes; the pipeline is fully automated.
Google user data — Limited Use
Daybrief's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the briefing features you see in the app, is never sold, is never used for advertising, and is never used to train generalized AI or machine-learning models.
Storage, retention, and deletion
- Data is encrypted in transit (TLS) and stored on encrypted volumes.
- Audio episodes are automatically deleted after 30 days. Transcripts remain so your library stays searchable.
- Disconnecting an account stops all syncing from it immediately. You can also revoke Daybrief's access at any time from your Google Account permissions or Microsoft account permissions page.
- To delete your account and all associated data, email us — everything (items, episodes, voice notes, preferences) is permanently removed.
What we share
Nothing, with three narrow exceptions: the service providers above (only to run the product), things you explicitly ask us to send (like a checksheet to your own inbox or task list), and if the law genuinely compels us. That's the entire list.
Changes
If this policy changes in any meaningful way, we'll tell you in the app before the change takes effect — no silent edits.
Contact
Questions, deletion requests, or anything else: me@sandenn.com. Daybrief is built and operated in New Brunswick, Canada.