# Privacy

This page says who can read what inside an organization. Roles are in [Organizations and roles](/organization).

## Your own chats

In [Chat](/chat), the sidebar lists only your own chats. This holds for every role.

## Personal bot chats

Chats with the [Personal bot](/personal-bot) are private. Owners and Admins see that a chat exists, whose it is, and how many tokens and minutes it used, but not its title and not what was said. They cannot open it. The chats and their files stay hidden from them, also in Slack and Teams direct messages with the Personal bot. You always read your own.

An Owner or Admin can take access for 2 hours. In the Console, under Settings, Capabilities, they choose "Take access" and confirm. The session lists show private chats of other people without content and offer no way to take access. The access holds for that one organization and ends after 2 hours. They can then read the Personal bot chats of other people, also older ones.

Every takeover is written to a log that nobody can change or delete: who, which organization, when it started, and when it ends. Owners and Admins read the log in the Console under Members, Audit log. The people whose chats are read are not told.

Owners and Admins always see activity totals for each person, without a takeover. They do not see what was said.

## Company Bot chats

Owners and Admins can read the chats with [Company Bots](/bots). They open them in the Console under Bots, Sessions, with the transcript of each chat. Members do not see the chats of others.

## Feedback on answers

When you rate an answer in [Chat](/chat) with a thumbs up or down, the rating and your optional comment are stored with the chat, the answer, and your name. For now GEKI reads it to improve the bots and the service. Later Owners and Admins of your organization will read it in the Console, like the chats of Company Bots.

## Memory

A [memory](/memory) belongs to one person. Only that person reads, edits, exports, and clears it in Chat. A Company Bot that reads memory reads the memory of the person it talks to. No key and no role reads the memory of another person. Owners and Admins see numbers only: how many people have a memory, how many pages, and the total size.

## Knowledge Bases

A [Knowledge Base](/knowledge) is shared. Anyone who can use a bot with access to it can have the bot show what is in it. When a bot has "Read & write" access, what one person tells the bot can end up in the pages and reach everyone. The History tab shows every change.

## Tokens and secrets

- Credentials in vaults, connector credentials, endpoint keys, and API keys are write-only. The Console and Chat never show a saved secret again.
- A connected account, such as a Microsoft 365 sign-in or a token for an MCP connector, is stored for that person only. Only that person's chats use it, and a trigger that runs as that person. It is deleted when the person leaves the organization. Owners and Admins see which accounts a person connected, never their content.
- API keys belong to a person or a service account. A person sees their own keys. Owners and Admins see and revoke every key of the organization.

## Channels

In a Slack or Teams channel, a bot answers as the connector, not as the person who writes. Everyone in the thread sees the answer. The bot reads the messages of members in a thread it is in, as context. A direct message with a Company Bot is a chat of that person. Owners and Admins can read it under Sessions like any other Company Bot chat. A direct message with the Personal bot stays private. Messages outside such threads are dropped.

## When a person leaves

When an Owner or Admin removes a person, that person leaves all groups, their own tokens are deleted, and their triggers are turned off.