Kico Privacy Policy

Effective date: October 21, 2026

This policy explains what information Kico collects, why, where it is kept, who receives it, and the choices you have. Kico is operated by Unifying Systems LLC, 5900 Balcones Drive, Suite 19133, Austin, TX 78731, USA (“Unifying Systems”, “we”, “us”). It covers the Kico service at kico.dev and app.kico.dev, the agent mailboxes at agents.kico.dev, and the preview sites at *.apps.kico.dev.

Kico is a workspace where you build and run software with AI agents. Agents read and write code, run it in isolated sandboxes, use tools you connect, and act on your instructions. Because of that, Kico handles a lot of the information you put into it. We try to be specific below about what happens to it.

Questions or requests: hello@kico.dev.

1. Who controls your data

Kico is a business product. Access is by invitation only; there is no public sign-up. Most content in Kico belongs to an organization (a company or team that has a Kico workspace). For content an organization puts into Kico, the organization decides how it is used, and we process it on the organization’s behalf. For your account details and for the accounts you connect personally (for example your Gmail or Slack), we decide how the data is processed, under this policy.

If your organization invited you, it may have its own policies about the data you put into its workspace. Owners and Admins of your organization can manage members, organization keys, data sources and some settings. They cannot see projects that nobody shared with them.

2. What we collect

Account and profile

Your name, email address and a password hash (scrypt). We never store your password itself.
If you link GitHub to sign in, your numeric GitHub user ID.
Your mail handle (for example ana.horvat@agents.kico.dev), notification preferences, default model choices, and when you last signed in.
Invitations: the invited email address, who invited you, and when.

Organization data

Organization name and address in Kico, its members and their roles, invitations, organization settings, and whether the organization agreed to model training (section 6).

Projects and code

The code, files and data in your projects, including repositories you import from GitHub or another Git host, packages the agent installs, build output, check results and screenshots taken by Kico’s checks.
Files you upload, and copies of files agents send you (kept so the download stays what you were sent).
Sharing settings, share links, and for “only these emails” links, the guest’s email address and a short-lived confirmation code.

Chats and agent conversations

Your messages to project agents and to your Kico assistant, the agents’ replies, their reasoning as shown, and every tool call and result.
Tasks, schedules, events and messages between people (and their assistants) in an organization.
Dictation: audio you record is sent through Kico to the transcription service your keys or model servers point to, and is not stored. If no such service is set up, your browser’s own speech recognition is used, which may send audio to your browser’s vendor.

Memory

A profile card about you (at most 2,000 characters), facts, and summaries of past tasks and project turns (“episodes”), with search indexes (embeddings) for them. Your assistant curates this so it can help you better. You can see, edit and delete all of it under Account, Memory, including “Forget everything”.

Mailboxes

Mail sent to your Kico address or to your agents’ addresses at agents.kico.dev: sender, recipients, subject, body, headers, attachments, the sending server’s address, and the results of sender checks (SPF, DKIM, DMARC, ARC).
Mail that your assistant or agents send, and mail waiting for your confirmation.

Connectors and what flows through them

When you connect an account at another service (for example Gmail, Google Drive, Google Calendar, Slack, GitHub, Linear, Notion, Atlassian), we store the connection: the server, your account name there, the scopes you granted, and the OAuth access and refresh tokens. Tokens are encrypted (section 4).
When an agent uses a connector tool on your behalf, the request and the vendor’s answer pass through Kico and become part of that agent’s conversation. That conversation is sent to the AI model that runs the agent (section 5).
Kico keeps a log of each connector call: which tool, which connector, and whether it succeeded. It does not log the arguments or the answer in that log.

Database connection credentials

For data sources you connect (PostgreSQL, MySQL/MariaDB, SQL Server, Oracle, SQLite files you upload), we store the host, database, user name and password, and optional SSH tunnel details. Passwords and keys are encrypted. We also store the schema (tables, columns) and descriptions and search indexes built from it. Queries agents run are read-only, limited in rows and time, and logged.

Secrets and model credentials

