Quave Pager logoQuave Pager
Google OAuth verification

Quave Pager Google Calendar demo

This page documents the least-privilege Google Calendar integration for project pager-503117. Pager reads selected calendars and turns upcoming events into Pager alarms.

Demo video

The video demonstrates the requested read-only Calendar scopes and the in-app workflow that creates Pager alarms from Google Calendar events.

Direct video link: https://pager.quave.ai/oauth-verification/quave-pager-google-calendar-demo.mp4

Reviewer navigation steps

  1. Install or open Quave Pager on Android or macOS.
  2. Paste the reviewer Pager API key in Setup so the receiver can register.
  3. Open Calendar and choose Connect Google. Google shows the two read-only Calendar permissions; choose Continue.
  4. Back in Calendar, review the calendar list (calendar.calendarlist.readonly) and enable the calendars Pager should watch.
  5. Create an event in Google Calendar, then run Sync all. The event appears under Upcoming synced events (calendar.events.readonly).
  6. Open Alarms to see the Calendar-type reminders Pager created (default 10 and 1 minutes before). They ring on the receiver at those times.
  7. Rename or delete the event in Google Calendar and run Sync all again: Pager updates or cancels its reminders. Pager never writes to Google Calendar.

Requested Google scopes

Quave Pager requests only these two read-only scopes. It does not create, edit, or delete Google Calendar events or calendars.

  • https://www.googleapis.com/auth/calendar.calendarlist.readonlyConsent screen: “See the list of Google calendars you’re subscribed to”Lists the calendars in the connected account so the user can choose which ones Pager watches. Shown in the video on the Calendar screen’s calendar list.
  • https://www.googleapis.com/auth/calendar.events.readonlyConsent screen: “View events on all your calendars”Reads upcoming events (title, time, status, RSVP, meeting link) from the enabled calendars only, so Pager can create, update, or cancel its own reminders. Shown in the video when a new Google Calendar event becomes Pager alarms, then is renamed and deleted.

Limited Use statement

Quave Pager's use of raw or derived user data received from Google Workspace APIs adheres to the Google User Data Policy, including the Limited Use requirements.

Quave Pager does not use AI or machine learning models, self-hosted or third-party, to process Google user data. Google Calendar data is never sent to AI providers, AI gateways, or model hubs, and is never used to create, train, or improve any AI or machine learning model.

See also the public Quave Pager Privacy Policy.