PII stays in the mobile app
Document images, selfie material, liveness evidence, and extracted identity details are handled inside the native mobile experience. The server does not need long-lived plaintext access to the user's identity packet.
A one-time chorethat protects you later.
Most people experience identity verification as friction. Ugnay treats it as a trust investment: a short native flow that helps protect future account recovery, signing, partner approvals, and high-risk actions without turning personal documents into permanent server-side baggage.
Native mobile flowPII stays localShort-lived validation artifactSecure Enclave / TEE protected recovery
PII local
TTL artifact
Hardware keys
Verified state
Why it matters
The verification step should earn its place.
eKYC asks the user to do work once: capture documents, confirm extracted details, take a selfie, pass liveness, verify a mobile number, and bind the device. That work becomes meaningful when it protects future recovery and sensitive actions instead of being repeated across every workflow.
After verification, Ugnay can make better decisions about account protection because identity, device trust, and recovery state are connected. The goal is not to collect more personal information. The goal is to use the minimum identity proof needed at the moment it matters, then keep durable private state under the user's control.
// containment model
How Ugnay keeps the sensitive parts contained.
The eKYC flow is designed around native device boundaries and short-lived server validation, not permanent plaintext storage of identity materials.
Backups leave only as encrypted blobs
Backup and restore data leaves the device as encrypted blobs. Those blobs are useful only when opened by keys protected by platform hardware: Secure Enclave on iOS and TEE or StrongBox-backed protection on Android.
Server validation uses a one-time artifact
For document, selfie, and liveness validation, the app uploads a one-time validation artifact with a TTL. It exists to complete the server-side verification check, then expires instead of becoming a permanent identity warehouse.
Trust becomes reusable without re-exposing documents
Once the account is verified, later workflows can rely on verified state, device binding, and recovery controls. The user should not have to resubmit sensitive documents every time a trusted action needs stronger assurance.
Design principle
Collect once. Protect continuously. Expose briefly.
Native screens hold the user-facing PII journey.
The user can see what is being captured and why, inside the app surface they are already using.
Encrypted blobs support recovery.
Recovery should not mean the server gets a plaintext copy of identity materials.
Validation artifacts are temporary by design.
Server validation gets the evidence it needs for the check, with expiration built into the handoff.