Security Architecture

Security by Design.

We believe that a security app shouldn't compromise on privacy. That's why SafeKey is built offline-first with military-grade encryption.

Offline-First Architecture

The most secure data is the data that never leaves your device. SafeKey does not request the android.permission.INTERNET permission. It is physically impossible for the app to transmit your data to the internet.

Unlike cloud-synced authenticators, your TOTP secrets are generated and stored strictly on your local hardware. You have complete sovereignty over your data.

Android Keystore & SQLCipher

Your accounts are stored in a local SQLite database that is fully encrypted using SQLCipher (AES-256-bit encryption).

The encryption key for the database is securely generated and stored in the Android Keystore system. This means the key material is protected by your device's trusted execution environment (TEE) or Secure Element (SE), making it exceptionally difficult to extract even on compromised devices.

Biometric Authentication

To prevent unauthorized physical access to your codes, SafeKey can be locked behind your device's biometric authentication (fingerprint, face unlock, or device pin). This adds an essential layer of security if you hand your unlocked phone to someone else.

How we compare

SafeKey
  • 100% Offline (No Internet)
  • Open Source
  • Zero Analytics/Trackers
  • Encrypted Database
  • Manual Encrypted Backups
Typical Cloud Authenticators
  • Cloud Synced
  • Closed Source
  • Contains Analytics/Crashlytics
  • Vulnerable to Account Hacks
  • Automatic Cloud Backups