Privacy Policy
1. Who we are, and the roles
SoftClinic GenX HIMS is operated by your healthcare facility and supplied by JVS Technologies Private Limited. Under the Digital Personal Data Protection Act, 2023:
- the healthcare facility (our tenant) is the Data Fiduciary — it decides why data is processed and operates the software;
- JVS is the Data Processor — we process data on the facility's instructions;
- the patient is the Data Principal — their data is processed through the software by facility staff, though the patient does not use the software directly.
2. What the software processes, and why
Two kinds of personal data pass through the software, and nothing else — there is no advertising, profiling, analytics or telemetry in this system.
(a) Your staff account data. So authorised users can sign in with least-privilege access and be attributed in the audit trail:
| Category | Handling |
|---|---|
| Staff name, email/login, assigned role, and (for a clinician) the linked HPR / doctor identity | Stored to operate the account and the audit trail |
| Account password | Stored only as a salted one-way hash — never in plain text, never recoverable |
(b) Patient data the facility handles via ABDM. Only what ABDM functions require — creating and verifying a patient's ABHA, sharing their health records with their consent, and retrieving records the patient has consented to share:
| Category | Handling |
|---|---|
| Patient name, mobile, email, address, photo, ABHA number and address, health records and their attachments | Encrypted at rest (AES-256-GCM) |
| Gender, date of birth, PIN/district/state, hospital record number | Stored unencrypted — held as administrative data |
| Aadhaar number and OTP | Never stored. Encrypted in transit to ABDM only, and never written to any database or log |
3. Consent
The facility is responsible for obtaining the patient's informed consent. An ABHA is created only after the patient accepts the ABDM enrolment declarations, and health records are shared only under a consent the patient grants in their own ABHA/PHR application — this software never assumes or creates consent on a patient's behalf. No record is released without an active, unexpired consent covering that exact record type and date range, and a consent that has been revoked, denied or expired cannot be reactivated. The consent controls in the software record that decision; they do not make it.
4. How the software protects data
- Encryption at rest (AES-256-GCM). The application refuses to start with this disabled.
- TLS 1.2/1.3 only in transit; older protocols are rejected.
- Health records exchanged with ABDM are additionally end-to-end encrypted (ABDM Fidelius).
- Role-based access, least-privilege by default, per-doctor record isolation, and strict separation between facilities (tenants).
- An append-only, tamper-evident audit trail that records who did what — and deliberately stores no passwords, OTPs, tokens, Aadhaar values or record contents.
5. Where it is stored, and for how long
All data is stored in India, in a private-network Microsoft Azure database. Records fetched from other hospitals are held in memory only and become inaccessible after 60 minutes — they are never written to disk. Records a facility created are kept under that facility's own clinical retention obligations. Staff account records are kept while the account is active. Erasure is possible on request (see §7).
6. Who else receives it
| Recipient | What they receive |
|---|---|
| ABDM / National Health Authority | The data ABDM requires — this is the purpose of the ABDM features |
| Microsoft Azure (India) | Hosting and storage |
| SMS provider (MSG91) | Mobile number and OTP only. No ABHA, no health data. India only |
We do not sell data, and no personal data is transferred outside India.
7. Rights
Your facility and its staff may, through JVS:
- Access and correct staff account details, and add or revoke staff access.
- Erasure — on request, records are permanently deleted. Two honest limits: the tamper-evident audit log and the raw gateway message log are not erased — the first must stay immutable to remain trustworthy, the second is not searchable by patient identity.
- Grievance — see §8. A facility may also complain to the Data Protection Board of India.
Patients exercise their rights over their own health data directly — access, correction, nomination and consent management through their own ABHA/PHR application (a hospital cannot change a patient's ABHA mobile or KYC-locked fields), and requests to the facility that treated them, which holds the primary obligation to them as Data Fiduciary.
8. Grievance Officer
Mr. Kirtan Valani, Grievance Officer
Email: operations@jvsgroup.com
Telephone: +91 90999 03150
For a complaint about a patient's personal data, the patient should normally contact the healthcare facility that treated them — it is the Data Fiduciary and holds the primary obligation. Facilities and their staff may contact our Grievance Officer at any time.
9. Breach notification
We will notify the Data Protection Board of India and affected parties of a personal data breach as required by §8(6) of the DPDP Act.
10. Changes
The version and date appear at the top of this page. Material changes will be notified to operating facilities.