Security & Compliance
Effective Date: 17th August 2026 | Last Updated: 18th August 2026
SwasthyaLink is operated by SGV VENTURES PRIVATE LIMITED. The confidentiality, integrity, and availability of patient health information are foundational to our design. This page describes the security controls we operate today and those on our roadmap, stated honestly so you can verify them.
Platform Hardening
LiteSpeed + CloudLinux (CageFS/LVE) isolation, ModSecurity WAF & cPGuard malware scanning provided by our hosting platform
Field Encryption
AES-256-GCM content encryption for sensitive PHI
RS256 Auth
Asymmetric signed tokens, 24-hour access lifespan
No-Training AI
Health data is not used to train AI models
1. Hosting & Platform Hardening
Our application is hosted on the DomainRacer platform (LiteSpeed web server with cPanel). The following infrastructure-level protections are provided by that hosting stack:
Kernel-level resource isolation (LVE) prevents cross-account resource starvation and limits privilege escalation between accounts.
Per-account virtualized filesystem limits directory traversal and unauthorized file access.
A web application firewall (ModSecurity) at the hosting layer filters common web exploits (SQLi, XSS, etc.) before requests reach the application.
The hosting platform's active security suite (cPGuard) performs malware scanning and brute-force/intrusion protection at the server layer.
HTTPS/TLS is provisioned and renewed by the platform; IP Blocker, Hotlink Protection, and Leech Protection provide additional access controls.
These are platform-provided controls. We do not operate the hypervisor, WAF, or malware scanner ourselves; they are part of the managed hosting environment (DomainRacer, LiteSpeed + cPanel). Our application-layer controls below provide defense in depth.
2. Encryption of Data
- In Transit: All traffic to
swasthyalink.co.inandapp.swasthyalink.co.inis served over HTTPS/TLS, provisioned and renewed by our hosting platform. - Field-Level Encryption at Rest (AES-256-GCM): Sensitive personal-health fields — chat messages, AI copilot transcripts, and emergency-contact details — are encrypted at the application layer using AES-256-GCM before they are written to the database. Decryption occurs only within authenticated server-side processing.
- Key Management: The field-encryption key is configured via environment on the server. We are evaluating moving to a dedicated secrets manager / KMS so the key is stored separately from the database.
3. Identity, Authentication & Access
- Authentication: Sign-in uses Google OAuth 2.0 (OpenID Connect) and time-bound OTP verification. Passwordless by design.
- Token Signing (RS256): Access tokens are signed with the RS256 (RSA) algorithm using an asymmetric key pair; short-lived (24-hour) access tokens bound to the authenticated session.
- Role-Based Access Control (RBAC): Patients, Doctors (RMPs), Pharmacies, and Diagnostic Centers have role-scoped access; clinical and health data is reachable only by roles relevant to the care interaction.
- Consent Gating: Users must open and accept the Terms of Use and Privacy Policy during onboarding; acceptance is recorded with a timestamp for evidentiary purposes.
4. Audit Logging
We maintain an append-only audit trail of key events (profile completion, consent acceptance, and other security-relevant actions), recording the actor, action, target, source IP, and a tamper-evidence hash. Retention is set to at least 180 days in alignment with CERT-In direction 20(21)/2022. Incident-response procedures are in place to notify affected users and authorities as required.
5. AI Processing Privacy
6. ABDM / Health Interoperability
SwasthyaLink is designed to align with the Ayushman Bharat Digital Mission (ABDM) framework for health-record interoperability. Current status: ABDM integration is in sandbox / evaluation mode (NHA development environment); no production health-record exchange is active yet.
On our roadmap (pending production credentialing and NHA approval):
- Production ABDM HIP/HIU onboarding with FHIR-based health-record exchange per NHA specifications.
- Curve25519 (ECDH) key exchange for ABDM health-data consent flows.
- DigiLocker integration for verified document and certificate fetch.
7. Data Residency
SwasthyaLink operates from infrastructure located in India. Personal and health data of Indian users is stored on servers within India.
8. Vulnerability Disclosure Program (VDP)
- Report suspected vulnerabilities to security@swasthyalink.co.in.
- Do not access, modify, or exfiltrate other users' data.
- Allow a reasonable remediation window before public disclosure.
9. Security Contact Desk
Company: SGV VENTURES PRIVATE LIMITED
Security Incidents: security@swasthyalink.co.in
Privacy / Grievance: privacy@swasthyalink.co.in · grievance@swasthyalink.co.in
10. Security Roadmap
Transparency note: the following are planned enhancements we intend to implement and will update here once live:
- External secrets manager / KMS for encryption-key isolation from the database.
- Production ABDM HIP/HIU onboarding (FHIR R4 exchange per NHA specs).
- Refresh-token rotation and shorter access-token lifetimes.
- Automated CERT-In-aligned incident reporting pipeline.