Privacy Policy

Calendar integrations — Life Intelligence

Supplement published: November 15, 2026. These integrations currently operate in controlled Staging testing, not general public Calendar access.

Calendar connections are optional. The service provider is identified in our Terms of Service. Availability checking and adding events are separate choices; generating or saving a Life plan does not automatically create external calendar events.

Google Calendar. Connecting Google Calendar requires a separate Google authorization in addition to signing into ACD AI. Read-only availability uses the calendar.events.freebusy permission. If you separately choose to add reviewed Life actions to an existing calendar you own, Google asks for calendar.events.owned and calendar.calendarlist.readonly. Google's owned-events permission also permits viewing, editing and deleting owned events; the ACD AI workflow implemented here only creates the events you confirm and reads those same operation IDs to reconcile uncertain results. It does not modify or delete unrelated existing events.

The service reads calendar identifiers, names and ownership metadata to offer eligible destination calendars, and busy-time intervals to avoid scheduling conflicts. It does not request Google event titles or descriptions for FreeBusy planning. When you confirm an export, the selected Life action title, start/end times, timezone and an opaque operation marker are sent to Google to create the event. No attendees are added by this workflow. Access and refresh tokens are encrypted on the server and are not delivered to the Flutter application. The private Life workspace retains operation identifiers, destination/event IDs, fingerprints and success/failure state to prevent duplicates and reconcile interrupted requests. The operation ledger does not store the event title or description; your Life action remains part of the Life data you saved.

You can disconnect Google Calendar through Calendar connections. The service removes its stored grant and pending authorization and attempts revocation at Google; it reports when provider revocation cannot be confirmed. You may also revoke access in your Google Account. A disconnected or expired authorization is not treated as confirmed availability or write permission. Deleting an individual Life schedule does not revoke the connection, erase the duplicate-protection history or delete events already added to Google. The existing account/data purge removes the server-side Life workspace and operation history and attempts grant revocation. Events already created with your approval remain in your chosen external calendar until you remove them there.

Apple Calendar. On iPhone, EventKit permission is requested only when you choose Apple Calendar. Reading availability requires the access level supported by iOS; the calendars you select are checked locally. Apple event titles and descriptions are not uploaded by this integration. Only bounded free-time windows may be sent to the planning service and retained with a schedule you save. These are local device inputs, not Apple provider evidence authenticated by the server. Adding an event is a separate review in Apple's native calendar editor, where you choose the destination and Save or Cancel. No event is created merely by generating a Life plan.

The iPhone keeps an opaque local operation record and event identifier to reduce duplicate exports. These records are local app data and are not automatically erased by a server-only disconnect; they remain until the app's local data is removed. A lost or uncertain save response is not blindly retried. Deleting Life records does not automatically modify or delete external Apple events. You can revoke Calendar access in iPhone Settings.

For questions about your information, use the contact and rights procedures in the main Privacy Policy.