How it worksThe security model
A key that can’t be copied, and the rules around it.
Seal is built on one idea: the key that opens your files and signs for you lives in your iPhone’s security chip, and nothing can copy it out. Here is what that means, in plain words, and where its limits are.
01Two halves
Every key has a private half and a public half.
The two halves are made together and fit only each other. What one half locks, only the other opens.
The private half
Stays in the chip
It opens files and signs. It stays in your iPhone’s chip, and nobody ever sees it.
- Made inside the chip; it never leaves it.
- Works only after Face ID.
- On a Ledger, the card’s private halves stay in the Ledger.
The public half
Safe to hand out
A small file. Whoever has it can seal files that only your iPhone opens, and check that a signature came from you.
- Send it with AirDrop, Messages or Mail, or paste it into any chat.
- To be sure a key is really someone’s, read the fingerprint to each other on a call.
02Either key opens
Two keys are two doors, not two locks.
When you seal a file, you tick the keys that may open it. Each ticked key opens the file on its own. You never need two at once.
That way, losing one key doesn’t lose the file. Seal suggests a second key for anything you must keep: a backup key, or a Ledger.
A vault is a saved set of these ticks, with a name. A change to a vault counts for files sealed from then on: files sealed before keep the keys they were sealed for.
03What is stored where
What Seal keeps, and where it keeps it.
| What | Where | What that means |
|---|---|---|
| This iPhone’s private key | The iPhone’s security chip (the Secure Enclave) | It never leaves the chip and works only after Face ID. It can’t be copied, by design. |
| A Ledger’s keys | The Ledger | Seal reads the card. It never writes to it, never changes a PIN, never makes or deletes a key there. |
| Files a vault keeps | This iPhone, in Seal’s own space | Sealed on the disk, and the disk keeps them unreadable while the phone is locked. Not in iCloud Drive and not in the Files app. If iCloud Backup is on, they travel in your phone’s backup, still sealed. Deleting Seal deletes them. |
| A file you’ve opened | Memory only | Never written to the disk. Closing the screen, or leaving the app, lets it go. |
| Text you copy from an opened file | The clipboard, for a short while | On this iPhone only. |
| An unsealed copy you save | Where you choose | After that, that copy is yours to look after. |
| Sealed files you share or save | Where you put them | A sealed file is safe to send anywhere: only its keys open it. |
| The OpenPGP PIN | The card, and nowhere else | Not saved, not logged. Three wrong tries and the card locks. |
04Face ID and the chip
The key belongs to this iPhone alone.
If you lose your iPhone
- The phone’s key goes with it: it can’t be copied, by design.
- Files sealed for another key you own, such as a Ledger or a backup key, still open with that key.
If you set up Face ID again
- iOS retires keys tied to the old Face ID, so this iPhone’s key stops working. Seal says so, and you can make a new one.
- Files sealed only for the old key can’t be opened.
That is why Seal asks you to seal anything you must keep for a second key too. A file sealed only for the iPhone’s key opens only on that iPhone.
05Signatures
Every signature names its purpose.
A signature says you stand behind exactly those bytes. Each one Seal makes names what it is for: a commit, a file, a pass. A signature made for one can’t be used as another, and never as a login.
For a commit, the phone shows the commit’s message, its author and its IDs, not the changes in the code: look at those on the Mac before you sign. On the Mac, the signature is checked with ssh-keygen before git gets it.
06The session lock
What the session lock does, and doesn’t do.
Anyone who gets into your computer, or into your account, can talk to the agents working there. The lock puts your phone in the way: a Claude Code session under it holds every message and every tool call until your iPhone signs a pass.
What it does
- It holds messages and tools in sessions started under it. Your other sessions are not under the lock.
- Nothing on the computer can make a pass, because the key is in your phone.
- While a pass is good, the session works as usual, with Claude’s own permission questions.
- From the phone, a line starting with
!arrives as a plain message, and is held. seal-gate pass droplocks it again before the 30 minutes are up.
What it doesn’t do
- A command typed with
!at the Mac’s own keyboard is not held. But whoever sits at your keyboard can open Terminal anyway. - The lock’s files belong to your user account. A hardened version, with its rules in an admin-owned file, is planned.
- It can’t stop someone using a stolen login on Anthropic’s own servers. It stops them running anything on your computer.
The Mac side is a Claude Code plugin, Seal for Mac: /seal:on locks every session on the Mac, and /seal:off needs your phone too. Away from the Mac, with Remote Control, the held message shows the request as one line you copy on the phone, and you paste the signature back as your next message.
07What Seal never does
The rules that don’t bend.
- It never talks to the internet. There is no account, no analytics and no network code. It reads and writes only what you hand it.
- It never holds a private key in a file. Yours stays in the chip; a Ledger’s stays in the Ledger.
- It never writes an opened file to the disk. Opened files live in memory, and closing the screen lets them go.
- It never asks for Face ID for a file it can’t open. Seal reads who a file is for before anything is opened, and says so first.
- It never shows what was open to someone glancing. When Seal isn’t in front (the app switcher, Control Center), it shows a plain cover. Leaving the app closes any opened file.
08Standard formats
Nothing depends on Seal.
OpenPGP, for sealed files
- What Seal seals, gpg opens. Files cross between the phone and any computer.
- A file sealed for someone’s key opens with Seal or with gpg on a computer.
- A file locked with a passphrase opens with GnuPG 2.3 or newer, or with Seal.
OpenSSH, for signatures
- What Seal signs, OpenSSH checks:
ssh-keygenon any computer. - Git signs commits with it, and GitHub can show them as Verified.
- A message you sign comes with the one line that checks it on a computer.