New version of uk-bank-statement-anonymiser comes with a new feature allowing the protection of transaction descriptions.
We need to incorporate the functionality, but very carefully as un-anonymised transaction descriptions can be a security risk.
Instead of simply adding a tick box, we need to have a button to turn on this option which gives an explicit warning of the dangers.
This button should only appear if there's data in the user always anonymise file, as it will fail otherwise.
The warning needs to ensure the user is happy that they've added all personally identifiable information to their always anonymise file.
It should also recommend that anonymised files with un-anonymised transaction descriptions should not be shared, but simply used for testing and demonstration purposes at an AGGREGATED level.
New version of uk-bank-statement-anonymiser comes with a new feature allowing the protection of transaction descriptions.
We need to incorporate the functionality, but very carefully as un-anonymised transaction descriptions can be a security risk.
Instead of simply adding a tick box, we need to have a button to turn on this option which gives an explicit warning of the dangers.
This button should only appear if there's data in the user always anonymise file, as it will fail otherwise.
The warning needs to ensure the user is happy that they've added all personally identifiable information to their always anonymise file.
It should also recommend that anonymised files with un-anonymised transaction descriptions should not be shared, but simply used for testing and demonstration purposes at an AGGREGATED level.