How Mum works

Built to be checked.

Mum runs on sealed computers that even we can’t open. This page explains how the whole system works, and how each part is checked.

A message’s journey

Sealed the whole way.

Here’s what happens when you send Mum a message, and who can read it at each step. The answer is always the same: you and your Mum. The web is the one exception, and we say how it works below.

01
Your phoneEncrypted here

You message Mum in Signal. Signal encrypts the message on your phone before it goes anywhere.

02
Mum’s Signal lineKey never leaves

Mum’s Signal account lives in its own sealed computer. Its key is created inside and never leaves sealed hardware, so Signal’s encryption ends inside hardware we can’t read, not on our servers.

03
Your MumNo way in

Before the line hands your message on, it and your Mum check each other’s hardware proof, and the message crosses our relay locked so only your Mum can open it. Your private Mum runs in its own confidential computer, with memory encrypted by the processor itself. Nobody can log in, open a shell or read its logs, including us. There are none.

04
The AI modelNobody reads along

The model that writes Mum’s replies runs inside a secure enclave on the graphics chip. Before your Mum sends it anything, it checks the enclave’s hardware proof, so nobody outside the enclave can read your conversation, including us.

05
Back to youEnd to end

Mum’s reply comes back the same way: locked to Mum’s Signal line across our relay, then encrypted end to end to your phone.

When Mum uses the web1920 × 1080

Every visit Mum makes is anonymized, unless you’ve asked it to sign in for you, and its browser uses a standard 1920×1080 window, the most common screen size in the world. To a website, it looks like one more ordinary visitor. Its visits come through ordinary home internet connections in your area. Browsing with Mum is private, and the AI that steers its browser isn’t told who you are.

Messages we can readNone
Logs from the sealed computersNone
Metadata keptNone
Sealed computers

Your keys only open for the right build.

Each person’s Mum runs in its own confidential computer. The processor encrypts its memory with a key that never leaves the chip, so from outside, its memory is only scrambled data. Nobody can log in, open a shell or read its logs, including us. There are none.

The chip also proves exactly which software is running. Your key is held in a hardware security module, which releases it only to a sealed computer whose proof matches a version recorded in the public log. Any other software, even a slightly changed version, doesn’t get it.

Who gets your keysExample
The logged builda91f 07c2 5be3 … 9d0c e44b
✓ Keys released
Any other builda91f 07c2 5be3 … 9d0c e44c
✕ Stays locked

One character different is a different build, so the keys stay locked.

No quiet changes

Every change goes on the record first.

Before a new version of Mum can receive anyone’s keys, its fingerprint is signed and added to a public log built so that entries can’t be quietly changed or removed. A version that isn’t in the log can’t get your key, so nothing changes without a public record.

Fingerprinted

Each new version gets a fingerprint of exactly what may run inside the sealed computer: the software, its commands and its settings. Change one character and the fingerprint changes.

Logged in public

We sign that fingerprint with a key that never leaves a hardware security module, and add it to the public log.

Checked before keys

A sealed computer gets a key or a message only when its chip’s proof matches a fingerprint in the log. Anything else stays locked.

How it’s checked

Checked, every time.

You don’t have to take our word for any of this. At every handover, hardware checks hardware, and one check is yours.

  1. 01
    The line and your Mum check each other

    Before Mum’s Signal line hands your Mum anything, the two sealed computers check each other’s hardware proof.

  2. 02
    Your key checks the chip

    Your key leaves its hardware security module only for a sealed computer whose chip proves it’s running a version in the public log.

  3. 03
    Your Mum checks the AI

    Before your Mum sends anything to the AI hardware, it checks the enclave’s hardware proof and that its software is published.

  4. 04
    You check the safety number

    Signal shows a safety number for your chat with Mum and warns you if it changes. Mum’s Signal key never leaves sealed hardware, so a change you didn’t expect is worth telling us about at hi@mum.ai.

By design

What we can’t do.

We can’t log in.

Nobody can log in to your Mum’s sealed computer, open a shell or read its logs. There are none.

We can’t read your messages.

Signal’s encryption ends inside a sealed computer whose key never leaves it, not on our servers.

We can’t change the code quietly.

Every new version is recorded in a public log before it can receive anyone’s keys.

We can’t read along with the AI.

Mum’s replies, reading, sorting and dreams run inside hardware-sealed enclaves, so nobody outside them can see your conversation.

We can’t see who you talk to.

Mum doesn’t store metadata, so there’s no record of who, when or where from.

We can’t see your Signal number.

Mum’s Signal line keeps the link between your Signal account and your Mum inside its sealed computer. Our other systems see only a stand-in.

At a glance

The whole system, in one table.

Where Mum runsSealed confidential computers. The processor encrypts their memory with a key that never leaves the chip.
Access for our teamTo the sealed computers, none. No logins, no shell, no logs.
KeysHeld in a hardware security module, released only to a sealed computer running a logged version.
UpdatesRecorded in a public log before they can receive any keys.
SignalMum’s key is created inside a sealed computer and never leaves sealed hardware.
AI modelReplies, voice, reading files and pictures, sorting your email and dreams run on sealed AI hardware that proves what it’s running.
Messages we can readNone.
MetadataNot stored. While a message is in transit, our relay knows which Mum it’s for and when it arrived, and deletes that within minutes of delivery.
Training on your dataNever.
Safety numberSignal warns you if Mum’s key ever changes.
AccountsA random ID. No name or email. Your Mum is tied to your Signal account.
Web browsingBrowsing with Mum is private, and the AI that steers its browser isn’t told who you are.
Deleting your accountSelf-serve in your Mum portal at mum.ai. Your sealed computer and its storage are deleted, and its key is destroyed.
Logins and cardsKept private in your own encrypted vault. Every payment needs your yes.
Earlier serversEarly testers’ data stays on our previous servers until each tester confirms everything moved. Then it’s erased.
Go on. Tell Mum.Private AI that lives in Signal.