Feature request: Tag movement, clearing all memory.

I'll start by saying that I happily use 1Password because, after my own security tests, I found it to be more secure than all other password managers. I'll explain why later, but there's still room for improvement.

Since 1Password is a more expensive password manager than average, I'm not saying it needs to be perfect, but it needs to have the features you'd expect from a password manager. Therefore, I'm suggesting two important features, which I'll now highlight:

Tag Movement:
Tags are used to better organize passwords, but without the ability to move passwords from one tag to another, password organization becomes unproductive!

The problem is that when you move passwords to another tag, the previous tag isn't deleted. Therefore, the password has two tags, and to delete the previous tag, you have to do it manually for each password. So, if you want to move 100 passwords, it becomes impossible.
This feature was requested 3 years ago but was not implemented, why was it not taken into consideration? 

This problem is more evident in the web app and the Android app because there's no way to rename or delete tags.
It's therefore appropriate to include a feature that allows you to move multiple passwords from one tag to another while keeping only the tag where they were moved, and to include the ability to delete or rename tags on Android and the web app as well.

Clear all memory when locked:
Another feature I recommend concerns the technical security aspect of 1Password and its memory management.
First of all, as I mentioned at the beginning, 1Password is the most secure of all because it has a memory management system unlike any other. This means:
All password managers delete passwords from the clipboard when they're copied, but keep them unencrypted in the dump memory until it's locked. However, 1Password automatically deletes all copied passwords from the clipboard and the dump memory after a short time, even when the database is open. This is truly extraordinary!

However, when the database is locked, all other data from non-password fields, such as username, URL, notes, and all other fields that aren't hidden, remain unencrypted in the dump memory. It would be nice if the entire memory were cleared when the database is locked.

To recap, I recommend these features:
Moving passwords from one tag to another, keeping only the tag where they were moved.
Ability to rename and delete tags in the web and Android apps.
Empty all memory (including "non-password" fields) when the database is locked.

Thanks for listening, and I hope my suggestions are helpful.