VERO DATA AND ENCRYPTION
Privacy, plainly.
Product privacy overview
Vault contents stay client-side encrypted
The encrypted vault contains saved hosts and authentication data, private keys in keychains, known SSH fingerprints, tags, custom terminal themes, and preferences. Vero derives a key from the vault password using Argon2id (64 MiB memory and three iterations) and encrypts data with XChaCha20-Poly1305 using a fresh salt and nonce when written.
Optional account and synchronization
Vero works in local mode without an account. If you sign in and enable sync, the service stores and transfers the encrypted vault envelope rather than plaintext hosts or private keys. The account password authenticates to the service; it does not unlock the vault. The vault password is not sent to the service. If the vault password is lost, the encrypted vault cannot be recovered.
Credentials and SSH identity
Refresh credentials are stored using secure storage provided by the operating system, including Windows Credential Manager, macOS Keychain, Linux Secret Service, or Android Keystore. Vero checks SSH host-key fingerprints and stops a connection when a trusted fingerprint changes until you review it.
Website and contact
This notice covers Vero product data practices described in the product overview. For a privacy question, contact privacy@runvero.app. Do not send passwords, private keys, or your vault password in a support request.
Contact
Privacy questions: privacy@vero.app.