Privacy Policy
Last updated: 11 July 2026 · v2
Raktify is operated by Choudhari EduHealth India Foundation, a registered non-profit (NGO-DARPAN MH/2025/0643345, 80G eligible) headquartered in Amravati, Maharashtra, India. This policy explains what personal data we collect when you use Raktify, how we use it, who we share it with, and the rights you have under India’s Digital Personal Data Protection Act 2023 (DPDP Act).
Raktify is free to use. We do not sell personal data, ever. We do not run advertising. The platform is funded by CSR partners and individual donations to the Foundation.
1. Who this policy applies to
This policy applies to everyone who uses Raktify in any capacity:
- Donors who register on the platform to give blood.
- Coordinators — NGO volunteers responsible for a district.
- Hospitals and blood banks that onboard institutionally.
- NGO admins and super admins who operate the platform.
- Camp organisers who host public blood-donation camps.
- Recipients of WhatsApp notifications from the platform.
2. What personal data we collect
2.1 Information you provide directly
- Full name, date of birth, gender, preferred language.
- Mobile number (used for OTP authentication; encrypted at rest).
- Email address (institutional users only).
- Address (village, taluka, district, pincode); GPS coordinates are not collected.
- Self-reported blood group (not used for matching — see Section 5).
- Aadhaar last 4 digits or other government-ID last 4 digits for coordinator verification (full Aadhaar number is never collected).
2.2 Information generated by your interactions
- Donation history (dates, components, volumes, blood bank). Donations are recorded by the blood bank at which you donate.
- Lab-verified blood group (written only by the blood bank’s verified staff).
- Transfusion-transmissible-infection (TTI) screening verdict per donation. Field-level test results never leave the blood bank’s screening interface.
- Eligibility status, deferral state and next-eligible date.
- Consent records — when you gave or withdrew consent, and for what purposes.
- Camp registration / RSVP history.
- Notification delivery logs (sent, delivered, read; for service reliability).
2.3 Information collected automatically
- IP address and approximate location of every authenticated request, for audit and abuse prevention.
- Browser type and PWA version, for compatibility.
- A locally-stored authentication token (JWT) in your browser’s localStorage so you stay signed in. Cleared on logout.
- An IndexedDB outbox that queues your availability toggles offline; replays automatically when you reconnect.
3. Why we collect each category
Every row below is the strict legal basis under the DPDP Act for each data category:
| Data | Purpose | Lawful basis (DPDP Act, Section 7) |
|---|---|---|
| Mobile + name + DOB | Authenticate the donor; match them to emergency requests | Consent + legitimate use (medical emergency) |
| Verified blood group | Determine compatibility with patient’s requested group | Consent (granted during donor registration) |
| Donation history + TTI verdict | Enforce deferral periods; safety of recipients | Legitimate use (statutory: Drugs & Cosmetics Act, 1940 / blood-bank regulations) |
| IP & device info | Audit log, abuse prevention | Legitimate use (security) |
| Camp RSVPs | Roster the donor for the camp organiser; remind them of the date | Consent (you RSVP'd) |
4. How we protect your data
Raktify is engineered as a life-critical healthcare system. Patient safety and donor privacy are enforced at the database layer, not just in application code:
- Row-Level Security (RLS) on every table. A coordinator from one district cannot read another district’s data even with valid credentials.
- Two-key hybrid encryption. Free-text PII (name, address) is encrypted with one AES-256-GCM key; TTI screening data with a separate key. A compromised application server cannot decrypt TTI data without separately compromising the screening key.
- Hash-chained audit log. Every state change in the system is appended to an immutable, SHA-256-chained audit log. Backdating or tampering breaks the chain and is detected automatically.
- Mobile masking. Your phone number is encrypted at rest and never returned to hospital users in API responses. Hospitals see
+91XXXXX1234at most. - TLS everywhere. All data in transit between your device, Raktify, and any third party is encrypted via TLS 1.2 or higher.
- Data residency. All Raktify data is hosted in Microsoft Azure’s Central India region (Pune).
5. The “self-reported blood group never used in matching” invariant
Donors enter their own blood group during registration so the platform can show it to them with an “Unverified” badge. This self-reported value is never queried by the matching engine. Only the lab-verified blood group — writable solely by an authenticated blood-bank user — is used for matching donors to emergency requests. This is a hard-coded rule in the matching algorithm and is enforced at the database layer.
6. Who we share your data with
We share only what is necessary, only with the parties listed below, and only for the purposes listed below:
- Coordinators in your district — see your name and blood group when activating donors for an emergency request, never your mobile number directly. All communication is mediated by the platform.
- The blood bank where you donate — has full access to your donation record at that bank, your verified blood group, your eligibility state, and your TTI screening results.
- The hospital you respond to (if any) — sees only that someone with the right blood group is willing to donate; never your name or contact.
- Camp organisers (when you RSVP) — see your name and blood group; mobile number is never shared.
- Choudhari EduHealth India Foundation operations team — for audit, abuse investigation, and grievance redressal.
6.1 Third-party processors
We use the following sub-processors. All are bound by data-processing agreements and, where applicable, India-resident or covered by standard contractual clauses:
- Microsoft Azure (Central India) — cloud hosting, database, secrets management.
- Meta Platforms Ireland — WhatsApp message delivery via Cloud API. Meta receives your mobile number and the template message content; Meta does not see your other personal data.
We do not share your data with advertising networks, data brokers, or analytics providers that track individual users across the web.
7. Your rights under DPDP Act 2023
You have the following rights, and we will honour each within 30 days of a valid request:
- Right to access — a copy of all personal data we hold about you, in a machine-readable format.
- Right to correction — fix any incorrect or outdated information.
- Right to erasure — see our Data deletion page for the precise process and what we cannot delete (audit records mandated by law are anonymised at source and access-restricted).
- Right to withdraw consent — at any time, from the donor dashboard or by emailing us. Withdrawal does not affect the lawfulness of prior processing.
- Right to nominate — designate someone to exercise your rights on your behalf, including in the event of death or incapacity.
- Right to grievance redressal — see Section 11 for our Grievance Officer contact.
8. Data retention
- Active donor profile — retained while your account is active and for 12 months after your last activity, after which we proactively contact you to reconfirm consent.
- Donation history at a blood bank — retained by the blood bank per Drugs & Cosmetics Act requirements (typically 5 years). On erasure, we anonymise the link between you and the records — the records themselves cannot be destroyed by law.
- TTI screening results — retained for 7 years per public-health-traceability requirements (lookback registry).
- Audit log entries — the audit log is append-only and hash-chained: entries cannot be edited or selectively deleted, so individual fields are never nulled out. Entries are tightly access-restricted, never shown to other users, and retained under our 7-year audit-retention policy, after which they are purged in full.
- Notification logs — the personal content (message variables and any external mobile number) is automatically scrubbed after 90 days; only anonymous delivery statistics are kept beyond that, for service-reliability reporting.
9. Children’s data
You must be 18 years or older to donate blood and to register as a donor on Raktify. We do not knowingly collect data from children under 18.
We do hold data about minors enrolled in our thalassemia patient registry. That data is added by a treating hospital or an authorised guardian; it is gated by Row-Level Security so only the treating hospital, the patient’s assigned coordinator, and NGO admins can see it. The guardian’s mobile number is the only contact channel and is held under the same encryption and access controls as a donor’s.
10. International data transfers
Raktify data is stored in Microsoft Azure’s Central India (Pune) region. Some third-party processors (notably Meta for WhatsApp delivery) operate outside India. The Government of India has designated specific countries as restricted; we will update this policy if any of our processors are added to that list.
11. Grievance redressal
If you have a concern about your data, a complaint about how we’ve handled it, or you wish to exercise any of the rights in Section 7:
Grievance Officer: Gaurav R. Choudhari
Email: contact@choudhari.ngo
Phone: +91 98505 41412
Address: Choudhari EduHealth India Foundation, 54, 2nd Lane, Rathi Nagar, VMV Road, Amravati, Maharashtra 444603
We will acknowledge your grievance within 72 hours and resolve it within 30 days. If you are not satisfied with our response, you may approach the Data Protection Board of India under DPDP Act 2023.
12. Changes to this policy
When we change this policy, we will update the “Last updated” date at the top of this page. Material changes will be announced via in-app notification and (for institutional users) by email. Continued use of Raktify after a change constitutes acceptance.