Short answers in plain words. Search, pick a topic, or just scroll.
Jump to a topic
Nothing here yet for that topic.
An app that remembers your logins for you. You remember one master password; it keeps every other password locked away, makes strong ones for you and fills them in, so each account can have its own.
A password manager for Android that keeps your passwords in an encrypted file on your phone. No account, no server of ours, no ads. It needs Android 8.0 or newer.
Chrome is far better than reusing one password. A dedicated manager adds a vault you can lock separately, works the same in every app and browser, and isn't tied to one company's account. Notes apps aren't encrypted and fill nothing in.
Your passwords sit in one encrypted file that only your master password (and key file, if you use one) opens, and the app can't go online, so nothing can leave your phone. Having everything in one place is a fair trade-off if your master password is strong and you keep a backup.
In a vault file on your phone, in the place you pick, such as phone storage or Google Drive. It's encrypted either way. Native Creds has no server, so no copy is kept anywhere you didn't choose. Uninstalling the app doesn't delete your vault file.
No account, ever, and no internet. The app has no internet permission, so it can't go online even if it wanted to. If you want sync, your Drive app does the uploading, not Native Creds.
One independent developer (Manideep's Crafty Apps). I can't see your passwords: there's no server, no analytics and no crash reporting. There are no ads or trackers, and no subscription or in-app purchases in this version. In Drive, Google stores only the encrypted file.
Not at the moment: the code isn't published and there has been no independent security audit. What protects you instead: the vault is a standard, open file format, and with no internet permission Android itself stops the app sending data off your phone.
It can't be recovered, by anyone, including me: there's no back door. Keep a written copy somewhere safe. If your fingerprint or screen lock still opens the vault, copy your logins into a new vault with a new master password.
Whoever finds it still needs your master password to open the vault. Lock or wipe the phone with Google's find-your-device tools, then open your vault from Drive or your backup on a new phone. If the only copy was on the lost phone, it's gone, so keep a backup (how).
Leave Use as my default vault on (why).
Three steps, once. After that, signing in shows only your phone's unlock prompt.
You still tap Unlock, then your login. Keep your master password: a new phone needs it.
Long beats clever: five or six random words you can remember, used nowhere else. Avoid names, dates and song lyrics. A strength meter shows as you type it.
No. A strong master password alone is fine. A key file is an extra file that works like a physical key: stronger, but lose it and you lose the vault. Keep it away from the vault file.
It's the vault autofill opens and where new logins are saved. Without one, Native Creds has to ask which file to use every time. You can keep several vaults under My vaults and change the default in Settings.
Yes, from a CSV export: Google Password Manager, Chrome, Edge, Firefox, Safari, Bitwarden, LastPass, Dashlane, NordPass and Proton Pass. You check duplicates before anything is added. Passkeys can't be imported, and 1Password's own file isn't supported yet.
A CSV holds passwords as plain text, so delete it afterwards. The app offers to.
Both phones need access to that file. Changes are combined automatically.
Still stuck? Settings > Autofill setup & diagnostics has an activity log.
Generally safer than typing: it matches the app or site address, so a lookalike phishing page gets no suggestion, and nothing sits on the clipboard. Turn autofill on only for a service you trust, because Android shows it the sign-in screens you use. Native Creds always makes you unlock and tap first.
No. With a default vault and fingerprint or screen lock on, you tap your phone's Unlock bar, use your unlock, then tap your login. No Native Creds screen shows. If the unlock fails or there's no default vault, the app's own unlock screen appears instead.
Yes, once Native Creds is your autofill service. After you sign in somewhere new, Android asks whether to save it to Native Creds; nothing is saved unless you tap Save. A changed password updates the entry, and the old one stays in its history.
Yes. Switch it on for each vault when you create it, or later from its ⋮ menu (Turn on quick unlock). Your master password always works as a backup, and you can turn it off any time (how it works).
It stands in for your master password on that phone, so it's only as strong as your phone's lock: anyone who can unlock your phone can open the vault. Native Creds asks Android for a strong fingerprint or your screen lock (PIN, pattern or password).
Yes. On the site's 2FA setup page choose can't scan the code and copy the key. In the entry tap Set up two-factor code and paste it; the 6-digit code shows with a countdown. There's no QR scanner yet.
After autofill, the code is copied ready to paste (you can switch that off in Settings).
It's convenient but a trade-off: whoever opens the vault gets both. For most accounts that's still far better than no second step. For your email or bank, some people prefer a separate authenticator app or security key. Your call.
Yes. In an entry, use the generator next to the password field: choose a length (8 to 64) and which kinds of characters to include. Passwords are made on your phone.
Yes: recovery codes, a scan, a key file. They're stored encrypted inside the vault. Files over 5 MB trigger a warning and over 20 MB are refused. Saving one out makes an ordinary, unprotected copy, so the app warns you first.
Make folders from a vault's ⋮ menu, search from the search box and sort from ⋮ > Sort by. Touch and hold to select several, then move, copy or delete. Deleting is permanent: there's no recycle bin or undo, so it asks first.
The moment you leave the app: pressing home, switching apps or turning the screen off. There's no timer to set. Opening a web link from the app, like these help pages, counts as leaving too.
Screenshots, screen recording and the recent-apps preview are blocked on purpose, so a passing glance or a screen-sharing app can't capture your vault.
Copied passwords and codes clear after 30 seconds, even if you've switched apps. Anything else you copy in that time is cleared too.
It doesn't: your Drive app does. Native Creds reads and writes the vault file through Android's file picker, and Drive moves it to the cloud. Google Drive is the one tested on real phones; others like Dropbox should work the same way but aren't verified.
To fetch the newest copy at once, use Sync now in the ⋮ menu, or pull down on the list.
Native Creds re-reads the file before saving and combines both versions. New logins from either phone are kept. If the same login was edited on both, the newer edit wins and the older one stays in that login's history. You'll see “Merged changes made on another device”.
Your vault is one file, so a backup is a copy of it: use Save a copy… in its ⋮ menu, or copy the file anywhere (and any key file, somewhere else).
On a new phone, tap Open an existing vault, pick the file and enter your master password, then turn autofill and device unlock on again.
Native Creds refused to overwrite the file because something looked unsafe, for example it was only half-synced. Nothing was overwritten and your changes are still in the app. Keep it open and tap Try again; if it keeps failing, tap Save a copy…. Don't close the app first.
Yes, and you won't see an error. When the vault is in Google Drive, the Drive app keeps your change on the phone and uploads it once you're back online. Native Creds has no internet access, so it can't tell the difference and shows no message.
Until the upload finishes, other phones won't have the change. To check, open the Drive app and look for the file's pending upload, or use Sync now once you're back online. If you edit the same login on another phone in the meantime, the two versions are combined (how).
KeePass is a long-established password manager for computers whose file format is public. Many apps read and write it (KeePassXC, KeePassDX, Strongbox, KeePassium), so you're never stuck with one app. Native Creds is independent and not affiliated with the KeePass project.
Yes. Native Creds opens KeePass files protected by a password, a key file or both. Tap Open an existing vault, or choose Native Creds from your file manager, Drive or an email attachment. Vaults from KeePassXC, Strongbox and KeePassium were tested both ways.
Yes, with another KeePass app: KeePassXC on Windows, Mac or Linux, or Strongbox or KeePassium on iPhone. Keep the vault in Drive and open the same file there. Native Creds itself is Android only.
Not yet. It can't create, store or use them, and passkeys aren't part of the CSV exports used for import. Passkeys saved in Google or on your phone keep working as before. Planned for after launch, with no date promised.
Email ManideepsCraftyApps+nativecreds@gmail.com with what you did, what happened, your phone model, Android version and app version. The logs in Settings are safe to share (no passwords or usernames). Never send your vault file, master password or a screenshot showing passwords.
Found a bug, want a feature, or did not find your answer? I would like to hear from you:
Made by Manideep. Small apps, built carefully, one piece at a time.
Native Creds · Manideep's Crafty Apps. Not affiliated with the KeePass project.