The FireAI Security Blog

By FireAI Security & Research Team · Published

What Privacy-Conscious Mac Users Are Turning On in 2026

What Privacy-Conscious Mac Users Are Turning On in 2026

None of the features below are new gimmicks. Most shipped years ago, buried in a settings menu most people never open. What has changed by 2026 is less the technology than the habit: more Mac users are actually turning these settings on, one at a time, as each becomes easier to find and understand. This is a tour of what each one actually does, sourced to Apple’s own documentation, and — just as importantly — what it does not do, because the gap between the two is where most privacy disappointment lives.

Advanced Data Protection: encrypting the iCloud data that used to be readable by Apple

Advanced Data Protection is an optional iCloud setting that extends end-to-end encryption to most of your iCloud data — Apple’s support documentation lists iCloud Backup, Photos and Notes among the categories covered — meaning that, once enabled, Apple itself cannot read that data even if compelled to. The tradeoff is real: turning it on disables browser access to your iCloud data at iCloud.com, since a trusted device is now required, and a few collaborative features such as iWork sharing and Shared Albums are not covered and continue to use standard protection. It is a strong setting for anyone worried about a stolen account or a legal order compelling Apple to hand over data — it does nothing, however, to protect data once it leaves iCloud and lands in an email, a screenshot, or another app.

Lockdown Mode: extreme protection for a narrow, specific group

Apple is unusually direct about who Lockdown Mode is for: "the very few individuals who, because of who they are or what they do, might be personally targeted by some of the most sophisticated digital threats." Enabling it blocks most message attachment types, disables complex web technologies that can slow down or break some sites, blocks incoming FaceTime calls from people you have not contacted recently, requires a device to be unlocked before it can connect over a cable, and prevents new configuration profiles from installing. This is not a setting for everyday privacy — it measurably degrades convenience — and it is aimed specifically at journalists, activists and others who might be targeted by mercenary spyware, not at general web tracking or data collection.

iCloud Private Relay: hiding your IP from websites, not full anonymity

Private Relay, bundled with an iCloud+ subscription, routes your Safari browsing through two separate relays so that, in Apple’s words, "no single party — not even Apple — can see both who you are and what sites you’re visiting." The first relay, run by Apple, sees your IP address but not the site you are visiting; the second, run by a separate operator, sees the site but assigns you a temporary IP instead of your real one. It stops your network provider from logging your full browsing history and stops websites from building a profile off your real IP address. It is not a general-purpose VPN: it only covers Safari traffic and some system requests, it requires a paid iCloud+ plan, it is unavailable in some countries, and some sites will ask for extra verification when they detect it.

Passkeys: removing the shared secret instead of just strengthening it

A passkey is a public-key credential: your device holds a private key that never leaves it, while the website or app stores only a public key that is useless to an attacker on its own. Because nothing secret is ever transmitted during sign-in — Face ID or Touch ID simply authorizes the local device to use the key — there is no password to phish, guess, or leak in a breach. The practical shift in 2026 is how many major sites now offer passkeys as the default, not an obscure option. What passkeys do not do: protect an account if someone gains physical access to an unlocked, authorized device, or fix the accounts you have not yet migrated away from a password.

Mail Privacy Protection: closing the tracking-pixel loophole

For years, marketing and phishing emails alike used invisible tracking pixels to learn your IP address and exactly when — and how many times — you opened a message. Apple’s Mail Privacy Protection defeats this by downloading remote content, including those pixels, in the background as soon as a message arrives rather than when you open it, and by hiding your IP address from the sender in the process. Senders can no longer tell whether, when, or how often you actually read a message. It only covers Apple Mail, though, and it does not stop a sender from including a malicious link — it protects your reading metadata, not the safety of everything in the message body.

Encrypted DNS: plugging the plaintext leak most people never notice

Every website visit starts with a DNS lookup, and on most networks that lookup travels in plain text — visible to your ISP, your office network, or anyone else on the same Wi-Fi, even when the page itself loads over HTTPS. Apple built native support for encrypted DNS into its platforms starting with the features it demonstrated at WWDC 2020, letting a Mac send those lookups over DNS-over-HTTPS or DNS-over-TLS instead, configured either through a configuration profile or Apple’s Network Extension APIs. Turning this on closes one specific leak — what domains you resolve — without touching the rest of your traffic, which is why it is usually paired with, not a replacement for, a VPN or Private Relay.

Per-app firewalls: watching where a Mac’s traffic actually goes

macOS ships a built-in Application Firewall that lets you allow or block incoming connections on a per-app basis, but by Apple’s own description it is aimed at unwanted inbound contact, grants automatic exceptions to system processes and signed apps opened by other apps, and does not distinguish between different destinations a single app might reach. That gap — knowing not just that an app can connect, but which specific hosts, domains and IP addresses it is actually talking to — is what has pushed more privacy-conscious users toward third-party, per-app firewalls that show outbound connections in plain language and let rules be set per host or domain rather than per app as a whole.

Local AI instead of cloud AI

The last shift is more architectural than a single toggle. As on-device AI features expanded, so did concern over what happens when a request is too complex for the device and gets sent to a server instead. Apple’s own answer, Private Cloud Compute, is built to extend on-device-style guarantees to that server-side step: user data is processed statelessly and is not retained even for debugging, and Apple has committed to publishing every production software image so outside researchers can verify what actually runs matches what was promised, rather than asking users to simply trust a policy document. The broader trend this points to — processing sensitive requests locally wherever possible, and treating any cloud step as something that has to earn trust through verifiable design rather than a promise — is showing up well beyond Apple’s own features, in everything from AI writing tools to security software.

The common thread, and where it stops

Every feature here does one specific job and stops there: Advanced Data Protection covers what Apple can read, not what you share; Private Relay covers Safari’s network path, not every app on the Mac; passkeys cover sign-in, not device theft; encrypted DNS covers lookups, not the payload of a connection. Stacking several of them closes more gaps than any single one — but stacking them also means understanding, honestly, what each one leaves uncovered, which is the only way to know what to add next.

How FireAI and HisnLabs fit in

FireAI fits one specific piece of this shift toward local processing: its on-device review of connections from unknown apps never sends your traffic anywhere to be analyzed, though it is worth saying plainly that a firewall is not a VPN, not encrypted DNS, and not a replacement for the built-in features described above — it complements them.

FireAI is HisnLabs’ own product: an on-device AI firewall for Mac. It shows every connection your apps make, in plain language, and lets you decide what leaves your Mac — its AI runs locally, so your traffic is never sent to us or anyone else. HisnLabs’ security research team is the group that keeps that decision-making accurate: cataloguing which domains are ordinary telemetry versus a real product, tracking the country and network behind a connection, and training the on-device model (its Autopilot feature) on real traffic patterns, all without any of it leaving your Mac.

You can read the technical decisions behind it, or try FireAI for 17 days, at FireAI, by HisnLabs.

Sources