Thursday September 3, 2026 1:13 pm
Perplexity’s New Mac Feature Tries to Keep Your Private Files Off the Cloud
Posted by Andru Edwards Categories: Software, Artificial Intelligence

You want AI to help with the messy, useful stuff: your tax return, a contract, the bloodwork PDF you can't make sense of. And every time, the same worry shows up. To get the help, do you have to hand all of it to somebody else's servers?
Perplexity says no, or at least not all of it. On September 1 it switched on a feature called Hybrid Compute in its Mac app. The idea: the cloud still does the heavy thinking, but the moment your task touches something private, that step runs on a small model on your own Mac instead. Your sensitive files are supposed to stay on the laptop.
How it's supposed to work
A normal AI agent sends everything to the cloud. Perplexity flips part of that. A frontier model in the cloud handles the parts that need horsepower: web search, planning, and working through a long task. When a step needs to read something private, the system hands that step down to a local model running on your Mac, finishes it there, and stitches the two halves back together without starting the task over.
Sitting in the middle is an on-device classifier that reads your content before anything leaves the machine. Perplexity says it can spot 37 kinds of personal information: names, addresses, account numbers, passwords, card numbers, government IDs. When it finds something, it does one of four things. It keeps that step local, masks the sensitive piece with a stand-in before sending the rest to the cloud, refuses the action outright, or stops and asks you first.
The masking is the clever bit. Say a document mentions a client's name and account number. The classifier can swap those for placeholders, send the harmless remainder to the cloud for the smart work, then drop the real values back in when the answer returns. In theory you get the cloud's brains without the cloud ever seeing the details.
What you actually need
This is Mac-only, and not every Mac qualifies. You need an Apple silicon machine running macOS 15 or later, with at least 24GB of unified memory. Perplexity recommends 32GB. If you're on an 8GB or 16GB laptop, you're out, because running a capable model on-device costs memory and there's no trick around that. The company points at the newer Mac mini and Mac Studio as the comfortable spot. It's switched on for Pro, Max, and Enterprise subscribers.
The use cases are the obvious ones. A finance team cross-referencing public filings against a confidential deal. A lawyer researching case law while keeping privileged notes on the machine. An ad shop poking at market trends without letting embargoed creative leave the building. All the moments where "just paste it into the chatbot" was never really an option.
The part that deserves a second look
Almost everything we know about what stays local comes from Perplexity's own description. The whole promise rests on that classifier catching the sensitive stuff every time, and a classifier that misses one account number sends it to the cloud along with everything else. Perplexity's own figures hint at the strain: it reports the detector's recall falling from about 0.97 on short passages to roughly 0.69 once a document runs past 10,000 characters. On a long, messy file, more slips through.
That doesn't make the feature a gimmick. A design that keeps most of your data home beats one that ships all of it off by default, and this is a real attempt at the harder version. But "hybrid" means part of your task still goes to the cloud. What matters is whether you can check what left your machine. Enterprise accounts get audit logs that trace where information flowed. Everyone else is mostly taking the company at its word.
Who it's for
If you already run everything through a chatbot and never think twice, this isn't aimed at you. It's for the person who's been holding back: the accountant, the paralegal, the founder with a folder of things they'd never paste into a web form. For them the pitch is real. Just go in knowing the guarantee is a classifier doing its best, not a wall. Check what it flags. Watch what it asks before it sends. And if a file is the kind of thing you genuinely cannot afford to leak, keep treating it that way until you can verify, not just hope, that it stayed put.