Clinical data, handled properly.

All traffic between a clinic browser and Asttona runs over TLS 1.2 or higher with modern cipher suites and HTTP Strict Transport Security. Plain HTTP requests are redirected, never served.

The database, file storage and backups are encrypted at rest with AES-256. This covers clinical notes, signed consent documents, before-and-after imagery, scans and attachments.

Encryption keys are held by the managed infrastructure provider's key service, rotated on their schedule, and never stored in application code or configuration repositories.

Each team member signs in with their own individual account. Shared logins are discouraged and can be blocked at clinic level. Passwords are stored only as salted hashes, never in readable form, and are checked against known breached-password lists.

MFA is available for every account and can be enforced clinic-wide, so a second factor is required in addition to the password. Administrator accounts should always have it switched on.

Permissions follow the role: practitioner, front desk, management and finance each see only the records and actions their job requires. Access to a patient record can be restricted by location in multi-site clinics, and revoked immediately when someone leaves.

Sessions expire after inactivity, can be ended remotely by an administrator, and a password change invalidates existing sessions on other devices.

Clinical records carry an access and change history: who opened a record, what was changed, from where and when. Consent signatures are locked to the visit they belong to and cannot be silently edited. Audit history is available to clinic administrators and is retained for the life of the record.

Security events are triaged on a defined severity scale. Confirmed incidents affecting clinic data are investigated, contained, and reported to the affected clinics with what happened, what data was involved and what was done — within the notification timeframes their regulator requires. A post-incident review follows every case.

Continuous database backups with point-in-time recovery, plus daily snapshots retained on a rolling schedule. File storage, including imagery and consent documents, is replicated across zones.

Recovery procedures are documented and rehearsed, with a target recovery point measured in minutes and a target recovery time measured in hours. Restores are tested rather than assumed.

Asttona runs on managed cloud infrastructure in certified data centres with physical access control, redundant power and networking, network isolation and continuous monitoring. There is no server to maintain in the clinic.

Every clinic is a separate tenant. Each request is scoped to the clinic that owns the data and enforced at the database layer, so one clinic's records can never be returned to another clinic's users — including on shared infrastructure.

Least-privilege internal access, reviewed change management, dependency and vulnerability monitoring, and confidentiality obligations for all staff. Support engineers access a clinic workspace only with that clinic's permission, and the access is logged.