Legal
Privacy policy
How Remote KVM handles data.
Effective 16 November 2026 · Applies to the Remote KVM app · Controller: RSC Labs, CNPJ 66.442.055/0001-60, Porto Alegre, RS, Brazil
The English text is the binding version. It is not translated.
The short version: Remote KVM needs no account. The app connects straight from your phone or tablet to your KVM device, and we run no relay and no server that sees your connection, your screen or your keys. Device passwords stay on your phone or tablet. Optional usage statistics and crash reports never contain addresses, device names or what is on your screen. The app has no ads, no advertising identifier and no tracking.
Contents
1. Who we are
This policy is issued by RSC Labs ("RSC Labs", "we", "us"), a company registered in Brazil under CNPJ 66.442.055/0001-60, with its registered address at Rua 14 de Julho, 460, Porto Alegre, Rio Grande do Sul, Brazil. RSC Labs is the data controller for the personal data described here. It covers the Remote KVM app. Our other app and this website are covered by the RSC Labs privacy policy.
2. What stays on your phone
The app stores these on your phone or tablet only. We never receive them.
- Your devices: name, address, port, model and settings per device.
- Passwords for your devices, in the iOS Keychain or the Android Keystore. They are kept on this phone or tablet only, available after the first unlock, and are never included in backups. If two-factor authentication is on, the code is never saved.
- Certificate fingerprints you chose to trust.
- Settings, macros and the last picture shown for each device.
- Pictures and keystrokes of your session. The video, your input and the clipboard text you paste go from your phone or tablet to your device and nowhere else. We do not receive them.
- Copy text from the screen (Pro) is recognised on your phone or tablet by Google ML Kit. The picture and the recognised text are not uploaded by the app. See section 4.6 for what the library itself reports to Google.
Backups. The device list, settings, macros and last pictures are kept in a folder that the operating system does not back up: on iOS it is excluded from iCloud and computer backups, and on Android backup and device transfer are switched off for the app. Passwords stay in the Keychain or Keystore for this device only and are never backed up.
3. What the app connects to
- Your KVM device, at the address you entered or found. Connections use TLS where the device offers it. The app shows the certificate fingerprint, remembers it, and blocks the connection if it changes. Plain HTTP is allowed only for private addresses and Tailscale, and the app labels it "Not encrypted". The JetKVM video stream is encrypted even then.
- Network search. To find devices, the app looks at your local network. iOS asks for local network access first. What the search finds is not sent to us.
- Wake-on-LAN sends a packet from your phone or tablet on your local network, or through your device.
- Google Firebase and RevenueCat, described in section 4.
4. What we collect
These providers process data on our behalf, under their own security and data-processing terms.
4.1 Usage statistics (Firebase Analytics, Google)
Collected only when "Share usage statistics" is on.
- What: which features are used and whether they worked: device added or removed, session started, ended or failed, paywall viewed, purchase started, completed or restored. The values are coarse: the driver (for example
jetkvm), the model, whether it is Tested or Beta, the length of a session in seconds, the kind of error (never the message) and the plan (free or Pro). One user property says whether the plan is free or Pro. - Never: host names, IP addresses, device names, user names, passwords, URLs, screen content or error messages. The app removes anything that is not on its fixed list before it reaches the library.
- Added by Google's library: a random per-install ID, the app version, the phone model, the OS version, the language and a country derived from the IP address. We use no advertising ID, no Android ID and no iOS identifier for vendors; these are switched off, and the Android advertising-ID permission is removed from the app. The app does not report screens and shows no tracking prompt.
- Why: to learn which features work and which fail, and to fix them.
- Retention: Google Analytics keeps event data for 2 months.
4.2 Crash reports (Firebase Crashlytics, Google)
Collected only when "Share usage statistics" is on.
- What: the technical details of a crash or an error: the stack trace, the app version, the phone model, the OS version, whether the app was in the foreground, and a per-install ID. Error text and notes have IP addresses, MAC addresses and host names removed before they are sent.
- Why: to fix crashes.
- Retention: Crashlytics keeps crash data for 90 days.
4.3 Performance timing (Firebase Performance Monitoring, Google)
Collected only when "Share usage statistics" is on.
- What: two timings, how long a connection takes and how long until the first picture, with the driver, the tier and the kind of video (for example
h264). Automatic network monitoring is off, so the library does not see the addresses the app connects to. - Why: to keep connections fast.
- Retention: as set by Google for Firebase Performance Monitoring.
4.4 Remote switches (Firebase Remote Config, Google)
- What: at launch the app asks Google for a small settings file. It carries switches, such as turning off a broken device driver, and a minimum app version. The request includes the per-install ID, the app version, the phone model, the OS version and the language, and your IP address reaches Google as in any request.
- Why: to turn off a broken driver without an app update.
- Your choice: this does not follow the usage statistics switch. In the EU, EEA and UK it runs from the first launch, before the question about usage statistics is answered.
4.5 App verification (Firebase App Check, with Google Play Integrity and Apple DeviceCheck)
- What: the app asks Play Integrity (Android) or DeviceCheck (iOS) for a token that says this is a genuine copy of the app. The app never reads or stores the token. Nothing is enforced yet.
- Why: to stop abuse of our Firebase project.
- Your choice: this does not follow the usage statistics switch, and in the EU, EEA and UK it also runs before the question is answered.
4.6 Text recognition (Google ML Kit, Google)
- What: when you use Copy text (Pro), the Google ML Kit library recognises the text on your phone or tablet. The picture and the recognised text are not sent to Google or to us. According to Google, the library itself collects technical data about its use and sends it to Google for diagnostics and usage analytics: device information (manufacturer, model, OS version), application information (package name and version), a per-installation identifier that is not intended to identify you or your device, performance metrics such as latency, and event and error information.
- When: only when the library runs, which is when you use Copy text.
- Your choice: this does not follow the usage statistics switch. To stop it, do not use Copy text.
4.7 Purchases (RevenueCat, with the Apple App Store or Google Play)
- What: if you buy Pro, or restore a purchase, RevenueCat receives a random anonymous ID created by the app, your store receipt or purchase token, the product, the app version and basic device information, and your IP address reaches it as in any request. The only attribute we set is the plan (free or Pro). We do not ask for your name or email. The store handles payment, and we do not see your card, Apple ID or Google account.
- When: the service starts with the app, to know whether Pro is active.
- Why: to unlock Pro on your phone or tablet and to restore it.
- Retention: RevenueCat keeps purchase records for as long as needed to give you Pro and for accounting.
4.8 In-app review prompt
After some good sessions the app may ask the system to show its rating sheet. Apple or Google runs the sheet. We receive no answer unless you leave a public review.
5. Traces
A trace is a text file that lists what your phone or tablet and a device said to each other during diagnostics. It is made only when you choose "Export trace", and it is shared through the system share sheet, to whoever you choose, for example us by email.
- Removed from the file: passwords, tokens, cookies, user names, IP addresses, and the address and name of the device.
- Kept: the model, the firmware version, the certificate fingerprint and how each step went.
Nothing is sent to us unless you send it. If you email us a trace, we use it only to fix that device's support, and we keep it for as long as the support request is open and for up to 12 months after.
6. What we do not do
- No account, no sign-in, no email collection.
- No ads and no advertising ID. No tracking across other apps and websites. We do not sell data.
- We do not receive your screen, your keystrokes, your clipboard or your passwords.
7. Your choices
- Usage statistics and crash reports: Settings, Privacy, "Share usage statistics". In the EU, EEA and UK the app is off until you answer the question shown the first time the device list appears. "Share" turns it on and "Don't share" keeps it off. Closing the question without an answer asks again later. Elsewhere it is on from the first launch, and you can turn it off at any time. Turning it off stops Analytics, Crashlytics and Performance Monitoring. The app picks the region from your phone's language and region settings, never from your location.
- Delete your data on the phone: delete a device in the app, or uninstall the app.
- Data held by Firebase or RevenueCat is tied to a random ID, not to you, so we cannot normally find your record. If you want it removed anyway, write to support@rsclabs.net and tell us what you can: the platform, the app version and the approximate date.
- Your rights. Wherever you live, we will honour access to the data we hold about you, correction, erasure, portability, withdrawal of consent, objection to processing based on legitimate interests, and information about who your data was shared with, as the LGPD (Lei nº 13.709/2018), the GDPR and the UK GDPR provide. Write to support@rsclabs.net. We may ask you to confirm the request is yours. If you are in Brazil and are unsatisfied with our response, you may complain to the ANPD; in the EEA or the UK, to your national supervisory authority.
8. Legal bases
Where the LGPD or the GDPR applies, we rely on consent for usage statistics, crash reports and performance timing in the EU, EEA and UK, where the app asks first; legitimate interests for the same measures elsewhere, and for the remote switches, app verification and library diagnostics in section 4, which keep the app working and secure; performance of a contract for purchases; and legal obligation for accounting records.
9. Retention
The retention period of each service is in section 4. Data on your phone or tablet stays until you delete the device in the app or uninstall the app.
10. Children
Remote KVM is a tool for people who manage computers. It is not directed to children, and the stores list it for ages 18 and over. We do not knowingly collect personal data from children under 13, or under the higher age that applies where they live. If you believe a child has sent us data, write to us and we will delete it.
11. International transfers
We are based in Brazil, and Google (Firebase, ML Kit) and RevenueCat process data in the United States and other countries. Where a transfer needs a safeguard, we rely on the mechanisms those providers offer, such as the EU-US Data Privacy Framework or the European Commission's standard contractual clauses.
12. Changes
When this policy changes in a way that matters, we update the effective date above, and the app's release notes say so. Earlier versions are available on request.
13. Contact
RSC Labs
Attention: privacy
Rua 14 de Julho, 460 — Porto Alegre, RS, Brazil
CNPJ 66.442.055/0001-60
Email: support@rsclabs.net