When someone verifies their identity through Verify, that check runs against the Document Verification Service (DVS). It's worth knowing exactly what sticks around afterwards, because Verify takes a deliberately light-touch approach to the sensitive stuff.

The short version: Verify never holds onto the identity document itself. It keeps just enough information to give you a clean audit trail, and nothing more.

Your customers' documents aren't stored
‍For security reasons, Verify doesn't keep a copy or record of the identity document used in a check — no licence numbers, no passport details, none of it. Once the verification is done, that information isn't retained.

‍

What Verify keeps

While the document itself isn't stored, Verify does record a small amount of information so you've always got a reliable trail to refer back to. For each verification, it logs:

• DVS Transaction ID — a unique reference for the check, so you can trace it back if it's ever queried.
• Document Type — the kind of document used (for example, a driver's licence or passport), without any of the actual details from it.
• Status — the outcome of the check, such as whether verification succeeded or failed.

Together, these give you everything you need for auditing and reporting — proof that a check happened, what type of document was involved, and how it turned out — while keeping the sensitive contents out of the system entirely.

Removing records

If you ever need verification records removed from the Verify module, this isn't something you can do yourself from within the module. Get in touch with your System Administrator, or raise a support ticket, and they'll take care of it for you.

Good to know
‍Because the records Verify keeps are limited to a transaction ID, document type, and status, there's no sensitive personal information sitting in the module waiting to be cleared. The removal process is about tidying up your audit history, not deleting customer data.

‍