security & privacy
UCAPTM only works if both sides trust it. Consent is enforced in code, identity document and bank account numbers are encrypted at the field level, and sharing and access events are recorded in your access history.
How we protect your data
Identity document and bank account numbers are encrypted at the field level; stored data is also encrypted at rest by our cloud provider.
No client reads anything without an explicit, scoped, time-bound grant from the consumer. Consent is enforced in code, not only promised in a policy.
Approvals, shares and revocations are recorded with a timestamp, so the history of a grant can be reviewed if it is ever questioned.
Verified at the source
Supported identity documents are matched to a live selfie through Smile ID. Evidence grade and freshness remain document-specific.
Canonical income details and linked supporting evidence remain distinct, so consumers and recipients can see what is asserted and what is supported.
Documents are stored once, linked to relevant claims and disclosed only through an explicit consent grant.
That single principle is what makes UCAPTM safe to integrate and safe to use. Nothing happens without an explicit grant, and every grant can be pulled in one tap.
We'll walk the consent model, the encryption and the audit trail in detail — built for the questions your risk team will ask.
