PhoneStage: Screen Mirroring

Effective date 2026-09-06 View app

1. Scope

This policy describes PhoneStage: 3D, its iPhone app and screen-broadcast extension, and the companion PhoneStage browser Viewer on tools.ipocket.xyz. It also explains the separate handling of visits to this product page and policy on ipocket.xyz. iPocket operates PhoneStage; you can contact us at contact@ipocket.xyz.

PhoneStage does not require a product account and has no in-app purchases or subscriptions. Its native iPhone app does not include advertising or third-party usage-analytics SDKs. Local processing and direct sharing with your chosen browser are distinct from information received by website or support services.

Screen sharing begins when you select PhoneStage and start a broadcast in the iOS system panel. ReplayKit supplies screen frames, and PhoneStage sends video to the connected Viewer. The screen may include content from other apps, notifications, or personal information that is visible while you share. Choose what you display and only approve browsers you trust. iOS may exclude protected content.

Device motion and screen-orientation data are used to align the 3D phone. Motion is not used for fitness tracking or location tracking. If background motion is unavailable, the Viewer can use screen orientation instead. This version processes video frames only; it does not transmit app audio or microphone audio.

Signaling, video, and motion travel over the local network between your devices. The screen-sharing connection does not use an iPocket cloud video relay or STUN/TURN service. WebRTC encrypts media in transit. This does not prevent someone with access to the receiving computer from viewing or recording the screen.

The iPhone app does not automatically save screen video to Photos or upload it for later access. Temporary frame buffers are used for the live connection. If you choose Record in the Viewer, the browser creates a recording locally and downloads it to your computer. You control those files; copies you later share, back up, or sync follow the destination’s policies.

3. Pairing, credentials, and local records

Pairing uses a short-lived code and requires approval on the iPhone. You can remember a trusted browser or allow only the current connection. Connection data can include device and browser identifiers, names, the webpage origin, local network address and port, protocol information, and connection timestamps.

Remembered authorization metadata is stored in shared app storage on the iPhone. Secret credentials are held in a device-only Keychain group shared by the app and its broadcast extension, without Keychain iCloud synchronization. The browser stores paired-device metadata and cryptographic credentials in IndexedDB. Remembered pairings do not retain the pairing PIN as a reusable login password.

The app and extension also share local session records and technical status such as connection errors, video dimensions, frame counts, and timing. These records are not screen recordings. Local session records may remain after a connection ends until replaced or cleaned by the app. System diagnostic logs follow operating-system retention and sharing controls; PhoneStage does not automatically send these logs to an iPocket diagnostics server.

The Viewer stores preferences such as rendering quality and control-panel visibility locally. Clearing browser website data removes its saved settings and pairing information. Uninstalling an app does not guarantee deletion of every Keychain item or a backup; orphaned credentials cannot restore authorization without matching app records.

4. Permissions

Screen broadcast: Starts and stops through iOS controls. Disconnecting the Viewer does not stop the system broadcast; stop it on the iPhone, including before reconnecting after a lost connection.
Local network: Required on the iPhone and, when requested, in the browser to establish the direct connection.
Motion: Used for device-orientation following when available. You can manage system permission where iOS exposes it; screen-orientation fallback remains available.
Camera: The iPhone app declares camera usage because its bundled WebRTC library contains camera APIs, but this version does not request camera capture for screen sharing. If you choose QR scanning in the Viewer, the Mac browser requests camera access, decodes the QR locally, and stops the camera after scanning or cancellation. Manual entry does not require camera access.

5. Websites and third-party services

Opening the Viewer, this landing page, or this policy sends normal web requests to hosting and content-delivery services. Those services can process IP addresses, requested URLs, browser information, and security or operational request data. Loading a webpage is separate from the direct local screen-sharing connection.

The companion Viewer is hosted through Cloudflare. Its website can load Google Analytics 4 when a measurement ID is configured. Website measurements may include page visits, interactions, browser/device information, approximate region, and cookie or browser identifiers. The Viewer website’s analytics setup is separate from the cookie controls on ipocket.xyz; those controls do not automatically apply to the Viewer.

On ipocket.xyz, the website uses the first-party stat.ipocket.xyz service based on Umami, Vercel Web Analytics, and Vercel Speed Insights. Google Analytics may also load after you enable analytics in the website’s cookie settings. The first-party tracker is configured to exclude URL queries and fragments and to respect Do Not Track. These website services are not built into the native PhoneStage app. PhoneStage does not send screen frames, device-motion streams, or pairing secrets to website analytics as event data.

Apple provides the operating-system APIs, app distribution, and any diagnostics you choose to share through Apple settings. WebRTC and the pairing cryptography libraries run in the app or browser; they are not cloud recording services. Hosting, analytics, and email providers may process website or support information outside your country under their policies. The direct local screen-sharing path does not send your screen to those providers.

For more information, see Apple’s privacy policy, Cloudflare’s privacy policy, Google’s privacy policy, Vercel’s privacy policy, and the iPocket website privacy policy.

6. Support, retention, and your choices

When you send a support email or submit the website contact form, we receive the contact information and content you choose to send, including attachments or diagnostic details. Review those details before sending. They are retained as reasonably needed to answer your request and meet applicable legal or security obligations.

You can stop broadcasting, remove trusted browsers on the iPhone, remove paired iPhones in the Viewer, clear browser website data, and delete recordings you downloaded. If you remove a pairing in an offline browser, also remove that browser in the iPhone app to revoke any remaining authorization. Previously downloaded files are not erased by removing a pairing.

We do not sell PhoneStage screen content or pairing credentials. You may contact us to request access, correction, or deletion of support information we hold, or exercise other rights provided by applicable law. We cannot retrieve or delete recordings that exist only on your devices or copies held by recipients you chose.

7. Children and policy changes

PhoneStage is a general-purpose demonstration tool and is not designed to collect information from children. If you believe a child has sent personal information to our support service, contact us so we can address the request. A parent or guardian should supervise screen sharing where appropriate.

We will update this page and its effective date when our practices change. For questions about this policy, email contact@ipocket.xyz or use our contact page.

Data collection details

Field	Category	Required	Purpose	Storage	Retention	Opt-out
Live screen and device orientation	User content and motion data	Yes	Display the iPhone screen and align the 3D phone in the connected Viewer; motion following is optional	Processed on the iPhone and transmitted directly to the connected browser over the local network; no iPocket cloud video relay	Screen and motion buffers are temporary; a Viewer recording is saved only when you use the recording feature	Stop the iOS screen broadcast; manage motion access in system settings where available
Pairing and trusted-device information	Local connection identifiers and credentials	Yes	Authenticate the browser and optionally remember approved devices	App shared storage and device-only Keychain on iPhone; IndexedDB in the browser	Temporary connection records are replaced or cleaned by the app; remembered pairings remain until removed or local storage is cleared	Choose a connection without remembering it, or remove pairing on both devices
Viewer settings and recordings	Local preferences and user-created files	No	Remember display preferences and record a demonstration when requested	Browser local storage, temporary recording buffers, and files downloaded to your computer	Preferences remain until cleared; downloaded files remain until you delete them	Do not record; clear website storage and delete downloaded files
Website traffic and support requests	Website measurements and customer support	No	Deliver and measure webpages, protect the service, and respond to messages you send	Website hosting and analytics providers; your email provider and the iPocket support mailbox	According to provider settings and policies, and as reasonably needed for support or applicable legal obligations	Use available website/browser privacy controls; do not send a support request