KPass is the best KeePass password manager for Android. It supports reading and modification of KDBX 3 and 4 files. We have reached the time when a password can be the main value, more expensive than money, gold and brilliants. Let's say the password for a bank account gives you access to all the money at once, YouTube password — access to all subscribers eyes, and password for a cloud service is key to your private docs. Top advice: generate good complex passwords and change them from time to time. KPass offers secure storage for your passwords, addresses, bank card details, private notes and syncs them across all your devices – giving you faster access to your online accounts, apps and important information. FAQ. Q: Why database is successfully opened while I used unregistered finger to authenticate? A: Because you entered correct credentials (password and key file). Your database is protected by secret key. Biometric sensor is used to save and restore this key. So if your biometric authentication was failed, but you entered correct credentials, database will be opened, but secret key will not be saved. We doesn't see any security issue in such use case. Q: How can I make sure KPass does not steal my passwords or other information? A: KPass does not collect, store or send any user data. You can check it in application permissions section. KPass does not request network and storage access. Instead, it uses Storage Access Framework – modern and secure native Android way to get data from content providers such as file system, cloud services (Google Drive, Dropbox e.t.c.), FTP-clients or anything else. So, it is impossible for KPass to steal any password or send an analytics. Q: Why KPass is not open source? How can I make sure it is secure enough? A: KPass user interface is closed-source and intellectual property of product owner. This is main value of the application. UI side does not contain any secure-sensitive part of code. Engine is powered by open-source project gokeepasslib – https://github.com/tobischo/gokeepasslib. Q: Why KPass autofill doesn't work in Chrome (Edge, Opera, something else)? A: KPass uses standard Android autofill framework interface. It makes that all applications supporting this system framework automatically support autofill services. Unfortunately not every application follow this approach. So Google Chrome and all Chromium-based browsers do not. We stick to unification principle developing KPass and will never implement any workaround to support specific applications, especially if its developers doesn't want autofill to be available. If you are not happy with it, you can request your purchase refund using Google Play option or via mail to [email protected]. When Chromium team decides to support Android autofill you will be able to buy Premium again.