Security Policy

We design Careflow with defense-in-depth: secure defaults, least privilege, multi-tenant isolation, and continuous improvement.

• HTTPS/TLS for data in transit
• Password hashing for credentials (not stored in plain text)
• Session-based authentication with role awareness
• Clinic-scoped authorization on API and database queries
• Input validation on API boundaries
• Separation of platform admin authentication from clinic authentication

Clinical and business records are associated with a clinic identifier. Application queries are scoped to the active clinic to reduce the risk of cross-tenant data exposure.

We use reputable cloud and database providers. Access to production systems is limited to authorized personnel. Backups and operational monitoring are used to support availability and recovery.

When clinics enable WhatsApp Business messaging, message content is transmitted through Meta's official APIs under the clinic's configuration. Payment data is handled by payment processors; Careflow does not store full card numbers on its servers.

We investigate suspected security incidents, contain impact, and notify affected clinics when legally required or contractually obligated, with information reasonably available at the time.

Use strong passwords, manage staff access, keep devices updated, and report suspected compromise promptly to support.

Email [email protected] with a responsible disclosure description. Do not access other tenants' data while testing.