DesktopHost approval
Every session requires the host's authorization. The viewer provides the computer ID and temporary access code, and the host can decline.
CLEAR SECURITY BOUNDARIES
Security should never be a guessing game.
What DesktopBee protects today, and the important limits of the current preview.
Session permissions
View Only and Full Control allow the host to restrict input. The relay checks remote-input messages instead of relying only on hidden buttons.
Transport encryption
Browser and Windows clients communicate with the relay over encrypted transport. This is not end-to-end encryption of screen data against the relay.
Optional product telemetry
Anonymous in-app usage tracking is off by default. If enabled, it reports broad app activity, not chat, remote screen content, access codes, or identity keys.
Preview limitation: DesktopBee is not yet independently security audited and does not support end-to-end encryption. Avoid use with highly sensitive systems, and only connect to devices you own or are authorized to access.
SECURITY QUESTIONS
Frequently asked
Can a device connect silently?
Not in the current preview. A one-time code and approval at the host are needed for each session.
Does the owner always remain in control?
The host may reject, restrict or disconnect a session. Always terminate the connection when finished.
Are remote screens used for product analytics?
No. Optional activity tracking uses a separate pseudonymous analytics ID and broad usage events; it does not collect remote session content.
Is Pro payment active?
No. Prices are proposals. Checkout and subscription entitlement enforcement are not enabled.
READY TO GET STARTED?
Remote support starts with a Windows PC.
Try DesktopBee Free with host approval and browser viewing. The download center always displays the current published release status.