Home/Security

Security

How we protect connections, where data is stored, and how to reach us if you find a vulnerability.

Last updated:

Encryption

On a connection made with a SmartDesk ID, screen images, keyboard and mouse input, clipboard, audio and transferred files are encrypted between the two devices. Only those two devices hold the key. The relay server that forwards the connection cannot decrypt the session; it only passes encrypted data along. In this sense, connections made with an ID are end-to-end encrypted.

The relay and ID servers cannot see session content, but they do see connection metadata (SmartDesk ID, IP address, duration). This is described in our privacy policy.

LayerHow
Device identityEvery device has its own Ed25519 key pair. The ID server signs the device's public key; the app verifies that signature with the server key built into it.
Session keyGenerated fresh and at random for every session, then sealed to the other device's public key with an ephemeral X25519 key (libsodium crypto_box: Curve25519, XSalsa20-Poly1305).
Session trafficEncrypted with XSalsa20-Poly1305 (libsodium secretbox); tampered packets are rejected.
TransportConnections through a relay are additionally carried inside TLS (WSS, port 443).

Because the SmartDesk ID server signs the devices' public keys, the security of the ID server is part of this model. If you want to run that server yourself, see self-hosted deployment.

Direct connection by IP address

The advanced "direct connection by IP address" option does not perform this key exchange yet, so connections made that way are not encrypted. It will be encrypted in a future version. Until then, use it only on a local network you trust. Connections made with a SmartDesk ID are not affected.

Servers and data location

Our primary infrastructure (ID server, relay and the Console management panel) runs in a data centre in Istanbul, Turkey. Users connecting from some countries may be routed through regional relays; on those routes the session stays encrypted as described above. Where the network allows, the two devices connect directly and traffic does not pass through a relay at all.

We also use service providers outside Turkey for the website, payments, email and error reporting. Which service processes which data is listed in the table in our privacy policy.

Data we collect

  • Account: name, email address, company name.
  • Device and connection: SmartDesk ID, device name, operating system and app version, IP address, connection metadata (duration, transport type, codec).
  • If device management is enabled: inventory data such as hardware, installed software and update status.
  • Error reports: crash reports and diagnostic logs. These do not contain screen content or session media.

Screen images, audio and clipboard content from a session are not stored on our servers. Details and retention periods are in the privacy policy.

Access control

  • Connection approval: To connect to a device, either the person at that device accepts the request or the device password is entered.
  • Wrong-password lockout: More than 6 failed attempts within a minute pause password entry for 1 minute; more than 30 failed attempts in total lock password sign-in.
  • Console: two-step verification (with an authenticator app) and role-based permissions.
  • Audit log: actions taken in the Console are recorded together with who took them.

Updates and code signing

  • Windows installers are Authenticode-signed; the macOS app is notarized by Apple.
  • Since version 3.3.8, the in-app automatic updater verifies the signature of the downloaded file before installing it.
  • Download SmartDesk only from smartdesk.help or the official app stores.

Self-hosted deployment

Enterprise customers can run SmartDesk on their own servers. In that setup the ID server, relay and Console run on your infrastructure. Write to info@smartdesk.help for details.

Reporting a vulnerability

If you believe you have found a security vulnerability in SmartDesk, write to info@smartdesk.help. Including the app version, operating system and steps to reproduce helps us look into it faster.

  • Please do not disclose details publicly until the issue is fixed.
  • While testing, do not access other users' data or run tests that disrupt the service.
  • To report SmartDesk being misused, for example in a scam, write to abuse@smartdesk.help.

Machine-readable contact: /.well-known/security.txt