Privacy Policy

Welcome to MediDibba, a family health management application developed and operated by Qudex, a collective of independent software developers. MediDibba is designed to help Indian families manage medicine inventories, health records, vaccination schedules, and emergency health information in a single, private, offline-capable mobile application.

This Privacy Policy explains how Qudex ("we", "us", "our") collects, uses, stores, protects, and shares your personal and health information when you use the MediDibba mobile application ("App") and any related services accessible via https://medidabba.com ("Website").

By downloading, installing, or using MediDibba, you acknowledge that you have read, understood, and agree to be bound by this Privacy Policy. If you do not agree, please do not use the App.

1.1 Definitions

• •"Personal Data" Any information relating to an identified or identifiable natural person, including name, phone number, email address, and date of birth.
• •"Health Data" Sensitive personal data relating to physical or mental health, including medicine records, diagnoses, lab reports, prescriptions, blood group, allergies, and vaccination history.
• •"User" Any individual who downloads, installs, or uses the MediDibba application.
• •"Family Member" A profile created within the App to represent a member of the User's household (e.g. Papa, Maa, child).
• •"App" The MediDibba mobile application for Android and iOS.
• •"Services" The App, Website, and all related features and functionality provided by Qudex.
• •"Qudex" The collective of independent freelance developers who built and operate MediDibba, reachable at privacy@medidibba.com
• •"Supabase" The third-party backend platform (supabase.com) used for database, authentication, and file storage.

We collect only the information that is strictly necessary to provide you with the features of MediDibba. We do not collect information beyond what is described below.

2.1 Information You Provide Directly

Account Information

• •Full name and email address — obtained from your Google Account when you sign in with Google OAuth
• •Profile photo URL — from your Google Account (not stored separately by us)
• •Phone number — optionally provided by you for family sharing invitations

Family Member Profiles

• •Name and relationship (e.g. Father, Mother, Child)
• •Date of birth — used to calculate age for the emergency card
• •Blood group (e.g. B+, O-)
• •Known allergies — stored as a list of text strings
• •Chronic health conditions (e.g. Diabetes, Hypertension)
• •Emergency contact name and phone number
• •Avatar emoji — a single emoji character chosen by you

Medicine Records

• •Medicine name, brand name, category, expiry date, quantity, and unit
• •Notes you choose to add about dosage or instructions
• •Photos of medicine strips or packaging — cropped and reduced on your device, then read by AI to extract the name, expiry date and quantity
• •AI-generated description of what the medicine is commonly used for, read from that same photo and saved with the medicine

Health Records

• •Uploaded files: prescriptions, lab reports, discharge summaries, bills, X-rays, vaccination certificates
• •File metadata: document type, date of visit, doctor name, hospital name
• •Tags you assign to records for search purposes
• •AI-generated summaries of uploaded health documents
• •Text and values read out of an uploaded document by AI — test results with their units and reference ranges, prescribed medicines, and the doctor, hospital and date printed on it

Vaccination Records

• •Vaccine name, date administered, dose number, next due date
• •Administering clinic or hospital name
• •Optional vaccination certificate photo

2.2 Information Collected Automatically

Authentication & Session Data

• •Google OAuth tokens — used only to authenticate your identity and create a session; not stored permanently
• •Expo Push Notification token — collected on first app launch after you grant notification permission; used only to send medicine expiry and vaccine due-date reminders

Usage Data

We do not collect analytics, crash reports, or behavioural tracking data in Phase 1 of the App. Future versions may introduce opt-in anonymous analytics, and this policy will be updated accordingly.

Device Information

We do not collect device identifiers, IMEI numbers, advertising IDs, or any persistent device fingerprints.

2.3 Information We Do NOT Collect

We do not collect: precise GPS location, contacts list, call history, SMS content, microphone audio, financial information (card numbers are handled entirely by Razorpay and never reach our servers), biometric data, or any data from other apps on your device.

We use the information we collect solely to provide, maintain, and improve the MediDibba App. Specifically:

• •Authenticate you and maintain your session: Google OAuth email, name, profile photo URL
• •Create and manage family member profiles: All family member data you enter
• •Display and manage your medicine cabinet: Medicine names, expiry dates, quantities, categories
• •Scanning medicine packaging: The cropped photo — sent server-side to Google Gemini; not stored by us unless you save the scan
• •Generate AI medicine descriptions: Read from the scanned photo by Google Gemini; saved with that medicine
• •Read uploaded health documents: The document itself — an image, or the text extracted from a PDF or Word file — sent to Google Gemini; the values it returns are saved to that record
• •Answer questions in the assistant: Your question and the selected family member's health record — sent to OpenAI GPT-4o mini through OpenRouter
• •Store and display health records: Uploaded files stored in private Supabase Storage; metadata in database
• •Show the offline emergency card: Blood group, allergies, conditions, medicines — read from local device storage
• •Send push notification reminders: Firebase Cloud Messaging device token, medicine expiry dates, vaccine due dates
• •Process subscription payments: Only your user ID is sent to Razorpay; payment details handled entirely by Razorpay
• •Family data sharing: Your phone number (used to find recipients); shared member IDs
• •Sync data across devices: All app data synced to Supabase database under your authenticated user ID