API keys, tokens and passwords you or your organization give Kico for your apps, your assistant, or AI providers; tokens of model subscriptions you connect (for example xAI Grok or Claude); Git tokens and GitHub App connections; Tailscale connections you set up for your own model servers. All of these are encrypted.

Browser sessions

Your assistant has its own web browser that you can watch and use. Sites you or the assistant sign in to there keep their cookies and sign-ins in the assistant’s private storage, so they persist between tasks.

Usage and logs

Token counts per model answer, with the model, user, organization, project and task, used to show usage and cost.
When projects were last opened and when their previews were used; resource measurements of sandboxes (memory, CPU, disk, network).
Technical logs of the Kico service.

Audit and activity logs

An audit log of platform administration actions and of every change made while a Kico administrator is signed in as you, with the acting person, the subject, the action, the target, the time and the IP address.
An activity log of your assistant’s tool calls, including actions taken on your behalf.

Cookies and local storage

Kico uses only cookies it needs to work: a session cookie (30 days), a short-lived cookie for each project preview, and short-lived cookies for sign-in flows. They are HttpOnly and, over HTTPS, Secure and host-only. The web app stores a few interface preferences in your browser’s local storage. We use no advertising or analytics cookies, and no third-party trackers.

3. Why we use it

We use your information to:

provide Kico: run your projects and agents, keep your chats, memory, mailboxes and settings, and carry out the actions you or your schedules ask for;
call the AI models you or your organization choose, and the services you connect, on your behalf;
secure the service: authenticate you, isolate sandboxes, detect abuse, and keep audit logs;
send service mail (invitations, password resets, sharing and organization notices, and message notifications you can turn off);
support you when you ask for help;
measure usage and capacity;
improve Kico’s own local model, only for organizations that opt in, as described in section 6;
comply with law.

Where GDPR or similar laws apply, our legal bases are: performing our contract with you or your organization; our legitimate interests in running, securing and improving the service; your consent where we ask for it (for example the training opt-in); and legal obligations.

We do not sell your personal information, we do not share it for cross-context behavioral advertising, and we do not use it for advertising of any kind.

4. Where it is stored and how it is protected

Location. Kico runs on Microsoft Azure in the South Central US region (Texas). The database, project files, assistant homes and mailboxes are stored there. Nightly database backups and disk snapshots are kept in Azure in the same subscription. Outgoing mail is sent through Azure Communication Services with its data location set to the United States.

Encryption of secrets. Every stored credential (model API keys, subscription tokens, Git tokens, connector OAuth tokens, database passwords and your secrets) is sealed with AES-256-GCM using a data key that belongs to its owner: one per user, one per organization, and one for the platform. Data keys are themselves encrypted by a master key that is kept outside the database, in Azure Key Vault, and handed to Kico at runtime. A copy of the database alone cannot open these values.

Sandboxes. Every project runs in its own container, and every user’s assistant runs in its own container. Sandboxes cannot reach each other, cannot reach Kico’s database, and cannot reach the rest of our cluster or cloud metadata services. They run on a separate Docker host that only Kico can reach.

Tokens stay out of sandboxes. AI provider keys, subscription tokens and connector tokens never enter a sandbox. Sandboxes call models and connectors through Kico, which adds the credential on its side. Secrets for your apps go through Kico’s egress proxy where possible, which adds them only for the hosts they are meant for; output shown to you hides secret values. Connector answers are scanned for the connection’s own tokens, which are replaced with “[redacted]”. Database credentials never reach a sandbox: queries go through Kico.

In transit. The web app, previews and APIs are served over HTTPS (TLS certificates from Let’s Encrypt). Calls to AI providers and connectors use HTTPS. Kico’s mail server offers STARTTLS to sending servers.

At rest. Azure encrypts its managed disks and storage at rest. On top of that, credentials are sealed as described above.

Access by our staff. Kico administrators can see organizations, accounts, usage and audit logs for operating the service, without the values of keys or secrets. For support, an administrator can sign in as you for at most one hour; during that session your password, API keys, model servers, Git connections, Tailscale, data source credentials, secrets and invitations are off limits, connector reads do not run, and every change is recorded in the audit log. You can see every such session under Account, Security.

