Where Does Mauth Store Tokens?
Mauth keeps TOTP secrets on-device with QR export on Android. Exact database filenames stay unpublished.
Last updated
Mauth is a young open-source authenticator with exports ahead of encryption. QR codes carry tokens out singly or batched with PIN gates where set. Package identity verifies across free-software catalogs.
Database filenames stay unpublished with encryption unchecked on the roadmap. Custom icons tuck into internal storage on recent builds. Quote exports and package while leaving storage internals unquoted.
Where Mauth stores this, by platform
/data/data/com.xinto.mauth
Private storage for the verified open-source package with unpublished database filenames. QR exports carry tokens with PIN gates. No cloud sync exists.
Frequently asked questions
How do I back up Mauth tokens?
Export QR codes singly or batched in authenticator format through the app menu with PIN gates where enabled. Custom icons copy into internal storage on recent builds. No cloud sync exists to lean on.
Which Mauth app is this?
Through the verified package ID across F-Droid and GitHub with Play testing beside it. Biometrics and PIN guard the app while encryption stays roadmap. Unrelated Mauth strings online belong elsewhere.
Where is the Mauth database file?
It stays unpublished. README confirms biometrics and PIN with encrypted storage still unchecked. Exact database filenames have no source, so this post quotes package plus export flows.
Notice an outdated path? Let us know.