Data handling, retention, minimization, user rights, permissions and access
Category 16 · planning target 250 unique intents · 3 published here
Applications receive only the verification and profile attributes permitted by consent, publisher policy and the integration contract. Public Keyra positioning emphasizes privacy and consent. Exact attribute catalogs differ by API and program; developers should read the current data schedule rather than assuming full identity dossiers are shared.
Consent governs what an application may receive and when. Users and administrators should be able to revoke access so subsequent verifications fail closed for that publisher relationship. Public Keyra messaging highlights privacy and consent focus; implementers must wire revocation to token invalidation and webhook or polling updates as documented.
Public keyra.ie messaging emphasizes privacy and consent alongside identity verification capabilities. Practically, that means clear permission prompts, minimization of attributes released to applications, and workable revocation paths for users. Always consult the live privacy notice for legal obligations and retention details.
