تخطَّ إلى المحتوى

سياسة الخصوصية

ما تجمعه Infirmy، وأين يُحفَظ، ومن يمكنه الاطّلاع عليه، وكيف تطلب حذفه. مكتوبة كوصفٍ لما يفعله هذا الموقع فعلاً.

آخر تحديث: 2026-09-26

هذه الوثيقة منشورة بالإنجليزية فقط، والنص الإنجليزي هو النص المعتمَد. إذا احتجت إلى شرحها بلغتك، راسِلنا وسيشرحها لك شخص.

What this covers

Infirmy is a marketplace that connects patients travelling for treatment with hospitals and medical facilitators in India. This policy describes what infirmy.com collects, where it is kept, who can see it and what you can ask us to do about it. It describes the site as it is actually built today, not as we intend it to work later.

Infirmy has not opened. No hospital or facilitator on this site has been verified yet, and no patient case has yet been shown to any provider.

The operator of this site is Parve Technologies.

What the case form collects, and why it is health data

If you post a case, the form asks for the condition or diagnosis that needs treating. That is information about your health, and in some countries — including under the EU General Data Protection Regulation and India's Digital Personal Data Protection Act — it is a special or sensitive category that carries extra protection. We treat everything you write in that form on that basis.

A posted case stores:

  • the condition or diagnosis you describe, in your own words
  • the treatment area, and any specific treatment you say a doctor advised
  • who the case is for — yourself, a family member, or someone you are helping
  • when you hope to travel, and the budget range you selected
  • the city you are travelling from and your preferred city in India
  • any free-text clinical notes you add
  • your name, and your email address and/or phone number
  • the language you asked to be answered in
  • the fact that you ticked the consent box, and the date and time we received the case

We keep both the individual fields and a copy of the whole submission as a single JSON record, so that a later change to the form cannot quietly drop something you told us.

We do not ask for, and the form does not have a field for, your passport number, your date of birth, your government identifiers, or your payment details.

We do not accept medical files

You cannot send us a scan, an X-ray, a laboratory result or any other medical document through this website. The case form has no file upload, and we operate no file storage of any kind. We hold no medical images or documents belonging to anybody.

This is deliberate. Medical images and test results are special-category health data, and we are not yet able to hold them to the standard that would require. Until we are, we would rather not have them at all.

From the medical part of the form we store only the text you type: your description of your condition and any clinical notes you add. A hospital that responds to your case will ask you for documents directly, and you would send them to that hospital, not to us.

An earlier version of this form showed an attachment area and then told you your files had been uploaded. They had not been — the file contents never left your browser, and only the file names were stored. That attachment area has been removed rather than fixed, for the reason above. If you posted a case and were told files had been uploaded, assume no file of yours ever reached us.

The other two forms

The provider application, for hospitals and facilitators, stores the organisation name and type, its city, registration and accreditation details as you enter them, specialties, patient volume, languages, and a named contact with their role, email address and phone number. This is business information about an organisation, not patient health data.

A provider's profile stores what the provider writes about itself: its hospitals and their addresses and size, departments, the procedures it offers and any price indication it sets (with the name of the person who set it, which is kept for our records and never shown), its international desk, and three short answers about how it works with patients from abroad. It also stores the doctors a provider chooses to list: name, qualifications, speciality, languages, years in practice and medical council registration number. A provider may list a doctor only after confirming that the doctor agreed; the doctor's name, qualifications and languages are then shown to patients, and the registration number is not. A doctor who wants to be removed can write to the contact address below. Registration and accreditation numbers a provider enters are used only to find its entry on the official register, and are never shown as typed.

What a patient sees of a profile is the copy Infirmy last reviewed, not what is being edited. Everything written by the provider is labelled as provided by the organisation. Only items Infirmy has looked up on an official register are shown as verified, each with the register, the date and a link to the entry. We keep every copy a provider sends for review, so we can see what changed and restore an earlier one.

