Privacy policy
Effective: October 8, 2026
Native Creds is an offline password manager for Android, made by Manideep's Crafty Apps (“I”, “me”). Native Creds does not collect, transmit or share any of your data. I never receive anything from the app. There is no account, no server, no ads and no analytics, and the app does not even have Android's internet permission.
Native Creds has no user accounts and I do not run any server for it. The app does not request Android's internet permission, so it cannot open network connections. It contains no advertising, no analytics, no crash reporting and no third-party tracking code.
Your passwords and other entries are stored in a vault file in the KeePass (KDBX) format, encrypted with the master password and/or key file that you choose. Native Creds reads and writes that file only in the location you pick through Android's file picker. I have no access to your vault, your master password or your key file, and I cannot recover them for you.
You may choose to store the vault file in a storage app on your phone such as Google Drive. In that case that app, not Native Creds, uploads and downloads the encrypted file, under that provider's own terms and privacy policy. Native Creds only reads and writes the file through Android.
Everything below stays in Native Creds' private app storage on your phone. It is excluded from Android cloud backup and device-to-device transfer, and is never sent anywhere.
If you choose Native Creds as your Android autofill service, Android gives Native Creds the structure of the screen you are signing in on (such as field types and the app or website name) so Native Creds can find the matching entry in your vault. This is processed on your device only, is not stored (other than the optional log above) and is never transmitted. When you accept Android's “Save” prompt, the login is written into your vault file. For sign-ins that use two pages, Native Creds may remember which entry you picked for a few minutes in memory only.
When you copy a username, a password or a two-factor code, it is placed on the Android clipboard, marked as sensitive (Android 13 and later hide it from the clipboard preview), and cleared after 30 seconds, also when you have switched to another app, or at once when the screen turns off. To keep that 30-second timer running after you leave Native Creds, the app runs a short background task for those 30 seconds (Android's “short service” foreground service); it does nothing else. While Native Creds is behind another app Android does not let it look at the clipboard, so if you copy something else in those 30 seconds it is cleared too; while Native Creds is in front, something else you copied is left alone. If Android stops Native Creds before the timer ends, the clipboard is cleared the next time you open Native Creds, and Android 13 and later also clear the clipboard by themselves after about an hour.
If you leave the option on, filling a login that has a two-factor code through autofill also copies the current code to the clipboard (cleared the same way) so you can paste it on the next page. You can turn this off in Settings.
While something is on the clipboard, other software on your device, for example your keyboard or a clipboard-sync feature, may be able to read it.
When you open a vault file from another app (“Open with Native Creds” in a file manager, Drive or a mail app), Native Creds reads that file with the permission that app gives it, on your device only. If that permission is read-only or temporary, Native Creds says so and does not remember the file.
Files you attach to an entry are stored encrypted inside your vault file. If you use “Save to…” on an attachment, Native Creds writes an ordinary, unencrypted copy to the place you choose; that copy is then outside the vault and outside Native Creds' control.
If you store a two-factor (TOTP) key in an entry, it is kept inside your encrypted vault file like a password. The codes are calculated on your device from that key and the clock; nothing is sent anywhere.
When you import a CSV export from another password manager, Native Creds reads the file on your device and writes the entries into your vault. The CSV file is not copied or sent anywhere; Native Creds offers to delete it afterwards.
Native Creds blocks screenshots, screen recording and the recent-apps preview of its screens.
I do not share your data with anyone, because I never have it.
All data listed above stays on your device until you remove it. Clearing Native Creds' storage in Android settings or uninstalling the app deletes all of it. Your vault files are ordinary files that you own: they stay where you saved them until you delete them yourself. There is no account and no server-side data to delete.
Vault files use the KDBX format's encryption. Device unlock relies on the Android Keystore. No method is perfectly secure; keeping your device locked and up to date, and keeping a backup of your vault file, remain your responsibility.
Native Creds is a general-purpose tool not directed at children, and it collects no personal information from anyone.
If the app's behaviour changes, this policy will be updated and the effective date changed.
Manideep's Crafty Apps · questions about this policy or how Native Creds handles data: