What the AvaDesk client sends
A factual description of the data that leaves a device, and where it goes.
Where it goes
Everything goes to desk.avahub.uk — the rendezvous server,
the relay and the console are all operated by AvaHub on infrastructure we
control. The client contacts no third party.
Sent automatically, without signing in
| What | When | Contains |
|---|---|---|
| Heartbeat | Every 15 seconds | Device ID, a per-install UUID, client version, and the IDs of any active sessions |
| Inventory | On change | Hostname, operating system and version, CPU, memory, logged-in username |
| Session records | On connect and disconnect | Which ID connected to which, and when. File transfers are recorded by name. |
Sent only when you sign in
Your username and password, in exchange for an access token; after that the token accompanies each request. Address book entries you create are stored on the server so they follow you between devices.
Not sent
- Screen contents, keystrokes and audio. A remote session is end-to-end encrypted between the two devices. When a direct connection is not possible the relay carries it, but the relay cannot read it.
- Files. File transfers go over the same encrypted session. Only their names appear in the session record.
- Any hardware fingerprint. Upstream RustDesk sends one
with its update check; AvaDesk does not, and its update check goes to
desk.avahub.ukrather than to RustDesk.
This page describes what the software does. It is not a legal privacy
policy, and it does not cover retention periods, lawful basis, or how to
exercise data-protection rights — those depend on how AvaHub operates
the service and should be written and reviewed accordingly.