Privacy

RC Pair privacy

Effective 13 October 2026

RC Pair pairs your iPhone or iPad with a computer you own. We run no server for it. Nothing about your device, its screen or the pairing comes to us unless you email us, share crash reports with developers or test RC Pair through TestFlight. If you email us, we use that email only to answer you and fix what you report.

On this page
  1. What stays on your device
  2. What your network can see
  3. Your computer and your agent
  4. What we don't receive unless you send it
  5. Apple's part
  6. If you email us
  7. This website
  8. How to stop and delete
  9. Children
  10. Your rights
  11. Who is responsible
  12. Changes to this page

What stays on your device

RC Pair keeps these on your iPhone or iPad.

  • A pairing not yet sent. It holds the pairing key and this device's name, model and ID. RC Pair deletes this copy when your computer confirms it saved them. If the send fails, the copy stays here so you can try again. A send that looks failed may still have reached your computer.
  • RC Pair's own random identity, including its keys. The pairing key you send is this identity's key, so RC Pair still holds its private half after a send. Start over pairs again with the same key, so a computer that got an earlier pairing can still use it. Delete RC Pair data on this device makes a new key for your next pairing. It does not take back a key a computer already has.
  • Your consent record. It holds which version of the consent wording you agreed to, the two switches you turned on, when you tapped, the app version, whether this is an iPhone or iPad, and a fingerprint of the exact wording you saw.
  • Setup progress and a few settings, such as which step you are on, whether a pairing has been sent and the name of the computer it went to. They also include when you reached the Developer Mode step and when this device last started, so RC Pair can tell it restarted.
  • A pairing code. It shows in RC Pair, in a notification and in iOS's progress display while you pair. iOS may also show that notification on the Lock Screen and on a paired Apple Watch. It sits on this device's clipboard for up to 2 minutes. When the attempt ends, RC Pair clears the clipboard if it still holds the code.
  • A short log of what the app is doing, for troubleshooting. It can include this device's name, model and ID, network addresses, and the name and address of any computer whose link you scanned or pasted. It is kept only in memory and is gone when the app closes.

iOS includes RC Pair's settings and consent record in your device backups, such as iCloud Backup. Its keys and any unsent pairing never restore to another device.

RC Pair also checks whether Developer Mode is on, when the device last restarted and whether you are on Wi-Fi. It uses these only to guide you through setup and never sends them anywhere.

While Only accept pairing from this device is on, RC Pair reads this device's own network addresses, which can include VPN addresses. It uses them to turn away pairing requests from other devices. If it turns one away, it notes those addresses in the troubleshooting log. The switch is on by default. If you turn it off, another device on your network can ask to pair with RC Pair. It still needs the code RC Pair shows on this device.

When you tap Paste link, RC Pair reads your clipboard once to find its link. It ignores anything else there and does not keep it. If RC Pair showed a pairing code, it checks the clipboard again when that attempt ends, so it can remove the code. If you copied something else since, iOS may ask whether to allow the paste. RC Pair does not keep what it finds.

Its notifications are created on the device. We send no push messages.

RC Pair does not use your contacts, photos, location, camera or microphone.

What your network can see

While you set up and pair, other devices on your Wi-Fi network can see that RC Pair is running on this device. They see this device's network address and an identifier that stays the same, even if you reinstall RC Pair, until you tap Delete RC Pair data on this device. This stops when setup ends, and each broadcast lasts at most 10 minutes.

Your computer and your agent

RC Pair sends the pairing key to one computer you choose, and only when you confirm. On that computer you run rcpair-receive, which shows a QR code. Scan it with the Camera app, or copy its link and tap Paste link in RC Pair. RC Pair then shows a sheet with that computer's name and address. The pairing is not sent until you tap Send.

RC Pair sends only to a private address, on your own network or on a private network such as Tailscale. It encrypts the pairing for that computer alone. If the link gives a computer name instead of an address, RC Pair asks the DNS server your device uses for that name's address before it shows the sheet. That server can be outside your private network, such as your carrier's.

