Who is responsible
Pairy is an independent product operated by Nuno Schumacher in the Netherlands. For privacy questions or requests, email [email protected]. For other legal matters, email [email protected].
The short version
- Pairy does not use advertising trackers or sell personal data.
- Screen frames, screenshots, notes, clipboard contents, and typed text are not uploaded to Pairy's control-plane servers.
- Remote sessions use encrypted WebRTC transport. Pairy does not configure those sessions for recording.
- Captures and notes stay on your devices until you delete them.
- The website has no Pairy analytics or marketing cookies.
Data the website handles
When you visit getpairy.com, Cloudflare processes ordinary request data such as IP address, browser and device information, requested URL, timestamps, and security signals to deliver and protect the site. Pairy does not add analytics, advertising pixels, account registration, or a mailing-list form. Cloudflare may use essential security cookies when needed to protect traffic.
Data the apps handle
Pairing and trust
The apps create random Mac, phone, and pair identifiers and may store a device display name so your devices can recognize trusted peers. Pairing credentials are stored in Apple Keychain on your devices. Pairy's remote service stores one-way credential hashes and limited pairing state; it does not receive the raw Keychain credential.
Simulator and session information
Simulator names, runtime information, selected-device state, and local connection preferences are used to show and control the Simulator you chose. They remain local except for the minimum identifiers and session state needed to establish a remote connection.
Screen, input, captures, and notes
Live screen frames and control events are transient. Nearby sessions travel directly over local TLS. Remote sessions travel through encrypted WebRTC transport provided by LiveKit Cloud. Pairy does not store or record relay media. Screenshots, thumbnails, recordings you explicitly export, and notes are stored locally until you delete them. Remote input and user-requested content may transit the encrypted session but are not written to Pairy's control-plane logs.
Reliability and security data
Pairy and its infrastructure providers may handle IP address, request metadata, connection timestamps, coarse session state, error categories, and numeric health metrics to authenticate devices, prevent abuse, keep the service reliable, and control infrastructure cost. Logs must not contain screen pixels, note text, typed text, pairing QR payloads, access tokens, or encryption keys.
Support messages
If you contact Pairy, we process your email address, message, attachments you choose to send, and relevant app/device versions to respond. Never email pairing secrets, access tokens, private keys, or a live pairing QR code.
Why data is processed
Depending on the context, Pairy processes data to perform the service you request, pursue legitimate interests in security and reliability, respond to a message you send, comply with legal obligations, or act with your consent. Pairy does not repurpose session data for advertising.
Service providers
- Cloudflare provides website hosting, DNS, security, the remote control plane, and email routing. See Cloudflare's Privacy Policy and Data Processing Addendum.
- LiveKit Incorporated provides encrypted WebRTC transport for remote sessions. Pairy does not enable LiveKit recording or inference features. See LiveKit's Privacy Policy.
- Apple distributes the iPhone app and provides platform services such as Keychain and, when purchases launch, StoreKit. Apple's own handling is governed by its Privacy Policy.
These providers may process data outside the European Economic Area. Where required, Pairy relies on provider contractual safeguards and other lawful transfer mechanisms.
Retention
- Local captures, notes, preferences, and trust records remain until you delete them, revoke a device, reset Pairy identity, or remove the app data.
- Active server pairing records remain while the pair is trusted. After revocation, limited encrypted cleanup state may remain only until the remote deletion is acknowledged or as needed to prevent abuse.
- Operational and security logs are kept only for the period needed to investigate reliability, security, fraud, or legal issues and are also subject to provider retention settings.
- Support messages are kept for the life of the case and a reasonable service history, then deleted or anonymized unless law requires longer retention.
Pairy will publish exact production retention periods before the public app release and will not extend retention without updating this policy.
Your choices and rights
You can delete captures and notes, revoke trusted devices, disable Remote, and reset Pairy identity from the apps. You may also request access, correction, export, restriction, objection, or deletion where applicable by emailing [email protected]. See the deletion guide for practical steps.
Pairy may need limited information to verify a request but will never ask you to send a password, bearer credential, private key, or pairing QR payload. You may lodge a complaint with the data-protection authority where you live or work.
Children
Pairy is a professional developer tool and is not directed to children. Pairy does not knowingly collect personal data from children under 16.
Changes
Material changes will be posted here with a new effective date. If a change materially affects existing app data, Pairy will provide additional notice where reasonably possible.