Security and privacy

RemoteDeck connects straight from your PC to your servers. Nothing about your servers, passwords or sessions goes to remotedeck.net, and there are no accounts, analytics or telemetry.

Where your sign-ins are kept

• Passwords you save are stored in Windows Credential Manager, protected by your Windows account. They are never written into RemoteDeck's own files.
• Your server list and settings are in %APPDATA%\RemoteDeck, without passwords.
• Azure Cloud Shell sign-ins are kept per connection, encrypted with Windows' data protection for your Windows account, so only you on that PC can use them. Sign Out on the connection removes them.
• Web page passwords you save with a web connection are in Windows Credential Manager too. Cookies and other browsing data stay in RemoteDeck's own browser storage on your PC, separate from Microsoft Edge.

How passwords are used

• SSH and SFTP: the saved password is handed to ssh through its own password request, never typed into the terminal. It only answers the login prompt of the exact user and server it was saved for, so a sudo prompt, a program on the server or a jump host on the way can't receive it.
• Telnet: the username and password are typed only at the login prompts in the first 30 seconds.
• FTP: credentials are passed to Windows' curl privately, not on its command line where other programs could see them.
• Web pages: a saved password is filled into a login form only when the page is on exactly the connection's own address (same https/http, host name and port) — never after a redirect to another site, into a look-alike address, or into a frame inside the page. It goes into the page as plain data, never as code. Auto sign-in presses Login only once per opening, so a wrong password can't loop. A sign-in you type is offered for saving only on that same site, and is kept in memory only while the offer is showing.
• Copy Password keeps the password on the clipboard for 30 seconds and keeps it out of Windows' clipboard history and cloud clipboard.

Protection against hostile servers

• File names sent by a server are cleaned before anything is saved, so a download can't land outside the folder you chose, also inside downloaded folders.
• File names sent by a server are cleaned before anything is saved on your PC, and every download is checked to land inside the folder you chose, so a hostile server can't place files elsewhere. Deleting on your PC sends to the Recycle Bin; Synchronize deletes nothing unless you tick it, and asks once more first.
• Web pages may only show web addresses, and windows they open stay under the same rules. Certificates Windows doesn't trust are shown to you with their fingerprint, and only the exact certificate you accept is remembered.
• Values you type for cloud connections reach the terminal only as settings, never as commands.

Moving to another PC

File → Export Settings writes your servers and settings to one file. Passwords are included only if you ask, and then encrypted with a password you choose (AES-256-GCM, with a key derived through 600,000 rounds of PBKDF2-SHA256). The file still lists server names, addresses and user names, so keep it private.

Updates you can trust

Every release is described in a small file that is digitally signed with RemoteDeck's signing key. The private half of that key is kept in a locked-down Azure Key Vault and is read only by the automated release process at the moment it publishes a release. It is never part of the app or the website, which carry only the public half used to check signatures. RemoteDeck installs an update only if that signature is valid, the file's SHA-256 checksum matches, and the new program carries the expected build number. A changed or substituted download is refused.

Each version is built and tested automatically before it is published: dozens of checks run the real app against real SSH, Remote Desktop, FTP and web servers on a test machine.

What remotedeck.net sees

When RemoteDeck checks for updates it downloads one small file. That request, like any visit to a website, shows your IP address to Cloudflare, which sits in front of remotedeck.net, and to the server that hosts the site. It includes nothing else: no identifier, no server names, no usage information. The website itself uses no cookies, scripts, analytics or content from other sites.

Report a security problem

Write to support@remotedeck.net. Please include the RemoteDeck build number (Help → About) and how to reproduce the problem.