Security & Data Control

Patient data stays on a server inside your practice, with role-based access — and an honest account of what is and is not claimed.
Review the details

Hosting, access, backups, responsibilities

Book a guided demo

Discuss your practice's environment

Security and data control

What running locally means for your patient data — and what your practice remains responsible for.

Local hosting

Sienna is deployed on a server inside your practice. Patient records are stored on that server, and the system is reached through a browser on your practice network. Day-to-day use does not depend on an external cloud service.

Role-based access

Access to Sienna is controlled through user accounts with role-based permissions, so the people who can view or change patient information are limited to the roles your practice assigns. Accounts, roles, and permissions are configured during installation and maintained by your practice.

Data protection arrangements

The network and access arrangements for your deployment are agreed during deployment planning. Transport encryption, encryption of stored data, and audit logging depend on the confirmed deployment for your practice, so they are stated in your written quotation rather than described generically here. If any of these applies to your setup, it will be written down before you rely on it.

Backups and recovery

Sienna includes backup and restore tooling, and backups stay inside your practice environment under your control. The backup schedule, storage location, retention period, and who is responsible for restoring are agreed as part of your deployment.

An optional cloud/off-site backup service is available as a priced add-on (see implementation details). No encrypted backup, retention period, or recovery guarantee is promised on this page.

Deployment and setup

Sienna is installed and configured on-site by our team, including the local environment required to run the platform inside your practice. What your practice needs for hardware, network, and power is assessed during deployment planning and set out in your written quotation. See implementation.

Practice responsibilities

Because Sienna runs inside your practice, the following remain your practice's responsibility: physical security of the server, power and network availability, network security, management of user accounts and roles, and the storage and safekeeping of backups. We cover these during onboarding.

What we do not claim

Rather than implying more than the current release supports, this is the boundary:

  • No security certification or formal regulatory compliance claim is made for Sienna.
  • No encrypted backup, retention period, or recovery guarantee is offered.
  • No uptime or availability guarantee is given, because availability depends on your local server, network, and power.
  • No encryption of stored data is claimed as standard; it is confirmed per deployment.
  • No audit logging capability is claimed.

Read the privacy policy for how the details you submit on this site are handled, or see implementation for installation, support, and terms.

See Sienna in a GP Workflow

Choose the entry point that fits your stage: a quick sandbox, a guided demo, or a practice-fit discussion for your clinic.

Book a guided demo

Walk through consultation, records, scheduling, and billing with the team.

Open the sandbox

Explore the product with sample patient data and no sales call.

Sandbox — Explore the interface and core workflows.
Guided demo — See how it works for GP practice use.
Practice-fit discussion — Confirm whether the current phase fits your clinic.