Purpose and legal-review boundary
This guide explains the OneView operational data boundary and helps a client assign responsibilities. It is not legal advice and does not determine the client's legal role or lawful basis.
Before production use, obtain Nigerian legal and data-protection review for the intended KYC purposes, data categories, providers, notices, retention, access, incident response, and any sector-specific obligations. Useful starting references include the current Nigeria Data Protection Act 2023 and current Nigeria Data Protection Commission guidance.
Data handled in the client environment
The client installation handles:
- KYC subject information submitted for an approved verification;
- verification requests, provider responses, normalised results, history, and permitted evidence;
- vendor credentials and connection settings;
- local users, roles, sessions, service accounts, branding, and activity history; and
- database, backup, certificate, installation, and recovery information.
A configured KYC provider receives the information required for the verification the client asks OneView to perform. That provider remains a separate third party. The client must assess its contract, security, processing locations, retention, and transfer obligations.
Online licensing and updates
OneView's online services process the customer, license, installation, version, platform, and limited usage information needed to activate a license, keep it current, determine update eligibility, and deliver approved releases.
These services do not require KYC subject data, verification requests or results, vendor credentials, local users, branding, database credentials, or browser-session data. Do not place personal data or secrets in error reports, support messages, request labels, or screenshots.
Shared-responsibility model
| Area | Client responsibility | OneView product responsibility |
|---|---|---|
| Purpose and lawful basis | Approve each verification purpose, lawful basis, notice, consent process where applicable, and permitted users. | Provides configurable Modules and Sub-modules with access controls; does not choose the client's lawful basis. |
| Data collection | Minimise fields, confirm authority to submit them, and keep live identity data out of tests and tickets. | Validates released request formats and sends approved requests to the selected provider. |
| Database and host | Secure, monitor, back up, restore, patch, and restrict the deployment infrastructure. | Provides supported setup, health, update, and recovery workflows. |
| Vendor processing | Assess providers, agree contracts, manage credentials, and approve endpoints and network access. | Uses the configured vendor connection for supported verification services. |
| Access | Maintain named users, least-privilege roles, service-account ownership, session review, and recovery ownership. | Enforces released authentication, permission, and revocation behavior. |
| Retention and rights | Set legally reviewed retention, export, correction, restriction, and deletion procedures, including backups and provider copies. | Provides the records and controls available in the installed release. |
| Incidents | Protect infrastructure, monitor all layers, make legally reviewed decisions, and coordinate affected providers and data subjects. | Provides activity history, safe diagnostics, and documented containment controls. |
| Licensing and updates | Maintain required outbound access, schedule maintenance, and protect recovery material. | Provides online license status and approved release delivery. |
Client privacy and governance checklist
- Assign legal/privacy and security owners.
- Document every verification purpose, lawful basis, data category, recipient, provider, and processing location.
- Publish accurate notices and implement required consent or other lawful-basis evidence.
- Complete the required privacy and security risk assessments.
- Collect only fields required for the approved purpose and use synthetic data in testing.
- Review agreements and due diligence for hosting, the database, OneView responsibilities, and every KYC provider.
- Configure individual users, least-privilege roles, service-account ownership, and session review.
- Approve retention and deletion rules for live records, exports, logs, backups, and provider copies.
- Encrypt and restrict the server, database, backups, certificates, and credentials.
- Test restore, account recovery, session revocation, credential rotation, and incident response.
- Review the data map and controls whenever Modules, Sub-modules, vendors, deployment, or law changes.
Safe support requests
Self-hosting does not grant OneView support routine access to the client host or database. Prefer client-run diagnostics and the smallest redacted evidence needed.
Before opening a support request:
- Reproduce with synthetic data where possible.
- Record the installed version, architecture, time and time zone, affected Module, Sub-module, vendor, and safe error code.
- Generate the documented sanitized installation report where relevant.
- Have the client's privacy or security owner approve every attachment.
Never send:
- KYC identifiers, names, dates of birth, addresses, images, biometrics, requests, responses, or results;
- passwords, API keys, setup or activation values, license values, certificates' private material, or other secrets;
- database credentials, database exports, configuration contents, unrestricted logs, or backup archives; or
- personal data or secrets hidden in filenames, URLs, headers, screenshots, ticket titles, or recordings.
If safe evidence is insufficient, stop and agree a client-approved support-data plan before collecting more.