Google Calendar Data & Privacy Disclosure

PAI does not request access to Calendar List, Free/Busy, Tasks, Contacts, Gmail, Drive, or other Google Workspace data. Although Google’s owned-events scope can technically reach events you own outside the primary calendar, PAI enforces a separate product restriction: it reads and changes events only on your primary Google Calendar. It does not access secondary, shared, or subscribed calendars.

• Find and read events on your primary calendar and answer calendar-related questions.
• Calculate your own availability from event times.
• Create, update, reschedule, and delete events, including recurrence, attendee, location, time-zone, and conferencing details when your request requires them.
• Undo a supported calendar change for up to 24 hours.
• Receive an optional daily agenda only when you explicitly choose to enable it. You can later disable it or change its delivery time from your account settings.

Depending on your request, PAI may process the connected Google account, primary-calendar identifier, event identifier, event title, description, date, time, time zone, location, attendees, recurrence and status information, conferencing or meeting-link information, and availability derived from event times. PAI also stores encrypted OAuth access and refresh tokens and related scope and expiration information while the connection is active.

PAI does not send raw or derived information obtained from Google APIs to OpenAI. Calendar reads, availability calculations, agenda generation, and Calendar mutations are handled by deterministic application logic; Google-derived text is screened at the connected-provider boundary before it can be used. OpenAI may process a user's original SMS request under the general Privacy Policy, but it does not receive the Google Calendar results or fields returned for that request.

PAI does not use Google Calendar data to fine-tune, evaluate, or train generalized AI or machine-learning models.

Google processes the authorization and Calendar API requests. Railway hosts PAI's application and database, Google Cloud Model Armor screens connected-provider text for security, and Linq transmits the Calendar result or action confirmation by SMS. OpenAI is not a recipient of raw or derived Google API data. PAI limits each transfer to the role described here, does not sell Google Calendar data, use it for advertising or marketing, distribute it to data brokers, or use it to determine creditworthiness. Google user data is not transferred in a merger, acquisition, or sale without your explicit prior consent.

PAI policy permits human access to Google Calendar content only when you expressly authorize access for a specific support matter, when access is necessary to investigate a security or abuse incident, or when required by law.

• OAuth tokens are encrypted in transit and stored encrypted at rest. The application receives token-encryption key material separately from token records; operational access and key-management evidence is verified outside the repository.
• Calendar action data is deleted promptly after a successful request unless needed for the 24-hour undo window. Temporary calendar artifacts and undo data are deleted no later than 24 hours after creation, followed by the next automated cleanup cycle, which normally runs about every five minutes.
• PAI schedules calendar-influenced message content in its own active systems for deletion after the temporary-use or undo period and issues supported provider-deletion requests. PAI has not established through repository evidence how quickly or completely a provider removes logs, backups, subprocessor copies, or content already delivered to a device.
• Deleted information may remain temporarily in infrastructure backups until the applicable backup lifecycle expires. Backup aging, restore, and post-restore deletion controls require separate operational evidence.
• Raw and derived Google API data is excluded from OpenAI processing. OpenAI retention controls for separate user-origin content are described in the full Privacy Policy.

The connection page asks you to connect and enable the daily agenda, connect without a daily agenda, or decline. None of the choices is selected in advance.

You may disconnect Google Calendar in PAI at any time. PAI then disables calendar access and the daily agenda, asks Google to revoke the authorization, deletes local OAuth tokens, and deletes connected-calendar artifacts, undo records, and related caches from active systems. You may also revoke access directly from your Google Account. Account deletion performs the same disconnection steps and removes other account data as described in the full Privacy Policy.

Manage Google access: https://myaccount.google.com/permissions

PAI complies with the Google API Services User Data Policy, including its Limited Use requirements, when using or transferring information obtained through Google APIs. Read the Google API Services User Data Policy.

Read PAI’s Privacy Policy and Terms and Conditions. Questions or privacy requests can be sent to [email protected].