On February 5, 2025, a macOS user discovered Apple Intelligence was phoning home every 15 minutes and explicitly disabled it using the provided settings. macOS 15 offered two layers of opt-out — a main toggle and a deeper privacy setting. Both existed. Both were used. The user said no. After upgrading from macOS 15 to macOS 27 — skipping one major version cycle — the opt-out toggle for Apple Intelligence no longer exists. The feature re-enabled itself despite the prior explicit refusal. Siri processes continue running in the background and cannot be killed. The "Apple Intelligence" label has been quietly removed from the Siri control panel, obscuring what the setting actually governs. The only partial mitigation discovered involves Screen Time restrictions — a parental-control feature repurposed as the last remaining tool to hide AI interface elements from menus. These restrictions do not disable Apple Intelligence; they merely conceal its surface-level integration points. The underlying model and processes remain active. The AI model occupies 22.28 GB of local storage. At Apple's current MacBook SSD pricing of roughly £500 per terabyte, that represents approximately £11 in storage value consumed without consent. The storage cost is trivial compared to the principle: a user's explicit refusal was overridden during a routine OS upgrade. This pattern is not unique to Apple. The author catalogs a broader industry trajectory: X (formerly Twitter) hosting child sexual abuse material despite pledges, OpenAI facing over 50 consumer harm and wrongful death lawsuits, and OpenAI and Microsoft acknowledging that LLMs are built on unlicensed web content. The common thread is that consent is treated as a speed bump rather than a boundary. The technical architecture of the problem matters. Unkillable background processes writing data for undisclosed purposes, multi-gigabyte models deployed without opt-in, and settings that disappear between versions are not bugs. They are design choices that convert user hardware into company infrastructure. The user owns the MacBook; Apple increasingly controls what runs on it. The consent erosion follows a recognizable playbook: launch with an opt-out, wait for adoption metrics, remove the opt-out, reframe objections as fringe. The user who said no in February 2025 is now running the feature they refused. Apple's response to "no" was to wait and then delete the question.
