Verify who someone is. Screen who they might be. One API.

What happens to PII

• Nexiel Age's and Nexiel Verify's age-verification checks use raw PII (name, DOB, address, document number, nationality) only for the single verification transaction and never persisted afterward. Deletion happens automatically, not a manual step someone can forget. What remains is only session id, client id, timestamp, method, boolean proofs, a SHA-256 hash of the presented wallet token, and the issuer signature validation result.
• An aml-identitycheck in Nexiel Verify, and every screening decision in Nexiel Screen, handles PII differently once the client has registered an encryption key. The actual disclosed claim values, the screening decision, and the frozen decision artifact are packaged into an “evidence pack” and encrypted (JWE, ECDH-ES key agreement, A256GCM content encryption, P-256 curve) to a public key the client registers from its own dashboard. Nexiel delivers that ciphertext once and keeps no readable copy afterward.
• The matching private key is generated in the client's own browser and never reaches Nexiel, not even once. When a key is registered, what Nexiel retains afterward is a single audit row: session or request id, client id, timestamp, classification, the frozen-artifact hashes, and a SHA-256 hash of the delivered ciphertext, proof of handoff, never the substantive data. AMLR makes the client, not Nexiel, the party required to retain its own CDD/screening evidence, so the client is responsible for keeping the evidence pack it receives. See setting up evidence pack encryption for how to register a key.
• Screen's KYB customer due-diligence records follow a separate, narrower ruleabout the client's own business entity, not any single check: EU AML Directives require an obliged entity to retain beneficial-ownership/UBO records for the life of a business relationship plus a statutory period after (a deliberate exception, not a contradiction, scoped only to self-declared UBO/director records). This path is not yet handling a real paying client: encryption-at-rest, separately audited access, an automated statutory purge, and written sign-off from engaged legal counsel on the retention period are all required first.
• Every screening decision, credential issuance, and admin action is logged immutably with a cryptographic hash chain, verifiable independently per client, not one shared chain across every customer.

How Screen works on its own

Screen is Nexiel's most mature product: live in production today, and fully usable on its own. A solicitor opening an AML file or an accountant screening a beneficial owner never has to touch an EUDI wallet to use it.