Why are items moved between vaults listed in "Recently Deleted"? Bad security model!

Jack_P_1P - you are totally missing my point. If I inadvertently move an item to the wrong vault for as little as one second, a copy of the item remains in the deleted items list associated with that vault. Certainly there is the possibility of someone watching and getting access for that one second, but come on - that's not the scenario I'm talking about.

Yes, in the worst-case, I need to change the password of that account. But in the case of something that is not super sensitive, I'll evaluate my risk and say, "nah, nobody could have seen it that quickly,* and just move on. But as it stands now, I can't. I have to remember that a copy of the item exists and they do have access and I can't stop that. So I am forced to change the account password, causing me more work. All because the tool can't figure out to do it "right"? That's absurd.

Moreover, you are also ignoring the issue that most people see the "move to vault" as a move, not copy/delete, and are NEVER going to think about the possibility of there existing copies of entries in a "deleted items" area. This is because you used the term _MOVE. If it's not a move, then don't call it a move. Call it what it is or change the underlying implementation.

As to your point about "data loss"? Come on - that's just words meant to placate me. If you implement it right, there's no chance for data loss. Tell me the scenario under which there would be data loss because you didn't do the "Copy / Delete" method as it exists now and I'll consider your logic and perhaps reconsider my position.

If you want to leave it as a copy / delete, then at least permanently and immediately delete the old copy so it can't be recovered form the deleted items list.

As it stands now, as far as I see it, this is a KNOWN security issue that I will continue to pester you on. For a security-industry company and product, it doesn't feel as if you are taking the possibility seriously.