Apple Intelligence Data Persists After Opt-Out on macOS

I said no to Apple Intelligence, and my Mac quietly ignored me anyway.

Here's what happened: I went into System Settings, found the Apple Intelligence toggle in macOS 15, and switched it off. Or so I thought. Turns out that wasn't enough. Buried deeper in the settings—because apparently saying "no" needs to be hard—are additional options for things like Writing Tools and Image Playground. I missed those. My 512GB MacBook Pro now has 22GB of AI model data sitting on disk that I never explicitly consented to downloading.

This isn't just about storage space, though I'm annoyed about that too. It's about what passes for consent in the AI industry these days. Apple didn't just make the opt-out confusing; they've since removed the main toggle entirely in recent betas. The "AI" industry has plenty of flaws, but the casual erasure of user choice around data collection and local processing? That's becoming a feature, not a bug.

What does it actually mean when a company decides you can't say no anymore, even to features that run entirely on your own device?

The Unexpected Download

The data showed up anyway. A 22.28 GB chunk labeled "Apple Intelligence" materialized on the system despite opting out. The user didn't download it; macOS did, silently, in the background. The storage breakdown in Settings showed it clearly: Apple Intelligence taking up nearly 23 GB, sitting in /System/Volumes/Data/private/var/db/os or wherever the system chose to stash it.

This isn't a bug—it's a design choice. Apple frames Apple Intelligence as an optional feature, but the on-device models and supporting data still get fetched without explicit user approval. The quote says it bluntly: "I said no and Apple said yes." That mismatch between user intent and system behavior is the core issue here.

The storage hit is real. Twenty-two gigabytes doesn't appear out of nowhere. The models power features like writing tools, image generation, and Siri upgrades. Even if you never open those features, the system downloads and caches the assets proactively. Some of this is baked into the OS update itself—macOS 27 ships with more AI scaffolding than previous versions.

Consent in the AI industry has never been straightforward. Training data collection, model deployment, and feature defaults often assume opt-in by absence. Apple's approach mirrors what we've seen from cloud AI providers: data moves first, questions follow. The difference is that on-device processing was supposed to be different. Users expect more control when the processing happens locally, not in a remote data center.

This matters because storage isn't infinite, and neither is user patience. A 22.28 GB download that can't be selectively removed forces users to choose between a functional OS update and reclaiming disk space. The uninstall option isn't there. Disabling Apple Intelligence in Settings doesn't free the space. It just sits there, a digital brick wall between the user and their own machine.

Taking Back Control

Apple Intelligence doesn't ask for permission to occupy your disk. It just takes the space—22.28 GB of it—and leaves you with a spreadsheet of system files you didn't approve. I traced it through About This Mac > Storage > Manage, where the number sat there like a billboard: "Apple Intelligence" at 22.28 GB. No opt-in prompt. No warning. Just a silent download that happened while I was editing text and drinking coffee.

The cleanup starts with the obvious: delete the model files. They live in /Library/Application Support/Apple Intelligence/, and removing that directory frees up the space. But macOS 27 has a habit of re-downloading them through mlmodelc caches and system extensions that respawn like weeds. You can prevent this by disabling Siri Intelligence in System Settings and killing the background process:

sudo rm -rf "/Library/Application Support/Apple Intelligence/"

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.aiassetcache.plist

To verify the space is actually gone, use du to check the directory size before and after:

sudo du -sh "/Library/Application Support/Apple Intelligence/"

You should see 0B or "No such file or directory." If the directory reappears, something in your system preferences is still set to auto-download. Go to System Settings > Siri & Search and turn off "Listen for 'Hey Siri'" and "Press Side Button for Siri." Apple frames this as convenience. I call it data hoarding with a UI.

What Apple Intelligence Actually Stores

Apple's approach here reveals something I find genuinely unsettling: the company is betting that users will accept having their on-device data repurposed for model training without meaningful opt-out mechanics. The on-device processing is pitched as a privacy win, but the default data collection for personalization means Apple is still very much in the business of learning from your behavior, not just processing it.

What's different from previous privacy stances is how this normalizes extraction through convenience. You get personalized responses because your emails, messages, and photos are being used to tune the model — and the friction to stop that is buried in settings most people never touch. This isn't unique to Apple; it's the same playbook Google and Meta have used for years, just with better branding.

The technical implementation actually makes this worse. On-device processing sounds private until you realize the models still need to be trained somehow, so Apple will likely push anonymized data upstream when it can. And developers building on top of these APIs won't know what data is being used to personalize responses versus what's treated as generic input. That ambiguity alone could cause serious privacy bugs in third-party apps.

I'm left wondering whether Apple's marketing around privacy will hold up when users realize their "private" AI assistant is quietly learning from their most personal conversations. The company has built its reputation on privacy as a premium feature, but this feels like the beginning of the end for that positioning.

The Bigger Privacy Question

Apple's approach here feels consistent with a broader pattern I've watched develop across the tech industry: the slow erosion of explicit user consent in favor of more subtle, friction-minimized data collection. I don't think this is accidental. When you bury refusal behind multi-step processes or reframe it as "not recommended," you're not really offering a choice — you're engineering one outcome while paying lip service to user agency.

This matters more than the specific feature because it speaks to how companies are adapting to growing privacy awareness. Rather than redesigning their value exchange around user control, they're optimizing the interface to preserve data flows. I've seen this in everything from cookie consent banners that make acceptance a single click while rejection requires navigating menus, to app permissions that default to maximum access. The friction isn't an accident — it's the design working as intended.

I'm genuinely uncertain whether this strategy is sustainable long-term. Users are getting better at recognizing these patterns, even if they can't always articulate what's happening. At some point, the gap between stated consent and actual user intent might become untenable. But for now, Apple's walking a line that lets them claim user approval while maintaining data collection rates that satisfy their business model. Whether that's a temporary workaround or the new normal is the question that keeps me up.

Conclusion

Apple's approach here feels deliberately obtuse rather than accidental. Hiding the real opt-out behind Screen Time restrictions—software meant for parental controls—turns a privacy setting into an Easter egg hunt. That 22.28GB isn't just wasted storage; it's the physical manifestation of a company deciding what data it wants to keep, regardless of what you click.

At £500 per terabyte on new MacBooks, that chunk of disk space costs roughly £11. But the storage cost is the least of it. The real issue is that "consent" in the AI industry seems to exist more as a buzzword than a practice. When saying "no" requires technical sleuthing through hidden menus, the question isn't whether Apple will change this—it's whether users should expect anything different from a company that's already moved the goalposts once.

I'm still not sure what to make of an industry that treats data collection as a fait accompli, then patches its mistakes only when called out publicly. The 22GB will eventually get cleaned up, but the precedent feels stickier than that.