Debian keyring prompt on VM bootup - disable?

I use Debian for a few things, like a standalone for Signal, etc. Also for some dvms.

The keyring prompt (two or three of them) on boot (and during template update) is deeply irritating.

I see here that someone has suggested removing the from a debian-dvm template.

Okay, but what are the safety implications of this?

Can passwords be saved in a browser after this? Normally I use Keepasxc from Vault (banking, shopping sites) but for some things like forums (i.e. low risk), I let the browser handle the login details, either in dvm or persistent qubes.

In this convenience:security tradeoff, I am leaning to convenience - but is it too much?

Is removing gnome-keyring removing the Debian system’s ability - for all applications - to manage passwords securely?

What if you are just using one login for one dvm?

And why doesn’t Fedora do this? Am I less safe - or more - using a browser/app’s ability to remember login/password on Fedora

I am aware that the devs have given us Vault for a reason, I just don’t understand how important that is.

And so, is it safe to remove gnome-keyring on Qubes’ Debian templates?

I don’t think there is a point in using keyring if you don’t want to save multiple passwords in the same qube. You need to enter the keyring password to decrypt the keyring storage every time you start the qube, then why not just enter the password to the website/app/etc directly instead of saving it in the keyring.
Also the passwords in the keyring are only protected when the keyring is locked so it’s a protection from something like your qubes storage being leaked (e.g. your backup+backup password). So it’s a very rare case.

sorry for slow response.

Problem is, I never asked to start using it - its just popped up recently. Happens every time on start up, each Debian qube.

I am led to believe some programs (e.g. Chromium) will call it every time they start up.

So this is what makes me worry - are these programs storing something in the keyring that I don’t know about?

In which case, will disabling the keyring (or setting the password to nothing) open up the app to attack?

Maybe you’ve installed something in the template that also installed the keyring package (e.g. gnome-keyring) as a dependency.

They’ll call it if it’s available.

It could store something there, but it’s better to ask this from the developers of these specific apps to know for sure.