Privacy policy
Last updated 20 October 2026
Coce is an app that runs on your own computers and lets you use coding agents from any of your devices. This policy covers the Coce app, including its connections to Google and Slack, and the website coce.app.
The short version: Coce runs on your machines and talks to Google, Slack and your AI provider directly. I, the publisher, have no server in that path, and I never receive your email, calendar, messages, files, chats or sign-in tokens.
Who is responsible
Coce is published by Andreas Mikael Blixt, an individual, who is the controller for the little personal data this policy says the publisher handles.
Andreas Mikael Blixt
Commelinstraat 2B
1093 TR Amsterdam
the Netherlands
Privacy questions and requests: privacy@coce.app. Help with Coce: support@coce.app. Security reports: security@coce.app.
How Coce handles data
You install Coce on one or more of your own computers. Your chats, your agents’ work, your settings and any sign-ins are stored on those computers. Coce has no account with the publisher, sends no analytics or usage data to the publisher, and has no server operated by the publisher.
Your agents work through an AI model provider that you choose and sign in to, such as Anthropic (for Claude) or OpenAI (for Codex). What you and your agents send to that provider is handled under your agreement with them, not this policy.
Connecting Google and Slack
You can connect a Google account (Gmail and Google Calendar) or a Slack workspace to Coce, so that your agents can do what you ask with your email, calendar or Slack. Each connection is something you add yourself, and you choose which of your projects can use it. Coce uses its own Google and Slack sign-in apps, so you sign in through Google’s or Slack’s own consent screen.
What each connection may access, and why
| Permission | What Coce does with it |
|---|---|
Gmail: read your email and settings (gmail.readonly) | Search your mail, and read the messages and threads an agent needs for the task you gave it. |
Gmail: manage drafts and send email (gmail.compose) | Create drafts for you to review. Coce never sends email: you send a draft yourself, from Gmail. |
Calendar: see your list of calendars (calendar.calendarlist.readonly) | Know which calendars you have, so an agent can look in the right one. |
Calendar: view and edit events on all your calendars (calendar.events) | See your events, and create or update events when you ask. |
Slack: search (search:read) | Search messages and files you can see. |
Slack: your channels and conversations (channels:read, groups:read, im:read, mpim:read) | List the channels and conversations you are in, and find channels by name. |
Slack: conversation history (channels:history, groups:history, im:history, mpim:history) | Read the messages and threads an agent needs for your task. |
Slack: send messages as you (chat:write) | Send or schedule a message as you, when you ask. |
Slack: reactions (reactions:read, reactions:write) | See reactions on a message, and add one as you, when you ask. |
Slack: people (users:read, users:read.email) | Show who wrote a message, and find a person by name or email. |
Slack: files and canvases (files:read, files:write, canvases:read) | Read files and canvases shared with you, and upload a file as you, when you ask. |
Slack: custom emoji (emoji:read) | List your workspace’s custom emoji. |
Coce only reads or changes anything when one of your agents uses the connection in a project you allowed it in. It does not copy your mailbox, calendar or workspace in the background, and it keeps no index of them.
Where the data goes
- Sign-in tokens stay on the computer you choose as Coce’s keeper, in its system keychain. Your other Coce computers get short-lived access, held in memory, when one of your agents there uses the connection. Long-lived tokens never leave the keeper.
- Requests go straight from your Coce to Google or Slack over an encrypted connection.
- What an agent reads becomes part of that chat. It is stored with the chat on your computers, and it is sent to the AI model provider you chose for that agent, because the agent needs to read it to do what you asked.
- A record of each use (which connection, which action, when, and from which chat) is kept on your computers, so you can see what your agents did.
What the publisher never receives
I never receive your sign-in tokens, your email, events, Slack messages or files, the results of any action, your chats, or the record of what your agents did. There is no server of mine that any of it passes through.
Google user data
Coce’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
In particular:
- Google user data is used only to do what you ask of your agents in Coce.
- Google user data must not be used to train, develop or improve AI or machine learning models. Coce and the publisher never use it that way.
- Besides your own computers, Coce sends it to one place: the AI model provider you chose for the agent, and only when the agent needs it to do what you asked.
- It is not sold or used for advertising.
- No person reads it: the publisher never has it.
So use Coce’s Google connection with model accounts that do not train on your chats. Some provider accounts let the provider train on your conversations unless you turn that off, and with Google connected, your email and calendar can appear in those conversations. Turn training off in your provider account, or use an account that does not train on chats, before you connect Google.
Slack data
The same holds for Slack: it is used only for what you ask, never to train models, and it is not exported in bulk or kept as a copy of your workspace.
Removing a connection and deleting data
- In Coce: remove the connection in Coce’s settings. Coce deletes its tokens from your keeper computer and asks Google or Slack to revoke them.
- At Google: open Third-party apps and services in your Google Account, choose Coce, and remove its access.
- At Slack: in your workspace, open Settings & administration, then Manage apps, choose Coce, and remove it.
- Chats: what an agent read stays in that chat on your computers until you delete the chat, or remove Coce and its data folder. Copies your AI provider keeps are deleted under that provider’s own settings and policy.
Since the publisher holds none of this data, there is nothing for me to delete on my side. The deletion is in your hands, and in your providers’.
The website
coce.app is a static site served by Cloudflare, which also serves the Coce downloads and install scripts. To deliver and protect the site, Cloudflare processes technical data about each request, such as your IP address, browser and the page requested. The site sets no cookies and uses no analytics or tracking.
If you write to one of the addresses above, I receive your email and address in my mailbox (hosted by Google Workspace) and use them only to answer you. I keep the correspondence as long as needed to help you, and delete it on request.
Your rights
The publisher processes personal data only to serve the website (legitimate interest in running and securing it) and to answer the email you send (to handle your request). Under the GDPR you may ask for access to, correction or deletion of your personal data, or object to or restrict its processing, by writing to privacy@coce.app. You can also complain to a data protection authority, such as the Dutch Autoriteit Persoonsgegevens.
Coce is not meant for children under 16.
Changes
If this policy changes, the new version is published here with its date. A change in how Coce uses Google or Slack data will also be shown in Coce before it applies.