BOIVA

Security and responsibility

Protect identity data from credential to decision

BOIVA provides security controls and verification signals. A secure implementation also depends on how your organization collects data, protects credentials, limits access, handles exceptions, and governs the final decision.

Documented foundations

Security designed into the integration boundary

Encryption for sensitive data

BOIVA's canonical documentation states that personally identifiable and sensitive data is encrypted, with decryption controlled through public and private key pairs.

Scoped information access

Client applications define the information scope they need, supporting narrower verification-status or attribute access instead of unnecessary data exposure.

Server-side credentials

Client ID, Client Key, and public access tokens must stay out of browser bundles, mobile applications, screenshots, repositories, and logs.

Environment separation

Sandbox and production use different base URLs and credentials, helping teams keep testing isolated from live verification activity.

What BOIVA provides

  • Documented authentication and verification contracts
  • Identity, selfie, and liveness signals according to the selected product
  • Sandbox and production environments
  • Structured results for downstream policy logic

What your organization governs

  • Lawful basis, notices, and user consent
  • Credential storage, access control, and log hygiene
  • Retention, deletion, and incident-response policy
  • Thresholds, manual review, exceptions, and final compliance or risk decisions

Review the exact contract before implementation

Use BOIVA's developer guide for the integration path and the canonical ReadMe pages for current endpoint fields and security documentation.

Start integratingCanonical security reference ↗