Privacy policy

Last updated: 12 November 2026

LinkDesk lets one PC (or phone) see and control another. This page explains what it keeps, what has to travel over the internet for that to work, and who handles it. There is no account, and the app has no analytics, advertising or tracking.

What stays on your device

Your settings, your ID, your address book of computers, the connection log, chat and files you receive are kept on your device (on Windows in your user's application data folder). A personal password is kept only as a scrambled hash, protected by Windows. None of this is sent to us.

Your sessions

A session's picture, sound, input, chat, clipboard and files travel end-to-end encrypted between the two devices (WebRTC: DTLS and SRTP). The password is checked without being sent. We don't run, see or record your sessions. To connect, LinkDesk uses these services, none of which can read a session:

• Finding the other PC: each LinkDesk registers its ID on the public PeerJS server (0.peerjs.com), which introduces the two devices. That server sees the ID and the device's internet address. You can use your own server instead (Settings → Network).
• Finding a direct path: STUN servers from Cloudflare and Google tell each device its own public internet address.
• Hard networks: when two networks block a direct connection, the encrypted session passes through a relay (ExpressTURN's free service, or your own). The relay passes encrypted data along and can't read it.
• Same network without internet: devices on the same network can find each other directly, without any of the above.

Each of these services has its own policy and may keep short-lived technical logs such as internet addresses.

Licences and updates

• Withdrawn licence keys: LinkDesk downloads the public list of withdrawn keys from our small update server (hosted by Cloudflare) about hourly and when Settings opens. That request sends nothing about you.
• Updates (licensed copies): at start and every few hours LinkDesk asks the same server for a newer version. So that only buyers get updates, that request shows your licence key, which holds the name you gave when you bought it, your PC's and phone's codes and its end date, not your devices' identity. The server doesn't store it.
• Your partner sees your licence: when you connect, your PC shows its key (or its trial's end) to the PC you connect to, so that PC can apply the free version's time limit fairly.

Buying a licence

LinkDesk shows a short PC code (and the phone app a phone code), made from a one-way scramble of the device's ID, so the ID itself can't be worked out from it. We keep the details below only to make your licence key, to help you with it later, to renew it, and to withdraw a key that was shared or refunded. They're used for nothing else, and never shared or sold. To have them removed, email us.

• On the payment page: payments are handled by Razorpay. Your card, UPI or bank details go to Razorpay, under Razorpay's own privacy policy; we never see them. The page asks for your name, email, phone number and your PC and phone codes. Razorpay passes those, with the amount, how you paid and the payment's reference, to our small order server (run on Cloudflare), so we can make your key.
• Paying by UPI directly: you send us your codes with your name, your contact (WhatsApp or email) and your payment reference. The payment goes through your own UPI app.

Children

LinkDesk isn't aimed at children under 13 and doesn't knowingly collect anything from them.

Changes and contact

If this policy changes, the new version is published on this page with a new date. Questions, or a request to remove your purchase details: kogantiaditya1990@gmail.com.