No system is perfectly secure. See our Security page for more detail.

5. Who receives your data

We share data only as needed to provide Kico, at your direction, or as described here.

AI model providers, chosen by you or your organization. When an agent works, its conversation (your messages, code, files it reads, tool results, connector results, memory it uses) is sent to the model you selected. Depending on that choice, this is one of: Anthropic, OpenAI, Google (Gemini API), OpenRouter (which routes to the model’s underlying provider), NVIDIA, xAI, Reflection AI, a model server you or your organization added (for example your own LM Studio, ollama or vLLM server, possibly reached over your Tailscale network), or a model server operated by Unifying Systems. Kico uses the credential of whoever sent the prompt: your own model subscription, then your own key, then your organization’s key, then a key Unifying Systems provides. Each provider processes the data under its own terms for the account in use. Embedding and transcription calls follow the same choice.

Microsoft Azure hosts the service, stores backups and sends mail (Azure Communication Services).

GitHub and other Git hosts, when you import, pull or push repositories.

Connector vendors. When you connect a service and an agent uses it, Kico sends requests to that vendor’s server with your token, as you direct.

Web search. When your assistant searches the web, the search query is sent to Exa, the search service built into the agent engine. Pages the assistant opens are fetched from their sites.

Recipients you choose. Mail and messages your agents send go to the recipients involved. Apps you share are visible to the people or links you share them with.

Other cases. We may disclose information to comply with law or valid legal process, to protect the rights, safety and security of users and the public, or as part of a merger, acquisition or sale of assets, in which case we will require the recipient to honor this policy and notify you.

6. Training Kico’s local model

Kico can improve a model that Unifying Systems runs on its own hardware (“the local model”). This happens only for organizations whose Owner or Admin turns it on; it is off by default.

When an organization opts in:

Kico keeps the raw model requests and answers of the organization’s projects (not of personal assistants) on Kico’s data volume for up to 48 hours, and at most 1 GB per project, oldest first.
When a project turn ran on the local model and the user’s assistant reviewed it, the assistant may record a training case from that turn: the local model’s steps and, for a mistake, the corrected steps, plus a screenshot of the check. Known secret values (keys, tokens, passwords Kico holds for the project and its people) are masked in cases.
Cases are exported to Unifying Systems’ training machine, which trains an adapter for the local model. Kico administrators can view cases.
Turning consent off deletes the kept raw calls of the organization’s projects at once, and its cases are no longer exported for training. Cases are deleted when the organization is deleted. You can ask us to delete existing cases earlier.

We do not use your data to train models for anyone else, and we do not provide it to third parties for training.

Google and Slack data. Data obtained through Google APIs (Gmail, Google Drive, Google Calendar) or from Slack is never used to develop, improve or train generalized AI or machine learning models, including Kico’s local model, and is not included in training cases.

7. Google user data

Kico’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.

Specifically:

What we access. Only the Google services you connect (Gmail, Google Drive, Google Calendar), with the scopes shown on Google’s consent screen. Kico connects through Google’s own remote MCP servers for these services.
How we use it. Only to provide the features you ask for: your assistant and the agents you give the connector to search, read and draft mail, find and read files, and read events and availability, when you ask them or when work you set up runs. Writes that an event started wait for your confirmation unless you allowed them.
Transfers. We transfer Google user data only to provide those features (for example to the AI model that carries out your request, under section 5), for security, to comply with law, or as part of a merger or acquisition with notice to you.
No advertising, no sale. We do not use Google user data for advertising, including retargeting or interest-based ads, and we do not sell it.
No generalized model training. We do not use Google user data to develop, improve or train generalized AI or ML models.
Human access. Our staff do not read Google user data unless you give us permission (for example in a support request), it is needed for security purposes such as investigating abuse, it is required by law, or it is aggregated and anonymized for internal operations.
Storage. OAuth tokens are encrypted as described in section 4. Content an agent retrieves becomes part of that conversation and is kept as long as the conversation is (section 8).
Revoking. Disconnect the connector under Account, Connectors; Kico revokes the tokens at Google and deletes the connection. You can also remove Kico’s access at myaccount.google.com/permissions.