3.1 Legal Basis for Processing (India — IT Act 2000)

Under the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 ("SPDI Rules"), we process your sensitive personal data on the following bases:

• •Consent: You provide explicit consent when you create an account and use the App. You may withdraw consent by deleting your account.
• •Contractual necessity: Processing is necessary to provide the Services you have requested.
• •Legitimate interest: We process minimal usage data to maintain the security and functionality of the App.

Medidibba uses AI to read and explain medical information.

These features are powered by third-party AI models: Google Gemini, and OpenAI GPT-4o mini reached through OpenRouter. Which model handles which task is set by us and can change; the providers we use are listed in the sub-processor section below. These features are assistive only. They do not diagnose conditions, prescribe treatment, or replace a consultation.

Where AI is used

• •Scanning medicine packaging and prescriptions to read the name, dosage and expiry date from a photograph.
• •Reading a document you upload — a photograph, a PDF or a Word file — to save the test values, dates, doctor, hospital and medicines printed on it, and to summarise it in plain language.
• •Answering your questions in the assistant, about the family member you have selected.
• •Checking your saved medicines against each other and against the allergies and conditions recorded on that profile.
• •Transcribing a voice note you record against a document.

AI can be wrong

AI-generated information may be inaccurate, incomplete or out of date.

Handwriting, poor lighting, damaged packaging and unfamiliar brand names all reduce accuracy. Scanned medicine details are shown to you to review and correct before they are saved.

Always verify medicine names, dosages, expiry dates, test results and any health guidance with your doctor or a qualified pharmacist before acting on it. Never start, stop or change a medicine based on what this app tells you.

In an emergency, contact your local emergency services or go to the nearest hospital. Do not rely on this app.

What is sent to the AI provider

• •The photograph you choose to scan.
• •A document you upload, when you leave "Read this document with AI" ticked. Images are sent as a picture; PDFs and Word files are sent as the text read out of them.
• •The question you type in the assistant, and the recent messages in that conversation.
• •For the assistant, the health record of the family member you have selected: their name, age, gender, blood group, allergies and conditions; their medicines and reminder times; how many doses were taken, missed or skipped in the last 30 days; their vaccinations; and the contents of their uploaded reports, including any notes you typed yourself.
• •Records belonging to family members you have not selected are not sent.
• •Your account email address, phone number and emergency contact details are never sent.

Your choice

Every document upload carries a "Read this document with AI" option. It is on by default. Turn it off and the file is stored in your vault without being sent to an AI provider, and the assistant will not be able to answer questions about what is inside it.

You can use Medidibba without AI features at all by entering medicine and record details manually.

What we keep

Requests are made from our servers, never directly from your device. What the AI read out of a document — the values, dates and summary — is saved to that record in your own account, so the assistant can answer from it later without sending the file again. The document itself stays in your vault and is deleted when you delete the record.

We keep a record of what the AI extracted and what you corrected, so we can measure and improve accuracy.

4.1 Where Your Data Is Stored

• •On your device: Local SQLite database stores medicine records, family member profiles, and emergency data for offline access. This data is encrypted by your device's native storage encryption.
• •Supabase (Singapore): Your account data, medicine records, health record metadata, and subscription status are stored in a PostgreSQL database hosted by Supabase on servers in the ap-southeast-1 (Singapore) region — the closest available region to India.
• •Supabase Storage: Uploaded health record files (prescriptions, lab reports, etc.) and medicine scan photos are stored in private Supabase Storage buckets in the same Singapore region.
• •Secure device store: Your authentication session token is stored in Expo SecureStore, which uses the device's hardware-backed secure enclave (iOS Keychain / Android Keystore).

4.2 Security Measures

We implement the following technical and organisational security measures:

• •Row Level Security (RLS): Every database table has RLS enabled. Authenticated users can only access rows they own. Even if someone obtained your anon API key, they could not access another user's data.
• •Private storage buckets: All health record files and medicine scan images are stored in private Supabase Storage buckets. Files are never publicly accessible.
• •Signed URLs: Health record files are accessed via short-lived signed URLs that expire within 1 hour of generation. These URLs are generated server-side and never stored in the database.
• •HTTPS everywhere: All data in transit between the App, our Edge Functions, and Supabase is encrypted using TLS 1.2 or higher.
• •No API keys in the app: Google Gemini, OpenRouter, Firebase, Resend and Razorpay secret keys are stored exclusively as server-side Edge Function secrets. They are never bundled into the app.
• •Secure session storage: JWT session tokens are stored in the device's hardware-backed secure keystore, not in plain AsyncStorage.
• •Offline data protection: Local SQLite data is protected by the device's full-disk encryption. We recommend users enable device screen lock and encryption.

