Privacy Policy

What the app accesses

You authorize the app through Google, then choose a calendar in the local controller. The app requests two permissions:

• Read your calendar list (calendar.calendarlist.readonly) to show calendars available to your account and let you select one.
• Read calendar events (calendar.events.readonly) to build Today and Upcoming. This Google permission permits reading events from all calendars you can access. The app's implementation retrieves events only from your selected calendar.

The app reads calendar names, identifiers, timezones, and access roles for selection. It retains the account identifier and selected calendar metadata. For the agenda, it retains event titles, start and end dates or times, locations, and identifiers needed to handle recurring events and cancellations.

Google's event responses can contain other event fields. The local server processes those responses to build the agenda; it does not retain event descriptions or attendee lists in its normalized event cache. The app never creates, edits, or deletes Google Calendar events. Upcoming marks exist only in the local controller.

Google documents these Calendar permissions. Google data is used only for the visible calendar features described here, subject to the Google API Services User Data Policy, including its Limited Use requirements.

Where information is stored

The local server stores OAuth client configuration, access and refresh tokens, the selected calendar, a recent event snapshot, and Upcoming selections in local files on your Mac. The application restricts access to its private runtime files using operating-system file permissions. These files are not encrypted by the app; disk encryption and access to the Mac are controlled by its owner.

The event cache covers today and the configured future window. It lets the app retain a last-good schedule during a temporary failure and recover after a restart. Upcoming selections store event occurrence identifiers, not a separate copy of event titles.

The board receives a rendered agenda image over encrypted local-network TLS with a device access token. It does not receive Google tokens or OAuth client credentials. The current display firmware does not verify the server certificate, so use it only on a trusted local network. People who can see the physical screen can read the agenda, and people with access to your local controller or Mac may be able to view stored calendar data.

Retention, disconnecting, and deletion

Local data has no fixed automatic expiration period. Successful syncs replace the event snapshot. Failed syncs retain the last complete snapshot. On its next update, the display marks the saved agenda stale; aging data is also marked stale after the freshness threshold. Upcoming marks remain until removed or invalidated by a connection or calendar change. Marks for events outside the current window may remain stored without being displayed.

Disconnect clears the app's locally stored access and refresh tokens, account identifier, and selected calendar. It stops further authorized calendar retrieval. It does not revoke Google's grant remotely, delete your OAuth client configuration, or guarantee removal of old event-cache files, backups, or the image already on the display. Previous-calendar data is no longer used for the active agenda.

1. Use Disconnect in the local controller to clear the local authorization.
2. Remove eInk Board's access in your Google Account connections if you also want to revoke the grant at Google.
3. To remove retained local data, stop the local server and delete its Calendar runtime data, including the event snapshot and Upcoming selections. Remove any separately configured OAuth client file and copies or backups you control.
4. Update or clear the physical display separately. E-paper can retain its last image while disconnected or powered off.

The maintainer cannot remotely delete files or backups on your Mac.

Where data goes

Your Mac communicates with Google for authorization, token renewal, calendar selection, and event retrieval. The local controller and board use the resulting agenda. The calendar integration does not send your calendar data to the maintainer, this website, analytics providers, advertising services, or AI systems. It does not sell data or publish a calendar feed.

These public information pages contain no analytics scripts or tracking cookies and do not connect to your calendar. The website's hosting provider may process normal request information, such as IP addresses and browser details, to deliver and protect the site. That website traffic is separate from the local calendar integration.

Policy changes

Changes to this policy will appear here with an updated date. Any new use of Google data beyond the purposes described here will be disclosed before it is introduced, with additional consent where required.