What Coco can do: every permission, in plain English

When you sign in, Google shows you a list of permissions. Some of the phrasing sounds broad, because Google's consent screen has no setting for "only the things the human approved" — permissions are all-or-nothing. So Coco asks for what it needs and then constrains itself to use each one narrowly. Here is the full list.

Read your email

Coco reads your Gmail to build your brief and to pull up a thread when you ask in the chat. This is the foundation of everything Coco does — it cannot summarize your day without reading the day's mail. It reads; it does not modify or delete your mail.

Read your calendar

Coco reads your Google Calendar so it knows what your day actually holds and can answer questions like "Am I free Thursday?" Reading your calendar never changes it.

Draft replies

Coco writes replies in your voice and saves them as drafts in your account. A draft sitting in your drafts folder has not gone anywhere — it is waiting for you.

Send a reply you have approved

Google's consent screen calls this "send email on your behalf." It reads as if Coco could send anything, anytime. It cannot, by design: Coco only ever uses this on the exact draft you have tapped to send. The permission exists so that your one-tap send actually works — not so Coco can email people on its own.

Add a calendar event you have asked for

Google calls this "view and edit events." Coco uses it only to add the specific event you asked for, with the details you confirmed. It does not move your existing meetings or delete anything.

Why the broad phrasing is not a red flag

Those broad labels — "send email on your behalf," "view and edit events" — are Google's wording, not a description of how Coco behaves. Coco holds the full permission and uses a sliver of it, only on what you confirm. The flip side of this is just as important: read what Coco will never do, and for the technical detail see Coco's security defenses.