Naya ID is built so that every verification is defensible. Not because a score declares it acceptable, but because the documents, the checks, the timestamps and the rule applied remain available and consistent. This page describes the framework we operate in, what an evidence file contains and how data is protected.
These three axes shape our technical choices. They are contractual and verifiable, not declarative.
We do not replace your compliance function: we produce the material it needs to demonstrate that its obligations are met. These are the frameworks our clients most often place us in.
Credit institutions, e-money issuers and decentralised financial systems must identify their customer and verify their identity against a document before opening. Naya ID provides the verification, the biometric match and the dated file that documents the operation.
Screening of sanctions, politically exposed persons and adverse media runs when the relationship starts, then periodically. Every match examined, whether retained or dismissed, remains available with its reason and timestamp.
The consent of the person being verified is captured explicitly and retained with the file. Purposes are limited to identity verification and compliance; retention periods are configured according to the applicable national law.
Where the obligation concerns a registry (SIM subscribers, service beneficiaries), the consolidated registry is exportable, with per-record detail, so an authority’s request can be answered without manual reconstruction.
An audit never looks at averages: it looks at one specific file, opened on one specific day. Every verification therefore retains all the elements that led to the decision, exportable as a PDF or through the API.
The file is produced on demand without reconstruction: it is assembled as the verification runs, not after the fact.
The security of an identity setup is judged as much on the infrastructure as on the daily practices of the teams that operate it.
These questions come early in our conversations with legal departments. Here are the principles; the contract makes them specific project by project.
No. The platform runs the checks, produces the elements and applies the rules you have defined. The decision remains yours: it binds you, and the file assembled serves to justify it.
In a secure cloud, in the environment agreed with you during scoping, or inside your own infrastructure for an on-premise deployment. The processing location is written into the contract, not merely announced.
You export the files concerned from the console or through the API: documents, checks, scores, the rule applied and manual decisions. Our compliance team can support your exchanges if you wish.
Not without written agreement and a defined scope. By default, a client’s data is used exclusively to process that client’s own verifications.
Under a confidentiality agreement we share the summary report of our penetration tests, our security policy, the list of sub-processors and a description of our incident-handling procedures.
By continuing to browse Naya ID, you accept our terms of use and our privacy policy. Beyond strictly functional cookies, we use Google Analytics to measure site audience, only if you accept it.
