Privacy Policy

Last updated: September 30, 2026

KISS Sorcar is an open-source AI agent framework (github.com/ksenxx/kiss_ai) that you install and run on your own computer. This policy explains what happens to your data when you use it, in particular when you connect a Google account so that its Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets or Google Chat agent can act for you. Those six agents reach Google through Composio, a third-party service that holds the Google credentials and forwards the API calls. (The one exception is the Google Chat agent's bot mode, which calls Google directly with a service-account key you supply; see below.) This page describes that arrangement so you can judge whether it suits you.

Who operates KISS Sorcar

KISS Sorcar is developed by Koushik Sen. There is no KISS Sorcar server or hosted service: the software runs on your machine, and the developer does not receive, collect, store or have access to your data. Composio is operated by Sampark Inc. under its own privacy policy and terms; you sign up with Composio directly, and the KISS Sorcar developer has no account of yours there and no access to your Composio project.

How a Google account is connected

Google only lets verified OAuth applications request Gmail, Drive and similar scopes from arbitrary users, so KISS Sorcar does not ship a Google OAuth app of its own. Instead:

You create a Composio project and give KISS Sorcar its API key, either as the COMPOSIO_API_KEY environment variable (which is read but never copied to disk) or once as a tool argument, in which case it is saved in ~/.kiss/third_party_agents/google/composio_api_key.json, readable only by your user account. This key authorises the copy of KISS Sorcar on your machine to act on the Google accounts connected to your project; treat it like a password.
When you ask an agent to connect a service, it requests a Connect Link from Composio and shows you the URL (opening it in your default browser when the machine has one). You sign in to Google there and click Allow on Google's consent screen. The agent never asks for your Google password or a two-factor code, and the link expires after about ten minutes.
Google issues the access and refresh tokens to Composio, which stores them encrypted on its servers. KISS Sorcar never receives them: Composio redacts credential fields in every API answer. On your machine the agent records only the identifier of the connected account, in ~/.kiss/third_party_agents/<service>/composio.json.
Every later Google API call is sent to Composio's proxy, which adds the Google token, forwards the request to Google and returns Google's response to your machine. Composio therefore sees the content of each request and response, for example the text of an email you asked the agent to read or send.

Which Google application appears on the consent screen, and which scopes it asks for, is decided by the Composio auth config the connection goes through, not by KISS Sorcar. Unless KISS_COMPOSIO_AUTH_CONFIG_<SERVICE> names one, KISS Sorcar reuses the newest auth config for that service in your project, and creates a Composio-managed one, using Composio's own Google application and its scope set, when the project has none. The scopes are listed on the consent screen before you click Allow. If you would rather have the consent screen name an OAuth client you registered yourself, with scopes you chose, create a custom auth config in your Composio project and point KISS Sorcar at it with that variable (Google Chat requires this, because Composio has no managed Chat application). Composio still stores and uses the tokens in that case.

What the agents do with Google data

Regardless of the scopes granted, the agents only call the Google APIs needed for the tasks you give them:

Agent	Operations
Gmail	Read the mailbox profile; list, search and read messages, threads and attachments; send and reply to email; create drafts; list and create labels and change the labels on a message; move messages to the trash and back. It has no tool that permanently deletes email.
Google Calendar	List calendars; list, read, create, update and delete events.
Google Drive	Search, read, download, upload, move and share files; create folders; move files to the trash.
Google Docs	Create, list, read and edit documents.
Google Sheets	Create, list and inspect spreadsheets; read, write, append and clear cell ranges; add sheets; apply Sheets API batch updates (formatting, resizing, charts, deleting sheets).
Google Chat	List, inspect and create spaces; list members; list, read, post, update and delete messages.

Google data is accessed only to carry out a task you gave the agent or a schedule you set up yourself (for example a Google Chat gateway that polls a space at an interval you chose). Nothing is fetched otherwise.
To perform a task, the agent may send relevant content (for example the text of an email or a spreadsheet range) to the large language model provider you have configured, such as Anthropic, OpenAI or Google. That transfer is governed by your agreement with that provider.
Google data is not sold, not used for advertising, and not used by the developer to train AI models. The developer never sees it.

What Composio stores

Because Composio sits between KISS Sorcar and Google, its handling of your data matters as much as ours. According to Composio's own documentation at the time of writing:

Composio stores the Google access and refresh tokens, encrypted at rest, and refreshes them itself (token custody architecture).
Composio keeps an execution log for every proxied call. By default that log includes the request arguments and the response data, not just metadata, and is retained for up to one year (data retention). Turning on Zero Data Retention in your project settings makes new logs keep metadata only; Composio offers it on paid plans. Files that pass through a tool call are staged in Composio's temporary storage for up to 24 hours.
Composio states that it does not use Google user data to train models, sell it or share it beyond what is needed to run its service, and that it follows Google's Limited Use requirements (Composio privacy policy). Its sub-processor list and compliance reports are published at trust.composio.dev.

These are Composio's commitments, which the KISS Sorcar developer cannot enforce or verify. If you cannot accept a third party holding your Google tokens and seeing your Google data in transit, do not connect a Google account through these agents; the MCP connector catalog includes a Google Workspace server that runs locally with an OAuth client you register yourself and caches tokens on your machine.

What stays on your computer

KISS Sorcar keeps its state under ~/.kiss/ (or the directory named by KISS_HOME): a Composio API key passed as a tool argument, the connected-account identifier of each Google service, and the task history in a local database (your prompts, the agent's replies and tool results, which may include Google content the agent retrieved). If you configured the Google Chat agent as a bot with a Google service account instead of a Composio connection, a copy of that service account's key file is stored there too and the agent calls Google Chat directly with it. The Google agents store no Google OAuth token on your machine; the separate Google Workspace MCP connector mentioned above does cache its own tokens locally. Nothing is uploaded to the developer.

Sharing

Your data is shared with nobody except Composio, which relays the Google API calls as described above; Google itself, which serves them; and the model provider you chose, which receives what the agent decides to put into a prompt. A task that sends an email, posts to a Chat space or shares a Drive file discloses that content to the recipients you named.

Revoking access and deleting data

Ask the agent to clear its authentication (each Google agent has a clear_<service>_auth tool). This forgets the connection locally (for Google Chat, it also removes the stored service-account key copy) and asks Composio to delete the connected account; that remote deletion is attempted once and a failure is not reported, so check the Composio dashboard. Deleting the connected account does not by itself withdraw Google's grant, so also:
Revoke the grant at myaccount.google.com/permissions. It is listed under Composio's application name, or under your own application's name if you used a custom auth config.
Remove execution logs and connected accounts in the Composio dashboard, or ask Composio to delete your data as its privacy policy describes.
Delete the ~/.kiss/ directory (or your KISS_HOME) to remove the locally stored API key, connection identifiers and task history, and unset COMPOSIO_API_KEY if you configured the key that way.

Google API Services User Data Policy

KISS Sorcar's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Changes and contact

Changes to this policy are published on this page. Questions: kisssorcar@gmail.com, or open an issue on GitHub.