Deployment model
OneView is installed in the client's environment and is reached through the HTTPS hostname selected during installation. The client provides and manages the server, network access, database, backups, and any organisation-wide monitoring required by policy.
OneView also uses online licensing and software-update services. The installation therefore requires the outbound network access listed in Requirements.
Client-owned information
The client controls its:
- verification requests, results, and permitted evidence;
- vendor credentials and connection choices;
- users, roles, sessions, branding, and activity history;
- database, backups, retention, and recovery procedures; and
- installation configuration, certificates, and recovery material.
OneView does not provide routine remote access to the client's host or database. A client must approve and supervise any exceptional support access under its own security and privacy procedures.
Information used by online services
Online licensing and update checks use only the installation, license, version, platform, and usage information required to provide those functions. They do not require KYC subject data, verification requests or results, vendor credentials, local-user records, branding, or database credentials.
See Data boundary & responsibilities for operational ownership and support redaction guidance.
Shared security responsibility
The client remains responsible for restricting server and database administration, applying host security updates, protecting backups and credentials, configuring HTTPS, and reviewing user access. OneView provides application access controls, encrypted sensitive configuration, signed licensing and updates, and audit functions within the released product.