Team0
ProductHow it worksWorks withUse casesAppsPilotsBook a call

You can see it, correct it, and switch it off.

Team0 holds a brain for each of your people and one for the company, so it has to be one you can inspect and control. Here is what each person can do, and how it runs.

You decide
Stop savingIt can still read
Stop all accessNext request refused
Withdraw a shareGone within a minute

Nothing hidden from you.

Everything Team0 understands can be opened to see its source, who said it, and what it replaced. Every agent read is written down: the full result is kept 24 hours, the read log’s content 24 hours to 30 days (set per person), and its record 30 days.

See the source
Each statement names the email, meeting or document it came from.
See every agent read
What each connected agent asked and what Team0 gave back, kept for the time each person sets.
Correct it once
Fix something in one place and every agent reads the fix.

Stopping, removing and deleting are different things.

Each control does one specific thing. So you always know what an action will and won’t do.

What each control does
When youWhat happens
Opt out of SlackTeam0 stops learning from your Slack messages.
Stop an agent from savingIt can still read. Nothing new from it is added.
Stop all access for an agentIts next request is refused. Your other agents are not affected.
Disconnect a sourceTeam0 stops reading it right away. What it learned before stays visible until you remove it.
Remove something Team0 learnedOne item at a time, and you can see where each came from before you do.
Stop sharing with the companyNew facts stop crossing. Previously shared work stays until it is separately withdrawn or removed.
Leave the companyThe work facts you shared stay with the company. Access is revoked and the private brain is erased after meeting bots are confirmed stopped; backups follow their retention policy.

Sharing is yours to choose.

Each person has a private brain. The company brain only gets what people choose to share.

Off until you choose
Nothing is shared until you turn it on, unless your company sets a default for people who haven’t chosen and shows it to you first. Your own choice always wins.
Work facts only
Only work facts cross, and from email only mail on your company’s own domains. Sensitive-content checks help hold private information back, but models can miss.
Your name on it
Each shared fact says who shared it: “shared by Kate”. The fact crosses, never the quotes or evidence behind it.
Withdraw any time
Withdraw the shared item from company use and retained shared copies. Information already read cannot be unread, and backups follow their restoration policy.
Your brain stays yours
Coworkers and admins cannot open your private brain through Team0. Permitted coworker lookups are visible to you. The server operator can technically read the database.
When someone leaves
The work facts they shared stay with the company. Their private brain is erased.

How it runs.

The short version. The full statement is on our security page.

Signed updates
Each nightly update is signed, checked before it installs and rolled back if it fails. Your install’s key can be revoked.
Health and cost you can see
Health checks, backups you can restore, and analytics on model cost and answer quality.
Your own cloud
Team0 runs in your AWS or Google Cloud account, or on a server of its own that we run for you.
Your model keys
AI models run on your company’s own keys, under your own terms. The selected providers process model inputs under the company’s agreements and settings.
Each person kept apart
Personal access is separated from company access, and sharing follows the person’s choice and the company’s disclosed policy.
We don’t browse it
We reach the install only through operator access you grant and can revoke. If we need to look at something to fix a problem, we ask first.
No SOC 2
We do not hold SOC 2. Installed in your cloud, your data stays under your own controls.
Agents get their own keys
Every agent connects with its own access, which you can change or revoke without affecting the others.
Security and data handling→Privacy policy→

External services are explicit.

Brain storage runs in the customer’s cloud. Clerk provides sign-in and agent OAuth. Selected model providers process model inputs, and Recall processes meeting recordings when enabled. The company controls those provider accounts; this is not an offline installation.

Every agent in your company, in the know.

Book a callHow it works→
Team0

A brain for each person and one for the company, read by every agent.

Product
  • Product
  • How it works
  • Sources
  • Walk through an example
  • Use cases
  • Apps
  • How a pilot works
Technology
  • The World Model
  • Architecture
  • Data model
  • Entity resolution
  • Truth maintenance
  • Trust and scope
  • Understanding Engine
  • Comparisons
  • The 31 problems
Second brain
  • What is a second brain
  • Markdown vs Team0
  • Memory vs understanding
  • How agents connect
  • A second brain you have to feed
Agents
  • Works with
  • Developers
  • Connect over MCP
Trust
  • Trust and control
  • Security
  • Privacy
  • Terms
Company
  • About
  • Blog
  • FAQ
  • Support
© 2026 Team0Every agent in your company, in the know.