HIPAA safeguard mapping

• Role-based access: patient, clinic owner, clinic staff, moderator, support, compliance and administrator are separate roles with separate permissions.
• Least privilege: SynQ staff roles can see access records and system events, not your clinical content.
• Human approval: sensitive clinical and AI actions require a named person to approve them before they take effect.
• Change control: every clinical text version records its author, reviewer and publication time.

• Unique account per person, with sign-out on this device or on every device.
• Device lock after a quiet period, so an unattended screen does not stay open.
• Encryption in transit for every connection between you, SynQ and the clinic.
• Documents stored privately, screened before they can be opened, and served through short-lived links after an ownership check on the server.
• Audit trail of every privileged access and administrative action, which cannot be edited or deleted.

Hosting and database services run on managed infrastructure with the provider's own physical controls. Tenant separation is enforced in the database itself: a clinic can only read rows belonging to that clinic, and a patient can only read their own.

A clinic sees what you send it and nothing more. A booking request carries the time, your reference and what you chose to describe. Documents reach a clinic only through a share you create, with an expiry you can see and withdraw.