Privacy policy

The hospital is the controller of its patients' records. We are a processor acting on the hospital's instructions — we do not decide what is collected or what it is used for, and we do not use it for our own purposes.

For the small amount of data we collect directly — a sales enquiry, a support request — we are the controller.

• Patient demographics, contact details and identifiers issued by the hospital
• Clinical records: consultations, prescriptions, lab and imaging results, admissions, nursing observations
• Financial records: invoices, payments, refunds, insurance claims
• Staff accounts: name, work email, role, department
• An audit entry for every write, recording who acted, on what, and when

We do not collect behavioural analytics inside the clinical application, and we do not place advertising or tracking technology anywhere in it.

Access is scoped to one of thirteen roles and enforced in the database, not merely hidden in the interface. A request that should not return a record does not return it, whichever client made it.

Our own staff do not browse hospital data. Access for support is granted by the hospital, limited in time and scope, and recorded in the same audit trail as any other access.

Each hospital runs against its own database instance with its own credentials, hosted in Google Cloud regions in India. There is no shared table with a tenant column, so there is no query that can cross from one hospital to another.

Data is encrypted in transit and at rest. Passwords are stored only as salted hashes and can never be read back by us or by hospital staff — a forgotten password is reset, not looked up.

Clinical records are retained for as long as the hospital's own retention obligations require — in India, commonly three years from the last entry, and longer for minors and medico-legal cases. The hospital sets the period; we do not delete clinical data on our own initiative.

If a hospital ends its contract, we export everything in a machine-readable format and delete our copies within 30 days of the export being confirmed.

• Ask for a copy of your record
• Ask for a factual error to be corrected
• Ask who has accessed your record and when
• Withdraw consent for any optional processing, such as appointment reminders

These requests go to your hospital, not to us — they hold the relationship and the legal duty. If a hospital asks us to help fulfil one, we will.

We use Google Cloud Platform for hosting and authentication, and Cloudflare R2 for document and image storage. Both are bound by data processing terms. We publish any change to this list to hospital administrators at least 30 days before it takes effect.

If we become aware of unauthorised access to hospital data, we will notify the affected hospital without undue delay and in any case within 72 hours, with what we know, what we do not yet know, and what we are doing about it. We will not wait until the picture is complete before telling you there is a problem.

Questions about this policy, or about how we handle data, go to sales@ecogeniustech.in. Postal enquiries: Unit 101, Oxford Towers, 139 HAL Old Airport Road, Hulsur Bazaar, Bangalore, Karnataka 560008.