@konrad_bujak I do not trust the privacy of web browsers, so I don't trust that they don't share the passwords generated. Most password generators and keepers still track user data. So, I created BCS Lock. It doesn't have any tracking or recording capabilities. I originally developed it for my personal use, then I decided there was no reason not to make it open source and publish it.

If you do not trust your browser, why not to code a browser instead of password generator? I still do not see the use-case for this. I generate random password, now I still need to keep it somewhere. In case of password managers, I have both.

@konrad_bujak The issue is that no matter how secure your browser is, it is still vulnerable. That is why I do not trust any browser to store my passwords, and I do not trust the password managers either. They store their data online, which automatically makes it vulnerable. Any data or application that is accessible from the internet, is at risk of being breached. Thus, I use local files and software for most.

Yes, local file called `passwords.txt` is best :p Ignoring the competition is bad idea, especially that what you mentioned is not a thing for a while already. You can selfhost password managers, which either way store data only locally with E2E for sync. However, I admire you for developing it and sharing your product on Products Hunt. Good luck!