Security

Last updated: July 2026

Built for health data

Your Clinic Heart was built from day 1 to handle protected health information (PHI) with the practices HIPAA requires. We store only administrative data; clinical data lives in the clinic's EHR.

Per-clinic isolation (multi-tenant)

Each clinic is an isolated tenant. Beyond filtering by clinic in the application, we enforce isolation at the database level with PostgreSQL Row-Level Security (RLS), so one clinic can never see another's data.

Encryption and access control

Information travels encrypted (TLS) and is stored encrypted at rest. Access is role-based (administrator, reception, operator) and sensitive actions are audit-logged. We do not include PHI in URLs, logs, or analytics.

PHI stays home

PHI lives only on our platform (hosting and database on Fly.io, under a Business Associate Agreement). Outgoing messages (email/SMS) carry no health information: they are a neutral notice with date, time, and a secure link — appointment details are served by our platform when the link is opened. This way, messaging providers never see PHI.

Payments without exposing cards

We never store card numbers. Validation and charging are handled by Stripe; we only store a secure token.

Contact

Reporting a security issue? Write to hello@yourclinicheart.com.