Security & data protection

Patient records, kept safe.

How Leap Care protects clinic and patient data: encryption, clinic isolation, access control, audit trails, and what happens if something goes wrong.

Last updated · 16 November 2026

Section 01

How we think about security

Clinics trust Leap Care with patient records, so security is built into how the product works rather than added later. Leap Care is built and run by smritix AI LLP, India, on the same platform as our other products. This page lists what we actually do today — nothing aspirational.

Section 02

Encryption

  • TLS 1.2 or higher on every connection, with HSTS — no unencrypted traffic accepted.
  • Secrets stored at rest — WhatsApp access tokens, telephony and payment credentials, webhook signing keys — are encrypted with AES-256-GCM before they reach the database, and decrypted only in memory on the server.
  • Encrypted database backups.
  • No plaintext secrets in application logs, and no secrets in source control.
Section 03

Clinic isolation and access control

  • Every database query is scoped to one clinic's workspace; one clinic can never read another's patients.
  • Every signed-in request is checked against the person's membership of that workspace.
  • Team roles limit who can see and change what, and clinical notes have their own access setting so front-desk staff see only what they need.
  • Call recordings and uploaded reports are stored privately and opened only through short-lived links after a permission check.
Section 04

Integrations and API

  • API keys are stored as hashes — the raw key is shown once and never stored — with scoped permissions, and can be revoked at any time.
  • Outgoing webhooks are signed with HMAC-SHA256 with replay protection; incoming webhooks (WhatsApp, payments, telephony) are verified by signature or secret before they are processed.
  • Sign-in and public endpoints are rate-limited, and forms are protected against bots.
Section 05

Audit trail

Significant actions — sign-ins, changes to records, billing events — are written to a structured activity log scoped to the clinic's workspace, recording who did what and when. Each clinic sees only its own log.

Section 06

Infrastructure

Application servers and the primary PostgreSQL database run on Railway in the EU (Netherlands). Production, staging and development use separate credentials, and debug tooling is disabled in production. The full list of providers that process data is in our Privacy Policy.

Data protection law

We handle personal data under India's Digital Personal Data Protection Act, 2023. The clinic is the Data Fiduciary for its patients' data and smritix AI LLP is its Data Processor, under our Data Processing Agreement.

Section 07

If something goes wrong

If a personal data breach happens, we inform affected clinics at once, notify the Data Protection Board of India and affected people without delay, and send the Board a detailed report within 72 hours, as the DPDP Rules require.

Section 08

Reporting a vulnerability

Found a security issue? Email support@leapcare.in with “Security” in the subject and steps to reproduce. Please don't access patient data or disrupt the service while testing. We work with researchers, not against them.

  • Within 24 hours — we acknowledge your report.
  • Within 72 hours — we reproduce it, assess severity and share initial findings.
  • Within 7 days — critical issues are fixed and deployed, and we tell you when the fix is live.