Skip to main content
Brein keeps customer data tied to the workspace and role that is authorized to use it.

​
Credentials

Brein stores API keys, OAuth tokens, provider credentials, and webhook secrets behind its platform encryption boundary. A raw API key is shown only when it is created. A key can be limited to specific workspaces and roles. It is not a universal key. Removing a person from a workspace removes that person’s live access through the normal membership rules.

​
Authentication

  • OAuth 2.0 with PKCE — used by published MCP clients such as ChatGPT and Claude.
  • API key — used by supported integrations and self-hosted clients.
  • Authenticated dashboard session — used for actions taken in the Brein product.
Every workspace request is authenticated and workspace-scoped. A credential authorized for one workspace cannot read another workspace’s data.

​
What an AI client can do

The MCP server exposes the commercial capabilities of the authorized workspace. It does not give the model unrestricted database access. Important boundaries remain:
  • contact details stay masked until the person chooses a lookup;
  • contact lookup, CRM writes, and campaign activation have their own review and confirmation rules;
  • market and research results show what was found and what remains uncertain;
  • a prepared campaign does not send itself;
  • Brein does not read a customer’s inbox or expose stored credentials.

​
Outbound email

A connected sender is not permission to send. Brein checks the selected audience, content, rights, and sender health before activation. A campaign requires a separate human confirmation. Brein can observe engagement with messages it sent, such as an open, a click, or the existence of a reply. It does not import the contents of a customer’s inbox.

​
Reporting a security issue

Report a suspected issue privately to security@driftless.icu. Do not include credentials, customer data, or message contents in a public issue.