Privacy Policy
Welcome to Phone2PC ("we", "our", or "the App"), developed by Li Jane. We value your trust and are strictly committed to safeguarding your personal privacy. This Privacy Policy outlines how Phone2PC handles data during peer-to-peer transmissions and cloud-assisted transit operations.
1. Primary Architecture: Local Peer-to-Peer (P2P) Direct Transfer
Phone2PC is fundamentally built around a direct local area network (LAN) architecture. When your phone and PC are connected to the same Wi-Fi network, files and text clips are transferred directly between your devices over local HTTP protocols. In this mode, no data ever leaves your local network, and no cloud accounts or internet connections are used.
2. Google Drive: Asynchronous Transit Relay (Not a Backup Service)
When devices are on different networks (e.g., cellular data vs. home Wi-Fi) or cannot establish a real-time peer-to-peer connection, Phone2PC provides an optional asynchronous cloud relay mechanism utilizing the Google Drive API.
Important Clarification on Google Drive Usage:
Google Drive in Phone2PC is used strictly as an intermediate transit medium (asynchronous mailbox relay) to bridge non-instantaneous file and text exchanges between your paired devices. It is NOT intended, designed, or used as a permanent cloud backup, long-term archiving, or secondary file storage service.
🛡 Google API Services User Data Policy Compliance
Phone2PC's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- Strictly Limited Scope (
drive.file): Phone2PC only requests access to files that were directly created by Phone2PC itself within its dedicated transit synchronization folder (Phone2PC_Sync). The App has absolutely no access to scan, view, modify, or delete any unrelated personal files, photos, or documents residing in your Google Drive. - Transit-Only Lifecycle: Files and text payloads uploaded to the designated device inbox (e.g.,
Phone2PC_Sync/to_{deviceId}/) serve solely as transient packages waiting for the target device to pull and complete download. Once delivered, the intermediate files fulfill their lifecycle. - No Proprietary Central Servers: All cloud communications take place exclusively and directly between your personal device and Google's official Drive API endpoints over secure HTTPS. We do not host intermediary servers that inspect, copy, or store your transmitted content.
- No Commercial Monetization & No AI Training: None of your Google user data or transferred files are ever sold, shared with third-party advertisers, or used to train or tune machine learning (ML) or artificial intelligence (AI) models.
3. Device Permissions Used & Purpose
- Storage / Media Access: Required strictly to allow you to select files/photos to send to your PC, and to save incoming files received from your PC into your chosen download directory (e.g.,
Downloads/Phone2PC). - Network & Wi-Fi: Required to establish local peer-to-peer sockets with your PC on the local network, and to communicate securely with Google Drive API endpoints when using the relay feature.
- Notifications (Optional): Used solely to provide foreground status of active background transfers, incoming file alerts, and local IP change reminders.
4. Data Retention, Management & Revocation
- Local Files: All files downloaded onto your device are stored in your local storage and can be deleted, moved, or managed at your sole discretion.
- Relay Folder Management: You can inspect or clear the transit folder (
Phone2PC_Sync) directly in your Google Drive web interface at any time. - Account Disconnection: You can sign out inside the App or revoke Phone2PC's access to your Google Account at any moment via your Google Account Security Dashboard.
5. Contact Us
If you have any questions or feedback regarding this Privacy Policy or your data security, please feel free to contact: