RDesk is a web-based remote-desktop service: a lightweight agent runs on the machines you choose, and a web console lets you view and control them from your browser. This policy explains what information the service handles, why, and the choices you have.
01Information we collect
To provide remote-access functionality, RDesk processes:
- Account information — the username, display name, and password (stored only as a salted hash) you create to sign in to the web console.
- Agent & device data — for each machine running the agent: a generated Display ID and agent identifier, machine name, operating-system version, screen size and memory size, the logged-in username reported by the device, and online/last-seen status.
- Connection & session metadata — timestamps of connections, which agent a session targeted, session duration, and approximate transfer volume, used to show activity and keep sessions healthy.
- Network information — IP addresses of agents and viewers, used for routing, security, and abuse prevention.
- Cookies — an authentication cookie that keeps you signed in to the console. The website and the sign-up pages also use Google Analytics cookies (see below). No advertising or cross-site tracking cookies are used.
- Website visit statistics — when you browse rdesk.bd, the page we visit, the site or campaign that linked you here (for example a Facebook or Instagram post or ad), your device type, and how long the page stayed open are recorded with a random, anonymous browser identifier kept in your browser's local storage. They are used only to count visits and are never shared or used for advertising. rdesk.bd and the app.rdesk.bd sign-up pages also use Google Analytics to measure visits, clicks on buttons such as "Free signup", and completed sign-ups; Google processes that data under its own privacy policy. Google Analytics is not used inside the console or during remote sessions.
02Screen content and files
During an active, approved remote session the agent transmits screen images, keyboard/mouse input, clipboard text, and any files you explicitly transfer. This content is relayed in real time between the agent and your browser to make remote control work. RDesk does not record sessions or retain screen content or transferred files on the server beyond what is needed to deliver them for the active session.
03How the information is used
- Authenticate you and maintain your signed-in session.
- List your agents, show their status, and establish remote-control connections.
- Enforce the connection-approval and unattended-access settings you configure.
- Protect the service — detecting abuse, unauthorized access, and operational faults.
RDesk does not use your data for advertising or profiling, and does not sell it.
04Access control & consent
A remote machine is only accessible to accounts authorized in your RDesk account. Unless unattended access is deliberately enabled on that machine, an operator physically present must approve each incoming connection. When a session is active, the agent shows an on-screen indicator so anyone at the machine can see it is being accessed and can end the session.
05The Microsoft Store app (RDesk)
The RDesk app from the Microsoft Store is an attended-only version of the agent. It connects to app.rdesk.bd and differs from the full agent in these ways:
- Every connection needs your approval. It has no unattended access and no “don’t ask again” option. A request you do not answer is refused automatically.
- It runs only while you have it open. It installs no Windows service, does not start with Windows, and does not update itself (the Microsoft Store updates it).
- What it sends to the server — the device data described in section 01 (Display ID, agent identifier, machine name, operating-system version, screen and memory size, and online status), plus the screen, input, clipboard and file content described in section 02, only during a session you approved.
- What it keeps on your computer — its Display ID, a diagnostic log and the list of who connected, in
C:\ProgramData\RDesk QuickSupport. Nothing in that folder is uploaded. Uninstalling the app removes the program; delete that folder as well to remove the ID and history.
06Data retention
Account and agent records are kept for as long as your account and agents remain registered with RDesk. Connection metadata is retained to display activity and for security, and may be cleared periodically by RDesk. Screen content and in-transit file data are not persisted after a session ends.
07Security
Console traffic is served over encrypted HTTPS, and passwords are stored only as salted hashes. Access to a machine requires a valid account, and unattended access can be protected with a separate password. No system can be guaranteed perfectly secure; you are responsible for keeping your credentials and unattended passwords confidential and for who you authorize.
08Your choices
- Remove an agent at any time from the dashboard to stop that machine from being reachable.
- Leave unattended access disabled so every connection needs on-device approval.
- Uninstall the agent to remove it and its local identifiers from a machine.
- Request deletion of your account and associated records by writing to support@rdesk.bd.
09Children
RDesk is a tool for IT administration and is not directed to children under 13. It should be used only by those authorized to administer the machines involved.
10Changes to this policy
This policy may be updated as the service evolves. Material changes will be reflected here with a revised “last updated” date.
11Contact
Questions about this policy or your data should be sent to RDesk at support@rdesk.bd.