Guide · Encryption
What is the Secure Enclave on iPhone, and what does it guard?
The Secure Enclave is a separate security system inside the chip of an iPhone, iPad or Apple silicon Mac, with its own processor and memory. Apple describes the Secure Enclave as a dedicated secure subsystem, isolated from the main processor, designed to keep sensitive user data secure even when the Application Processor kernel becomes compromised. An app can ask it to use a key, but never to hand the key over. It guards keys, not what you have already unlocked and opened on screen.
On this page
A small computer inside the chip
Your iPhone’s main processor runs iOS and every app. The Secure Enclave is a second, much smaller system on the same chip, walled off from the first. Apple says it is isolated from the main processor and has its own parts:
- Its own processor, used for nothing else.
- Its own encrypted memory, checked so that tampering shows.
- An encryption engine whose hardware keys software can’t pull out.
- A boot ROM that can’t be changed and checks the Enclave’s own system before it starts.
The idea is simple. If someone finds a flaw in iOS and takes over the main system, the keys in the Enclave are still out of reach. Apple describes the Secure Enclave as a dedicated secure subsystem, isolated from the main processor, designed to keep sensitive user data secure even when the Application Processor kernel becomes compromised.
What it holds
Apple’s security guide says the Enclave manages a root key unique to each device and guards Face ID and Touch ID data. Three everyday things depend on it.
- Your passcode. It is mixed with the device key, so a guess can only be tested on that phone, at the speed the phone allows. Apple says one try takes about 80 milliseconds, and longer waits follow wrong tries.
- Your face or fingerprint. The data used to match you stays inside the Enclave. The rest of the phone hears only “match” or “no match”.
- The disk keys. Data on the phone is encrypted, and the keys that open it depend on the device key. Apple says all data on an iPhone is stored in encrypted form, and that setting a passcode turns on Data Protection.
How apps use it
An app can ask the Enclave to make a key, then ask it to sign or decrypt something with that key. The key stays inside, and the app gets back only the answer. The app can also attach a rule, such as “only after a live face or fingerprint match”. Then even the app that made the key can’t use it without you. This is how Apple describes keys that never leave the chip.
That rule has a catch. If you add a new face or finger, the phone can retire keys tied to the old set on purpose, when the app asked for that as it made the key. It is a safety feature: a thief who adds their own face gains nothing. But any app that uses such a key needs a second way back in, or a new enrolment locks you out of your own data.
What it doesn’t protect
The Enclave keeps keys safe. It does not judge what happens after you unlock.
- An unlocked phone. Once you are in, apps read their data the normal way. Whoever holds the open phone sees what you see.
- A known passcode. Someone who watched you type it gets in the way you do. The Enclave only slows guessing, as Apple’s passcode page explains.
- Copies that left the phone. A photo you sent, shared or uploaded is outside its reach.
- Most app keys. Many apps keep keys in the Keychain, which the device protects but which apps can read while the phone is unlocked. Using the Enclave is a choice each app makes. Apple says keychain items in a class marked “This device only” are protected with the device’s own key when they are copied during a backup, which makes them useless if they are restored to a different device.
So the chip inside is a fact about the phone, not a promise about every app on it. For a wider view of what the phone encrypts on its own, see are photos encrypted on iPhone?. For the cipher side, see the AES guide, and for who can hold your keys at all, zero-knowledge encryption.
A worked example: unlocking your phone
Here is what happens in the half second after you look at the screen.
- The camera system sends what it sees to the Enclave, not to iOS.
- The Enclave compares it with the stored data and decides.
- On a match, it releases the keys that let iOS read your data. iOS itself never sees your face data.
- On a miss, nothing is released, and after a few misses the phone asks for the passcode.
Typing the passcode follows the same path: the Enclave checks the guess against the device key, at its own pace. Both paths are in Apple’s security guide.
Questions to ask an app that says it uses it
- Which key lives there? The key that opens your data, or something smaller, such as a login token?
- When can the app use it? Any time the phone is unlocked, or only after a live match?
- What happens when you change your face or finger? There should be a written way back.
Where Sealed helps, and where it doesn’t
It helps if you want the vault key bound to the Enclave, through an optional mode described on its feature page. Maximum Security is part of Sealed Pro.
It doesn’t use the Enclave by default. Without Maximum Security, the app can read your vault key whenever the phone is unlocked, because the key sits in the Keychain.
It doesn’t protect a photo once it is open on screen, or a copy you exported. Until you delete them, the originals stay in Photos, outside the vault.
Questions and answers
Does every iPhone have a Secure Enclave?
Most recent models do, and so does every Mac with Apple silicon. Apple’s security guide lists the chips.
Can an app read a key out of the Secure Enclave?
No. An app asks it to use a key and gets back only the result, as Apple describes.
Is the Secure Enclave the same as the Keychain?
No. The Keychain is a store for passwords and keys that apps use while the phone is unlocked. The Enclave is hardware that can hold a key and use it without ever handing it out. Apple says keychain items in a class marked “This device only” are protected with the device’s own key when they are copied during a backup, which makes them useless if they are restored to a different device.
Sources
What this page says about Sealed was checked against the app on .
- Apple Platform Security, Secure Enclave — published December 19, 2024; isolated from the main processor; its own processor, memory protection, AES engine and boot ROM; manages a device-unique root key and protects Face ID and Touch ID data. Read 13 Nov 2026
- Apple Platform Security, Passcodes and passwords — published December 19, 2024; the passcode is entangled with the device’s UID, and one try takes about 80 milliseconds. Read 13 Nov 2026
- Sealed on the App Store — the listing for the app used as the example
Get Sealed
Sealed is free to download, and Sealed Pro is an optional in-app purchase.