Privacy Information

Company and scope

Klark Health Ltd develops Klark. This interim information does not establish deployment-specific processing roles or replace a reviewed privacy notice.

Public website enquiries

The public pilot enquiry page provides an email link to pilot@klark.health. Opening the link does not send an enquiry; you choose whether to send it through your email client. The page has no enquiry form. Do not provide patient-identifiable or clinical information through public enquiries. Website hosting may produce operational access logs; the applicable data inventory requires review.

Account identity information

Supported product workflows may use account identifiers, authentication information and organisation membership to manage access. These are distinct from public website enquiries.

Clinical workflow information

Supported workflows process structured clinical-session information for clinician review. The permitted data and processing responsibilities must be confirmed for the applicable deployment.

Generated reports

Generated reports may contain clinical information and may be retained separately from the capture session. Session-oriented capture does not mean that nothing is stored.

Operational and audit records

Supported recorded executions can retain identifiers, runtime versions and payload hashes. Operational and audit records are distinct from generated reports; this is not a claim that every action is logged.

Retention and responsibilities

Retention, deletion, processing responsibilities and the handling of privacy requests require approval for the applicable deployment before clinical use. No universal retention period or controller/processor role is asserted here.

Privacy contact

Privacy contact is currently unavailable pending mailbox and monitoring confirmation. A monitored request route and a reviewed privacy notice are required before deployment.

Deployment privacy roles

Customer and Klark responsibilities

The responsibilities of Klark Health Ltd and the customer depend on the deployment, jurisdiction and supported workflow. Controller and processor roles must be established through review of the actual processing arrangements.

Before clinical use

The applicable purposes, safeguards, subprocessors, retention, request handling and incident responsibilities require legal and information-governance review. This page does not assert a universal regulatory role or completed data-processing agreement.