← Field Manual
BRIEF · 02401 InitiateDigitalPrivacy & OPSEC· 15 min read· updated 2026-05-31

Your Phone Is the Whole Game

The hardest laptop in the world means nothing if the phone in your pocket is a tracking beacon. The honest entry point to the entire Field Manual.

§ BRIEFING

TL;DR

Your phone is the single largest surveillance surface in your life and the first thing to handle, not the last. Five distinct leaks (baseband, SIM, OS telemetry, app SDKs, push) need different fixes. A tiered path works for most people: Tier 0 sane defaults in an afternoon, Tier 1 GrapheneOS on a Pixel for the committed, Tier 2 burner discipline for specific situations. Until the phone is handled, the rest of the manual is wallpaper.

What you'll be able to do

  • Name the five surfaces through which a smartphone leaks you, and which are fixable.
  • Execute the Tier 0 checklist on your current phone in one focused afternoon.
  • Decide honestly whether Tier 1 (de-Googled) fits your life and what you would give up.
  • Know when to reach for a separate device instead of hardening the daily driver.
  • Sequence the rest of the Field Manual correctly, starting from the phone outward.

Prerequisites

  • ·A smartphone.
  • ·Willingness to change defaults and uninstall a few apps you thought you needed.
  • ·An afternoon for Tier 0; a weekend for Tier 1 if you decide to go there.

Threat model

Passive, commercial-scale surveillance: ad-tech, data brokers, OS-vendor telemetry, app-SDK leakage, and the cellular network itself. Not a targeted state-level adversary, not custody, not border compulsion. Those need different tools, named honestly in the limits section.

You can run Qubes on your laptop, pay for everything in cash, register your car to a holding company, and route your traffic through a self-hosted VPN. If you carry a stock smartphone in your pocket while you do any of it, almost none of it matters. The phone watched you do it.

Your phone is the most intimate surveillance device most people will ever own. It sits on your body for sixteen hours a day. It knows where you sleep, who you sleep next to, which gym you skipped this week, which church or mosque or bar you walked into, and which doctor you saw last Tuesday. It does not know these things because anyone hacked it. It knows them because that is what the device is. The surveillance is the product, not a bug.

Most newcomers to this material start with a laptop and an encrypted messenger and feel safer. That order of operations is backwards. The phone is the whole game. If the phone is not handled, nothing else you do moves the needle in any real way.

By the end of this guide you will understand the five surfaces through which a phone leaks you, which of those you can realistically close and which you cannot, and a tiered path from "I just want sane defaults" to "I run a de-Googled phone on purpose" to "I use a separate device for specific situations." This is the front door to the rest of the manual. Walk through it first.

The hardest laptop in the world is wallpaper if the phone in your pocket is reporting to three trillion-dollar companies every six seconds.

§ 01

The five surfaces a phone leaks through.

Before any fix, a clear picture of what the device actually does. Each of these is a distinct leak with its own physics. Treating them as one blob ("my phone spies on me") is why most people give up.

SurfaceWhat it leaksWho sees itFixable?
Baseband + cell towerContinuous location to whichever towers your phone is talking to. Roughly: city block to neighborhood, sometimes building-level.Your mobile carrier, anyone the carrier sells data to, anyone with a lawful intercept order, anyone running an IMSI catcher near you.Only by powering the radio off or leaving the phone behind. You cannot fix this in software.
SIM / eSIM identityTies the device to a real-world identity (in most countries, your government ID). Persistent across reboots and SIM swaps if the IMEI is the same.Carrier, regulator, anyone who subpoenas the carrier, attackers who SIM-swap you.Partially. Prepaid SIMs in privacy-friendly jurisdictions, eSIM data-only plans, or a separate device with no SIM at all.
OS-level telemetryCrash reports, usage analytics, advertising IDs, 'helpful' location history, push tokens, device fingerprints. Default-on.Apple, Google, and every partner they share with under their privacy policies.Mostly yes. Settings get you 70%. GrapheneOS or a de-Googled Android gets you most of the rest.
App telemetry & SDKsEvery app you install ships embedded analytics, ad SDKs, and crash reporters. They phone home constantly, often with location and contacts.The app vendor, plus 5 to 50 third-party data brokers per app.Yes. Prune ruthlessly, block at DNS, sandbox the rest.
Push notificationsEven end-to-end encrypted apps usually route 'you got a message' pings through Apple Push (APNs) or Google FCM. Metadata travels with them.Apple or Google, plus the app vendor.Partially. Some apps support direct push or no push; on GrapheneOS you can run without Google services entirely.
Same phone, five different leaks. The fix depends on which one you care about.

§ 02

Three tiers. Pick the one that matches your life.

You do not have to live in a Faraday bag. You also do not have to keep the default phone the carrier sold you. There is a usable middle and a hard-mode top end, and most people belong in the middle.

