Setting data-retention schedules for verification data
Keeping verification results forever is a liability. Keeping them too briefly fails an audit. Here is how to set a defensible schedule.
Map each field to a driver
Some data you keep because a regulator requires it for a number of years. Some you keep only while the customer relationship is active. Some you only needed for the moment of the decision. Classify every field you store into one of these.
Build the deletion job first
A retention schedule with no automated deletion is a policy document, not a control. Write the job that ages out records past their retention date before you promise anyone a schedule.
Handle the deletion request
When a user asks to delete their data, or closes their account, your system should anonymise or remove verification records on the schedule while preserving anything you are legally required to keep, and be able to explain the difference.