A provider can send a colleague a link that opens one section of its profile for 7 days, without an account. We store only a one-way fingerprint of that link, not the link itself, together with when it was last used and how many times.

The search alert form stores only the treatment, city and budget you were looking for, and the email address you gave, so that we can tell you when there is something to show you.

Both are stored the same way as a case, with the date and time received.

Accounts, passwords and the session cookie

You can browse Infirmy without an account. You need one to post a case (a patient account) or to apply as a hospital or facilitator (a provider account), and the case or application is linked to it. When you create one, we store your email address (lower-cased), your name, whether you registered as a patient or as a provider, your preferred language, and optionally your organisation name and phone number.

While this site can send email, we confirm the address on your account before you post or apply, by emailing it a 6-digit code. We store a one-way fingerprint of each code, never the code itself, with the address it was sent to and when; a code works once, for 15 minutes, and stops working after 5 wrong tries. We record the time your address was confirmed. The case you post carries the address on your account, not one typed into the form.

You can also create an account or sign in with Google. If you do, Google tells us your name, your email address, whether Google has confirmed that address, and an identifier for your Google account. We ask for nothing else: no contacts, no calendar, no files. We never see your Google password. We store the name, the address and the identifier on your account, and because Google has confirmed the address we do not email you a code to confirm it again. An account made this way has no password of ours.

If an account with that address already exists, we link it to your Google account. If that account's address had never been confirmed, we also discard its password and end every session on it, because whoever created it may not have owned the address. Google learns that you signed in to Infirmy; it is not told what you do here. Nothing from Google is loaded on our pages: your browser contacts Google only when you press the button. While you are away at Google, a cookie that only our server can read, which lasts ten minutes and is deleted when you come back, carries a random value that checks the sign-in returning to us is the one you began. Google's own terms and privacy policy apply on its side.

We never store your password. We store a PBKDF2-SHA256 hash of it, with a random per-account salt and 100,000 iterations. A copy of our database does not contain anyone's password.

When you sign in we set one cookie, named infirmy_session. It holds a random 256-bit token and nothing else — no name, no email, no identifier we could read from it. The cookie is httpOnly (JavaScript on the page cannot read it), SameSite=Lax, marked Secure in production, and it expires after 30 days. Our database stores only a SHA-256 hash of that token, so a leaked copy of the sessions table is not a set of usable logins.

That cookie is strictly necessary to keep you signed in. It is the only cookie this site sets, and if you are not signed in, this site sets no cookies at all.

Signing out deletes the cookie and the session record. Changing your password signs out every other device on the account. There is no password reset yet — see below for whether Infirmy sends email at all.

Email

Infirmy sends email through Resend, a transactional email provider, for three messages only: a 6-digit code that confirms the address on your account, a confirmation when you post a case, which carries the private link to your case, and a notification to a hospital when you have chosen it. The notification to a hospital contains nothing about you or your case — only a link to its own inbox. We do not send marketing email. A posted case is linked to the account that posted it, from the session, never by matching addresses afterwards.

There is still no password reset. If you lose your password, you lose access to that account regardless of whether email is configured — that is a feature we have not built, not a consequence of not sending mail.

