Privacy Policy

pi-calendar-briefing · last updated 5 September 2026

What this application is

pi-calendar-briefing is a personal, single-user script running on a Raspberry Pi owned and operated by one individual. It reads that same individual's Google Calendar and sends him a summary of his own day. It is not offered to the public, has no user accounts, and is not a commercial service.

What data it accesses

The application requests exactly two Google OAuth scopes, deliberately chosen as the narrowest pair that covers its function:

• …/auth/calendar.calendarlist.readonly — read-only. Lists which calendars the account is subscribed to, so the briefing can cover all of them.
• …/auth/calendar.events — read and write access to events. Used to read the day's schedule, and to create or amend events at the operator's own request.

From those calendars it reads event titles, start and end times, locations, all-day/tentative status, colour labels, and video-conference links, for a window of roughly the next two weeks.

What it deliberately cannot do

The broader …/auth/calendar scope was rejected on purpose. As a result this application has no technical ability to:

• delete a calendar, or erase all events from one;
• change a calendar's sharing permissions, or grant access to any other person;
• rename a calendar or alter its properties;
• subscribe the account to, or unsubscribe it from, any calendar.

Its write capability stops at individual events.

How the data is used

Calendar entries are formatted into a plain-text daily briefing and delivered to the operator's own private Discord direct message. Write access is used solely to create or amend events that the operator has explicitly asked for.

Calendar content is not analysed, profiled, used for advertising, used to train any model, sold, or shared with anyone.

Storage and retention

• Calendar data is fetched at run time, rendered, sent, and discarded. It is never written to a database or a file.
• The local run log records only counts and error messages — for example “4 events” — never event content.
• The Google OAuth refresh token is stored in a single file on the operator's own device, readable only by the operator's account (mode 600). It is never transmitted anywhere except to Google's own token endpoint.
• The delivered briefing message persists in the operator's own Discord direct message history, subject to Discord's retention policy.

Third parties

No analytics, no trackers, no advertising, no third-party data processors beyond the services that carry the message itself: Google (source of the calendar data) and Discord (delivery of the resulting message to the operator). Publicly available weather and currency-exchange endpoints are also queried; those requests contain no personal data.

Revoking access

Access can be withdrawn at any time at myaccount.google.com/permissions. Revocation immediately and permanently stops all calendar access by this application.

Contact

Questions about this policy: kennyjiang2006@gmail.com