KlarkPilot enquiries: pilot@klark.health. Do not include patient-identifiable or clinical information.

Security and data protection

Implemented technical controls

Supported Operator report-generation operations authenticate the Operator and check session ownership and runtime authorisation on the server. Recorded report executions can preserve session identifiers, runtime versions and payload hashes. These statements describe supported implementation paths, not a certification of a live deployment.

Deployment-specific configuration

Available controls depend on deployment configuration. Access settings, data location, retention and recovery arrangements require review for the proposed deployment.

Internal processes

Release and incident procedures require operational evidence for the applicable deployment. No staffing level, testing frequency or response-time commitment is published here.

Planned assurance

Clinical safety, information governance and independent security assessment require scoped review before pilot use. This page does not represent those reviews as complete.

Third-party certification

No third-party certification is claimed on this page. Technical architecture alone does not establish certification or regulatory compliance.

Customer responsibilities

The deploying organisation must establish local authorisation, appropriate product roles and clinical oversight for its proposed workflow. Responsibilities must be agreed before clinical use.

Contact

Security contact is currently unavailable pending mailbox and monitoring confirmation.