Consent & privacy

Sovera is built to a consent-first, data-minimizing standard. Consent must be recorded before any biometric template is created, subject PII is tokenized rather than stored in the clear, and a subject can be erased on request. All of this runs on infrastructure inside Zimbabwe.

Consent comes first

Record consent before you start a flow that captures biometrics. A verification that would create a face template without a prior consent record should not proceed. Recording consent needs the consent:write scope.

Record consent

Provide the purpose and how consent was captured. Sovera returns a consentId and a subjectToken you use to refer to the subject afterward, without handling raw PII again.

curl -X POST https://verify.lioncapventures.com/v1/consent \
  -H "Authorization: Bearer svk_live_xxxxxxxx" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "purpose": "account_onboarding_kyc",
    "method": "checkbox",
    "policyVersion": "2026-07-01",
    "subject": { "firstName": "Tapiwa", "lastName": "Moyo" }
  }'

{
  "consentId": "con_4d19ab",
  "subjectToken": "sub_7c2f81e0",
  "status": "granted",
  "grantedAt": "2026-07-04T17:40:00Z"
}

Revoke consent

A subject can withdraw consent. Revoking marks the consent record inactive. It requires the consent:write scope.

curl -X POST https://verify.lioncapventures.com/v1/consent/con_4d19ab/revoke \
  -H "Authorization: Bearer svk_live_xxxxxxxx"

Erase a subject

To honor a data subject access request (DSAR), erase a subject by subjectToken. Sovera deletes the associated biometric templates and tokenized PII. It requires the consent:write scope.

curl -X POST https://verify.lioncapventures.com/v1/subjects/erase \
  -H "Authorization: Bearer svk_live_xxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{ "subjectToken": "sub_7c2f81e0" }'

{
  "subjectToken": "sub_7c2f81e0",
  "erased": true,
  "status": "erased"
}