What encryption is being used?

SecretSafe uses AES 256 bit encryption as well as PBKDF2 to secure your data.

AES is a standard in cryptography and used by the US government and other government agencies around the world for protecting top secret data. With proper implementation and a strong encryption key (your master password), AES is considered unbreakable.

PBKDF2 SHA-256 is used to derive the encryption key from your master password. This key is then salted and hashed. The default iteration count used with PBKDF2 is 100,001 iterations on the client (this client-side iteration count is configurable from your account settings), and then an additional 100,000 iterations when stored on our servers (for a total of 200,001 iterations by default).

SecretSafe does not write any cryptographic code. SecretSafe only invokes crypto from popular and reputable crypto libraries that are written and maintained by cryptography experts. The following crypto libraries are used:

• JavaScript (web, browser extension, desktop, and CLI safes)
  • Web Crypto
  • Node.js Crypto
  • Forge
• C# (mobile safe)
  • CommonCrypto (iOS, Apple)
  • Javax.Crypto (Android, Oracle)
  • BouncyCastle (Android)

SecretSafe always encrypts and/or hashes your data on your local device before it is ever sent to the cloud servers for syncing. The SecretSafe servers are only used for storing encrypted data. It is not possible to get your unencrypted data from the SecretSafe cloud servers.