TierWho it's forCostWhat you lose
Tier 0 — Sane defaultsAnyone with a phone and an afternoon. Required baseline before anything else.Free. Time.Almost nothing. A few apps you did not need.
Tier 1 — De-GoogledPeople who have done Tier 0, want a real step change, and accept friction.A used Pixel and a weekend.Some banking apps, some games, the seamless Apple/Google ecosystem, occasional 'this app needs Play Services' frustration.
Tier 2 — Burner disciplineSpecific situations: a trip, a meeting, an action, a relationship change. Not a daily-driver swap.Cost of a second device plus a prepaid SIM.Convenience. You have to think about which device you are carrying and why.
Most readers should do Tier 0 this weekend and consider Tier 1 over the next quarter.

§ 03

Tier 0: the afternoon that closes most of the doors.

This is the work everyone should do, regardless of how serious they are about the rest of the manual. It costs nothing, takes roughly one focused afternoon, and removes the easiest 70% of the leakage. Do it on the phone you have right now.

§ CHECKLIST, Tier 0 checklist (do this once, audit quarterly)

§ 04

Tier 1: a de-Googled phone, on purpose.

At some point Tier 0 stops being enough. The OS itself is the problem, not the apps. The mature answer in 2026 is GrapheneOS on a Google Pixel. It is the hardened Android distribution that the security community actually uses. It is not a fringe project, it is the boring correct answer, and the irony of running it on Google's own hardware is real and worth thinking about.

  1. STEP 01

    Buy a supported Pixel

    Check the GrapheneOS supported-devices list and buy a model that is current. New or recent used is fine. Pay with a method that does not link the device to your loyalty profile.

  2. STEP 02

    Install GrapheneOS

    Use the official web installer from a hardened laptop on a trusted network. The whole flash takes under ten minutes. Do not sideload random builds from forums.

  3. STEP 03

    Decide on Sandboxed Google Play, or not

    GrapheneOS lets you run Google Play in a sandbox without granting it system privileges. This is the pragmatic choice if you need a few apps that demand it (banking, airlines). Skip it entirely if you can live in the F-Droid / Aurora / direct-APK world.

  4. STEP 04

    Use profiles like rooms

    Set up multiple user profiles: one for daily life, one for financial apps, one for travel, one for whatever you want to be able to nuke without losing everything. Each profile is cryptographically isolated.

  5. STEP 05

    Reinstall the Tier 0 hygiene on top

    The OS is hardened, but app pruning, DNS blocking, and permissions discipline still apply. Tier 1 replaces the foundation; it does not replace the habits.

§ 05

Tier 2: when to reach for a separate device.

Some situations are not a hardening problem. They are a "do not bring that device" problem. A trip across a hostile border. A meeting whose attendance you do not want triangulated. A new relationship you are not ready to publish to your contacts graph. For these, the right tool is a separate device with its own discipline, not a heroic settings screen on your daily driver.

This is its own guide, deliberately. The short version: a cheap, fresh device, a prepaid SIM or no SIM at all, a provisioning ritual that never crosses paths with your daily identity, and a clear retirement plan. The long version lives in Devices That Don't Follow You Home.

§ 06

Verification: how to check that it stuck.

§ CHECKLIST, Did the work actually work?

§ 07

What this does NOT protect against.

✓ PROTECTS AGAINST

  • +The default firehose of telemetry from a stock smartphone.
  • +Ad-tech and data-broker profiling that depends on the advertising ID and app SDKs.
  • +Casual location aggregation by apps you forgot you installed.
  • +Lock-screen leaks of message previews and Siri/Assistant queries.
  • +Most of the metadata exposure that comes from using cloud-backed messaging by default.

✗ DOES NOT PROTECT AGAINST

  • A targeted, well-resourced adversary willing to spend on a zero-day. If you are that target, this guide is a starting line, not a finish.
  • Baseband and SIM-level surveillance. The carrier still knows where the radio is.
  • Your contacts, who probably have all of your data backed up to their cloud with default settings.
  • Lawful intercept at the carrier, the messenger provider, or the cloud backup.
  • Biometric or password compulsion at a border or in custody.
  • Anything you voluntarily post. The phone is not the leak here, the human is.
  • Apps you reinstall later because you forgot why you removed them. Discipline drifts.

This guide is the front door. It is the one you read first, not last. Once the phone is handled, the rest of the manual compounds, because every other discipline assumes that the device on your body is not undoing it in real time.

§ REFERENCES

  1. [01]GrapheneOS, the hardened Android distribution
  2. [02]EFF Surveillance Self-Defense, mobile guides
  3. [03]Apple, Advanced Data Protection for iCloud
  4. [04]Google, Activity controls and Timeline
  5. [05]NextDNS, encrypted DNS with telemetry blocking
  6. [06]Exodus Privacy, app tracker analysis

↳ last updated · 2026-05-31

Field notes for education. Private engagements: Greyshrine.

§ 00, BOOTING FIELD MANUAL
● LINK · NEGOTIATING
JTA //

JUSTIN · THE · ARCHITECT

> establishing secure channel…

HANDSHAKE004%READY
● STATUS: HANDSHAKE
LAT 00.000 · LON 00.000