Once a client has completed an identity verification, you can purge it to permanently destroy the sensitive data captured during the process. This helps you meet data protection and minimisation obligations, and reduces the risk of unauthorised access to personal information you no longer need to hold.
Purging is immediate and cannot be reversed. Permanently destroyed data cannot be recovered, so make sure you no longer need the identity document or its extracted data before you continue.
Who can purge
Anyone with access to the verification can purge it, except read-only users. Purge verification is only available once the verification is Completed and hasn't already been purged.
How to purge verification data
Go to ID Verification and open the Verifications tab.
Click the row of the Completed verification you want to purge.
In the top-right of the detail view, click the â‹® menu and select Purge verification.
A Confirm action window asks: "Are you sure you want to purge this verification?" Click Confirm to proceed.
Once purged, a banner on the verification reads: "This verification has been purged - I.D. documents and PII stored with third-parties have been permanently deleted." If AML & CTF screening was run, the banner also notes that AML & CTF screening results are not affected.
Automatic purging
Verifications can also be purged automatically by your organisation's data retention policy. When a verification is due to be purged, it shows "This verification is scheduled to be purged in N days".
What's destroyed and what's kept
Purging is intentionally scoped so you don't lose your compliance record.
| Destroyed | Kept |
|---|---|
| The identity document captured during verification (for example, the driver's licence or passport image and selfie). | The AML & CTF screening results, if screening was run as part of the verification. Screening outcomes stay intact and continue to appear in the AML & CTF screening tab. |
| The document outputs: the data extracted from the ID (name, address, date of birth, document number, expiry date and so on). | The certificate of verification and multi-bureau check report, which you can still download from Download reports. |
| The audit log for the verification request, which continues to show the full history of the request from creation through to purge. | |
| The request details (verification ID, name, email, mobile, status, timestamps, sender), so the record of who was verified and when stays available. |
Audit log
When a verification is purged, an event is automatically added to its audit log recording:
The action (verification purged).
The team member who performed the purge.
The timestamp.
This gives you a defensible record that the sensitive data was destroyed, and by whom.
