Privacy policy
Last updated 14 November 2026
This policy says what personal information Kosem AI ("kosem") collects, how kosem uses it, who it shares it with, and the choices and rights you have. It covers kosem.ai, the console at app.kosem.ai, kosem's API, its docs and the emails it sends (together, "the service").
The short version
- kosem collects what it needs to run the service and keep it secure: your email address and name, how you use the service, and what your organization stores in it.
- kosem doesn't sell your personal information, doesn't show ads and uses no advertising or analytics trackers.
- kosem doesn't use your content to train AI models, unless your organization opts in.
- Your organization's content belongs to it. kosem processes it only to provide the service, on your organization's instructions.
- kosem stores data in the United States, on Google Cloud.
- To ask about your data, or to have it deleted, write to privacy@kosem.ai.
This summary helps you read the policy. The full text below is what applies.
Two roles
kosem handles personal information in two ways:
- As a controller, for information about you as a visitor, someone on the waitlist, a user of the service or a billing contact. This policy governs it.
- As a processor, for Customer Content: what an organization, its people, its service accounts and its agents put into the service or create in it, such as code, images, environments, agents' conversations, files, secrets, sites and requests to models. kosem processes it on the organization's behalf, under the Terms of service and any data processing agreement the organization signs with kosem. The organization decides what goes into the service and who can see it. If you have a question about Customer Content that names you, ask the organization first. kosem helps it answer.
What kosem collects
What you give kosem
- The waitlist. On kosem.ai: your email address, when you joined and, if you give them, your name, your company and what you'd like your agents to do. On the console's sign-in page, when kosem hasn't admitted your address yet: your email address, how many times you tried to sign in, and whether with a code or Google.
- Your account. Your email address and the name you give. With Google sign-in, kosem also receives Google's identifier for your account and whether Google has verified your address. kosem keeps no passwords. The codes it emails you for signing in are stored only as keyed hashes, and expire after 15 minutes.
- Organizations and projects. Their names, their members and the roles people hold, and the addresses people invite.
- Billing. Stripe collects your card details, and kosem never receives your full card number. kosem keeps Stripe's identifier for your organization, its purchases, credits, invoices and the billing contact's email address.
- What you send kosem, such as questions for support or reports of security issues.
What kosem records as you use the service
- Audit logs. Sign-ins, changes, credentials issued, secrets read and other calls to the service. Each entry names who acted (a person's email address, an agent or a service account), when, from which IP address and with which user agent. Your organization can read its own audit logs.
- Operational logs. kosem's servers and Google's load balancer log requests, with IP addresses, addresses requested and user agents, to run the service, secure it and fix errors.
- Usage. Requests, tokens, agents' requests and web searches, by organization, project, model and agent, for the service's usage pages, its limits and billing.
- Cookies and browser storage, as Cookies and browser storage lists them.
Customer Content
- Code and files in environments, the images environments start from, and their disks.
- Agents' conversations: the messages people write, what agents answer, the commands they run and their output, the files agents keep and the sites they publish.
- Secrets. kosem seals their values with Cloud KMS keys and redacts them from agents' output.
- Requests to models through the LLM gateway. The gateway passes prompts and answers between your callers and your model providers. Its request log keeps each request's model, caller, token counts, timing, status, user agent and errors, and a provider's error message can quote part of a request. It doesn't keep prompts or answers. Agents' prompts and answers are part of their conversations.
- Connections to other services, such as model providers' keys, which kosem never shows again once written, and GitHub App installations.
How kosem uses information
- To provide the service: to review the waitlist, sign you in, run agents and environments, route requests to models, publish sites, and send the emails the service needs, such as sign-in codes, invitations and approvals from the waitlist.
- To keep it secure: to detect and stop abuse, fraud and attacks, and to enforce limits and the Terms of service.
- To bill: to measure usage, take payments through Stripe and keep the records that tax and accounting law requires.
- To support you: to answer questions and investigate problems you report.
- To improve the service: from usage figures and operational logs.
- To write to you about your account, the private beta, security and changes to the service or these terms. Any email about kosem's news has a link to unsubscribe.
- To meet legal obligations, and to protect the rights and safety of people, kosem and the service.
kosem's staff look at Customer Content only to provide support you ask for, to keep the service secure, or when the law requires it. They work in a separate staff application, which can't sign in as you, and which records every action they take.
AI models and your content
- No training on your content. kosem doesn't use Customer Content to train or fine-tune AI models, unless your organization opts in. If kosem offers such a choice, it stays off until your organization turns it on, and turning it off stops any further use.
- Your model providers. The LLM gateway sends requests to the providers your organization connects, such as Anthropic, OpenAI, Google or a server it runs, with your organization's key and under its own agreement with that provider. That agreement governs what the provider does with the requests.
- kosem's own model. kosem uses a Gemini model on Google Cloud's Vertex AI, under kosem's own account, to write a short title for an agent's conversation from its first message. Google processes it as kosem's subprocessor, and under Google Cloud's terms doesn't use it to train its models.
- The web. When an agent searches the web or reads a page, Exa receives the query or the page's address, and returns the results.
Legal bases, in the EEA, the UK and Switzerland
- Contract: to provide the service you or your organization signed up for, and the waitlist you asked to join.
- Legitimate interests: to keep the service secure, prevent abuse, improve the service and write to the people who use it, where those interests aren't outweighed by your rights.
- Legal obligation: to keep tax and accounting records, and to answer lawful requests.
- Consent, where kosem asks for it. You can withdraw it at any time.
Who kosem shares information with
kosem doesn't sell personal information, and doesn't share it for advertising.
Subprocessors process information for kosem, under contracts that hold them to protect it and use it only for kosem:
| Subprocessor | What it does for kosem | Where |
|---|---|---|
| Google Cloud | Hosting, databases, storage, encryption keys and logs; Vertex AI for agents' titles | United States (us-central1, Iowa) |
| Google Workspace | kosem's email | United States and other countries |
| Resend | Sends the service's emails, such as sign-in codes and invitations | United States |
| Stripe | Payments, invoices and fraud prevention | United States and other countries |
| Exa | Web searches and pages that agents read | United States |
kosem updates this list before a new subprocessor starts processing personal information.
kosem also shares information:
- With the services your organization connects, such as model providers, GitHub, AWS, Google Cloud and tools whose tokens it stores as secrets. kosem sends them what your organization's agents and callers send, under your organization's own accounts and agreements.
- Within your organization. People with roles in it can see what those roles allow, such as audit logs that name you, your membership and what you write in agents shared with a project.
- When the law requires it, or to protect people, kosem or the service. kosem tells the organization concerned first, unless the law forbids it.
- In a merger, acquisition or sale of assets, where information passes to the new owner under this policy's protections. kosem tells you before that happens.
Cookies and browser storage
kosem uses only the cookies the service needs to work. It uses no advertising or analytics cookies, so it doesn't ask for your consent to them.
| Name | Where | What it's for | How long it lasts |
|---|---|---|---|
__Host-kosem_session |
app.kosem.ai | Keeps you signed in | 30 days without use, and 90 days at most |
__Host-kosem_sign_in |
app.kosem.ai | Ties a sign-in code to the browser that asked for it | Until that sign-in ends |
__Host-kosem_google_sign_in |
app.kosem.ai | Ties a Google sign-in to the browser that started it | Until that sign-in ends |
__Host-kosem_device |
app.kosem.ai | Remembers a browser that signed in before, so that others asking for codes for your address can't lock you out | 90 days |
__Host-kosem |
The site you open | Signs you in to a private site that an agent published | 1 hour |
kosem.theme |
Your browser's storage | Remembers whether you chose the light or the dark theme | Until you clear it |
If you sign in with Google, Google's sign-in button loads Google's script, which can set Google's own cookies, under Google's privacy policy.
Where kosem stores information
kosem stores and processes the service's data in the United States, in Google Cloud's us-central1 region. Its subprocessors process information where the table above says.
If you're in the European Economic Area, the United Kingdom or Switzerland, your information is transferred to the United States. Where the law requires a safeguard for that transfer, kosem relies on the European Commission's Standard Contractual Clauses, with the UK's International Data Transfer Addendum and the amendments Swiss law requires, or on another mechanism the law allows. To ask for a copy, write to privacy@kosem.ai.
How long kosem keeps information
| Information | How long kosem keeps it |
|---|---|
| Sign-in codes | 15 minutes |
| Sessions | 30 days without use, and 90 days at most |
| Known browsers | 90 days |
| Audit logs: Admin Activity, System Events and account activity | 400 days |
| Audit logs: Data Access | 30 days, or up to 400 days as your organization sets |
| Audit logs: Policy Denied | 30 days |
| The LLM gateway's request log | 90 days. Daily totals stay with your organization's usage. |
| Operational logs | 30 days |
| Customer Content in a project that's deleted | 30 days after the deletion is requested, when kosem purges the project. Until then, the project's owners can restore it. |
| Accounts and organizations | While they exist, then as Deleting your information says |
| Billing records | As long as tax and accounting law requires |
| The waitlist, from kosem.ai and the console's sign-in page | Until kosem opens to everyone, or you ask kosem to remove you |
| Database backups | 14 days |
Audit log entries that name you stay until they expire, after your account is deleted too, since they're your organization's record of who did what.
Deleting your information
- Projects, agents, environments, secrets and sites: delete them in the console, if your role allows it. A deleted project can be restored for 30 days, then kosem purges it.
- Your account or your organization: during the private beta, write to privacy@kosem.ai from your account's address. kosem deletes it within 30 days, except billing records the law requires kosem to keep and audit log entries until they expire. Copies in backups are gone 14 days after that.
- The waitlist: write to privacy@kosem.ai, and kosem removes your address.
Security
- Every connection to the service is encrypted with TLS.
- Google Cloud encrypts the service's data at rest. kosem seals secrets' values with Cloud KMS keys, never shows them again once written, and redacts them from agents' output. Model providers' keys are never shown again either.
- Each environment runs in a microVM of its own, isolated by hardware virtualization, which can't reach cloud metadata servers or private networks.
- People and agents can do only what their roles and grants allow, and the service records every change in audit logs.
- kosem's staff work through a separate application, which can't sign in as a customer and records every action.
No system is perfectly secure. If kosem learns of a breach that affects your personal information, it tells you, and the authorities, as the law requires. To report a vulnerability, write to security@kosem.ai.
Your rights
Wherever you live, you can ask kosem to tell you what personal information it holds about you, give you a copy, correct it or delete it. Write to privacy@kosem.ai. kosem first checks that the request comes from you, then answers within 30 days, at no charge. kosem doesn't treat you differently for using these rights.
In the EEA, the UK and Switzerland, you can also ask kosem to restrict how it processes your information, object to processing based on legitimate interests, receive your information in a portable format and withdraw consent you gave. You can complain to your data protection authority, though kosem would like the chance to help first.
In California and other US states with privacy laws, you have the right to know what personal information kosem collects, uses and discloses, and to delete and correct it. In the last 12 months, kosem collected these categories: identifiers, such as your email address, name and IP address; commercial information, such as purchases and credits; internet and network activity, such as logs and usage; and the content you put in the service. It collected them from you, from your organization and from your use of the service, for the purposes and with the recipients this policy lists. kosem doesn't sell or share personal information, as those laws define it, and uses no sensitive personal information beyond what the service needs. You can use an authorized agent to make a request.
For Customer Content, kosem acts for your organization. Send requests about it to your organization, and kosem helps it answer them.
Children
The service is for businesses and professionals, and for people 18 and over. kosem doesn't knowingly collect information from children. If you think a child gave kosem personal information, write to privacy@kosem.ai, and kosem deletes it.
Changes to this policy
kosem updates this policy as the service changes, and the date at the top says when it last did. Before a material change takes effect, kosem emails the people who have accounts. To see an earlier version, write to privacy@kosem.ai.
Contact
Kosem AI
- Privacy: privacy@kosem.ai
- Security: security@kosem.ai
- Legal: legal@kosem.ai