Understanding what exactly is protected, would help me to understand the usage of this potentially very usefull feature imho.
Best answer by JimM
It will protect "any information entered" and does not discriminate in terms of what to protect based on the contents of that information. It might be your credit card number in one instance and a shopping list, or some trivial data in another instance.
To be a bit more granular in answering this question, let's take a particular setting of that shield and discuss it a bit. If, for instance, you have "prevent programs from accessing protected credentials" checked in the main settings, it will prevent untrusted programs from accessing secure areas such as Windows secure storage, cookie information, stored passwords, and saved forms.
Regarding the troubles you've run into before, I notice the last time you contacted support, you were running version 184.108.40.206. The current version is 220.127.116.11. There have been a number of improvements made to the Identity Shield since last time you contacted us. It would be worth ensuring you are on the most current version. You can look into this by going to My Account from the main screen of the program.
It's also entirely possible that the programs you are running into issues with are considered "untrusted." If they are not listed as Known-Good on our end, they will be flagged as Unknowns and treated with a greater degree of suspicion. One possible solution would be for us to whitelist the files in question if that is deemed appropriate. However, based on your case history, I see at least one of those programs is a macro scripting program. The thing about scripting programs is that while there are ways to make good scripts like "fill out this form for me," "do a bunch of boring stuff in this game for me so I don't have to do it myself," etc., you could also conceivably do something nefarious with a script like "make a record of everything typed into a form and then send it somewhere" or "duplicate your files until the hard drive is full." So I suspect that probably our threat researchers would not want to go so far as to whitelist the scripting utility itself. Ultimately, more research would need to be done to come to a firm conclusion regarding that tool or any other program you'd like us to check into, but we can do so on a program-by-program basis if you'd like. Please let me know if you'd like us to do that for you, and I can reopen that support ticket.