Legal
Privacy policy
MyParcha handles health data, which is the most sensitive category of personal data there is. This page says what we do with it in specific terms, including the parts that are not flattering.
Last updated 26 August 2026
1. Who is responsible
This service is operated by MyParcha Innovations, a sole proprietorship registered in India, at Plot No. 419, A Block, Dayal Residency, Faizabad Road, Chinhat, Lucknow, Uttar Pradesh 226028, India. In this policy “we”, “us” and “MyParcha” mean that entity.
This policy is written to the Digital Personal Data Protection Act, 2023 (DPDP Act) and the Information Technology Act, 2000 together with the rules made under it.
2. Two different relationships — read this first
MyParcha sits in two distinct positions, and your rights differ depending on which one applies to you.
- When a clinic, lab or hospital uses MyParcha, that organisation decides what is collected and why. It is the Data Fiduciary for its patients; we are its Data Processor and act on its instructions. If you are a patient of such a clinic, your first point of contact is the clinic — though you may always write to us and we will help.
- When you use MyParcha directly — /decode, /my, or the enquiry form — we are the Data Fiduciary and the whole of this policy applies to us directly.
3. What we collect
Health data. Images of medical documents — prescriptions, lab reports, discharge summaries, hospital bills — and the structured data read from them: medicines, dosages, lab values, dates, diagnoses, procedures and amounts.
Identifiers. A patient’s name, mobile number, age and sex, where a clinic records them or where a patient supplies them to reach their own records.
Account data for clinic staff: name, work email, the organisation they belong to and their role.
Enquiry data that you type into the contact form: name, work email, organisation and what you wrote.
Operational logs. IP address, timestamps and request metadata, kept to run the service, apply rate limits and investigate abuse or a security incident.
We do not sell personal data. We do not use health data for advertising, and we do not build advertising profiles of anyone.
4. The free decode tool, specifically
A photograph uploaded to /decode is not stored.
It is held in memory for the length of the request, read, and discarded. No record row is created and no file is written to storage. The tool is rate limited by IP address, and that rate-limit counter is the only thing that persists.
The single exception is if you choose to create a share link for a decoded result. That is an explicit action, and only then is anything saved.
While the image is being read, it is sent to our machine-reading provider — see section 6. It is not stored by us either way.
5. Why we process it
- To read a document and return structured data — the service you or your clinic asked for.
- To let clinic staff review and correct anything the system was not confident about.
- To let a patient reach a copy of their own record, and to verify a document is unaltered.
- To keep an audit trail of who accessed or changed a record, which is a safety requirement, not an optional feature.
- To secure the service — rate limiting, abuse prevention, incident investigation.
- To reply to you if you contact us.
Where we act as a Data Fiduciary, we process personal data on the basis of your consent, or for the legitimate uses permitted by the DPDP Act. You may withdraw consent at any time — see section 9.
6. Where the data lives, and the one edge that leaves India
Our database, our document storage, our web application and our processing worker all run in Indian regions — Mumbai and Bangalore. Backups stay in India and are encrypted.
One processing step currently sends document images outside India.
Machine reading of a document image is performed by Google’s Gemini API. At present that request is served from outside India, which means the image — and therefore the health data on it — crosses a border for the duration of that call. We are disclosing this rather than burying it in a service description, because it is the first thing any honest review would ask about.
What we are doing about it, in order:
- Moving to an India-region endpoint for this provider as soon as one is available to us.
- Redacting patient identifiers from the image before it is sent, so that what leaves is clinical content rather than an identifiable person.
- A zero-retention commitment from the provider, confirmed in writing.
Until that first item is done, this remains true and this page will say so. When it changes, this paragraph changes with it.
7. Who else can see it
We use the following processors. Each is bound to process data only on our instructions, and only for the purpose named.
| Processor | Purpose | Location | Health data |
|---|---|---|---|
| Supabase | Managed Postgres database and object storage | Mumbai, India | Yes |
| Vercel | Web application hosting | Mumbai, India (bom1) | Yes |
| DigitalOcean | Document-processing worker, backups | Bangalore, India (blr1) | Yes |
| Google (Gemini API) | Machine reading of document images | Outside India — see the cross-border note below | Yes |
| Resend | Transactional email delivery | Outside India | No |
Beyond these, we disclose personal data only where the law compels it, and we will tell the person concerned unless we are prohibited from doing so.
8. How long we keep it
- Clinical records held for a clinic — for as long as that clinic’s account is active, and thereafter as required by applicable medical record-keeping rules. A clinic may ask us to export and then delete its data.
- Free decode uploads — not retained at all.
- Enquiry form submissions — kept while we are in correspondence with you, and deleted on request.
- Operational logs — a rolling window, kept only as long as needed for security and reliability.
- Audit trails — retained for the life of the associated record, because their purpose is to remain checkable afterwards.
9. Your rights
Under the DPDP Act you may:
- Ask what personal data of yours we hold and how it is being processed.
- Have inaccurate or incomplete data corrected, updated or completed.
- Ask for erasure, where we are not required to keep it by law.
- Nominate another person to exercise these rights on your behalf if you are unable to.
- Withdraw consent, as easily as you gave it. Withdrawal does not undo processing already carried out lawfully.
- Have a grievance heard and answered — see section 12.
To exercise any of these, write to [email protected]. We will respond within a reasonable period and in any case within the time the law allows. Where a clinic is the Data Fiduciary for your record, we will forward your request to them and support them in answering it.
10. How it is protected
Encryption in transit, private storage with short-lived signed access, strict separation between organisations so one clinic can never read another’s records, role-based access for staff, and an audit trail on access to records. The controls are set out in full at /security, along with what has not been done yet.
11. Children
MyParcha is not offered directly to children. Where a clinic records a child’s medical document, the clinic obtains consent from the parent or lawful guardian as part of treatment. We do not track children, do not target advertising at anyone, and do not process a child’s data in any way likely to cause a detrimental effect on their wellbeing.
12. Grievance redressal
If you are unhappy with how your data has been handled, tell us and we will answer. The full procedure, including escalation, is at /grievance.
- Grievance Officer
- Aditya Kumar Singh
- [email protected]
- Telephone
- +91 63873 33961
- Post
- Plot No. 419, A Block, Dayal ResidencyFaizabad Road, ChinhatLucknow, Uttar Pradesh 226028India
If our answer does not satisfy you, you may complain to the Data Protection Board of India under the DPDP Act.
13. Changes
When this policy changes materially we will update the date at the top and, where the change affects how health data is handled, tell affected clinics directly. We do not make a change quietly and rely on you re-reading the page.