Skip to content
BaseThread

Security & privacy

It's your team's context. It stays yours.

BaseThread holds some of your most sensitive context, so it's built local-first and private by default.

Where your context lives

Local-first by design, private by default

Your context is the source of truth in the cloud, mirrored to your own machine, and read by tools running on your key. Here's the path it takes.

Source of truth

BaseThread cloud

  • Encrypted at rest (AES-256-GCM)
  • Row-level security per workspace
Synced

Your machine

  • Local mirror by the Mac agent
  • Reads work offline
Over MCP

Your AI tools

  • Read by your own AI tools
  • They run on your accounts

Never used to train models. Your context only ever answers your team's questions.

The guarantees

Built for your most sensitive context

Local-first

Your context syncs to your own machine and reads work offline. The cloud is the source of truth, not a hard dependency for every read.

Encrypted at rest

Sensitive context is encrypted with AES-256-GCM. The encryption key lives outside the database.

Your tools, your accounts

The AI tools you connect run on your own accounts. BaseThread serves them context over MCP; it does not run your AI for you.

Never training data

Your context is used to answer your team's questions. It is never used to train models.

Row-level security

Access is enforced at the database with row-level security, so members only ever read the workspaces they belong to.

Self-host on the roadmap

Cloud today, with self-host and on-prem options planned for teams that need context to stay inside their own infrastructure.

FAQ

Security questions, answered

In your BaseThread workspace in the cloud, with row-level security so only your members can read it, and mirrored locally to each member's machine by the Mac agent. Sensitive fields are encrypted at rest with AES-256-GCM.

Get your team's AI tools on the same page

BaseThread is the shared context-graph that Claude Code, Cursor, and every AI tool your team uses can read, so no one re-explains the same context twice.

Request access