Who is responsible
Pairy is an independent product operated by Nuno de Assis Miranda Schumacher in the Netherlands (KVK 99971186; VAT ID NL005422031B69).
Public service and correspondence address: Verdunplein 17, Box G1459, 5627SZ Eindhoven, Netherlands. The visiting address is shielded in the Dutch Business Register. Telephone: +31 6 29833499.
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, or account registration. Cloudflare may use essential security cookies when needed to protect traffic.
Waitlist
The website offers an optional launch waitlist. Submitting the form stores your email address and the time you submitted it, plus whether you signed up from the home page or the waitlist page. No IP address and no user agent are stored with your entry. To limit automated abuse, the form briefly counts submissions against a salted one-way hash of the connecting IP address; that counter holds no address, is not linked to your entry, and expires after one minute.
The lawful basis is your consent, given by submitting the form. There is no confirmation email. The list exists for a single message announcing that Pairy is publicly available. At send time the addresses are imported into MailerLite (UAB MailerLite, Lithuania), which hosts the data in the EU and provides the unsubscribe link. After that message the list is retired and deleted.
The waitlist is website collection only. The Pairy apps do not ask for an email address and do not send one to this list. To be removed at any time, email [email protected].
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, 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.
Mac update checks
When you manually check for a Mac update or allow automatic checks, Pairy requests its signed HTTPS update feed and, only when you approve or have enabled automatic downloads, the selected update artifact. Pairy does not send a stable device identifier or system profile with these checks and adds no update analytics or tracking. The hosting service necessarily processes ordinary HTTPS request metadata such as IP address, timestamp, requested URL, and user agent to deliver and protect the files.
Subscriptions
Pairy creates a random subscription identifier on your iPhone and uses RevenueCat to load products, process purchase and restore state, and determine whether the pairy_live entitlement is active. Pairy does not require your name or email for this identifier. The iPhone app shows the same existing value as its Support ID under Settings → About Pairy; this is an alias, not a new identifier. It is not your Apple ID or an authentication credential. Apple processes payment and Apple Account information; Pairy does not receive your payment-card details. Before a remote connection token is issued, Pairy's control plane asks RevenueCat whether the entitlement for that identifier is currently active.
Pairy copies the Support ID only when you tap Copy Support ID. This support feature adds it to no diagnostics, logs, analytics, new upload, or automatic email; the underlying identifier's existing RevenueCat and authenticated Remote uses remain as described above. You choose whether and where to paste the copied value.
For App Store privacy disclosure, Pairy's app-level inventory includes linked user and device identifiers, purchase history, product interaction used for allowance and session control, and other diagnostic data. These are used for app functionality, not tracking. Screen and input data that only transits a live encrypted session is not retained by Pairy or configured for recording.
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, authoritative DNS, security, and the remote control plane. 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 and Data Processing Addendum.
- RevenueCat, Inc. provides subscription product, purchase, restore, and entitlement processing using Pairy's random subscription identifier. See RevenueCat's Privacy Policy and Data Processing Addendum.
- Apple distributes the iPhone app and provides platform services including Keychain and StoreKit payments. Apple's own handling is governed by its Privacy Policy.
- Fastmail directly hosts Pairy's role-address mail. Cloudflare provides authoritative DNS but does not route support messages. See Fastmail's Privacy Policy and Data Processing Agreement.
These providers may process data outside the European Economic Area. Pairy's founder has not signed a separate DPA or enterprise agreement with Cloudflare, LiveKit, RevenueCat, or Fastmail; Pairy uses their standard online account terms to the founder's knowledge. The applicable terms version, transfer mechanism, and account-level settings remain pre-publication checks.
Retention
- Local captures, notes, preferences, and trust records remain until you delete them, revoke a device, reset Pairy identity, or remove the app data.
- Each app keeps at most two 512 KB connection-diagnostic files and reads at most the latest seven days. The per-Mac control plane keeps at most 200 content-free diagnostic events for 24 hours.
- Pairing and normalized subscription-authority records are needed while the relevant pair or subscription remains active. Pairy's approved target is to remove resolvable inactive operational records within 30 days after the relevant pairing is revoked or the verified subscription access ends.
- Completed allowance and session-accounting rows have an approved 30-day target after the applicable allowance window closes. Content-free security and abuse records have an approved 90-day target, unless a documented active investigation, legal obligation, or legal claim requires longer.
- Ordinary support messages and chosen attachments have an approved 90-day target after the case closes. Pairy retains a minimal deletion-request audit—received date, verification and completion status, and any documented exception—for 12 months after completion, without retaining secrets or unnecessary message content.
- Limited invoices, payout, tax, and other basic business records are retained for seven years where Dutch law requires it. This exception does not extend the life of Simulator content, pair credentials, session logs, or ordinary support attachments.
- Cloudflare, LiveKit, RevenueCat, Apple, and Fastmail apply their own documented operational or legal retention to data they process.
Pairy handles verified privacy requests without undue delay and normally completes them within 28 calendar days. If applicable law requires a faster response, that deadline applies. If applicable law permits more time for a complex request, Pairy will explain the extension within the initial 28-day period.
Implementation status: the founder-operated verified-request workflow is production-deployed and controlled-provider rehearsed. The policy above is founder-approved. Pairy's general 30/90-day server-expiry schedule is production-deployed and has passed configuration, staged/public, Remote, Local, and Demo regression proof. Provider-controlled recovery, security, billing, and legal retention remains subject to the provider terms and account configuration described above.
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.
You may copy the non-secret lookup value from Pairy on iPhone → Settings → About Pairy → Copy Support ID. A request remains valid if the Support ID is unavailable. Pairy may need limited safe 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.