Delete local captures and notes
Delete individual screenshots and notes from the Pairy inbox or gallery where they appear. On the Mac, Pairy app files are stored under ~/Library/Application Support/Pairy. Removing that folder deletes ordinary local app files, but it does not remove Keychain credentials.
Remove a trusted phone
Use the trusted-devices controls in Pairy on the Mac or phone to revoke the pair. Revocation blocks the device locally first and then removes its remote authorization. If the network is unavailable, encrypted cleanup state may remain temporarily so Pairy can retry the remote revocation later.
Reset Pairy identity
Use Reset Pairy Identity when you need to remove all local trust and rotate the phone's pairing identity. This invalidates existing pairing relationships but does not change the subscription customer or Support ID. Pairy may retain only the old encrypted revocation capability needed to finish pending server cleanup.
Delete app credentials
Pairing credentials live in Apple Keychain and can outlive ordinary app-file deletion. Use Pairy's reset/revocation controls before uninstalling when possible. If a test build no longer exposes those controls, contact [email protected] for guidance.
Leave the launch waitlist
If you gave your email address to the website waitlist, email [email protected] from that address and it is removed. No Support ID is needed; the waitlist is website-only and holds nothing but the address, the time it was submitted, and which page it came from. The list is deleted after the single launch announcement in any case.
Request remote-service deletion
- Email [email protected] with the subject “Pairy data deletion request.”
- In Pairy on iPhone → Settings → About Pairy → Copy Support ID, copy the non-secret random identifier. Paste only that value into your request and share it only with Pairy support.
- Do not send a pairing QR code, bearer credential, token, password, private key, or Keychain export.
- Requests remain valid if the Support ID is unavailable. Pairy support may use limited, safe verification steps to confirm that the request concerns your records, but will never ask for a secret.
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.
Operational status: Pairy's private founder-operated verified-request workflow is deployed and has passed a controlled end-to-end Cloudflare and RevenueCat rehearsal. It is not a public lookup API. The 28-day target and retention schedule are 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 provider terms and account configuration.
The verified-request workflow is designed to end active Remote service, remove resolvable pairing, diagnostic, subscription-authority, allowance, session, and accounting records, and delete the matching RevenueCat customer and aliases. It is not a public lookup endpoint, and the Support ID alone is not proof of ownership.
What Pairy cannot delete for you
Pairy cannot delete files you exported elsewhere, messages or attachments in another person's mailbox, data controlled independently by Apple, or copies you made outside Pairy. Deleting Pairy or RevenueCat service data does not cancel an Apple subscription; manage renewal separately through Apple. Infrastructure providers may also retain limited security, billing, legal, or recovery records under their own obligations and retention schedules. Cloudflare may retain deleted Durable Object data in point-in-time recovery history for up to 30 days; Pairy does not restore deleted customer data except where a security or disaster-recovery need makes restoration necessary.
Questions
For help with deletion, email [email protected]. See the Privacy Policy for data categories, purposes, providers, and rights.
