PILOT DATA HANDLING · TECHNICAL SUMMARY

ONE Desk pilot data handling

Updated 13 October 2026. This page describes the current pilot architecture, not a substitute for a legally reviewed privacy policy or data processing agreement.

Where desktop data travels

In the native LAN pilot, video frames and user-authorized input are carried over authenticated, TLS-encrypted LAN connections between participating computers. The ONE Desk public marketing website and ONE Accounts portal do not provide internet relay or host those LAN desktop streams.

Local data

ONE Desk stores local enrollment and administrator trust settings and audit events to support security controls, connection records and troubleshooting. The Windows uninstaller offers a separate choice to keep or delete ONE Desk's saved local settings. Avoid sharing security-event files publicly because they may contain computer names and private IP addresses.

Account portal

Workspace registration requests collect the name, email address and organization name supplied by the requester. Account activation uses authenticated sign-in with an authenticator app. Customers should not provide remote access passwords or secret access codes in registration or support requests.

Operational and legal review

Before offering paid general-availability service, a complete controller identity, retention schedule, applicable jurisdiction, international transfer information, contact and deletion procedures, processor inventory and security commitments must be formally approved and published.

Questions

For a pilot-related data-handling enquiry contact info@mchilsconsultancy.com. Do not send remote support credentials by email.