How your data moves

This is the boundary between your browser, Thinkpool cloud, the computer running the bridge and repository, and your AI provider.

The four stops

1. Your browser renders the room, sends room content, and seals provider keys.
2. Thinkpool cloud stores account, room, and readable transcript data. It relays sealed key envelopes but cannot open them.
3. Local bridge and repository run on the host computer. The agent reads and changes the repository there.
4. Your AI provider is contacted by the local agent. Prompts may include code context chosen by that agent.

What Thinkpool stores

Thinkpool stores account and plan data, room membership and metadata, room chat, cleaned terminal output, terminal and room events, attachments, and operational request metadata. Thinkpool does not upload the repository as a file tree.

Controls

Room owners can delete a room, export readable room records as JSON, keep a room until manual deletion, or set it to expire after 24 hours, 7 days, or 30 days. Account deletion is available in Settings.

Proof

The security architecture, bridge protocol and outbound domains, subprocessor inventory, vulnerability disclosure, and security.txt are published.