4.3 Data Retention

• •Active account data: Retained for as long as your account exists.
• •Medicine records: Retained until you delete them or your account is deleted.
• •Health record files: Retained in Supabase Storage until you delete the record or your account.
• •Notification log: Pruned automatically after 90 days to prevent unlimited growth.
• •Medicine scan images: Sent to Google Gemini to be read. Kept by us only if you save the scan to a medicine.
• •Deleted account data: Permanently deleted within 30 days of account deletion request. Backups purged within 60 days.

4.4 Data Breach Response

In the event of a data breach that affects your personal or health data, we will:

• •Notify affected users within 72 hours of becoming aware of the breach
• •Notify the Indian Computer Emergency Response Team (CERT-In) as required by the IT (Amendment) Act, 2008
• •Send breach notification to your registered email address or via in-app notification
• •Provide a summary of what data was affected and steps taken to remediate

We do not sell, rent, or trade your personal or health data to any third party. Ever.

We share your data only in the following limited circumstances:

5.1 Third-Party Service Providers

We use the following third-party services to operate MediDibba. Each receives only the minimum data necessary for their function:

• •Database & Auth: Supabase (supabase.com) — All app data stored in Supabase PostgreSQL. Authentication handled via Supabase Auth. Privacy policy: supabase.com/privacy
• •File Storage: Supabase Storage — Health record files and medicine scan images stored in private buckets in Singapore region.
• •Google Sign-In: Google LLC — Name, email, profile photo from your Google Account used for authentication only. Google Privacy Policy applies.
• •Reading photos and documents: Google Gemini — Medicine photos, uploaded documents, and text extracted from PDFs and Word files are sent for extraction, summarising and transcription. Google Cloud DPA applies.
• •Assistant: OpenRouter, which routes to OpenAI — Your question and the selected family member's health record are sent, including their name, age, blood group, allergies, conditions, medicines, reminder times, dose history and report contents. OpenRouter and OpenAI privacy policies apply.
• •Push Notifications: Firebase Cloud Messaging (Google) — A device token is used to deliver reminders and alerts. Notification titles and bodies may name a family member and a medicine. Google Privacy Policy applies.
• •Invitation Emails: Resend (resend.com) — The email address you invite, and the name of the person inviting them, are sent to deliver the invitation. Resend Privacy Policy applies.
• •Payments: Razorpay — Your user ID and subscription plan are sent to create an order. Payment card/UPI details are handled entirely by Razorpay and never reach our servers. Razorpay Privacy Policy applies.

5.2 Family Sharing

If you use the Family Sharing feature to grant another MediDibba user access to your family data:

• •The invited user receives read-only access to specific family member profiles you choose
• •They cannot modify, delete, or download your data
• •You can revoke sharing access at any time from Settings → Family Profiles
• •The invited user is identified by their phone number, which must match a registered MediDibba account

5.3 Legal Disclosure

We may disclose your information if required by law or in good faith belief that such disclosure is necessary to:

• •Comply with a legal obligation, court order, or government request under Indian law
• •Protect and defend the rights or property of Qudex
• •Prevent or investigate possible wrongdoing in connection with the Services
• •Protect the personal safety of users of the Services or the public

We will always attempt to notify you before disclosing your data in response to a legal request, unless we are legally prohibited from doing so.

Under the Information Technology Act, 2000, the SPDI Rules, 2011, and in alignment with best global privacy practices, you have the following rights with respect to your personal and health data:

6.1 Right to Access

You can access all your personal data directly within the App. Your medicines, health records, family profiles, and vaccination records are available to you at all times. You may also request a complete export of your data by emailing privacy@medidibba.com.

6.2 Right to Correction

You can edit any family member profile, medicine record, or health record directly within the App at any time. If you are unable to correct data through the App, contact us and we will correct it within 15 working days.

6.3 Right to Deletion

You have the right to delete your data in the following ways:

• •Individual records: Delete any medicine, health record, or family member directly in the App.
• •Full account deletion: Go to Settings → Delete Account (available in App version 1.1+). Or email privacy@medidibba.com with the subject line "Account Deletion Request". We will permanently delete your account and all associated data within 30 days.
• •Offline data: Uninstalling the App removes all locally stored SQLite data from your device.

