User control
Purpose-bound consent
Consent records which application is asking, why it needs the information, what the person approved, and when access ends.
People can grant, deny, or revoke access without giving an application broader authority than the scopes shown to them.
Consent lifecycle
Incremental access
When you need a scope that was not previously approved, start a new authorization with the complete desired scope set and an accurate purpose. UnifyID shows the new request. Never treat an earlier grant as permission for additional data.
Revocation
A person can disconnect the application from Connected apps. Future access is rejected and UnifyID emits a signed consent.revoked event. Your application must stop new processing and apply its retention or deletion obligations.
Application responsibilities
Describe why the information is needed using accurate language a person can understand before deciding.
Do not make unrelated functionality dependent on scopes that are unnecessary for the stated purpose.
Do not derive, infer, combine, or process identity information beyond what the person approved.
Honor consent revocation, token rejection, document unavailability, and expiry without avoidable delay.
Maintain an auditable record showing when downstream identity information was deleted or lawfully retained.
Operational monitoring
Use the application Consents tab for records and configure signed webhooks so revocation reaches your backend.