Rustty
en
español es english en

rustty --privacy

Last reviewed: 5 June 2026. Everything on this page can be verified by reading the code: github.com/Aleixenandros/Rustty.

summary // the essentials, in six lines

no data collection

Rustty collects no personal data and sends no telemetry. There are no accounts of ours, no sign-up, and no contact with Rustty servers.

all on your machine

Profiles, passwords and files stay on your machine, on your own remote servers when you open a session, or with the sync provider you choose.

encrypted sync

Optional and end-to-end: Google Drive, WebDAV, iCloud Drive or a local folder only ever receive an encrypted blob (rustty-sync.bin).

The only network connections Rustty initiates are:

  1. to the servers you specify for your sessions;
  2. to the sync backend, if you enable it;
  3. to the Tauri update checker, if you enable it;
  4. to Apple's or Microsoft's CAs when the operating system validates the binary signature as it runs.

Put another way: this program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it.

controller // who processes the data

Rustty is an open source project developed by Alejandro Soriano. The application is local-first: it runs entirely on your machine and there is no associated cloud service.

For any question about this policy, open an issue on the repository: github.com/Aleixenandros/Rustty/issues.

local data // what the app writes, and where

To work, Rustty creates and reads the following on your own machine:

  • Connection profiles (profiles.json): name, host, port, user, authentication type, key path, folder and profile options. No passwords.
  • Preferences: theme, typeface, shortcuts, language and window size or position, in the WebView localStorage.
  • Passwords (optional): if you choose to store them, they go to the system keyring under the rustty service — KWallet or GNOME Keyring on Linux, Keychain on macOS, Credential Manager on Windows. Rustty never stores passwords in plain text in its own files.
  • KeePass databases (optional): a referenced .kdbx is decrypted in memory only while the session is active, and locks when the app closes.
  • Backup configuration (optional): sync_config.json and sync_state.json hold the chosen backend and sync metadata. The master passphrase, the WebDAV password and the Google Drive OAuth token live in the keyring.
  • Encrypted backups (optional): .rustty-sync.bin files hold profiles, preferences, themes and shortcuts encrypted with your passphrase. They exclude the keyring, the unlocked KeePass database, and local paths such as keepassPath.
  • Local logs and WebView cache: used by Tauri for diagnostics, and transmitted to no one.

The exact paths, per system:

Linux    ~/.local/share/com.rustty.app/
macOS    ~/Library/Application Support/com.rustty.app/
Windows  %APPDATA%\com.rustty.app\

network // where it connects, and why

By design, Rustty only connects to the following, and always on an explicit action of yours:

  • Your SSH, SFTP and RDP servers. Pressing Connect opens the encrypted connection to the host in your profile. You choose the destination and the ciphers.
  • Host verification (TOFU): the fingerprint check is local, against your own known_hosts. No third party is involved.
  • Google Drive (optional): if you connect it, Rustty opens OAuth in your browser, uses a local callback and uploads or downloads rustty-sync.bin from appDataFolder. The refresh token stays in the keyring.
  • WebDAV (optional): GET, PUT and MKCOL requests against the URL you provide. The password is stored in the keyring.
  • iCloud Drive or a local/NAS folder (optional): Rustty writes the encrypted blob into a local folder. If that folder belongs to iCloud, Syncthing, OneDrive or Dropbox, the onward sync is done by that software.
  • Tauri updater (optional): on Windows, macOS and AppImage it may fetch releases/latest/download/latest.json from GitHub, download the new version and verify its signature before installing. It only runs if you press Check for updates or enable the check on startup. None of your data is sent: it is a download.
  • System signature validation: macOS and Windows may contact Gatekeeper, Notary or SmartScreen the first time you run the binary. That is operating system behaviour, not Rustty.

There is no analytics, no telemetry, no automatic crash reporting and no servers of ours. Were any of those ever added, it would be optional and opt-in, and documented here.

third parties // what you send to remote servers

When you connect to an SSH, SFTP or RDP server, the data in flight — credentials, commands and files — is processed by that remote server. Rustty acts only as a client: it does not intercept, store or analyse that traffic outside the session itself.

Each server's privacy policy is up to its administrator. Rustty has no control over, and no responsibility for, what those servers keep.

If you enable sync, the provider you choose handles transport and storage of the encrypted blob. Rustty sends it no keyring passwords, no unlocked KeePass databases and no decrypted profile content.

rustty.es // this very site

This site is static. It uses no cookies, installs no tracking SDKs and loads no pixels or analytics of any kind. It loads no third-party resources either: the typeface, the CSS, the JavaScript and the images are all served from our own server.

It queries the public GitHub API (api.github.com/repos/Aleixenandros/Rustty/releases/latest) at most once per browser session, to show the version number and build the download links. Your browser makes that request, and it goes to GitHub alone.

The server hosting rustty.es keeps standard Apache access logs (IP, user-agent, requested resource and response code) for at most 30 days, for operations and diagnostics. They are not cross-referenced with any other source, not shared with third parties, and deleted automatically.

your rights // and how to exercise them

Since Rustty stores no personal data on any server of the controller's, GDPR rights are exercised directly on your own machine:

  • Access and portability: export profiles, preferences and encrypted backups from Preferences → Backups.
  • Rectification: edit the profiles in the application itself.
  • Erasure: delete the data directory shown above, or uninstall the application. For stored passwords, remove the rustty service entries from the system keyring.

Minors

Rustty is not aimed at children under 14. The application collects no information from any user, so it processes no data from minors under any circumstances.

Changes to this policy

If the policy changes — say, when an optional feature that talks to an external service is added — this page is updated and the change noted in the GitHub releases. The date above always reflects the latest revision.

Licence and sovereignty

Rustty is distributed under the Apache-2.0 licence. Its code is public and auditable: you can verify everything described here by reading it. How the binaries are signed, and how to check a download is genuine, is in the code signing policy.

Spotted something that doesn't match how the application behaves? Open an issue. This policy is reviewed on any legitimate report.