The answer, step by step
- 01Encrypted vault content
After unlock, the current key opens every item and attachment ciphertext. Only successful AES-GCM authentication counts as verified; failures are counted separately.
- 02User-held recovery key
A CloudKit structure read-back verifies that the configuration does not contain the 12-word phrase. Until then, the state remains pending.
- 03Daily access protection
Daily password protection and current Face ID authorization must be configured, with the last successful verification time shown.
- 04CloudKit ciphertext read-back
Known record IDs are fetched directly and compared with ciphertext. A newer failure overrides an older success receipt.
- 05All three states matter
Pending means evidence is unavailable and must not masquerade as safe. Failed requires action and cannot be hidden by an older success.
How to check this claim
Open each status from the home ticker or Security Center. Check the latest time, authenticated item and attachment counts, verified CloudKit counts, and any failure after the success receipt.
See the full verification protocol →What this answer does not claim
Direct answers
Why is a status pending?
The first unlock, local ciphertext authentication, or successful CloudKit read-back has not completed. Pending is neither failed nor verified.
Does successful sync prove decryption?
No. Read-back proves matching ciphertext exists; correct-key AES-GCM authentication proves decryption.
What should I do after a failure?
Pause new writes and sharing, record the time and error, inspect network, iCloud account, and local unlock state, then rerun the relevant check.