Privacy

Updated November 9, 2026

This page covers two things: what this website collects when you visit it, and what the Phone Use apps send over the network when you use them.

This website

phoneuse.tech is a set of static pages on a server we run. It sets no cookies, stores nothing in your browser, and has no ad trackers. The fonts and images come from the same server.

Visit counts. We count visits with Plausible, which we host ourselves. It records the page, the site you came from, your country, browser, operating system and type of device, and which download buttons were clicked. It uses no cookies and doesn't store your IP address, so we see totals, not people.

Server logs. The web server logs each request: your IP address, the time, the file asked for, the page you came from and your browser. We use the logs only to keep the site running, and they're deleted after two weeks.

Bridge mailing list. If you sign up to hear about a finished bridge, your email address goes to Kit, which keeps the list for us. Kit emails you a link to confirm, and you're added only once you click it. We use the list only to tell you about the bridge, and never sell or share it. Every email has an unsubscribe link. See Kit's privacy policy.

The Phone Use apps

The Phone Use apps have no accounts, analytics, advertising or tracking. The full app privacy policy is on GitHub; this is a summary that agrees with it.

On your network. Phone Use on your computer receives your iPhone's screen through Screen Mirroring and sends taps and keystrokes to it over Bluetooth, directly or through the bridge. The screen's picture stays on your computer, and reading the screen as text runs on your computer. The iPhone app talks only to the computer you paired it with, over your local network: it sends your settings, your Allow and Deny answers, its notification tokens and, if you move the bridge to another Wi-Fi network, that network's password, encrypted with the key from your pairing.

The push relay is the one thing that leaves your devices for a server we run. Notifications and the Live Activity reach your iPhone through Apple's push notification service, which needs an Apple key, so most computers send them through a small relay on Cloudflare Workers.

• The iPhone app registers with the relay an identifier derived from your pairing key, its push tokens, the current Live Activity's id, whether it's a production or development build, and the app's bundle id. No names and no account.
• The relay keeps one record per registration. It expires after 30 days without a refresh, and Unpair in the app deletes it.
• Your computer sends the kind of notification with its details sealed by a key from your pairing, which the relay can't read. The relay fills in fixed wording, such as "An agent asks to use your iPhone", and passes it to Apple; your iPhone opens the sealed details itself.
• The relay logs one line per notification: the first characters of the registration identifier, the kind, and Apple's answer. Cloudflare's standard request logs and rate limiting see IP addresses.

A computer set up with its own Apple key sends notifications straight to Apple instead, and doesn't use the relay.

Your agent. If you connect an AI agent, such as Claude Code, it can see your iPhone's screen and use it, within the controls you set. What the agent does with that information is governed by its provider's terms and privacy policy.

Questions

To ask about this policy, or to have your email removed from the mailing list, open an issue on GitHub or use the unsubscribe link in any email. If this policy changes, the new version appears here with a new date.