Biometric Data Policy

Last updated: 18 November 2026

1. What this policy covers

VU Credentials Ltd (“VU”, “we”) makes a scan of a person’s face geometry in two checks, each only with that person’s agreement:

  • Verifying yourself: you read your passport’s chip with your phone, and we compare a short video of your face with the photo on the chip, to issue you VU credentials.
  • A face check at a business’s counter: a business you are dealing with asks to confirm that you hold the passport your VU ID came from, and we compare a photo taken on its phone with the photo on your passport’s chip.

This policy applies wherever you are. It is our written policy under the Illinois Biometric Information Privacy Act (740 ILCS 14/15(a)), Colorado’s law on biometric identifiers (C.R.S. 6-1-1314) and Texas’s law on biometric identifiers (Bus. & Com. Code 503.001). Our Privacy Policy covers the rest of the personal data we handle.

2. What we collect

  • A scan of face geometry from the video or photo of your face, and from the photo on your passport’s chip. These are biometric identifiers and biometric information.
  • The images themselves: the frames of the video our provider selects, and the chip’s photo.
  • Two scores: how sure the check is that a live person was present, and how alike the two faces are. A score is a number. It cannot recreate a face or identify anyone.

We compare your face only with the photo on your own passport. We never search your face against other people’s, keep a collection of faces, or collect fingerprints, voiceprints, or scans of the hand or eye.

3. Why, and nothing else

Our only purpose is to confirm that you are the person who holds the passport: to issue you VU credentials, or to answer a business’s check that you agreed to. We never use biometric data for marketing or advertising, to track you, or to train or improve any system, ours or our providers’. We never sell, lease or trade it, and never otherwise profit from it.

4. Notice and consent, before anything is scanned

  • Before any scan, VU’s own screen tells you in writing that a scan of face geometry will be made, why, who handles it and how long it is kept. A business cannot change that screen.
  • Nothing is scanned unless you tap to agree. That tap is your written release: we record the version and language of the words you saw, a fingerprint of their text, and the time.
  • Saying no costs you nothing. When you verify yourself, nothing of your face is checked or kept. At a business’s counter, the business must let you prove who you are another way, such as by showing your document to its staff, and treat that equally.
  • Anyone under 18 is stopped when the chip shows their age, before any face is captured, and what was read is deleted.

5. Who receives it

  • VU, which makes the decision.
  • Amazon Web Services, Inc. (Amazon Rekognition, United States, Virginia), which checks that a face is live and compares the two faces for us.
  • Google LLC (Google Cloud, United States, Iowa), which runs our servers.

Both act only on our instructions, under written data protection terms, and our AWS account is opted out of AWS using any content to improve its services. The business never receives your biometric data, only the result: that you were verified or not, or at a counter “it’s them”, “not them” or “couldn’t confirm”.

We disclose biometric data to no one else, unless you consent, or a valid warrant or subpoena, or the law, requires it.

6. How long we keep it, and when it is destroyed

WhatDestroyed
Verifying yourself: the images and face scansHeld only in our server’s memory, and destroyed as soon as the decision is made, a few seconds after your face is captured.
Verifying yourself, if you ask a person to review the decisionKept on your own phone, and sent encrypted to the reviewer for the review alone. Destroyed when the review ends, and always within 30 days.
A face check at a business’s counter: the chip’s photo, the image from the business’s phone and the face scansHeld encrypted, under a key for that one check, until the result is known. Destroyed then, and always within 5 minutes of the business asking.
The two scoresA verification’s scores are part of its audit record, kept 5 years after your credentials lapse. A counter check keeps none.

Biometric data is never written to our database, so it is never in our backups. A record that you agreed contains no image, scan or score: we keep it to show that you consented, for 5 years after you withdraw consent to verification, and for 6 years after a counter check.

In every case we destroy biometric data well before the law’s outer limits: when its purpose is met, and never later than 3 years after your last interaction with us (Illinois), 24 months (Colorado), or a year after the purpose ends (Texas).

7. How we protect it

With at least the care we give our most confidential data, and in line with our industry: encryption in transit and at rest; keys held in Google Cloud’s key-management service; images opened only in memory, never on a person’s screen except a reviewer’s you asked for; and access limited to those who need it, with every review opening logged.

8. If something goes wrong

If biometric data may have been accessed, used or disclosed without authority, we follow our incident response procedure: we stop the harm first, preserve the evidence, find out what happened and whose data it reached, and fix the cause. We tell the people affected, and the regulators the law names, as each law requires, and never later than 30 days after we determine that it happened. Report a concern to legal@vucredentials.com.

9. Your choices

  • You may decline any scan, and withdraw your consent at any time.
  • Every decision is automatic, and you may ask a person to review one that goes against you. At a counter, you may show the business another ID instead.
  • To ask a question, withdraw consent or ask what we hold, write to legal@vucredentials.com. People in the United States have the further rights in section 15 of our Privacy Policy, and people in Washington State those in our Consumer Health Data Privacy Policy.

10. Keeping this policy current

We follow this policy, review it at least once a year, and change it before we change how we handle biometric data. The date at the top shows when it last changed.