Frequently asked questions

Cocal brings the calendars in your Cocal account into the chat you use. Ask it to show your schedule, find open time, create or change events, and use Cocal features such as invite links and booking links. Calendar changes are written to the calendar they belong to.

No. Cocal gives your connected chat a way to work with the calendars you already use. Ordinary event reads come from your calendar when you ask for them, and calendar changes go back to it. You can keep using your calendar app as usual.

Yes. Cocal works with Google Calendar, Outlook and iCloud Calendar, and you can connect accounts from all three. Outlook works with personal, work and school Microsoft accounts. Add them from your account page after you sign in.

Cocal works with Claude, ChatGPT, Gemini, and Claude Code. The visual calendar appears in clients and surfaces that support interactive apps. Availability checks, conflict detection, and supported calendar actions still work in plain chat where it does not. The connection guide covers setup and availability details for each client.

The built-in connections look up and change your calendar. Cocal shows you the calendar: a real day view in the conversation, every connected calendar account on one grid, who an invitation will email before it goes out, and booking and invite links other people can use. See what Cocal adds.

Yes. You can connect several accounts, such as work and personal, across Google Calendar, Outlook and iCloud Calendar, then enable the individual calendars Cocal should use. Calendars shared with those accounts can be enabled too. You can change the selection at any time.

For Google Calendar, Cocal requests permission to read and write events, plus read access to your calendar list and free/busy times. For Outlook, it requests permission to read and write your calendars, read your Outlook time zone setting, and read your basic profile. Neither includes permission to manage calendar sharing or read your email. You can review the exact Google and Microsoft permissions in the privacy policy.

No. By default, Cocal asks you to confirm event creates and updates that involve people outside your own calendars. It shows the proposed event and recipient list, then waits for you to confirm or discard it. You can widen that to events whose time conflicts with another event, or to every event. For several events, Cocal checks the batch first and asks Claude or your connected client to prepare any required previews individually. Confirm each preview to apply its change.

Deletes and invitation responses can happen without a preview, and so can changes that only involve your own calendars unless you choose to see previews for every event. Choose when previews appear, or turn them off, under Event previews in Cocal settings. How previews work.

Preferences are plain-language rules saved to your Cocal account. Cocal brings them into each new conversation, so rules such as which calendar to use or times to avoid do not need to be repeated. You can edit them in chat or on the web, and Cocal keeps the edit history. Preferences belong to your account only.

Invite links, booking links, calendar syncs, and event-preview drafts are optional Cocal-specific features. They keep the records needed to make those features work. They are separate from ordinary event listing, search, detail, conflict, and availability reads, which fetch current data from your calendar provider when requested.

The privacy policy lists the data, purpose, retention, and deletion behavior for each feature.

An invite link starts with an event on the organizer’s Google Calendar, or one they organize on Outlook. Cocal stores a limited event snapshot so the public page can show the title, time, location, and timezone without reopening the organizer’s calendar. A guest enters an email address to join. Cocal adds that address as an attendee, and the organizer’s calendar sends the invitation. Organizers can set an access code, expiry, or guest cap and see how many people joined.

A booking link lets someone choose a time inside hours the host set. Cocal calculates slots against the calendars the host chose to count as busy, then creates an event on the host’s calendar with the booker as a guest. The booker receives a private link to reschedule or cancel. They can optionally connect their own Google Calendar for a free/busy check without sharing event details with Cocal.

It is an optional feature that mirrors events between two of your calendars. You choose the direction, time window, filters, and whether a mirror shows full, limited, or busy-only detail. A sync that includes an Outlook calendar or an iCloud calendar runs one way. Syncs run every 15 minutes or when you choose Sync now, so changes are not instant.

Cocal does not keep a general copy of your calendar. Ordinary calendar reads fetch current event data from your calendar provider and return it to the client you connected without writing those results to Cocal’s application database. Cocal does cache calendar-list metadata, and the optional Cocal-specific features above keep the bounded records they need. The privacy policy describes those exceptions in full.

The log records metadata such as the tool name, time, duration, source, and whether the call succeeded, failed, or was blocked. It does not store tool arguments or results, so it does not contain event titles, descriptions, attendees, or search terms from the call. Activity entries are shown for 90 days and removed opportunistically after that window.

No. Cocal does not use data from Google Calendar, Outlook or iCloud Calendar to train artificial intelligence or machine learning models, and it does not use that data for advertising. A limited calendar sample may be processed by a model provider to suggest calendar categories during onboarding or after you connect an account. That user-facing categorization is described in the privacy policy.

Remove a calendar account from the Calendars tab of your Cocal account. You can also revoke Cocal at the provider: in your Google account settings for Google Calendar, at account.live.com for a personal Microsoft account, or at myapps.microsoft.com for a work or school Outlook account. Removing an account deletes that connection’s local credentials and cached calendar rows but does not delete your Cocal account or the events in your calendar.

To remove your Cocal account and its user-scoped product records, use Delete account in Cocal settings. Events already stored in your calendars are not deleted. Contact-form records and data already delivered to another provider are handled separately, as the privacy policy explains.