1. Data we process
Account and device identifiers, connection metadata and necessary security events
This information supports login, device binding, scheduling, entitlement checks, abuse prevention and troubleshooting.
PRIVACY
Process only what the service needs.
JDesk handles the account, device, connection and security metadata required to provide the service. Remote screen content, keyboard content, clipboard text and file contents are not ordinary control-plane operator data.
Trusted native remote sessionsWeb manages identity and authorization; native clients carry control and media.
2. Remote-session content
Remote control and media follow the product end-to-end encryption boundary
Relay forwards encrypted bytes and does not require remote-session plaintext to provide routing.
3. Retention and rights
Retention follows business necessity and applicable law
Account deletion, device removal and applicable data-rights workflows are exposed through current product and privacy controls.
Start with secure remote access, then add what you need.
Core remote access remains simple; advanced performance and governance are enabled by published entitlements.