Encrypted voice recorder: the honest Mac guide
"Encrypted voice recorder" can mean three different things: an app with a passcode lock, a cloud recorder with encrypted storage, or local audio files protected by disk encryption. The strongest setup on a Mac is the third: a recorder that saves raw audio in a local folder - like Nerpa - plus FileVault and, for the most sensitive projects, an encrypted disk image. No app lock screen protects recordings as verifiably as full-disk encryption does. Steps below, with the trade-offs stated plainly.
What "encrypted" actually means
Marketing uses one word for three very different guarantees. Before picking an app, work out which one you actually need:
- Level 1: a locked app. The recorder asks for a PIN or Face ID before showing recordings. This stops someone picking up your phone and playing a memo. It usually protects nothing once the file is exported, and says nothing about where files are stored.
- Level 2: encrypted cloud storage. The app uploads recordings to its servers and encrypts them there and in transit. That protects the pipe and the vendor's disk - but a copy of every recording now exists on someone else's infrastructure, under their retention rules, subject to their breach history.
- Level 3: local files plus disk encryption. The recording is a plain file on your machine, and the disk itself is encrypted. There is no second copy to worry about, and the encryption is the operating system's - audited, documented, tied to your password.
Levels 1 and 2 are what most "encrypted recorder" apps sell. Level 3 is what security professionals actually run, because it removes the question "who else holds a copy?" instead of answering it.
The strongest setup on a Mac
Everything you need is already built into macOS - two steps, no third-party apps:
- Turn on FileVault. System Settings - Privacy & Security - FileVault - Turn On. From that moment the entire startup disk is encrypted with XTS-AES: every file on it, including all recordings, is unreadable without your password. If the Mac is lost or stolen, the recordings are effectively gone with it. There is no meaningful downside for a machine that sleeps in an office.
- Keep the most sensitive projects in an encrypted disk image. Open Disk Utility - File - New Image - Blank Image, choose 256-bit AES encryption and a strong password. Mount it, drop recordings inside, unmount when done. The image is a single file that is unreadable without the password - a vault for the client work, the interview, or the legal call you cannot afford to leak.
The prerequisite for both steps is that recordings are local files in the first place. A recorder that uploads everything to its own cloud has already made the decision for you - read what "keeping files local" really means to see why that choice matters more than any padlock icon.
Where Nerpa fits - honestly
Nerpa is not an "encrypted recorder" in the app-lock sense, and we won't pretend otherwise. What it gives you is the foundation that makes the steps above work:
- Raw audio stays local. Every recording lands as a standard audio file in a folder on your Mac - the same file you could copy to a USB stick or into an encrypted image. No vendor cloud holds a copy of your calls.
- No bot joins your calls. The meeting is captured from your Mac's own audio, so there's no third-party participant to admit and no recording stored on a conferencing vendor's side either.
- Transcription runs on your computer. Your audio is not uploaded for transcription; AI features and device sync use servers in the European Union under EU rules. That is a data-residency guarantee, not end-to-end encryption - we state the difference plainly rather than blur it.
- You add the encryption layer you need. FileVault protects everything by default; the disk image adds a vault per client. Because the files are ordinary, any macOS security tool works on them - nothing is trapped inside an app.
That combination - local files you can encrypt yourself, plus honest limits - is worth more than a proprietary lock screen. The same reasoning applies to the transcript side: who can actually see a meeting recording depends mostly on where it lives and who it was shared with, not on the app's icon.
Local recordings, your encryption, your rules
Nerpa records calls without a bot and keeps every raw audio file in a folder on your Mac - so FileVault and an encrypted disk image cover the rest. Speaker-aware transcripts, minutes, and per-person history included.
Latest stable release. Requires macOS 12+
Recorder options compared
| iPhone Voice Memos | "Encrypted" recorder apps | Nerpa (Mac) | |
|---|---|---|---|
| Where files live | On device; iCloud if sync is on | Usually the vendor's cloud | Folder on your Mac, no cloud copy |
| Encryption at rest | Device encryption (OS-level) | Vendor-managed, varies by app | Whatever you enable: FileVault + disk images |
| App lock / PIN | No (Screen Time workarounds) | Yes - usually the headline feature | No - macOS account protects access |
| Meeting capture | Microphone only, held to the phone | Phone mic; some add bot recording | System audio from the Mac, no bot joins |
| Transcript + minutes | Basic transcription on device | Sometimes, via the vendor's cloud | Yes - speaker labels, decisions, action items |
| Export control | Share sheet per memo | App-dependent, some lock exports | Plain files - copy anywhere, anytime |
Read the table by row, not by column: "encrypted" in an app's name tells you about the lock screen, not about where your files end up. For memos recorded on the go, the iPhone's own recorder is better than its reputation - just check whether iCloud sync is on before recording anything sensitive; where voice memos actually live explains the storage and sync mechanics.
For client calls specifically
Client work adds two requirements that consumer recorder apps ignore. First, the recording itself is often contractually or legally sensitive - a consultant's call about a client's finances is not the same risk class as a grocery list. Second, the transcript often outlives the audio in usefulness: months later you search decisions and numbers, not waveforms. A local-file recorder plus disk encryption covers the audio, and per-person filing keeps the transcripts organized instead of scattered - the client call log that builds itself shows the workflow.
One rule outweighs all of the above: consent. Encryption protects a recording you were allowed to make in the first place - the privacy rules for meeting recordings apply before the first byte is stored, not after.
Frequently asked questions
Does the iPhone voice recorder encrypt recordings?
Yes - Voice Memos are stored in an encrypted container on the device, like the rest of iOS app data. The caveat is sync: if the memos back up to iCloud, copies exist on Apple servers protected by Apple's standard security, which is strong but is not end-to-end encryption unless you enable Advanced Data Protection. Recording sensitive material, or syncing it, changes the answer.
What is the most secure way to record voice on a Mac?
Record to a local file, keep the whole disk encrypted with FileVault, and put the most sensitive recordings in an AES-256 encrypted disk image. That setup means the recording never leaves your machine, is unreadable if the Mac is lost, and stays under your password - no app vendor, no cloud copy.
Is Nerpa an encrypted voice recorder?
Honest answer: Nerpa does not add its own encryption vault. What it does is keep every raw recording as a plain audio file in a folder on your Mac - there is no vendor cloud holding your calls - so the encryption layer is whatever you choose: FileVault protects the disk, an encrypted disk image protects individual projects, and transcription runs on your computer. Local files plus your own disk encryption is a stronger, more verifiable setup than an app claiming a proprietary lock screen.
Do encrypted voice recorder apps still upload audio to the cloud?
Often yes - a padlock icon usually means the app locks its interface or encrypts files in transit and at rest on the vendor's servers, not that recordings never leave your device. Check two things before trusting one: where the raw files are stored (on-device only vs synced), and whether transcription or backup features send audio anywhere by default.