Keychain and data protection
Passwords and private keys live in the device keychain; app data is protected by the iOS Data Protection classes.
Security & Privacy
remoteNX connects you to servers that matter. So everything that could let data out is off – until you turn it on deliberately.
Passwords and private keys live in the device keychain; app data is protected by the iOS Data Protection classes.
If you want, remoteNX asks for Face ID when it opens – immediately or after a time you choose.
In the app switcher remoteNX shows a cover instead of your session or server list.
If the app stays in the background for more than 20 seconds, running sessions are ended cleanly.
On the first connection remoteNX remembers the host key and warns you clearly if it changes.
RDP connections use TLS 1.2 or newer; legacy RDP security is off.
Drive redirection is off by default. When you turn it on you can make it read-only per connection; the session then cannot change or store anything there.
An import never turns on risky options: no drives, no microphone, no turning NLA off, no passwords and no bypassing certificate errors.
No account, no advertising IDs, no tracking across apps. Optional statistics only with your consent.
Only with consent. Host names, user names, IP addresses, paths and terminal content are removed on the device; our server in the EU also drops the sender's IP address.
remoteNX uses proven open-source building blocks. All licences are in the app under Settings → Acknowledgements.
remoteNX uses only standard encryption (such as TLS and SSH) and is declared accordingly with Apple.
What exactly happens with data is in the privacy policy. Found a vulnerability? Write to us confidentially at support@remotenx.app.