Private Kernel: activate (smartphone)
Owning your machine and your data is the first act of rebellion against the Machine-God. Part 2.
Digital Grimoire — Initiate Letters (Premium Series)
Weekly letters for those who refuse to live as data fodder. What follows is a Digital Grimoire: a field manual written as an initiation. It’s a sequence of articles reserved for Cyber Hermetica initiates (the premium circle).
Introduction
We live inside an Age of Control where the Machine God prices, profiles, nudges, and gradually turns every platform into a detection sensor. Privacy, in this environment, stops being bourgeois, the polite desire “to be left alone“, and becomes what it has always been: moral and practical discipline.
Over the next weeks, we will move step by step through the core architecture of Surveillance Capitalism and the Digital Panopticon, learning how to deal with it according to a Cypherpunk ethos:
The data-offering ritual of surveillance capitalism
How Governemnts and Criminals alike leverage your data against you
Anonymity as the alchemical negation of correlation
The technical arcana of cryptography (trust without trust)
Cryptopolitiks and Observation Systems
Private Kernels as foundation
Private Comms as substrate
Private Money as agency
Agentic AI as force multiplier
…and much more!
Each issue is designed to be stand alone, but together they form a single narrative arc: from diagnosis to practice.
A battlefield in your pocket
In the previous issue we’ve seen how Operative Systems such as Windows can quickly and easily become Observation Systems: silent witnesses and recorders to all that happens on our laptops.
Smartphones are no exception. In fact, they are perhaps the easiest way to enforce the Digital Panopticon model. As Edward Snowden often says: they are extremely easy to hack and compromise.
But you don’t really need to be hacked to be surveilled through your smartphone. One could say that Stock smartphones – those sold with a pre-installed Android operating system – are built around permanent surveillance components.
The most practical example is Google Play Services: a system service that cannot be meaningfully disabled or removed and operates with near-root privileges.
It has continuous access to system data, metadata, sensors, network activity, location signals, and application behavior. Its reach extends across files, memory, Wi-Fi, Bluetooth, and device identifiers, while updates routinely expand its capabilities without user consent. An example is Google’s silent rollout of Android System SafetyCore, which enabled on-device content scanning under the banner of safety without user consent. I’ve written about SafetyCore here.
This pattern repeats across platforms; it’s not just Google Android. Apple follows a similar trajectory, for example when they attempted to deploy the NeuralHash system in 2021: an AI protocol designed to scan and analyze user media directly on the device, effectively bypassing the protective promises of end-to-end encryption.
device.init
telemetry = enabled
user_consent = assumed
privacy_mode = marketing_label
boot.sequence → observation_layer.activeWhat is marketed as “functionality” or “security” increasingly functions as embedded observation, which aligns seamlessly for remote monitoring and forensic access.
