Patient data protected in layers

1. Layer 01

   Browser

   • HTTPS (TLS 1.2+) on every surface
   • httpOnly and Secure sessions
   • Two-step verification

2. Layer 02

   Application

   • Permissions per role and branch on every endpoint
   • Standard errors that never leak data
   • AI follows user permissions; actions require confirmation

3. Layer 03

   Data

   • Per-clinic isolation (row-level security)
   • Sensitive identifiers encrypted with AES-256-GCM per organization
   • Hash-chained audit log

4. Layer 04

   Operations

   • Servers in Indonesia
   • Encrypted backups
   • Staff access only through a justified emergency procedure

Key controls

• Servers in Indonesia

  Clinic data is stored and processed in data centers in Indonesia.

• Encryption

  TLS 1.2+ in transit; sensitive identifiers are encrypted with AES-256-GCM using per-organization keys.

• Per-clinic isolation

  Data is separated per clinic at the database level (row-level security).

• Chained audit log

  Access to and changes of sensitive data are recorded with a hash chain.

• Granular roles and permissions

  Access rights per role and branch; the AI Assistant follows the same permissions.

• Strong authentication

  Two-step verification; SSO and IP allowlist for Enterprise.

• Versioned medical records

  Corrections are stored as a new version with a reason, in line with MoH Regulation 24/2022.

• Controlled staff access

  The Medivana team only accesses clinic data through a recorded, justified emergency procedure. Backups are encrypted.