PhoneMCP Privacy Policy

The short version

Your files, photos, messages and sensor data stay on your phone unless your own AI assistant asks for them, and every tool is off until you switch it on. We run no ads, no trackers, and we never sell data.

What the app can access

• Every capability (files, camera, contacts, sensors, location, SMS) is disabled by default and enabled per tool by you, with a consent dialog for sensitive ones.
• Data read by a tool is delivered directly to the AI client you connected. The app has no AI of its own and sends nothing anywhere else.
• Photos/videos (READ_MEDIA permissions) are read only when your AI client calls the file-access tool, which you must first enable.

What the relay (phonemcp.ai) processes

• Device registration: a random device id, your phone's model name, a hashed device secret, and a one-way hash of a device identifier used solely to prevent free-trial abuse.
• Client authorization: OAuth client names/redirect URIs and one-way hashes of access/refresh tokens. Refresh tokens expire after 90 days of non-use.
• Relayed traffic: when Remote access is on, MCP requests and responses pass through the relay over TLS to reach your phone. They are forwarded in memory and not stored. The relay never sees your phone's local auth token.
• Usage counters: aggregate daily counts (connections, forwarded requests) with no request contents.
• Subscriptions: purchases are processed by Google Play. We receive and verify a purchase token; we never see card details.

Retention & backups

• Expired pairing codes, authorization codes and tokens become unusable immediately and are purged with routine maintenance.
• Encrypted database backups are kept for 14 days on infrastructure in Sweden.

Your choices

• Turn Remote access off at any time — the tunnel closes and the relay can no longer reach the phone.
• Revoke any paired AI client from the app.
• Local-network use never involves the relay at all.

Contact

Premex AB — premex.se, or open an issue at github.com/premex-ab/phone-mcp.