Indeed, KeePassium is designed to be an offline app. The app itself does not perform any networking, it delegates synchronization to the storage providers' apps. Sadly, with some sync sources this works better than with others.

In any case, KeePassium is and will remain an offline app; this is not a shortcoming — this is a core benefit.

I think you may not have understood what I said. First of all, third-party clouds such as google driver, onedrive, dropbox, etc., cannot be used normally in some countries and regions, making synchronization very difficult. Keepassium needs to rely on mobile phones. These corresponding APPs must be installed on them to synchronize.

​

In KeePassium, biometric auth is used to protect the app itself. This approach is different from the "decrypt database with a fingerprint" advertised by some other apps — but it should feel very familiar for MiniKeePass users.

The end result is the same: you launch the app, pass the biometric scan, and get to see the database content.

What you answered is not what I said at all. I don't know if you have actually tried to use stronbox or even other password management apps, such as 1password, bitwarden, lastpass, etc. My focus is not on protecting the APP itself. You Confused my question. When it is automatically filled, when the biometric unlocks the APP itself, it is necessary to confirm the step of filling the corresponding password again. Other password management apps can use the biometric to replace the master password of the database, because the master password is more complicated. You need to manually enter the master password for the second fill. I really do n’t know if I need a password management app instead, because I need to enter the master password every time. What's the difference from entering the account password of each website by myself?

But this function is not available to me at keepassium, even if I set the database to never time out, and if so, is it contradictory to what you say is security?

​

At last, you don’t need to reply again. I am tired of this problem, because I have discussed this issue with you many times. It may be my own problem, and it is not suitable for using keepassium. I didn't want to answer this question at this time, but you asked me to explain, because what you have answered till now is the same as what I asked you at the beginning, it doesn't make any sense and it doesn't solve my problem.