Verification Privacy Notice
How we process your personal data, including biometric data, when you verify your identity for an organisation.
Last Updated : 11 Oct, 2026
Verification Privacy Notice
How we process your personal data, including biometric data, when you verify your identity for an organisation.
Last Updated : 11 Oct, 2026
About this notice
This notice explains how secuveri GmbH ("secuveri", "we"), Baarerstrasse 135, 6300 Zug, Switzerland, processes your personal data, including biometric data, when you complete an identity verification that an organisation has asked you to do. It supplements our Privacy Policy and our End User Terms.
1. Scope
This notice applies whenever you use a verification flow powered by secuveri, whether on a secuveri page, inside an organisation's website or app, or on a page branded by the organisation.
2. Who is involved
The organisation: The organisation that asked you to verify is the controller. It decides why you are verified, which checks run, and what happens with the result.
secuveri as processor: secuveri runs the checks on the organisation's behalf and only on its instructions.
secuveri as controller: For limited purposes, secuveri is an independent controller: it keeps the service secure, prevents abuse of the verification itself (for example the same device trying many different documents), improves its fraud detection (section 6), meets its own legal obligations and defends legal claims.
- The organisation
- The organisation that asked you to verify is the controller. It decides why you are verified, which checks run, and what happens with the result.
- secuveri as processor
- secuveri runs the checks on the organisation's behalf and only on its instructions.
- secuveri as controller
- For limited purposes, secuveri is an independent controller: it keeps the service secure, prevents abuse of the verification itself (for example the same device trying many different documents), improves its fraud detection (section 6), meets its own legal obligations and defends legal claims.
If the flow carries the organisation's branding, secuveri is still the provider behind it, and the organisation should tell you so.
3. What we process
Which items apply depends on the checks the organisation has enabled.
- Document images: photos of the front and back of your ID card, passport or other identity document.
- Document data: name, date of birth, sex, nationality, document number, expiry date, issuing country, the machine-readable zone (MRZ) and other printed text.
- Chip data: if you scan your document's chip with your phone, the data stored on it, including the passport photo and the issuer's digital signature.
- Selfie and liveness captures: images or short frame sequences of your face, including frames taken while the screen shows colours to confirm a real person is present.
- Biometric data: templates of your facial features, calculated from your selfie and from the portrait on your document so the two can be compared, plus liveness, deepfake and photo-manipulation scores.
- Results: whether the document appears genuine and valid, whether the faces match, whether a live person was present, and the overall outcome.
- Technical data: IP address, browser, operating system, device type, timestamps, session identifiers, and a cookie that recognises the same device across attempts.
- Consent record: when you agreed, to which text version, from which device.
4. Why we process it
- To verify your identity for the organisation: read and check your document, confirm a real person is present, and compare your face with your document photo.
- To detect fraud: forged or edited documents, photos, screens, masks or deepfakes presented to the camera, and repeated attempts from one device.
- To keep the service secure and investigate incidents.
- To improve our fraud detection: train and test the models that spot forged documents and fake faces (section 6).
- To meet legal obligations and establish or defend legal claims.
We do not sell, rent or trade your data, and we do not use it for advertising.
5. How we handle biometric data
When the organisation's workflow includes a selfie, we:
- capture selfie images in your browser after you allow camera access;
- check that a real, live person is present and that the images aren't a photo, screen, mask or deepfake;
- calculate a template of your facial features from the selfie and from your document's portrait, and compare the two;
- send the result to the organisation.
Biometric data is processed and stored only in Switzerland, encrypted, accessible only to authorised staff, used only for the purposes in section 4, and deleted on the schedule in section 10.
6. Improving our fraud detection
Fraudsters keep inventing new fakes. To recognise them, our models have to learn from real verifications, both real attacks and genuine captures, so they can tell the two apart.
- What we use: images of documents, selfie and liveness captures, and the check results from verifications, especially those identified as fraud attempts.
- What we train: fraud-detection models only: document tamper and forgery detection, detection of printed or on-screen documents and faces, liveness, deepfake and morph detection. These models learn what fakes look like, not who you are.
- What we don't train: face-recognition models that identify or match people, unless you give separate, explicit consent.
- How: only images and check results go into a separate, access-controlled training store in Switzerland. We remove names, document numbers and other identifiers, and we never put face templates into it. It is never shared with other organisations or sold.
- Not used: verifications of people under 18, verifications from organisations that switched training off, and verifications someone has objected to.
- How long: see section 10.
- Your choice: you can object at any time by writing to privacy@secuveri.com with your verification ID if you have it. The organisation can also switch this off for all its verifications. We then exclude your data from future training and delete it from the training store; what models have already learned can't be removed from them.
7. Legal basis and consent
- Biometric data: your explicit consent, given before the camera starts by selecting "Continue" after a notice that names biometric processing. We store a record of that consent with the verification.
- Other verification data: the organisation's legal basis, for example a legal duty such as anti-money-laundering law, a contract with you, or its legitimate interest in preventing fraud.
- Security and abuse prevention: our legitimate interest, and the organisation's, in a secure service.
- Improving fraud detection (section 6): our legitimate interest in detecting new fraud techniques, which also protects you against people using your identity. You can object.
You can withdraw your consent at any time by contacting the organisation or privacy@secuveri.com, quoting your verification ID if you have it. We then stop processing your biometric data and delete it, including from the training store. Withdrawal doesn't affect processing that already took place.
If you don't want to give consent, don't continue. The organisation decides whether it offers another way to verify you.
8. Automated decisions and human review
The checks run automatically, and the result goes to the organisation, which decides what follows. Where a decision based solely on automated processing has legal or similarly significant effects on you, you can ask the organisation to have a person review it, to give your point of view, and to be told the main reasons.
9. Who receives your data
- The organisation that asked you to verify: the result, and the data and captures it has configured.
- Our hosting provider, which stores and runs everything in data centres in Switzerland.
- Authorities, only where Swiss law requires it.
- Professional advisers, such as lawyers and auditors, under confidentiality, where necessary.
- A buyer or successor, in a merger or sale of the business, under the same protections.
Your browser loads everything for the verification from secuveri's own servers. It doesn't contact analytics, advertising or CDN providers during a verification.
10. How long we keep it
The organisation decides how long its verification data is kept, based on its own legal obligations; anti-money-laundering law, for example, can require identification records to be kept for several years. If the organisation hasn't set a period, or asks for earlier deletion, we keep:
Selfie, liveness and document images: 30 days
Face templates and biometric scores: 30 days
Document data and the verification report: 90 days
Device correlation against repeated attempts: 30 days
Consent record: As long as the verification report
Security logs: 365 days
Training store: verifications identified as fraud attempts: 3 years
Training store: other verifications: 1 year
- Selfie, liveness and document images
- 30 days
- Face templates and biometric scores
- 30 days
- Document data and the verification report
- 90 days
- Device correlation against repeated attempts
- 30 days
- Consent record
- As long as the verification report
- Security logs
- 365 days
- Training store: verifications identified as fraud attempts
- 3 years
- Training store: other verifications
- 1 year
After that, data is deleted or irreversibly anonymised automatically. Data in the training store is pseudonymised and follows its own periods above. The organisation's privacy notice explains how long it keeps your data, including any copy it holds itself.
11. U.S. biometric privacy laws
If a biometric privacy law applies to you, for example in Illinois, Texas or Washington:
- this notice is our written policy for biometric data;
- section 10 is our public retention schedule;
- biometric data is destroyed when the purpose of the verification is fulfilled, and in any case within the period required by that law;
- we obtain your written consent electronically before capture;
- we never sell, lease, trade or otherwise profit from biometric data.
12. Security
- Images and sensitive fields are encrypted at rest; connections are encrypted in transit.
- Access is restricted and logged.
- Backups are encrypted and stored in Switzerland.
13. Children
The organisation must ensure it has a lawful basis to verify anyone under 18 and, where required, a parent's or guardian's permission. Verifications of people under 18 are excluded from model training.
14. Your rights
You can ask to access, correct, delete or receive a copy of your data, to restrict or object to processing (including use for model training, section 6), and to withdraw consent.
For a specific verification, contact the organisation first; we will forward requests we receive and help it respond. For the purposes where secuveri is controller (section 2), including model training, write to privacy@secuveri.com.
You can complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC, edoeb.admin.ch) or your local data protection authority in the EU.
15. Changes
We may update this notice. The current version and its date are always published at this address.
Contact
secuveri GmbH, Baarerstrasse 135, 6300 Zug, Switzerland. For questions about this notice or your verification data, write to us.
Questions about your verification data?
secuveri GmbH · Zug, Switzerland