There once was one credit card entered into QB but it was removed. QB did not clean up the data and left (as I remember) an expiration date. This QB encrypted and password protected the database.
This is NO sensitive data in QB at all, but still needs to be encrypted.
The simplest solution would be for QB to disable checking account storage credit card stoarage, etc if the user decides to not password protect.
If I were an employee, I would be embarrassed that my company had not taken action to address this issue considering how many people wanted the problem fixed. Forcing users to enter passwords because the programmers did not clean up after deleted entries is unforgivable.
