Tuplay 隐私政策

ENGLISH VERSION

Tuplay Privacy Policy

Effective and last updated: September 13, 2026 · Applies to the Microsoft Store version of Tuplay

1. Summary

Tuplay mirrors iPhone and Android screens and device audio to your Windows computer without a developer-operated cloud relay. It requires no developer account and includes no advertising, developer telemetry, installation reporting or automatic log upload. It does not sell mirroring data or build advertising profiles. Mirroring still transfers data between devices, and the app stores local diagnostic information.

2. Connections and data transfers

On startup, Tuplay inspects network interfaces and monitors Android devices. When the receiver and network are available, it starts AirPlay discovery and advertises a receiver name and network service information to devices on the local network. Discovery does not wait for a mirroring-button click. Device information includes names, models, identifiers, Android serial numbers, authorization state, USB locations, transport identifiers, interface names, IP addresses, ports and connection status. It is used to identify devices, choose interfaces and diagnose connections.

AirPlay transfers iPhone video, device audio, connection and media information to the computer; an Apple USB network is still a network connection. Android mirroring uses bundled scrcpy and ADB over USB or wireless connections and also sends keyboard and mouse actions to the selected phone. Android clipboard changes are synchronized to the computer by default, and pasting in the mirroring window can send the computer's clipboard to Android. The pairing address, port and six-digit code you enter are passed to local ADB to pair with the selected phone, not to the developer's server.

3. Local storage and other services

Tuplay uses %LOCALAPPDATA%\Tuplay for close-window and launch preferences, plugin cache and timestamped logs under logs. Windows may redirect these paths for a Store package. Logs can contain receiver and network names, IP addresses, phone names, models and identifiers, Android serial numbers, pairing addresses, launch arguments, performance data and errors. Media metadata supplied by the phone may add titles, artists, albums or descriptions. These are not anonymous statistics and are not automatically uploaded.

Tuplay does not save the six-digit pairing code in its own settings or logs; it passes the code as an argument to local ADB. ADB separately maintains authorization keys and paired-device records, potentially outside Tuplay's data directory. Defaults do not record mirrored media to files, and the normal interface has no screenshot or recording-save feature. Custom UxPlay configuration can enable recording or dumps; you must manage those files separately. Existing clipboard content is not automatically cleared when mirroring ends.

Settings, logs and cache have no unified automatic expiry; exiting does not delete them. After fully exiting, you can remove these local files. Store uninstall or reset follows Windows package storage behavior and may not remove ADB authorization or separately saved copies. Bundled UxPlay, GStreamer, scrcpy, ADB, SDL and FFmpeg process mirroring locally; their use does not mean media is sent to their developers. Tuplay has no developer cloud relay or independent automatic-update reporting. Microsoft Store services are covered by Microsoft's Privacy Statement. External links open only when selected, without automatically attaching mirrored content or local logs.

4. Security and your choices

Use trusted networks and authorize only trusted computers. Default AirPlay reception has no PIN or password enabled, so a local network should not be treated as private to you alone. Connection protection depends on the protocol and system; this policy does not promise identical encryption or confirmation for every connection. Local files rely on Windows account and file permissions.

Stop iPhone mirroring on the phone, stop the receiver, close the mirror window or fully exit Tuplay. Minimizing the main window to the tray may keep mirroring active. For Android, disable USB or wireless debugging, forget the computer in paired devices, or revoke debugging authorization. Stopping Tuplay does not automatically stop the shared ADB service or revoke trust. To avoid clipboard exchange, end Android mirroring and clear previously copied content on each device. Avoid copying sensitive content during a session. You may also disable launch at login and remove local files after exiting. Removing ADB credentials can affect other ADB tools and is separate from revoking phone authorization.

5. Feedback, changes and contact

The developer is 信神荼 (Tu Tools). For privacy questions or requests to access, correct or delete information you voluntarily submitted, contact xinshentu@gmail.com or use the Tu Tools feedback page. Feedback is optional. We receive the product, category, message and optional contact details you submit, together with submission and processing timestamps, so we can handle and respond to your request. Website and email services also process connection information such as IP addresses and request times.

Feedback is not automatically published and has no fixed automatic deletion period; contact us to request deletion. Do not send passwords, verification codes or unrelated sensitive information. Review and redact logs before sharing them. We cannot remotely access or delete data stored only on your device. Changes to the app's data practices will be reflected here with an updated date. Microsoft Store, Windows and external services have their own privacy policies.