Google Calendar · Privacy

Google Calendar privacy notice

This notice explains how Front's Codex handles data obtained through its optional Google Calendar integration. It is intentionally limited to Google Calendar data and is not a complete privacy policy for every feature in Front's Codex. Operated by Frontiverse; privacy contact: [email protected].

What Codex accesses

When you choose to connect a Google account, Codex requests permission to view and edit calendar events and to list your calendars. Codex uses the calendar list to show available calendars and their names and time zones. It does not request your Google profile or email address through this integration.

After you select calendars, Codex can import events from those calendars and synchronize events you explicitly link to Google destinations. Event information may include titles, dates and times, locations, notes, recurrence details, event identifiers, and sync/conflict status. Selecting a calendar enables its events to be imported; selecting a calendar does not by itself publish Codex-only events to Google.

How data is used and shared

Calendar data is used to provide the calendar-selection, import, event synchronization, and conflict-review features you request. Codex sends or updates event data with Google Calendar when needed to perform that sync. It does not use Google Calendar data for advertising or sell it.

Cloudflare provides the Worker and database infrastructure that processes and stores sync data for Codex. Google receives the data necessary to read or update the calendars you selected and linked. The Calendar integration does not automatically send Google Calendar data to Codex's AI feature.

Storage and security

Google refresh tokens and linked event details are encrypted at rest in Cloudflare D1 using AES-GCM. The Worker can decrypt them to perform background synchronization, so this storage is not end-to-end encrypted. Calendar IDs, calendar names, time zones, account-routing identifiers, and sync metadata are stored for calendar selection and synchronization. Calendar records also pass through your browser and may remain in Codex's local browser storage.

Retention and deletion

You can disconnect a Google account from Calendar Setup. Codex attempts to revoke the Google authorization and, when the disconnect operation succeeds, removes the account token, calendar list, sync state, event mirrors, and queued review data from its active Worker database. If Google cannot confirm revocation, you can revoke Codex in your Google Account security settings.

Disconnecting does not delete events already in Google Calendar. Events previously imported into Codex may remain in that browser's local Codex data until you delete them there. Disconnecting removes their Google connection rather than erasing those local event records.

For a privacy or deletion request concerning Google Calendar data, contact [email protected]. Google data is subject to Google's own privacy terms and controls.

Google API Services User Data Policy

Front's Codex will use and transfer information received from Google APIs in adherence to the Google API Services User Data Policy, including its Limited Use requirements.