Security built around the least patient data possible

Swarna Shivansh only needs to know that a visit happened, where and how to reach the patient. The rest of the design follows from that.

How the platform is designed. Controls described as they are built, not as audit results.

Minimal patient data

Appointment events are processed to send a request. Contact details are not stored with clinical identifiers, and clinical notes are never read.

Encryption

Designed for TLS 1.3 in transit and AES 256 encryption at rest for customer data.

No public model training

Customer reviews, replies and data are not used to train public models.

Access control

Role based permissions, multi factor authentication and SAML single sign on.

Audit trail

Every draft, edit, approval and publish is logged with who did it and when.

Human approval

No public reply is published without a person your organization authorizes.

Security questions

Is Swarna Shivansh SOC 2 certified?
Not yet. We have not completed a SOC 2 audit. Send security questionnaires to security@swarnashivansh.com and we will answer them in full.
Where is data hosted?
We confirm hosting regions and subprocessors in the subprocessor list and in your agreement.
How do I report a vulnerability?
Email security@swarnashivansh.com. Our security.txt file lists the contact and policy.
Do you sign a BAA?
Yes. A business associate agreement is available on request before any practice system is connected.