Your access,
explained.

The tool reads the signed-in Stanford account’s exposed class-calendar information and Google Calendar event data needed to compare and synchronize class events. It also reads Google account identity, calendar-list metadata, and sharing rules to verify the account and private destination.

Google permissions cover events on calendars the user owns. Application code restricts routine writes to the bound Stanford Classes calendar; primary-calendar cleanup requires approval of exact legacy events. The app does not request permission to create calendars or modify sharing settings.

Account and calendar information is used to retrieve the source calendar, prepare requested previews, perform explicitly authorized synchronization, verify results, and recover from interrupted operations.

The sync code does not sell calendar data or send it to advertising or analytics services. Account data is exchanged with the relevant Stanford and Google services to carry out the requested operation.

Calendar Classes Sync follows the Google API Services User Data Policy, including Limited Use requirements, for information received from Google APIs. The sync code does not use calendar data to train or improve generalized AI models.

Google client configuration and refresh credentials are stored in macOS Keychain. Access tokens, retrieved event titles, descriptions, locations, and full event records remain in memory during local processing.

The local SQLite operation journal stores identifiers, fingerprints, operation timestamps, source-to-event mappings, event start and end boundaries, and verification metadata. It does not store credentials, event titles, descriptions, or locations. The journal is recovery evidence, not a full calendar-content archive.

Codex tools may return a requested preview or summary to the chat. Such information is then handled under the applicable Codex or ChatGPT provider’s policies and the user’s account settings. This policy does not replace those policies or claim that information shown in a chat stays solely on the Mac.

Google and Stanford process authorized requests under their own policies. There is no public hosted synchronization server or continuous monitoring service.

To revoke Google access, open Google Account connections, select Codex Calendar Classes Sync, and remove its access. Revocation prevents future authorized requests but does not erase local records.

To remove local data, ask Codex to close active sync sessions, remove Calendar Classes Sync’s macOS Keychain credential record, and delete its local operation journal. The Keychain record uses the service name com.codex.calendar-classes-sync.oauth; the journal is ~/.local/share/codex-calendar-classes-sync/operations.sqlite3. Local removal does not itself revoke Google’s grant, so revoke access separately when disconnecting.

There is no automatic retention expiry. Eligible completed operation records can be pruned on request; active mappings and unresolved recovery evidence remain until explicitly removed. Review uncertain operations before deleting their evidence, because removing it can prevent safe reconciliation and duplicate detection.

Neither revocation nor local deletion removes events already in Google Calendar. Remote event removal is a separate, explicitly authorized operation.

These static pages contain no account login, forms, analytics scripts, credentials, or calendar data. The hosting provider may process ordinary web-request information required to serve and protect the site.

This is a personal app operated by its sole user. Support and developer contact details are shown in the Google authorization flow.