隐私政策
Privacy Policy
本政策说明 Remote Phone 当前 TestFlight 测试版本如何处理信息。Remote Phone 是连接并操控你有权访问的远端 iPhone、Android 或 HarmonyOS 设备的控制端应用。它不要求你注册 Remote Phone 账号。
1. 远端连接与功能所需的信息
- 设备连接：应用使用你输入的连接地址、远端设备标识、型号、系统版本和屏幕尺寸等信息建立连接、识别目标并显示设备状态。
- 画面与操控：远端画面、截图和视频编码信息传到控制端用于解码显示；你发起的触控、按键和设备操作命令传到所选设备或接入服务。当前版本没有默认开启的视频录制或向开发者集中上传远端画面的功能。
- 装包工具：你提供的软件包、二维码或清单链接用于识别和安装软件。清单可能由控制端读取；安装链接会交给所选设备或设备平台执行下载和安装。相关提供方会收到执行这些请求所需的链接及网络信息。
- 开发环境准备：只有在你确认执行相关操作后，应用才会为远端 iPhone 请求开发环境准备。该流程可向 Apple 签名服务发送设备 ECID、硬件标识、随机值和固件参数，并访问必要的资源提供方。
2. 本地保存与诊断
应用在本机保存最近使用的连接地址、所选设备、画质设置、软件包链接设置、会话所有权记录及开发环境准备记录。需要 Android ADB 授权时，应用可生成并在本地应用数据目录保存 ADB 身份私钥。iPhone 配对身份在会话内存中使用，不作为应用偏好设置持久保存。
连接、安装和错误诊断信息可能包含设备标识、地址、软件包链接及运行状态，并出现在应用诊断界面或系统调试日志中。只有你主动复制、导出或发送反馈时，相关诊断材料才会经该操作分享给接收方；当前版本不集成开发者的自动广告、行为分析或崩溃上报服务。
3. 相机、相册、本地网络与剪贴板
相机用于你打开的二维码扫描功能；你选取的相册图片用于本地识别二维码。应用不为这些功能上传整份相册或相机画面到开发者服务器。本地网络访问用于连接设备或接入服务；剪贴板内容在你使用粘贴功能时读取。你可在系统设置中撤销相关权限，也可以手动输入连接地址或软件包链接。
4. 接入服务与第三方
核心远控通信在控制端与你选择的设备、云设备平台、ADB 入口或 HDC 服务之间进行。相应服务运营方可能处理所需的设备信息、画面、命令和网络元数据；其保存和删除规则由该服务运营方负责。请使用你有权访问且信任的设备和服务。资源下载、Apple 签名及软件包提供方按你发起的功能请求处理相关信息。
Apple 的 TestFlight 分发和反馈功能可能按 Apple 的规则处理测试信息。本隐私政策网页托管于 Cloudflare；提供网页和安全防护时，Cloudflare 可能处理 IP 地址及请求信息，详见 Cloudflare 隐私政策。此页面没有配置广告、统计脚本、表单或应用数据上传入口。
5. 保存期限、清除与选择
会话内存数据用于当前连接；本地偏好与 ADB 身份在本机保留以供后续使用。你可以通过系统提供的删除应用数据方式清除本地保存项：iOS 删除应用及其数据，Android 清除应用存储；桌面系统还需清理对应的用户级应用数据。系统备份、系统日志及远端平台留存的数据遵循各自的保存规则，清除应用数据不会自动删除这些副本。
你可以断开连接、停止使用相关功能或撤销系统权限。如需删除由远端平台保存的信息，应联系该平台运营方。发送反馈或诊断前，请检查并移除不希望分享的设备地址、链接、画面或其他个人信息。
6. 联系与政策更新
测试用户可通过 TestFlight 中 Remote Phone 的“发送 Beta 版反馈”联系开发者，提出隐私问题、更正或删除请求。请说明请求涉及的信息与场景，不必发送签名私钥、密码或无关的远端画面。本政策随实际功能或数据处理方式变更而更新，最新生效日期会显示在本页顶部。
Privacy Policy
This policy describes the current TestFlight beta of Remote Phone, a controller for remote iPhone, Android and HarmonyOS devices you are authorized to access. No Remote Phone account registration is required.
1. Information used to provide remote control
The app uses connection addresses you enter and remote device identifiers, model, OS version and screen dimensions to establish a connection and identify the target. Remote screenshots, video and encoding information are received for display. Touch, key and device-operation commands you initiate are sent to the selected device or access service. The current app has no video recording enabled by default or centralized upload of remote pictures to the developer.
Package and QR-code links are used to resolve and install software. A manifest may be fetched by the controller; installation links are sent to the chosen device or device platform for download and installation. Those providers receive the links and network information necessary for the requests. If you confirm developer-environment preparation for a remote iPhone, Apple’s signing service may receive its ECID, hardware identifiers, nonce and firmware parameters, and the app accesses the required resource providers.
2. Local storage and diagnostics
Recent endpoints, selected devices, quality preferences, package-link preferences, session ownership and preparation records are saved on your device. When Android ADB authorization is needed, an ADB identity private key may be generated and stored in the app’s local data directory. iPhone pairing identities are used in session memory rather than persisted as app preferences.
Connection, installation and error diagnostics may contain device identifiers, endpoints, package links and operational details in the app or system debug logs. You share diagnostic material with a recipient when you actively copy, export or send feedback. The current app has no integrated developer advertising, behavioral analytics or automatic crash-reporting service.
3. Permissions and clipboard
The camera scans QR codes when you open the scanner. A photo you select is used for local QR recognition, without uploading the entire photo library or camera feed to the developer. Local-network access connects to devices or access services. Clipboard contents are read when you use a paste action. You can revoke permissions in system settings and enter endpoints or package links manually.
4. Services and other providers
Remote-control communication takes place between your controller and your selected device, cloud-device platform, ADB endpoint or HDC service. Their operators may process the required device details, pictures, commands and network metadata and are responsible for their own retention and deletion practices. Use services you trust and are authorized to access. Download providers, Apple signing services and package providers process information for the feature requests you initiate.
Apple may process beta distribution and feedback information under its own rules. Cloudflare hosts this policy page and may process IP addresses and request information to deliver and protect it; see the Cloudflare Privacy Policy. This page has no configured advertising, analytics scripts, forms or app-data upload endpoint.
5. Retention, deletion and choices
Session-memory data serves the current connection. Local preferences and ADB identities remain on the controller for later use. Clear locally saved data through the operating system: delete the app and its data on iOS or clear app storage on Android; desktop systems also require removal of the corresponding user-level app data. System backups, system logs and remote-platform records follow their respective retention practices and are not automatically removed by clearing the app’s data.
You may disconnect, stop using a feature or revoke system permissions. Contact the remote-service operator about data it retains. Before sharing feedback or diagnostics, review and remove endpoints, links, pictures or other personal information you do not want to disclose.
6. Contact and updates
Beta users can contact the developer through “Send Beta Feedback” for Remote Phone in TestFlight for privacy questions, corrections or deletion requests. Describe the relevant information and context without sending signing private keys, passwords or unrelated remote pictures. This policy will be updated when functionality or data handling changes; the latest effective date appears at the top.