How we handle your data.

1. Who we are

MedScan ("we", "us") is the operator of the MedScan app and website. For privacy-related queries we act as the data fiduciaryas defined under the Digital Personal Data Protection Act, 2023 ("DPDP Act").

2. What we collect

• Account data. Your email address, and optional profile name and city.
• Health documents you upload. Prescriptions, lab reports, and any text or images you attach to a profile.
• Questions you ask.When you use the Ask surface to ask a general health question, your question text and our reply are stored alongside the family member you tagged the conversation to (or untagged if you didn't).
• Derived data. The structured extractions produced from your documents (medication names, dosages, lab values), the plain-language explanations we generate, and the reminders you set.
• Family profiles. If you create a profile for a family member, the information you add about them — including any consent records.
• Operational logs. Standard server logs (IP, user agent, request timestamps), retained for a maximum of 30 days and used only for security and debugging.

3. What we do not collect

• We do not sell, rent, or share your medical documents or your chat conversations with pharmaceutical companies, insurers, hospitals, or any other third party. Your prescription, lab report, the questions you ask, and the explanations we generate stay between you and us.
• We do not use behavioural advertising SDKs to profile you. We don't track which articles you read, how long you scroll, or build a behavioural profile from your visit.
• We do not train AI models on the medical documents you upload or the health questions you ask.

3a. Limited tracking we do use

Two narrow signals run on the site so we can keep it working and afford to keep the basics free:

• Vercel Analytics— anonymous page-view counts and a small set of named events (e.g. "a user clicked the CTA", "a result page rendered"). No cookies, no IP retention beyond the request, no profile built across sessions. Used to understand which parts of the product actually get used.
• Google Ads conversion tag (gtag.js)— when you arrive on the site by clicking a Google Ads search result, a small tag tells Google "the click reached the page." This lets us measure whether paid acquisition is working at all and decide whether to keep spending. Google sees the page-view signal but not your medical documents — those never leave our servers. If you arrived via any other route (organic search, a direct link, a friend), the tag still loads but does not associate you with any ad click.

Both can be blocked by browser-level privacy controls (uBlock Origin, Brave shields, Firefox strict mode, Safari Cross-Site Tracking Prevention). The product works fine without them — we'll just have less data on whether our experiments succeeded.

4. Where we store it

Your account and document data is stored on servers located within India, operated by tier-1 cloud providers under industry-standard encryption (TLS in transit, AES-256 at rest). Backup copies remain in India.

5. How we use AI

We use large language models to produce plain-language explanations and to answer general health questions on the Ask surface. We use enterprise-tier endpoints that are contractually bound to not retain your data after processing and not train any models on it. We never send your raw document or your question to a model endpoint that does not have these guarantees.

6. Your rights under the DPDP Act

• Access. Download everything we hold about you, in a machine-readable format, any time.
• Correction. Fix anything that is wrong.
• Erasure. Delete everything. Deletion is immediate and permanent; we keep only a hashed record that your account existed, for fraud prevention.
• Grievance. Raise a concern with our grievance officer (contact below) and receive a response within 15 days.

7. Family profiles and consent

When you add a family member, you confirm that you have their consent — or, if they are a minor or dependent adult, that you have lawful authority to manage their health records. We will soon support a verified-consent flow where the person themselves confirms via SMS.

8. Security incidents

If we ever experience a personal data breach affecting you, we will notify you and the Data Protection Board within the timelines required by the DPDP Act. We will explain what happened, what data was affected, and what we are doing about it.

9. Contact

Grievance officer: privacy@medscan.live. General queries: hello@medscan.live.