6.4 Right to Data Portability

You may request a machine-readable export of your data (JSON format) by emailing privacy@medidibba.com. We will provide this within 15 working days at no charge.

6.5 Right to Withdraw Consent

You may withdraw your consent to our processing of your data at any time by deleting your account. Withdrawal of consent does not affect the lawfulness of processing carried out prior to withdrawal.

6.6 Right to Opt Out of Notifications

You can disable any or all push notifications from within the App at Settings → Notification Preferences, or from your device's system notification settings.

Contact us: To exercise any of the above rights, email us at privacy@medidibba.com. We will respond within 15 working days. For urgent matters relating to data breach or misuse, please mark your email "URGENT".

MediDibba is designed to be used by adults (18 years and older) to manage health information for their households, including children within the family.

• •The App is not directed at children as primary users
• •A child’s health data (e.g. vaccination records, medicines) is entered and managed by an adult family member
• •We do not knowingly collect personal data directly from children under 13
• •If you are a parent or guardian and believe your child has provided personal data to us directly, please contact us at privacy@medidibba.com and we will delete that data promptly

MediDibba's family member profile feature is designed to let parents and caregivers manage children's health data on their behalf. Children's health records are stored under the parent's authenticated account and are subject to the same privacy protections as adult data.

The MediDibba mobile application does not use cookies, as it is a native mobile app, not a web browser application.

The MediDibba website at https://medidibba.com may use:

• •Essential cookies: Required for the website to function (e.g. session management for the privacy policy page). These cannot be disabled.
• •No analytics cookies: We do not use Google Analytics, Facebook Pixel, or any third-party tracking on the website in Phase 1.
• •No advertising cookies: We do not run advertisements and therefore do not use any advertising tracking.

The App uses the following local storage mechanisms on your device, none of which track behaviour across apps:

• •AsyncStorage: Stores your Supabase authentication session so you stay logged in between app restarts.
• •Expo SecureStore: Stores encrypted session tokens in the device hardware keystore.
• •MMKV Storage: Stores your app preferences (notification settings, language choice, last sync time). Local only, never sent to our servers.
• •SQLite: Stores medicine records and family member data for offline access. Local only.

The App may contain links to third-party websites or services (for example, links to doctor directories or pharmacy websites in future versions). This Privacy Policy does not apply to those third-party services.

We encourage you to read the privacy policies of any third-party services you access through the App. We are not responsible for the privacy practices or content of third-party websites or services.

The third-party services integrated into MediDibba (Supabase, Google, OpenRouter, OpenAI, Resend, Razorpay, Expo) each have their own privacy policies. Links to their privacy policies are listed in Section 5.1 of this document.

MediDibba is operated in India and primarily stores your data in Supabase's Singapore (ap-southeast-1) region. However, some data processing may occur outside India:

• •Google Gemini: Medicine photos, uploaded documents and the text extracted from them are processed on Google servers, which may be located in various regions.
• •OpenRouter and OpenAI: Assistant questions and the selected family member's health record are processed on servers in the United States.
• •Firebase Cloud Messaging: Your device notification token, and the text of each reminder sent to it, are processed on Google servers in the United States.
• •Resend: Invitation emails are delivered from servers in the United States.
• •Razorpay: Payment processing occurs on Razorpay's servers, which are located in India and comply with RBI data localisation requirements.

By using MediDibba, you consent to your data being transferred to and processed in these countries, which may have different data protection laws than India. We ensure that our third-party providers maintain adequate security standards and contractual obligations to protect your data.

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. When we make significant changes, we will:

• •Update the "Effective date" at the top of this policy
• •Send a push notification to all active users describing the key changes
• •Display an in-app banner for 30 days after the update goes live
• •Post the updated policy at https://medidabba.com/privacy

Your continued use of MediDibba after the effective date of the revised policy constitutes your acceptance of the changes. If you do not agree with the updated policy, you should stop using the App and request account deletion.

Material changes — such as changes to the categories of data we collect, new third-party sharing arrangements, or changes to your rights — will be communicated with at least 30 days advance notice before they take effect.

In accordance with the Information Technology Act, 2000 and the SPDI Rules, 2011, we have designated a Grievance Officer for addressing complaints and concerns regarding the processing of personal data:

You may file a grievance if you believe your personal data has been processed in violation of this Privacy Policy or applicable Indian law. We will acknowledge receipt within 48 hours and resolve the grievance within 30 days.

If your grievance is not resolved to your satisfaction, you may approach the Adjudicating Officer under the Information Technology Act, 2000, or such other authority as may be established under Indian data protection law.

If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please reach out:

• •Email: privacy@medidibba.com
• •Website: https://medidibba.com
• •App: Settings → Help & Privacy within the MediDibba application