1. Who we are
Patient-Tap (“we”, “us”) is operated by Team Vishwakarma gng, an independent student team building Patient-Tap for CODEAMBLE 2026, based in Pune, Maharashtra, India. For personal data processed through our services we act as the Data Fiduciary under the Digital Personal Data Protection Act, 2023 (“DPDP Act”).
Patient-Tap is currently a prototype being demonstrated at CODEAMBLE 2026. Some features described here are still being built; this policy describes how they work or will work, and we will update it before anything changes materially.
Contact for privacy questions: privacy@patient-tap.shop. Our Grievance Officer is listed in section 12.
2. What this policy covers
This policy covers:
- this website, including its forms (waitlist, contact, medicine reports);
- MedVerify, the medicine-verification tool at /verify;
- the web demo at /app and the blood/organ donation tools at /donate;
- the Patient-Tap Android app and the NFC tags (wristbands, cards, keychains) it writes to.
Websites we link to — such as e-RaktKosh, NOTTO or a payment page — have their own policies, which we don't control.
3. Data we collect on this website
| What | Why | Kept for |
|---|---|---|
| Waitlist: email, optional name, what you're interested in, the version of this notice you agreed to | To tell you when Patient-Tap launches (consent) | Until you unsubscribe or ask us to delete it, or 24 months after launch |
| Contact form: name, email, topic, your message | To reply to you, and to handle data-rights requests and grievances | 12 months after the conversation ends (longer only if the law requires) |
| Medicine reports: the code read from the pack, reason, optional details and city | To spot counterfeit and substandard medicines | 24 months, then aggregated or deleted |
| MedVerify checks: the product code, batch and serial looked up and the verdict | To answer your check, detect copied codes, and find counterfeit hot spots | 90 days |
| Hashed network address: a salted SHA-256 hash of your IP address | Rate-limiting and abuse prevention | 24 hours for rate limits; up to 90 days alongside a MedVerify check |
| Hosting logs kept by our host (Vercel): IP address, browser type, pages requested, time | Security and keeping the site running | As set by Vercel — typically a few days |
| Analytics — only if you opt in: aggregate page views without cookies | To learn which pages are useful | Aggregated; no individual profile is built |
We never store your raw IP address in our database. We do not ask for, and you should not enter, health information in the website's forms.
4. MedVerify and your camera
When you scan a pack, your camera feed is processed only inside your browser to read the QR code or barcode. No image or video ever leaves your device. Only the decoded text (product code, batch, serial, expiry) is sent to our server to look it up. You can also type the code in instead.
You can block camera access at any time in your browser settings. MedVerify still works with typed codes.
5. The web demo and donation tools
The web demo at /app runs entirely in your browser with sample data. Nothing you type there is sent to us or stored after you close the tab. Please don't enter a real person's medical details into the demo.
The blood-donation eligibility check and blood-type explorer on /donate also run only in your browser — we never receive your answers.
6. The Android app and your health data
The app handles health data — allergies, medications, conditions, blood group, a do-not-resuscitate preference, donor status and emergency contacts. We treat it as the most sensitive data we hold. You decide what goes on your tag.
On your phone and on your tag (works offline)
- Your profile is stored on your phone and written to your NFC tag encrypted with AES-256-GCM. Without a network, nothing is sent to us.
- Anyone who taps your tag with the Patient-Tap responder app can read the record — that is the point: a paramedic must be able to read it when you can't speak. Only put on the tag what you are comfortable with an emergency responder seeing.
- Document auto-fill uses on-device text recognition (Google ML Kit). Photos of your documents are processed on the phone and are not uploaded.
- Fingerprint and face unlock are handled by Android. We never receive or store biometric data.
- Medication reminders are scheduled locally on your phone.
Optional cloud features (only if you sign in)
- Account: if you sign in with Google we receive your name, email and Google account ID.
- Backup and sync: your profile is encrypted on your phone before upload, so the copy on our servers is not readable by us.
- Emergency alerts: if you turn them on, a scan of your tag can send an SMS or email to your emergency contacts. That message includes your name and, with your location permission, your location at the time. Messages are delivered through Twilio (SMS) and Resend (email).
- Access log: scans of your tag can be recorded — the time, the responder ID and, where the scanning phone shares it, the location of the scan — so you can see who opened your record and where.
- Shareable links you create can be given an expiry date, and you can revoke them at any time.
- Payments: handled by Razorpay. We receive the payment status and an order reference. We never see or store your card, UPI or bank details.
Your emergency contacts
When you add someone as an emergency contact you are sharing their name and phone number with us. Please tell them and make sure they are happy to receive alerts.
7. How we use data — and what we never do
We use personal data only to:
- provide the features you ask for;
- keep the service secure and prevent abuse;
- reply to you and handle your requests;
- comply with the law.
We will never:
- sell or rent your personal data;
- use your health data for advertising or profiling;
- share your health data with insurers or employers;
- track you across other websites.
We process data on the basis of your consent (DPDP Act, section 6) or, where the Act allows it, for legitimate uses (section 7) — for example responding to a medical emergency or complying with a legal obligation.
8. Who processes data for us
We use a small number of service providers (“Data Processors”) bound by contracts to process data only on our instructions:
| Provider | Purpose | Location |
|---|---|---|
| Vercel Inc. | Website hosting, and analytics if you opt in | Global edge network; our server functions run in Mumbai |
| Supabase Inc. | Database for website forms and MedVerify | Mumbai, India (ap-south-1) |
| Google LLC | Sign-in (app only) | Global |
| Razorpay Software Pvt. Ltd. | Payments (app only, once live) | India |
| Twilio Inc. / Resend | Delivering emergency SMS and email alerts (app only) | Global |
Some providers may process data outside India. The DPDP Act allows this except to countries the Government of India restricts, and we will follow any such restriction. We may also disclose data when Indian law requires it — for example a valid order from a court or authority.
9. How we protect data
- Records on tags and backups are encrypted with AES-256-GCM, which also detects tampering.
- HTTPS everywhere, with HSTS and a strict Content-Security-Policy on every page.
- The database is locked down: Row-Level Security on every table, with no direct access from the internet, and every request gated by a server-only secret.
- Network addresses are salted and hashed; forms are validated and rate-limited.
- Dependencies are audited for known vulnerabilities on every change.
No system is perfectly secure. If a personal data breach happens we will inform the Data Protection Board of India and every affected person, as the DPDP Act requires, and report cyber incidents to CERT-In where required. See our security page to report a vulnerability.
10. Children
Our website forms are for people aged 18 or over. A child's Patient-Tap profile — for example on a school wristband — must be created by a parent or lawful guardian, who gives consent on the child's behalf (DPDP Act, section 9). We do not track children or target advertising at them.
11. Your rights
Under the DPDP Act you have the right to:
- get a summary of the personal data we hold about you and how we use it;
- have inaccurate data corrected, completed or updated;
- have your data erased when it is no longer needed or you withdraw consent;
- withdraw consent at any time — as easily as you gave it. This does not affect anything done before you withdrew;
- nominate someone to exercise your rights if you die or become incapacitated;
- have your grievances addressed (see below).
To use any of these rights, use our contact form (topic “My data”) or email privacy@patient-tap.shop. We may need to confirm your identity first. Data on an NFC tag you hold is under your control: you can rewrite or wipe it with the app at any time.
12. Grievance Officer
If you have a complaint about how we handle your data, contact our Grievance Officer:
Viral Dhoka
Grievance Officer, Patient-Tap
Email: grievance@patient-tap.shop
Pune, Maharashtra, India
Complaints are acknowledged and resolved within 7 days of receipt; resolved within 30 days. If you're not satisfied with our response, you can complain to the Data Protection Board of India.
13. Changes to this policy
We will post any change here and update the date at the top. If a change materially affects how we use data you have already given us, we will tell you (for example by email if you're on the waitlist) and ask for fresh consent where the law requires it.