A privacy‑first Mac setup for everyday work

“Privacy‑first” usually renders as a VPN ad. The version that actually changes your day is smaller and more local: which of your everyday actions — dictating, screenshotting, recording, syncing — touch a server, and which don’t have to. macOS gives you the switches; this is the setup walkthrough, in the order I’d flip them on a new Mac.

Disk first: FileVault

FileVault encrypts the whole disk with your password; a lost or stolen Mac becomes a lost bag, not a data breach. It’s a System Settings toggle, it’s on by default on recent macOS, and it costs nothing you’ll notice on Apple Silicon. This is the one setting that protects you from hardware, not behavior — start here because everything else assumes the machine itself is safe.

The iCloud question, asked deliberately

iCloud is the boundary where your data leaves the Mac, so decide it on purpose rather than by default. Advanced Data Protection (in your Apple account settings) extends end‑to‑end encryption to most iCloud categories — photos, backups, notes — meaning Apple holds keys it can’t read. What stays out of the cloud is a personal list; the point of the exercise is choosing, not drifting. Files that sync through iCloud Drive are the same trade with a narrower key: convenient, visible to the infrastructure, and fine for material you’d hand to the vendor anyway.

Dictation that never leaves

Apple’s built‑in dictation has an on‑device mode for supported languages — worth a try, because dictation is the highest‑frequency voice‑to‑cloud leak on a typical workday. For longer‑form dictation the third‑party on‑device apps have gotten genuinely good: the offline dictation field includes Handy (free and open source, 43 MB), VoiceInk, MacWhisper, and Snapbak — all of which run speech models on the machine, so the voice never becomes a network request. Snapbak (which I make — weight that) runs Parakeet on the Neural Engine with published accuracy and latency numbers, and a custom dictionary so your actual vocabulary comes out right.

Capture with redaction built in

Screenshots are the other high‑frequency leak: an email in a nav bar, a token in a URL bar, a customer’s name in a sidebar. The habit‑based fix is a review glance before every share; the tool‑based fix is Smart Redact — Snapbak scans the shot on the device and pre‑blurs emails, card numbers, common key formats, and faces before anything leaves. On‑device detection matters here for the same reason as dictation: the sensitive image never uploads to be scanned by someone else’s server.

Recordings, notes, and the local line

Screen recordings of real work contain everything: customer data, internal dashboards, code. Keeping them local by default — sharing as explicit exports rather than automatic uploads — keeps that material where it started. The same line applies to meeting tools: the bot‑based notetakers put a participant in your call that is somebody’s server; the bot‑free approaches keep the audio on your machine, and Snapbak’s meeting minutes are being built the same way — local transcript first, planned for a later release. Where cloud features exist at all (Snapbak’s Cloud AI, coming soon), the design rule worth demanding is transcript‑only: text goes up; frames and voice never do.

The audit habit

Once a quarter, open System Settings → Privacy & Security and read the microphone, camera, and screen‑recording permission lists. Every entry is an app that can see or hear your work; revoking the ones you don’t recognize takes a minute and closes the gap that no settings walkthrough can. Privacy on a Mac isn’t one purchase — it’s these switches, checked sometimes, and a bias toward tools whose answer to “where does this go?” is “nowhere.”