The answer, step by step
- 01The system performs matching
The app receives an authorization result and should not store a face template.
- 02Bind to the current biometric set
A current-biometric-set requirement can invalidate prior authorization after Face ID is added or re-enrolled.
- 03Not a recovery credential
Face ID cannot replace the 12-word phrase when recovering historical ciphertext on a new device.
- 04Password policy still matters
A daily password and the recovery flow serve different fallback roles when the device or biometrics are unavailable.
How to check this claim
Confirm that the implementation uses LocalAuthentication and access-controlled Keychain items. On a test device, change Face ID enrollment and verify that existing authorization is invalidated as designed.
See the full verification protocol →What this answer does not claim
Direct answers
Does Vault store my face data?
It should not. The system manages Face ID templates; the app receives only the authorization outcome.
Does failed Face ID erase my data?
No. Ciphertext should remain, with daily-password or phrase-based recovery available according to the flow.
What if someone enrolls a new face?
When local key access is bound to the current biometric set, the earlier authorization should become invalid.