chrome-use Remote is a remote control for chrome-use running on your own computer. It has no user accounts, no analytics, no advertising and no tracking SDKs. The developer operates no server that receives your conversations, pages or files.
You pair the app with your computer by scanning a QR code that your computer shows. Pairing keys are stored in the device keychain (iOS) or keystore (Android) and on your computer under ~/.chrome-use/mobile/. Everything exchanged after pairing — tasks you type, images you attach, agent replies, approval requests, screenshots and schedule information — is end-to-end encrypted (AES-256-GCM) between the app and your computer. It travels over the network path you choose (local network, Tailscale, or your own tunnel such as Cloudflare Tunnel); operators of that path cannot read it.
Your computer's agent (Codex, Claude Code, OpenCode or Pi) may send tasks and page content to the model service it is configured with; that service's own terms and privacy policy apply. See the chrome-use privacy policy for what happens on the computer.
If you allow notifications, the app sends its Apple Push Notification service or Firebase Cloud Messaging device token to the developer's push relay (chrome-use-push.leeguoo.com, a Cloudflare Worker). The relay returns a signed token that the app hands to your paired computers. When something needs you, your computer encrypts a short notice (conversation title, the reason, and at most a 120-character preview of the agent's reply) with a key only your phone has, and the relay forwards the encrypted blob to Apple or Google. The relay stores nothing: no device tokens, no notification contents and no logs of contents. Cloudflare, Apple and Google process the request as infrastructure providers.
The 14-day free trial and the one-time unlock are handled by the App Store or Google Play (or, for directly downloaded Android builds, an activation code). The developer receives no payment details. Purchase status is checked on the device.
| Data | Where it goes |
|---|---|
| Tasks, images, agent replies, screenshots | Only between the app and your paired computer, end-to-end encrypted. Cached on the device to show history; deleted when you remove the computer or uninstall the app. |
| Pairing keys | Device keychain/keystore and your computer. Never sent to the developer. Deleted when you remove the computer in the app; on iOS, keychain entries can remain after the app is uninstalled, so revoke the device on the computer to make them useless. |
| Push device token | Sent to the push relay to obtain a relay token and to deliver notifications; not stored by the relay. |
| Camera | Used only to scan the pairing QR code; images are not saved or sent. |
| Face ID / passcode | Handled by the operating system; the app only receives success or failure. |
Remove a computer in the app, or run chrome-use mobile revoke <id> on the computer, to end access immediately. Uninstalling the app deletes its cached history; pairing keys in the iOS keychain can remain until you remove the computer in the app or revoke the device on the computer. The app is not directed at children.
Questions: leeguoooo@gmail.com · Source: github.com/leeguooooo/chrome-use