Privacy Policy
Last updated: 2026-11-09
Remote Phone lets someone share an Android phone's screen with a helper they approve, so the helper can see and control it from another phone or a web browser. This policy explains what the Android app, the website, the web controller and our servers handle. Remote Phone is operated by Zalor Digital.
Third-Party Services
We use the following third-party services, which may collect or process data:
- Google AdMob: Shows ads in the Android app. Where the law requires it, you are asked for consent first.
- Firebase and Google Analytics: Usage analytics, anonymous sign-in, push notifications and the database used to find a device and deliver connection requests.
- Google Play: Android subscriptions and billing.
- Polar / Zalor Digital: Web subscriptions and payments go through Polar; your Zalor Digital account (zalordigital.com) holds which subscriptions you have.
Data We Handle and Security
We and these services handle the following data:
- Device or Other IDs: Advertising ID (AD_ID), an anonymous user ID, a push notification token and your device code.
- Device Information: Manufacturer, brand, model, Android version and app version. We use these to deliver connection requests and fix problems on specific devices.
- IP Address and Approximate Location: Your IP address is processed by our servers and partners. Approximate location is derived from it for localized content and ads. Our server logs may contain IP addresses, connection times and shortened session codes.
- App Activity and Diagnostics: Events such as screens opened, connections, errors and ads shown, used to keep the service working and improve it.
- Usage Limits: An anonymous ID and the time used each day, to apply the free limits.
- Purchases: Your subscription status. On the web, Premium comes from your Zalor Digital account: you sign in at zalordigital.com and our relay checks your account's RemotePhones subscription. There are no license keys.
- Saved Devices on the Web: The "My devices" list is stored in your browser.
Security: Connections use HTTPS/TLS encryption. Sessions are not end-to-end encrypted: they pass through our relay server, which forwards them without storing the video.
User Control: You can stop sharing at any time, turn off the Accessibility Service in Android settings, reset or opt out of personalized ads (Settings > Google > Ads) and clear browser data. To ask us to delete your data, email us using the address below.
Accessibility Service
Remote Phone uses the Android Accessibility Service only to perform touch actions (tap, long press and swipe) sent by a helper you approved. Once you turn the service on, it stays on until you turn it off in Android settings. Actions are carried out only during a session you approved.
The service is not used to read text or screen content, monitor your behavior or collect personal information. It only checks that the active window is available and where its edges are, so that touches land in the right place.
Screen Sharing
Screen sharing starts only after you accept a request and allow Android's screen sharing prompt. Your helper can see what is on your screen during the session, so close anything private first.
- The video passes through our relay server in real time to reach your helper.
- No screenshots are saved on your device or on our servers.
- We do not store video or images.
- Earlier versions offered an optional AI helper that sent screenshots to an AI service (Anthropic or Google) when it was used. That feature has been removed.
Voice Calls
During a session, a helper can ask to talk to you. Your microphone is used only if you accept that request and Android has microphone permission, and only until the call ends. You can end the call at any time.
- Voice passes through our voice relay server in real time to reach the other person, encrypted with a key created for that call.
- That key is delivered through our main relay server, so calls are not end-to-end encrypted.
- We do not record or store voice. Our logs keep only technical details such as call length and amount of data.
Sending Files
During a session, a helper using the Android app can send a file of up to 500 MB to the phone being shared. It is saved to that phone's Downloads folder, and the transfer can be cancelled while it is running.
- The file passes through our file relay server in real time, encrypted with a key created for that transfer.
- The file's name and size and that key are delivered through our main relay server, so transfers are not end-to-end encrypted.
- We do not store files. Our logs keep only technical details such as transfer length and amount of data, not file names or contents.