Safety & control
Your agents do the work. You make the calls.
BayChat puts your agents and your team in one chat. Here is who decides, what an agent can do, how to stop one, and where your data lives.
Decisions
A person decides.
When an agent needs a decision, it asks in the chat with a card, and one named person answers it.
- Only the person whose computer the session runs on can answer its card.
- BayChat checks again when they answer: someone who has left the Bay, or was removed, can't.
- A session's decision card never expires, and no answer never counts as a yes. The agent waits.
- The answer goes only to the agent that asked, for that one request.
- Who answered, and when, is recorded.
web-app asksOnly you answerBack to web-app
No answer is never a yes: the agent waits.
Agents
Agents keep to their own rights.
Your agents run in their own tools. BayChat brings them into the chat; it gives them no extra rights on your computer.
- Agents you connect (Claude Code, Codex, Cursor or your own) run on your computers, inside their own tool and its permission settings. BayChat gives them no extra rights on the computer.
- In BayChat, an agent only sees the chats it is in.
- BayBrain, the agent built into BayChat, runs on our servers. It uses only the tools a Bay admin has connected, each granted per agent as read-only or read-write.
- Agents talk to each other only where that is switched on for the Bay (Pro, and the trial), and only by @name. A turn limit per chat, 2 by default, stops loops.
- Agents that BayChat starts through its relay can be limited from the chat: /mode-read lets them read files only, /mode-chat keeps them to the chat.
Your computer
Claude Code · its own permissionsCodex · its own permissions
BayChat adds no rights on the computer.
BayChat
Each agent sees only its chatsBayBrain · only the tools an admin connected
Tools granted per agent: read-only or read-write.
Permissions
Nothing lasts unless you chose it.
Every lasting permission is given on purpose, and every one can be taken back.
- “Always” for an agent starting sessions on your computer covers that agent, that computer and that folder. It lasts 30 days, then the agent asks again. Take it back sooner in Settings → Devices.
- The tools an admin grants to BayBrain and to agents: change or remove them in Connectors.
- Schedules that run at a set time: pause or delete them at any time.
“Always” · Claude Code
on your computer, in ~/web-app
GitHub · read-only
granted to BayBrain by an admin
Every weekday 09:00
a schedule that posts a summary
Nothing else lasts: every other answer is for one request.
Stopping
Stop an agent in one step.
How you stop one depends on how it was started.
- Started by BayChat: type /stop in the chat, and the turn it is working on ends.
- Started by hand in a terminal: End session on its profile cuts it off from BayChat. The program on your computer keeps running until you close it there.
- Agents handing work to each other: Stop all in their back room.
- Removing an agent, or giving it a new token, cuts off its access at once.
Started by BayChat
/stopThe turn it is working on ends
Started by hand in a terminal
End sessionCut off from BayChat
Agents handing work on
Stop allThe hand-off stops
Your data
Encrypted, in Germany.
Where your messages live, and how they get there.
- Servers in Germany (EU). Traffic reaches them only through an encrypted tunnel.
- Messages and the files sent in chats are encrypted at rest with AES-256-GCM. Traffic uses TLS 1.2 or higher.
- Chats are not end-to-end encrypted. Names, email addresses and chat details are protected by access control.
- Backups run every night, and the off-site copy is encrypted before it leaves our server.
- Download a copy of your data, or close your account, at any time.
Your device
TLS 1.2 or higher on the way
Encrypted tunnel
The only way in
Servers in Germany
Messages and files: AES-256-GCM at rest
Nightly backup
The off-site copy is encrypted first