Privacy Policy

Last updated 29 October 2026

Draft pending legal review. This page is not final.

This policy explains what information Ojira collects, why, who else sees it, and the choices you have. It covers two different situations: people who visit our website or ask for a demo, and hospitals that use the Ojira software for their patients.

1. Who is responsible for what

Website visitors and demo requests: Ojira decides why and how this information is used, so Ojira is the "data fiduciary" (the controller).

Hospital and patient data: when a hospital or clinic uses Ojira, the hospital decides what patient data is entered and why. Ojira only stores and processes it on the hospital’s behalf, as a "data processor". The hospital is the data fiduciary for its patients and staff, and is responsible for getting patients’ consent and for answering patients’ requests. If you are a patient and want to see or correct your records, please ask your hospital first.

2. What we collect

On the public website:

  • Demo request form: your name, hospital or clinic, phone, email, hospital size and any note you write. We also store the IP address the request came from, only to stop spam and abuse.
  • We do not use advertising or analytics trackers on the website.

Inside the software (entered by the hospital’s staff):

  • Patient details: name, age, gender, phone, address and similar registration details.
  • Health information: visits, doctor notes, diagnoses, prescriptions, lab orders and reports, bed and admission records, insurance claims and discharge summaries.
  • Billing: charges, payments, pharmacy bills and stock.
  • Staff accounts: name, email, role and a password stored only as a one-way hash.
  • Audit trail: which staff member did what and when, with the IP address. It cannot be edited or deleted from inside the software.

3. How we use it

  • To run the software for the hospital: queues, results, prescriptions, billing, insurance and messages.
  • To contact you about a demo you asked for.
  • To keep the service secure, find misuse and keep backups.
  • To meet legal duties.

We do not sell personal information and we do not use patient data for advertising.

4. Who else handles the data

Some features send limited data to outside service providers. Each is used only for the feature named.

  • Our hosting and database provider, where the data is stored.
  • WhatsApp messages (a feature the hospital switches on): the message and the patient’s phone number go to Meta (WhatsApp Business Cloud API) or Twilio, whichever the hospital connects.
  • Pharmacy bill scanning and voice dictation parsing (optional, off until the hospital adds a key): the bill image or the dictated text goes to Anthropic, which processes it to return the result.
  • Voice typing for prescriptions uses the speech feature built into your browser. In Chrome this sends audio to Google. Doctors can type instead.
  • Staff push notifications use Google Firebase Cloud Messaging.
  • Online payments, if the hospital turns them on, use Razorpay. UPI QR codes are drawn on the device and are not sent to anyone.
  • The website loads fonts from Google Fonts, so Google can see a visitor’s IP address.
  • Authorities, when the law requires it.

5. How long we keep it

Demo requests are kept until we have answered them and for a reasonable period after, then deleted on request.

Hospital records stay for as long as the hospital has an account, because medical and billing records often must be kept for years. When a hospital leaves, it can ask for an export and for deletion, subject to any record-keeping duty. Database backups are kept for 14 days and then removed.

6. How we protect it

No system is perfectly secure. If we learn of a breach that affects personal data, we will tell the affected hospital without undue delay so it can meet its own duties, and we will notify the authorities as the law requires.

  • Each hospital’s data is kept separate from other hospitals’.
  • Staff only see the screens their role allows. The hospital head can switch whole modules off.
  • Passwords are hashed. Sign-in uses expiring tokens.
  • Every important action is written to an audit trail.
  • Daily database backups.

7. Your rights

Under India’s Digital Personal Data Protection Act, 2023 you may ask to access, correct, complete or erase your personal data, withdraw consent, and have your grievance heard. For website and demo data, write to us at the address below. For patient data, ask the hospital that treated you; we will help the hospital respond.

8. Children

Hospitals record children’s health information as part of treatment. For patients under 18, the hospital is responsible for getting a parent’s or guardian’s consent. Our website is not aimed at children.

9. Cookies and local storage

We use only what the software needs to work: a sign-in cookie and a small cookie holding your role and display name, plus browser storage for preferences such as language and the collapsed menu. We do not use advertising cookies.

10. Changes to this policy

If we change this policy in a way that matters, we will update the date on this page and tell hospitals using the software.

11. Contact

Ojira.

Also read our Terms of Service.