Your computer receives the pairing key, this device's name, model and device ID, the RC Pair version, and a copy of your consent record. The copy leaves out whether this is an iPhone or iPad. rcpair-receive saves them in two files, set so only your user account can read them. By default they go in a .rcpair folder in your home folder. It also notes the network address this device sent from and the time the pairing arrived. It prints the device's name, model, address and ID in the terminal, so if an agent runs rcpair-receive, the agent sees them. If you give rcpair-receive a command to run when a pairing arrives, that command gets both files. None of it comes to us.

The pairing key works like a key to this device. Software on a computer that holds it, including any AI agent you run there, can see the screen and control it, the same as someone holding it. It can also list, open, install and remove apps, see running processes, read the system log and crash logs, read and change the clipboard, set a simulated location and restart the device. Apple's developer services on a paired device also include backup and network capture. Treat the key as full access to this device.

You run that computer and the agent. We do not. Your agent may send what it sees to the company that runs it, under that company's own privacy terms. Your private network provider carries traffic between this device and your computer under its own privacy terms.

If the software on your computer tells RC Pair a session has started, RC Pair shows a Live Activity on the Lock Screen and in the Dynamic Island with the name that computer gives itself. RC Pair cannot tell on its own that it is being controlled. The name is never sent to us. iOS may also show it on a paired Apple Watch or Mac. With the open tools available today, no computer can start it yet, so you will not see it. You can always stop control on the device.

What we don't receive unless you send it

  • Your screen or anything on it, except screenshots you choose to attach to an email or TestFlight feedback.
  • The pairing key.
  • Your device's name, model, ID or network addresses, unless you send them in a support email. Crash reports and TestFlight data from Apple do include details about the device, such as its model and iOS version.
  • Your passcode or Apple Account password. RC Pair never asks for them.

RC Pair has no analytics or ads, and no outside code that collects data. There is nothing to sign up for. We pass no data from RC Pair to anyone. We do not sell or share personal information.

These companies handle personal data connected with RC Pair. Porkbun, in the US, receives email sent to support@rcpair.si and forwards it to our Microsoft 365 mailbox. Microsoft, in the US, stores that email for us. Each gets your email address, what you write and anything you attach. GitHub, in the US, hosts this website and gets your IP address when you visit it. DigitalOcean, in the US, hosts the server that counts visits to this website and stores the records described under This website. Apple handles crash reports and TestFlight data under its own terms.

Apple's part

This page covers RC Pair from the App Store and from TestFlight testing.

  • Apple handles downloads and updates under Apple's own privacy policy. Apple shows us totals, such as download counts, that do not identify you.
  • If you turned on Share With App Developers in Settings > Privacy & Security > Analytics & Improvements, Apple may pass us crash reports for RC Pair. We read them only in Apple's tools and use them only to fix bugs.
  • If you test RC Pair through TestFlight, Apple passes us the feedback, screenshots and crash reports you choose to send, with your email address if you use the feedback form. If we invited you by email, we also see the name and email address we invited. With each piece of feedback or crash, Apple includes details about the device, such as model, iOS version, language, time zone, battery level, free storage and network type. For each tester, Apple also shows us whether the build is installed and how many sessions and crashes it had. We use all of this only to fix the app. We delete feedback and screenshots after 12 months. Crash reports stay in Apple's tools.

Our legal basis for crash reports and TestFlight data is our legitimate interest in fixing the app. Crash reports stay in Apple's tools, and Apple keeps them under its own terms.

If you email us

Write to support@rcpair.si any time. We get your email address, what you write and anything you attach. Emailing us is up to you. Nothing in RC Pair needs it.

Email support in the app opens a blank email to us with the subject RC Pair support. RC Pair adds nothing else to it.

Copy diagnostic report is a separate button. It puts a report on this device's clipboard so you can read it and paste it into an email if you want to. RC Pair never sends it on its own. The report holds these.

  • The RC Pair version and build, and the version of its pairing engine.
  • Whether this is an iPhone or iPad, and its iOS version.
  • Whether Only accept pairing from this device is on.
  • The app's recent activity, up to its last 200 notes. These can include this device's name and model, the name and address of any computer whose link you scanned or pasted, even if you did not send to it, network addresses of pairing connections, and error codes from a failed send.
  • The pairing engine's log. It can include RC Pair's own identifier, this device's name, model and ID, and network addresses of pairing connections. If RC Pair turned a pairing request away, it also lists all of this device's network addresses, which can include public and VPN addresses.

