What a company is trusting us with.
The short answer for anyone filling in a security questionnaire: what is encrypted, who decides who gets in, what our server holds, who else handles it, and for how long.
Security in brief
Encryption
A session between two computers running JoyRemote is carried inside TLS 1.3 on a local network, and inside QUIC, which is also TLS 1.3, over the internet. The screen, keyboard and mouse input, the clipboard, transferred files and audio all travel inside that encryption.
The one exception is the page a computer serves to a phone or a browser on its own network, which is plain HTTP. A company can switch that page off on all of its computers.
Device keys
Each computer generates its own key, and the private half never leaves it. Each end of a session proves which computer it is with that key. This is how JoyRemote knows who is connecting, not a password and not a certificate fingerprint.
Approval
Every connection is approved on the screen of the computer being reached, unless that computer has been told to remember a particular viewer. The computer asking cannot approve itself. On a company computer, the company's list of viewers counts as that approval. The person at the keyboard can still block any viewer, and sees the blue circle whenever somebody is connected.
What the server sees
Computers on the same network never involve our server. Over the internet, the directory introduces two computers to each other by number. When a network will not let them talk directly, our relay carries the traffic between them, still encrypted end to end, and the relay cannot read it. The screen, the keyboard, and the contents of files never pass through our server or are stored on it, except as that encrypted relay traffic.
The company's say, and its limits
A computer nobody enrolled is unchanged, and the directory cannot let anyone into it. An enrolled computer accepts the company's list of viewers, signed by the directory's key. The people who decide that list sign in to the console with a link sent to their e-mail; there is no password to steal. A computer removed from the company forgets the list.
What the directory holds for a company
- The organisation's name.
- Its members' e-mail addresses and roles.
- Its enrolment tokens, kept hashed.
- For each enrolled computer: its device public key, number, name, platform and JoyRemote build, and the facts on the fleet list: operating system, signed-in user, uptime, free disk space, whether a restart is pending, and whether it is online.
- The company's list of viewers.
- The audit log: for each event, its name, the time, the computer's number, the other party's number and name, and for a file transfer the file names and sizes.
What the directory holds for every computer, in a company or not, is on the privacy page.
Where it is stored
The directory and the relay run on a server we rent from OVHcloud, in the European Union. Payments are held by whoever took them: Paddle for computers, Google Play or the App Store for phones. We never see card details.
Sub-processors
| Who | What for | Where |
|---|---|---|
| Paddle.com Market Ltd | Payments for computers and Teams. Merchant of record: takes the money, handles VAT, issues invoices | United Kingdom |
| Google Play: purchases in the Android app | See Google's privacy policy | |
| Apple | App Store: purchases in the iPhone app | See Apple's privacy policy |
| OVH SAS (OVHcloud) | Hosts the directory and the relay server | OVHcloud, European Union |
| Placeholder, not yet in use | Sending console sign-in links by e-mail | An SMTP provider named here before it is used for customer data |
We will tell each company's owners at least 30 days before adding or replacing a sub-processor, and change this table at the same time.
How long things are kept
- Audit log: 90 days.
- Console sign-in links: valid for 15 minutes.
- Console sign-ins: last 30 days, then you sign in again.
Reporting a vulnerability
Write to info@joyremote.com. We will answer within 5 business days. Please give us a chance to fix the problem before telling anybody else.
Certifications
None yet. JoyRemote has not been audited for SOC 2 or ISO 27001, and we offer no contractual SLA. We will say here when that changes.
Data processing agreement
For companies in the scope of the GDPR, our data processing agreement sets out what we do with the company's data on its behalf.
Last updated October 2026.