Resend is based in United States and processes the message content and recipient address for the three message types above, under a GDPR Article 28 data processing agreement (https://resend.com/legal/dpa, https://resend.com/security/gdpr). If you are in the European Union or the United Kingdom, sending you either of these messages is a transfer of your name and email address outside your region, in addition to the Cloudflare transfer described below.

What your own browser stores

While you fill in the case form or the provider application, your answers are kept in this browser as you type, so that if you reload the page, close it or come back later you carry on where you left off. They are not sent to us until you post or apply. They are kept encrypted, with a key that we give only to your own signed-in account: once you are signed out, what is left on the device cannot be read, even by someone using the same browser. It does not protect against someone who uses this device while your account is still signed in. Your consent ticks are never kept, and nothing is kept while the case form says the patient is under 18.

You can start a case, hospital application or facilitator application before you have an account; you create one, or sign in, on its last step. Until then there is no key to encrypt your answers with, so they are kept unencrypted in this browser tab only, which is what lets them survive a reload or a visit to Google to sign in. The browser deletes them when you close the tab. The moment you have an account they are moved into the store described above, which only your own account can open, and the unencrypted copy is deleted; they are also deleted when you post or apply, press "Start over", or sign out.

A saved form is deleted when you post it, when you press "Start over", and when you sign out on this browser — signing out removes every saved form on it, for every account. Otherwise it stops being readable after 30 days and is removed the next time you visit the site. Your browser may remove it sooner (some browsers clear a site's storage after a few days without a visit), and clearing your browser data removes it at once.

If you save a hospital to your shortlist, that is kept in your browser too. Older versions of this site also kept the reference numbers of cases posted from this browser; the dashboard still shows any it finds, labelled "this browser only". This information stays on your device and is not sent to us, and clearing your browser data removes it.

Your browser also remembers one word, "patient" or "provider", for which side of Infirmy you last used, so that pages show you only the links meant for you. It holds nothing else, is not sent to us, and clearing your browser data removes it.

One more marker is kept for the length of the browser tab's session, to record that you have already been counted as having started the case form so that we do not count you five times. It holds nothing about you and disappears when you close the tab.

Analytics

We use Cloudflare Web Analytics to count visits. It is cookieless: it sets no cookie, writes nothing to your browser's storage, and does not follow you to other sites or build a profile of you. Because of that we do not show a cookie consent banner — there is nothing to consent to.

It records the page you viewed, the page that referred you, your approximate country, and general browser and device type. It does not record your name, your email address, or anything you typed into a form.

Separately, each time someone moves past the first question on the case form, their browser asks us to record one thing: that a form was started, the language of the page, and the time. That request is allowed to carry only those three facts — never an identifier, an address, or anything you typed — and we do not know, and this document does not promise, that every such request is successfully tallied; nothing about posting your case depends on it either way. If it is being tallied, we use it together with how many cases are actually finished, to tell whether the form is too long.

There is no Google Analytics, no advertising pixel, and no session-recording tool on this site.

Where it is stored, and who processes it

Infirmy runs on Cloudflare. The site itself is a Cloudflare Worker, and everything described above is stored in Cloudflare D1, Cloudflare's hosted SQL database. Cloudflare processes this data on our instructions in order to host the service.

Apart from Cloudflare, this site sends data to one other company: Resend, the email provider described in the Email section above, which handles only the message content and recipient address needed to send you a confirmation code or a case confirmation, or send a hospital a lead notification. It loads no third-party scripts, and fonts are served from our own domain, not from a font provider.

If you choose Sign in with Google, your browser goes to Google and back, as described in the Accounts section. Google is not given your case, your condition or anything you type on this site.

Infirmy is operated from India and the hospitals on it are in India, but the database itself runs on Cloudflare D1 in the APAC region, currently served from Singapore, with no regional restriction set on where it may run. If you are in the European Union or the United Kingdom, that is a transfer outside your region regardless of which of these countries your data is stored in.

Who sees your case

The point of Infirmy is to put your case in front of hospitals that can treat you, and that happens in two steps rather than one. No hospital sees anything about your case until you choose it by name.

Step one, matching. When you post, we compare three things from your case with the published profiles of hospitals an operator has approved: the treatment area you chose, the country you would travel from (as a world region), and the language you want to be answered in. Up to three hospitals whose profiles list all three are shown to you, on the confirmation screen and through a private link. This comparison happens inside Infirmy. The hospitals are not told about your case, and they see nothing of it at this step. We record which hospitals were shown to you and how each was ranked, so that we can explain the result to you or to a hospital that asks.

Step two, your choice. Beside each hospital there is a box with a sentence naming that organisation. If you tick it and press the button, that one hospital receives your name, your email address and phone number, the city and country you would travel from, everything you wrote about your condition and your history, and the language you want to be answered in. A hospital you do not tick receives nothing. The same choice is available from your dashboard if you were signed in when you posted.

The private link works without signing in, for 90 days. Anyone who has it can see which hospitals were shown to you and make this choice, so keep it to yourself. We store only a one-way fingerprint of it, not the link itself.

You can withdraw that agreement at any time, in the same place you gave it. Withdrawing stops the hospital reading your case here from that moment. It cannot undo a disclosure that already happened, so if a hospital has already contacted you, ask them to delete what they hold as well — and tell us, and we will ask them too.

We keep a record of each agreement: which case, which organisation, the exact sentence you were shown, the language it was shown in, when you agreed, and when you withdrew. That record exists so that we can show what you were actually asked, rather than describe it afterwards.

As the site stands today, no provider account has been approved, so no real posted case is visible to anybody outside Infirmy. The provider lead inbox shows no cases to anyone who is not an approved provider.

We do not sell personal data, and we do not share it with advertisers or data brokers. We may disclose information where the law requires it.

Provider accounts are approved by a person, by hand, before they could ever see a real lead. Registering as a provider is a claim, not a credential, and an unapproved provider account sees the same closed, empty inbox that a passer-by sees.

How long we keep it

We keep a posted case until you ask us to delete it. We have not yet set a fixed retention period, and we would rather say so than publish a schedule we do not follow.

Your own expired login sessions are cleared out the next time you sign in. We do not yet run a scheduled sweep for accounts that never come back, so a session row can otherwise sit past its expiry date unused. Everything else stays until it is deleted on request.

Asking us to delete your case, and your other rights

You can ask us to delete your case at any time, and we will. Write to hello@infirmy.com with the reference number you were given. Deletion is done by hand: we mark the record deleted first, so that a mistake can be undone, and remove it permanently once you confirm.

You can also ask us for a copy of what we hold about you, ask us to correct it, or withdraw your consent. There is no self-service button for any of this yet — every request is handled by a person, at the same address.

Depending on where you live, the law may give you further rights, including the right to complain to a data protection authority. Being in the European Union, the United Kingdom or India gives you rights under, respectively, the GDPR, the UK GDPR and the Digital Personal Data Protection Act, 2023.

Our lawful basis for holding your case is your consent, which you give explicitly on the form and can withdraw. Our basis for the login cookie is that it is strictly necessary to provide the account you asked for.

Grievance Officer

India's IT Rules, 2021 require us to name a Grievance Officer you can complain to about content or conduct on this site, and to state how quickly we respond.

Grievance Officer: Pratik Bhoir.

Write to hello@infirmy.com to reach them. We acknowledge a complaint within 24 hours of receiving it, and aim to resolve it within 7 days.

This is a separate route from the data-rights request above, though you can use the same address for both — write to us about a deletion, correction or access request the way that section describes, and about anything else through this one.

Children

Infirmy does not accept a case for a patient under 18, and the case form asks and checks this before anything else about the case is collected.

This is a deliberate choice, not an oversight. India's Digital Personal Data Protection Act lets a data fiduciary hold a child's personal data only with verifiable consent from a parent or guardian — evidenced by an identity-and-age check we have no way to perform on a website form. An adult ticking a box that says "I am the parent or guardian" is not that, and the Act's one healthcare carve-out from this rule applies only to a clinical establishment or a registered healthcare professional, not to a marketplace like Infirmy. Rather than hold a child's health information under a promise of consent we could not actually verify, we do not collect it at all.

If the patient turns out to be under 18 partway through a conversation that started here, we still hold nothing about them beyond what this policy already describes for the adult who posted the case.

Changes and contact

If we change how we handle your information, we will change this page and the date at the top of it. For anything in this policy, write to hello@infirmy.com.