The report never holds your screen, the pairing key or the pairing code. It stays on the clipboard until something replaces it, and iOS can share it with your other Apple devices through Universal Clipboard.

We use your email only to answer you and fix the problem you report. Our legal basis is our legitimate interest in answering you and keeping the app working. We make no automated decisions about you and build no profiles.

We keep a support conversation for 12 months after it ends, then delete it. Ask and we will delete it sooner.

Email to support@rcpair.si goes to Porkbun, in the US, which forwards it to our Microsoft 365 mailbox. Microsoft, in the US, stores it there for us. Both get your email address, what you write and anything you attach. Our reply comes from a Rising Creek Construction email address.

This website

This site counts visits so we can see how many people come and which of our posts brought them. It sets no cookies, stores nothing on your device and loads no scripts from other companies.

Each page asks our counter at t.rcpair.si for a blank image. That request tells it which page you opened, the tag in the link you followed if it had one (such as ?r=x-launch), the name of the site that sent you (such as x.com), any link you tap that leaves the page and, when you leave, how long you stayed and how far you scrolled. Our server records this with the time and your browser type. It removes the last part of your IP address before anything is saved, so we never store your full address. DigitalOcean, in the US, hosts that server. We use these records only to count visits and we delete them after 12 months. Our legal basis is our legitimate interest in knowing whether this site reaches people.

GitHub, in the US, hosts the pages themselves on GitHub Pages. When you visit, GitHub gets your IP address, the page you ask for and your browser type. GitHub logs and stores visitors' IP addresses for security, whether or not they are signed in to GitHub, and describes its practices in the GitHub General Privacy Statement. We do not receive or keep those logs. Our legal basis for using GitHub is our legitimate interest in running a secure site.

How to stop and delete

  • To stop remote control right away, turn off Developer Mode in Settings > Privacy & Security. Then delete both files rcpair-receive saved on every computer you sent a pairing to. By default they are in ~/.rcpair, named with this device's ID and ending in .rppair.plist and .json. If Developer Mode is turned on again, a computer that still has the key may be able to connect again.
  • Delete RC Pair data on this device removes RC Pair's identity and keys, any pairing not yet sent and your consent record. It also removes the name of the computer you sent to, the note that a pairing was sent and your choice for the Only accept pairing from this device switch, which goes back on. It puts setup back at the first step.
  • Start over removes any pairing not yet sent, your consent record and the name of the computer you sent to. It puts setup back at the first step.
  • Start over keeps RC Pair's identity, the Only accept pairing from this device switch and the note that a pairing was sent. Settings shows the same RC Pair, and your next pairing uses the same key as the last one. To pair with a new key, use Delete RC Pair data on this device instead.
  • Neither one clears the troubleshooting log. That log is gone when the app closes. Neither one can reach your computer.
  • RC Pair's keys and pairing data can stay on the device after you remove the app. Tap Delete RC Pair data on this device first.

Didn't set this up? Turn off Developer Mode, change your passcode and delete RC Pair. stopstalkerware.org can help.

Children

RC Pair is for people 18 and older, and it asks you to confirm your age before setup. It is not meant for children, and we do not knowingly collect personal information from anyone under 13. If we learn that a child has emailed us, we will delete the message. A parent can also ask us to.

Your rights

The personal data we hold is email you send us, the visit records described under This website, and the crash reports, TestFlight data and TestFlight tester details Apple passes to us. GitHub keeps its own records of visits to this website, and we cannot see them. You can ask for access, correction, deletion, restriction or a portable copy, and you can object to our use of it. Crash reports do not name you, so we may not be able to find yours. Visit records do not name you either and keep only part of your IP address. Email support@rcpair.si and we will answer within one month.

Everything else stays on your device, its backups or your computer, so you control it directly.

If you are in the EU or UK, you can complain to your data protection authority. In the UK that is the Information Commissioner's Office.

Who is responsible

RC Pair is published by Rising Creek Construction LLC, a Texas company. It is responsible for the personal data described on this page. Reach us at support@rcpair.si.

Changes to this page

If we change how RC Pair handles data, we will update this page and its date before the change reaches the app.