Skip to content

Identity verification notice and consent

Last updated: 9 September 2026 · Version 1.0

PRUVILO / baforge2 uses Didit for identity checks before protected deal actions. Read this notice before choosing whether to start.

Who is responsible

PRUVILO is operated under the unregistered project name baforge2. This is not a registered company name. The operator’s full legal identity and postal address have not yet been published. Contact [email protected] for privacy questions and verification reviews. This notice describes the current development integration, not a certification of regulatory compliance.

What the selected workflow checks

The selected Didit workflow includes ID Verification, Liveness, Face Match, Device & IP Analysis and AML Screening. It processes your identity document and extracted information, your selfie or liveness capture and facial biometric comparison, device and network information, and identity information checked against screening sources. Only submit your own genuine, unaltered documents. Do not submit another person’s identity or synthetic facial images.

Why these checks are used

These checks help establish identity, detect impersonation and suspicious activity, and assess eligibility for protected deal actions. AML screening can produce possible matches that need review; a match is not proof of wrongdoing. Verification does not guarantee that someone is honest, owns a product or will fulfil a deal. This process is separate from fingerprint or Face ID used to unlock your device.

Who processes the information

Didit processes verification submissions through its verification service. PRUVILO’s integration records provider/session references, verification status and consent/security audit records. It does not display your identity documents or biometric captures to another deal participant. Authorised support may need to review a disputed result. Didit’s own verification privacy notice describes its processing; hosting locations, contractual arrangements and any applicable transfer formalities remain to be confirmed for launch.

Retention and provider settings

A project-specific retention period and Didit’s saved model-training preference have not yet been confirmed. We therefore do not promise that optional training is disabled or that verification data is deleted after a particular number of days. Check the linked Didit privacy notice and contact us before submitting if these details affect your decision. Using Live credentials during development can process real personal data; calling a screen a preview does not make that data synthetic.

Your choice and requests

You may choose Not now and keep access to Home; protected deal actions require verification. Starting is a separate, explicit choice, not an automatic consequence of signup. To request access, correction, deletion, withdrawal of consent or review of a result, contact [email protected]. Withdrawal does not undo processing already lawfully performed and may prevent further verification-dependent actions. Any continued retention must have an applicable lawful basis. Do not send identity documents, PINs or OTPs by ordinary support email.

Privacy requests, support and complaints

[email protected]