livingbrain.wiki Sign in

Security and privacy

It only knows what you're allowed to know.

Living Brain reads with the asker's own access. Grants, roles, agent keys, the audit log and encryption at rest per scope are live. Hidden-text screening, mail and bring-your-own key are planned, and the limits are stated plainly.

Where you ask decides what it can use.

your DMs private channel shared brain
What it can use, by where you ask
Asked inShared brainPrivate channel memoryPersonal memory
Public channelYesNoNo
Private channelYesThat channelNo
Your DMsYesChannels you're inYes

Always limited to what the person asking can already see. It follows your chat's permissions (Slack channels, Discord roles), which are planned. In the web app and over MCP, reads follow the grants an owner or admin sets for each person, role, agent account, folder or project. How grants work.

Encrypted per scope, at rest.

Live

The access rules above aren't only a check in code. Each scope has its own data key, so a leaked key exposes that scope and nothing else. Page bodies and fact values are sealed with XChaCha20-Poly1305 under the key of their scope.

page textAES-256-GCM, scope keyciphertext in storage
scope keywrapped byworkspace key, in a separate key service
Scopes: shared brain · each private channel · each person · customer-safe pages. Bring your own key on Teams is planned.
01

One key per scope

The shared brain and every person have their own data key, stored wrapped and rotated by version. Pages, sources and facts are sealed under the key of the scope they belong to.

02

Search without opening everything

Search uses a blind index: keyed hashes of the words in each scope, so a query only touches the scopes you can see. Matching pages are decrypted in memory for that one request.

03

Keys on your device (planned)

Planned: the CLI and the app keeping scopes under a key from your keychain or passkey, and searching locally without a network round trip. Today the service holds the keys.

04

Delete the key, erase the memory

Forget a channel, offboard a person or revoke a mailbox: delete that scope's key and its memory is unreadable everywhere, backups included.

The honest limit: the service holds the wrapping key and decrypts to serve and answer, so this is not end-to-end encryption, and the model reads the text to write the wiki. Slugs, subjects and attribute names are stored in plain text. Hosted plans protect your data at rest and scope by scope, but not from the running service itself. For "even you can't read it", self-host on the Community or Teams plan. Keyword hashes also reveal which words repeat within a scope, never across scopes.

Hidden text is screened.

Planned

Everything it reads, from Slack and Discord, mail, imports, agent logs and git, is screened for hidden text by PromptDecode, a sister Factory Zero venture, so an invisible instruction in one message can't reach every agent's context. Anything that decodes to an instruction is held for a person to review.

Mail stays yours.

Planned

Connected mailboxes (Gmail, Outlook, IMAP) stay in the owner's personal memory, encrypted with their key, unless they share a specific label or folder. Every message passes Owlpost's spoofing and prompt-injection checks first, and mail can never trigger actions. Revoke a mailbox and its stored mail is erased.

What leaves your machine.

Planned
  • Anonymous usage counts. The CLI and a self-hosted server send counts and timings, bucketed, with no free text and no ids beyond a random one. The first run shows the exact batch, and livingbrain telemetry off turns it off.
  • Never collected. Message text, page bodies and secrets. They stay out of the logs too.
  • Your own monitoring. Living Brain exports its metrics, traces and logs over OpenTelemetry. The audit log in the web app, for owners and admins, records settings and access changes.

Your data, your call.

  • Not used for training. Your messages and pages never train models, ours or anyone else's.
  • Plain Markdown. Export the whole wiki any time, or keep it in your own git repo. You own it
  • Self-host for full control. The Community plan is free for up to 5 people on your own Cloudflare account; larger teams need a Teams license. The code is public on GitHub. Plans

Who else touches it.

Today the marketing site and the hosted app run on Cloudflare. Everything else here is planned, and labelled so.

  • Cloudflare (hosting). The site.
  • Polar (payments) (planned, not in use yet). Hosted plans through Polar as Merchant of Record. Nothing is on sale yet.

Factory Zero ventures this site uses or will use: Cratefield (framework, planned); Owlpost (email, planned); SupportGenius (support, planned); SupportGenius (bug reports, planned); promptdecode (security screening, planned); Keep Shipping (deploys, planned). The full list, with what is live and what is planned, is in the Factory Zero registry.