What iPC Does
iPC connects your Apple devices and Windows PC. It sends files and links and shares copied text through AirText. This policy covers the iPhone, native Mac and Windows apps, the Chrome extension and iPC's delivery-notification service.
Your Files, Links And Copied Text
You choose the devices and categories you want to sync. Local transfers travel between paired devices over an authenticated, encrypted connection. When a file or link uses the offline relay, an encrypted copy is stored in iPC's hidden app-data folder in your own Google Drive account. iPC does not use a developer-owned Firebase storage bucket to hold your photos, videos or documents. Drive storage limits and internet access still apply.
AirText shares newly copied text with your selected paired device when text sync is enabled. This may include passwords or other sensitive text you copy. Do not enable it for devices you do not trust. Desktop apps need to be running; on iPhone, return to iPC after copying or use Paste Text To PC. AirText currently uses the local network, not the Drive file relay. Its text log is temporary and held in memory rather than saved as a permanent text history. Text placed on the system clipboard is also subject to your operating system's clipboard and clipboard-history settings.
Google Sign-In And Device Pairing
iPC uses Google sign-in to connect the same account across your devices. The apps display your account email and keep authentication credentials and pairing secrets on your device using the platform's protected storage. The Drive permission is limited to iPC's app-data folder; it does not grant access to your ordinary, user-visible Drive files.
The delivery service stores limited operational metadata in Firebase/Google Cloud: a derived account identifier, paired device identifiers, push-notification tokens, pairing-confirmation state, timestamps and rate-limit counters. It uses that information to authenticate delivery signals and prevent abuse. Notification requests do not include your file contents, copied text or shared URL. Infrastructure providers may process normal request information, such as IP addresses and error/status data.
Photos, Files And Clipboard Permissions
On iPhone, Camera selects existing photos and videos. Photos permission lets received media be saved to Photos. Files access lets you select documents and save received documents to your chosen destination. Clipboard/paste permission supports manual paste and AirText. Background App Refresh and cellular access help eligible transfers, but iOS controls background execution.
On Mac and Windows, iPC reads files you choose, share, paste or drop into it, writes received files to your chosen folder, and reads/writes the clipboard for enabled text sharing. The Mac Share extension receives the items you explicitly share with iPC.
History, Previews And Diagnostics
The apps may retain local delivery receipts, filenames, link history, thumbnails, caches and operational logs. Clearing history removes the app's history; it does not delete a file already saved to Desktop, Photos or Files. Temporary transfer copies may be kept until delivery or saving can be confirmed, and retained if recovery is needed.
Link previews can contact the shared website or preview providers to obtain titles, icons or images. Those services may receive the requested URL and your IP address. Delivery-service logs are limited to operational information; local troubleshooting logs may include filenames or URLs. Do not send support logs without reviewing them for personal information.
The current iPhone source disables automatic Crashlytics collection. Any change to diagnostics in the public release must be disclosed here and reflected in the App Store privacy answers. No advertising or cross-app advertising tracking is part of iPC's current implementation. We do not sell user data.
Your Controls And Data Removal
Disable a sync category, change the selected device, unpair a device, sign out, or clear local history in the apps. You can also revoke Google access in your Google Account's permissions. Revoking access prevents future authorized access but does not automatically remove previously saved destination files or all existing Drive app-data copies.
Drive transfer records are removed according to delivery, cleanup and explicit deletion behavior. Local receipts, caches and logs remain until cleared or removed with app data. Delivery-service metadata has an expiry configuration for inactive records; the final deployed retention and deletion controls must be verified before launch. Contact support for questions about developer-held operational data.
Services And Google Limited Use
iPC uses Google Sign-In, Google Drive, Firebase Cloud Messaging and Google Cloud/Firebase delivery metadata services. Apple operates App Store purchases in the planned paid release. Shared websites and preview providers have their own privacy practices. Review Google's privacy policy and Firebase privacy information.
iPC's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including Limited Use requirements. Google user data is used to provide and maintain iPC, not for advertising.
Purchases In The Planned Release
The proposed free allowance and one-time unlock are not active in the current preview. When implemented, Apple will process payment. iPC's entitlement service will need verified purchase identifiers, an account-bound unlock and an idempotent count of successful file/link sends. Billing will not need file contents, shared URLs or AirText text. Update this section to the exact implemented system before publishing it.
Contact
For privacy and support questions, email ipcanswermenow@gmail.com. Updates to this policy will use a new last-updated date.
Owner checks before publication
Finish and approve the download, help, privacy and support URLs, then replace both desktop Temp Website placeholders.
Complete the website before final production signing, notarization and App Store submission.
Confirm the deployed metadata-expiry policies, diagnostic settings, log retention and purchase data match the final privacy text.
Do not advertise saved multiple-PC selection or Chrome-on-Mac sending until their release gates pass. A Chrome extension running on Mac still needs a compatible Mac bridge and an iPhone-recipient path.
The Windows HEIF codec license is a binary-distribution issue, not something a privacy-policy sentence can resolve. Keep that separate release gate open until a compliant dependency is verified.
