Indie apps for iOS, Mac & Android
MSafe
A password manager that can't phone home.
Your vault is stored on your phone, encrypted with AES-256-GCM, and there is no server to breach because MSafe doesn't operate one. No account to create. No email to verify. No cloud to sync to. The app doesn't even request network permission - it literally cannot connect to the internet.
Free stores up to 25 credentials. Pro removes the cap with a one-time purchase.
Features
AES-256-GCM
Every credential is authenticated and encrypted with a fresh random IV. The session key is derived from your master password via PBKDF2-SHA256 with 600,000 iterations.
No internet permission
MSafe doesn't declare android.permission.INTERNET. The OS will refuse to let it make any network call. The app physically cannot phone home.
Biometric unlock
Optional fingerprint unlock backed by an Android Keystore RSA-2048 key with user-authentication required on every use. Your master password always works as a fallback.
You control your backups
Export individual credentials or your full vault as a printable QR-code PDF, write entries to NFC tags, or save the whole vault as an encrypted .msafe file. All exports stay encrypted.
Password health
Live entropy meter on the password generator, plus a Password Health dashboard that flags weak passwords and reuses across services.
Android autofill
Set MSafe as your autofill provider and fill credentials into apps and browsers with one tap, gated by biometric or master password.
Material 3
Modern Compose UI with light and dark themes that follow your system setting. Built with Jetpack Compose and Hilt.
Ten-strike wipe
Ten consecutive wrong master-password attempts wipe the vault. There is no recovery email and no back door - your master password is the only key.
What MSafe will never do
Request network access. Create an account or collect your email. Embed analytics, crash reporters, or tracking SDKs. Show ads. Upload your vault to a server, because there are no servers. The only way your vault leaves your phone is if you explicitly export it - and even the exports are encrypted.
Permissions
Camera
Only when you scan a QR code to import.
NFC
Only when you read or write a tag.
Biometric
Only if you turn on fingerprint unlock.
Autofill
Only if you enable it in Android system settings.
System requirements
Android 11 (API level 30) or later. Optional features need the matching hardware: NFC, camera, and a fingerprint sensor.