# The honest phone

What this service is, and the lines it doesn't cross. These are product decisions, not
defaults to tune: changing one is a decision to make in the open, here.

## What you get

- **One phone per person.** Each user gets their own Android instance and their own `/data`.
  Nothing of one user's phone is visible from another's.
- **State sealed per person.** A user's `/data` is stored encrypted under a key minted for
  that user (`stateKey`, SSE-C); another user's VM can't read it. On the phone itself, the host
  directory holding it has a random name, so an app can't learn whose phone it is from its
  mount table.
- **A phone that reads as a phone.** It reports a battery, the person's own time zone and
  language, USB debugging and developer options off.

## What we don't do

- **No Google apps bundled without a license.** Google Mobile Services may only be preinstalled
  by device makers who sign Google's distribution agreement. We ship microG, an open-source
  reimplementation, instead. Apps that demand Play Integrity's device or strong verdict
  (most banking and payment apps) will not work, and we say so rather than work around it.
- **No device-fingerprint spoofing.** The phone says what it is: our own neutral identity,
  "Phonebase" (`apps/mobile/image/identity.env`), user/release-keys, the real Android
  version and the real security patch level. It does not claim to be a Pixel or any other
  maker's device, and it does not fake attestation.
- **No ban evasion.** No residential-proxy rotation, no IP or device rotation to look like
  someone else, no getting around a site's rate limits, captchas, or purchase limits.
- **User-directed only.** The phone acts for the person it belongs to, on their own accounts,
  on what they asked. No account creation at scale, no fake accounts, no scraping other
  people's data, no ticket or purchase-limit macros.

## What that costs, and why we accept it

Some apps won't run: anything that requires hardware-backed integrity (banks, many payment
screens, some DRM). A service that spoofs its way past those checks takes on licensing risk,
breaks all at once when the leaked keys it relies on are revoked, and looks exactly like the
fraud infrastructure platforms fight. We'd rather be the phone people and companies can trust
with a logged-in account, and be clear about which apps that rules out.

## For agents

The MCP server (`apps/mcp`) states these rules to the model it serves: act only on what the
user asked, never create accounts or get around a site's limits, release the phone when done.