Chris Hornung, MD

Daily Brief

Daily Brief Privacy Policy

Effective date: October 2, 2026

This policy covers Daily Brief, a personal application operated by Chris Hornung, MD, and its informational pages on chrishornungmd.com.

Information accessed and collected

With Google account authorization, Daily Brief accesses Google Calendar using read-only permission. It retrieves events from configured calendars available to that account and extracts event titles, start dates and times, and all-day status for the daily brief. Google may return additional event metadata in the API response; the current brief uses the fields listed above.

The app stores OAuth authorization tokens locally to maintain the connection. It may also combine calendar events with locally configured tasks and other daily information.

How information is used

Calendar information is used to prepare and deliver a personal daily overview. Daily Brief does not create, edit, or delete Google Calendar events. Calendar information is not used for advertising, sold, or used to train general-purpose AI models.

Storage and retention

Original calendar records remain in Google Calendar, on Google’s infrastructure. The local Daily Brief installation also saves authorization tokens, collected brief data, and the formatted brief on the operator’s computer. These local files are retained until replaced during subsequent runs or deleted by the operator; the app has no automatic retention deadline. Delivered copies may remain in the configured messaging or email service and its backups according to that service’s settings.

Revoking authorization stops future access but does not automatically remove existing local files or delivered messages.

Sharing and service providers

Daily Brief communicates with Google to retrieve authorized Calendar data. The generated brief is sent to the configured recipient through Apple Messages (iMessage), or through the configured email service when email delivery is used. Those providers process the information needed to deliver and store the message. Calendar data is not published on this website.

The current local Calendar collection and brief formatting code does not send calendar data to an AI provider. The Daily Brief informational pages contain no analytics scripts, account sign-in, or data-entry forms. The website hosting provider may process ordinary request information, such as IP addresses, to serve these pages.

Access and security

Google authorization controls Calendar access. Local tokens and brief files rely on the operator’s device and account protections. Anyone with access to those files may be able to view brief data or use saved authorization credentials. No credentials or calendar records are included in these public webpages.

Your choices and deletion

You can stop using Daily Brief and revoke its access through your Google Account’s third-party connections. To remove saved copies, delete the local authorization token and generated brief files, and remove delivered messages from the relevant messaging or email service. To request help with access or deletion, contact chrishornung14@gmail.com. Deleting Daily Brief files does not delete your original Google Calendar events.

Google API data use

Daily Brief’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Policy changes and contact

Updates to this policy will appear on this page with a revised effective date. Questions about privacy: chrishornung14@gmail.com.