How iOS 18 Securely Stores Call Recordings Locally

Apple introduces native call recording within the Phone app in iOS 18, routing the generated audio files directly into the native Notes app for management. This article examines the security mechanisms Apple uses to protect these audio files on local storage, including the Data Protection API, application sandboxing, hardware-backed encryption via the Secure Enclave, and on-device transcription processing.

Sandboxing and the Notes App Container

When a call recording finishes, the Phone app does not expose the raw audio file to a universally accessible directory. Instead, the system transfers the audio directly into the protected application container of the Notes app, specifically into a dedicated "Call Recordings" folder.

Under the iOS security architecture, every app runs in a tightly controlled sandbox. The Notes app container is isolated from third-party applications, preventing other apps from scanning, accessing, or reading the audio files without explicit system-level permissions granted by the user.

Hardware-Backed Data Protection and Encryption

At the filesystem level, iOS 18 safeguards call recordings using Apple's Data Protection technology, which pairs file-based encryption keys with the hardware-based Secure Enclave.

Each audio file is encrypted using an individual AES-256 key. This file key is wrapped by a class key derived from both the user’s passcode and the device’s hardware UID (Unique ID). By default, media saved to the Notes storage container utilizes the "Complete Protection" or "Protected Until First User Authentication" class. This ensures the raw audio cannot be decrypted or read off the storage chips when the device is locked or powered off, rendering physical flash-memory extraction attacks ineffective.

On-Device Transcription and Privacy

Alongside audio storage, the Phone app generates live and post-call transcriptions using Apple Intelligence. On supported hardware, the speech-to-text processing and summarization occur entirely on-device via the Neural Engine.

Because the transcription happens locally, the raw audio file never leaves local storage to be processed on remote servers. The resulting text transcript is stored alongside the audio file within the same encrypted Notes container, bound by the identical hardware-level encryption rules.

Secondary User-Level Access Controls

Because call recordings reside in the Notes app, users can apply secondary layers of defense to individual recordings. Notes containing call audio and transcripts can be locked using Face ID, Touch ID, or a custom password. This adds a dedicated, user-managed cryptographic layer on top of standard device-level file encryption, ensuring that even if an unlocked device is handed to a third party, the call recording remains unplayable and unreadable without biometric authentication.