Frequently asked questions

Cocal brings the Google 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 Google Calendar.

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

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.

Yes. You can connect several Google accounts, such as work and personal, 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.

Cocal requests permission to read and write events, plus read access to your calendar list and free/busy times. It does not request permission to manage calendar sharing. You can review the exact Google scopes in the privacy policy.

No. By default, Cocal asks you to confirm individual 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. Changes that only involve your own calendars, bulk changes, deletes, and invitation responses can happen right away. You can turn confirmation off or disable individual tools in your Cocal settings.

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-confirmation 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 Google when requested.

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

An invite link starts with an event already on the organizer's Google Calendar. 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 Google sends the calendar 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 a Google Calendar event 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 Google Calendars you configure. You choose the direction, time window, filters, and whether a mirror shows full, limited, or busy-only detail. 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 Google 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 Google user data 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.

Disconnect a Google account from your Cocal dashboard, or revoke Cocal through your Google account settings. Disconnecting removes that connection's local credentials and cached calendar rows but does not delete your Cocal account or events in Google Calendar.

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