Vaulted Desktop. Last updated 18 September 2026.
Vaulted Desktop (“Vaulted”) is a desktop client for HashiCorp Vault, published by IronMade.
Vaulted has no backend. There is no account, no sign-up, and no service operated by the publisher for the app to talk to. It connects only to the Vault servers you configure and, for browser-based sign-in, to the identity provider your organisation has configured on those servers.
What the publisher collects
Nothing. No telemetry, no analytics, no crash reporting, no usage statistics, no advertising identifiers. The application contains no analytics SDK of any kind, and no data of any description is transmitted to IronMade.
What Vaulted stores, and where
Everything stays on your computer.
Server profiles — address, namespace, TLS settings, chosen auth method
Where: a configuration file in your user profile
Notes: never contains a token or any secret
Vault token
Where: Windows Credential Manager (macOS Keychain on macOS)
Notes: only if you tick “Remember in OS keychain”; deleted when you choose “Log out & forget token” or delete the profile
Secret values you view
Where: process memory only
Notes: wiped when the session ends, locks, or the app closes. Never written to disk
Search index
Where: process memory only
Notes: never written to disk; discarded when you sign out
Preferences — appearance, idle-lock timeout
Where: the same local configuration file
Notes: contains no personal data
Your licence
Where: held by the Microsoft Store (Windows) or the Mac App Store (macOS App Store build), not by Vaulted
Notes: Vaulted stores no licence key, serial, receipt or trial clock of its own. The macOS build downloaded directly is free and has no licence at all
Uninstalling Vaulted removes the application. Remove a remembered token beforehand with Log out & forget token, or delete the entry from Windows Credential Manager afterwards.
Where Vaulted connects
- The Vault servers you configure. Your infrastructure, addressed by you. Vaulted sends your credentials or token there to authenticate, and requests the secrets you ask for. Connections use TLS with certificate verification on by default.
- Your identity provider, if you sign in with OIDC/SSO. Your system browser
opens the provider your Vault server nominates, and Vaulted listens briefly on a local
address (
127.0.0.1) to receive the redirect back. That listener accepts only that one response and is not reachable from outside your computer. - The update service for your platform. On Windows, updates are delivered by the Microsoft Store under its own terms. On macOS, Vaulted checks a public GitHub release feed. Update checks reveal nothing about you beyond what any download request reveals — they carry no identifier and no information about your servers or secrets.
- Your platform’s store licence service. Vaulted is sold as a 15-day trial followed by a one-time purchase, and it asks the store whether this copy is trialling, purchased, or expired. On Windows that question goes to Microsoft through the Windows Store licence API; on the Mac App Store build it goes to Apple through StoreKit, which also handles starting the free trial (a $0 in-app purchase), buying, and restoring a purchase under your Apple ID. Either way it goes to the platform under their terms, and never to IronMade — we receive no notification that you installed it, tried it, or bought it beyond the sales figures the stores report to any publisher. Buying opens the store’s own purchase flow; Vaulted never sees your payment details, and there is no account to create with us. The macOS build downloaded directly from GitHub Releases is free and makes no licence request at all.
There are no other network connections.
Secret material
Vaulted is a tool for handling credentials, so to be explicit: the secrets you read through Vaulted travel only between your computer and the Vault servers you configured. They are never sent to IronMade, never written to disk by Vaulted, and never included in any report.
Two consequences worth knowing:
- Copying a secret puts it on your system clipboard. Vaulted clears it
automatically after 30 seconds if it has not been replaced, but operating system clipboard
history features (Windows
Win+V, third-party clipboard managers) may retain it beyond that. That is outside Vaulted’s control. - Deep content search reads every secret in a mount to build a searchable index in memory. This produces one entry per secret in your Vault server’s own audit log — kept by your organisation, not by us. Vaulted asks for explicit confirmation before doing it.
Children
Vaulted is a tool for infrastructure administrators and is not directed at children.
Changes
Material changes to this policy will be published here with an updated date. Because Vaulted collects nothing, changes are expected to be rare.
Contact
Questions about privacy, or anything else: support@ironmade.site.
You can also open an issue at github.com/WhisKeySwitch/vaulted-releases/issues, but GitHub issues are public. Email is the right channel for anything you would rather not have indexed, and in either case please do not include secrets, tokens or server addresses.