8. Slack data

If you connect Slack, Kico acts with a user token you grant through Slack’s consent screen, and only when you or work you set up asks it to: reading channels, messages, files and users you have access to, searching, and posting. Slack data is used only to provide those features, is not sold, is not used for advertising, and is not used to train AI or ML models. Tokens are encrypted and never enter a sandbox. Disconnecting Slack under Account, Connectors revokes the token at Slack and deletes the connection. Slack content an agent retrieved stays in that conversation until it is deleted (section 9).

9. Retention and deletion

We keep data while your account or organization is active, unless a shorter period is listed here.

Data	Kept
Session cookie	30 days, or until you sign out or change your password (which ends every session)
Invitation links	valid 7 days; records removed 90 days after use, withdrawal or expiry
Password reset links	valid 1 hour; records removed after 30 days
Guest confirmation codes / guest sessions	1 day / 7 days after expiry
Revoked share links, seen share notices	90 days
Service mail outbox	sent mail 90 days, failed mail 365 days
Raw model calls kept for training (opt-in only)	up to 48 hours, at most 1 GB per project
Sandbox resource measurements	30 days
Old agent mail addresses after a rename	keep delivering for 90 days
Database backups	nightly, kept 14 days
Disk snapshots	kept 30 days
Chats, memory, mailboxes, project files, activity and usage records, audit log	until deleted as described below

What you can delete yourself.

Projects: deleting a project removes its sandbox, files, chat history, checks, sent-file copies and preview.
Memory: delete single facts or episodes, or “Forget everything”.
Connectors: disconnecting revokes the tokens at the vendor (when the vendor supports revocation) and deletes the connection.
Model subscriptions, API keys, Git connections, data sources and secrets: removing them deletes the stored credential.

Deleting your account. Ask us at hello@kico.dev or ask an administrator. When an account is deleted, your memory, connections and their tokens, model subscriptions, personal secrets and keys, mailboxes and their mail, assistant activity, and your assistant’s sandbox and private storage (including its browser profile and mail files) are deleted. Projects you created in an organization belong to that organization and move to a member it picks. Usage records stay without your user ID. Audit log entries keep the email address recorded at the time, because they are a security record.

Deleting an organization. An Owner (or Kico) can delete an organization. It closes at once and is removed for good after 30 days: projects with files, sandboxes and chat sessions, data sources, keys, model servers, secrets, shares, invitations, memberships and training cases. It can be restored until then. Member accounts stay.

Backups. Deleted data leaves the nightly database backups within 14 days and disk snapshots within 30 days.

10. Your rights

Depending on where you live (for example under the GDPR, UK GDPR, or California and other US state laws), you may have the right to:

know what personal information we hold about you and get a copy of it;
correct it;
delete it;
receive it in a portable format;
object to or restrict certain processing;
withdraw consent at any time, where processing is based on consent;
not be discriminated against for using these rights;
appeal our decision on your request.

Much of this you can do yourself in Kico (Account settings, Memory, Connectors, project Files download). For anything else, write to hello@kico.dev. We will verify your identity and respond within the time the law requires (generally 30 days, 45 days in California). If your organization controls the data in question, we may refer you to it or act on its instructions. You may also complain to your local data protection authority.

We do not sell personal information or share it for cross-context behavioral advertising, as those terms are defined under California law, and we have not done so in the past 12 months.

11. International transfers

Kico is operated from the United States and its data is stored in the United States. AI providers and connector vendors you choose may process data in other countries under their own terms. If you use Kico from outside the US, your information is transferred to the US. Where required, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses.

12. Children

Kico is a business service for adults. It is not directed to children, and we do not knowingly collect personal information from anyone under 16. If you believe a child has given us personal information, contact us and we will delete it.

13. Changes

We may update this policy. We will post the new version here with a new effective date, and for material changes we will notify account holders by email or in Kico before they take effect.

14. Contact

Unifying Systems LLC 5900 Balcones Drive, Suite 19133 Austin, TX 78731, USA hello@kico.dev