Privacy Policy

OpenMD (“OpenMD”, “we”, “us”), available at openmd.health, is a free medical AI platform. Health information is among the most sensitive data there is, and this policy is written to be read: it explains exactly what we collect, why, where it lives, and how to delete it. Two commitments up front: we never sell your data, and we show no third-party advertising.

1. Information we collect

Information you provide

• Health conversations — messages, symptoms, and files (lab reports, prescriptions, photos) you share with the OpenMD Assistant, MedSearch, EatWell, or MindCare. Signed out, conversations live only in your own browser (session storage). If you sign in, assistant consultations are saved to your account so they follow you across devices — you can delete any saved consultation from the sidebar at any time, and deletion is immediate.
• Health stats — values you enter in BioHack (age, height, weight, heart rate, sleep, lifestyle). These stay in your browser unless you sign in and sync them.
• HomeCare bookings — name, contact details, visit address, and notes you submit when booking a provider, plus provider application details (including license numbers, which we verify).

Information from your Google account (with your consent)

• Sign-in — when you sign in with Google we receive your name, email address, and profile picture. We use this only to create and identify your OpenMD account.
• Google Health / Fitness data — only if you explicitly connect it, we access your steps, heart rate, sleep, weight, and related fitness metrics to power your BioHack digital twin. We request read-only access.

Information collected automatically

• Usage metering — to enforce our fair-use limit we count AI calls per account, API key, or hashed IP address. The IP itself is stored only as a one-way hash.
• Analytics — privacy-respecting, aggregate page analytics via Vercel Analytics (no advertising cookies, no cross-site tracking).

2. How we use information

• To generate AI responses to your health questions.
• To operate your account, API keys, and the MCP server.
• To render your BioHack digital twin from synced fitness data.
• To connect patients with verified HomeCare providers and process bookings.
• To keep the service safe (fair-use limits, abuse prevention).

We do not sell personal data, use it for advertising, or train our own or third-party foundation models on your health conversations or connected Google data.

3. Google user data — Limited Use disclosure

OpenMD’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically: Google user data is used only to provide the user-facing features described above; it is never transferred to third parties except as necessary to provide those features, never used for advertising, and never used to determine creditworthiness or for lending. Humans do not read this data except with your explicit consent, for security purposes, to comply with law, or in aggregated/anonymized form.

4. Where data lives and who processes it

• Supabase (database) — account records, API-key hashes, usage counters, encrypted Google tokens, HomeCare providers and bookings. Protected by row-level security; access requires server-side secrets.
• Google Gemini — processes the text and files you send to the assistant in order to generate a response.
• Stripe — processes HomeCare payments. We never see or store card numbers.
• Vercel — hosts the site and provides aggregate analytics.

Each processor receives only what it needs to perform its function. We use a single first-party session cookie (omd_session) to keep you signed in — no advertising or tracking cookies.

5. Retention and deletion

• Disconnect Google Health any time from your account page — we delete the stored tokens immediately.
• Revoke API keys any time from your account page.
• Delete your account and all associated data by emailing aryamansingha@gmail.com from your account email. We complete deletion within 30 days and confirm it.
• You can also revoke OpenMD’s access entirely at myaccount.google.com/permissions.

6. Security

All traffic is encrypted in transit (HTTPS with HSTS). Data at rest is encrypted by our providers. API-key secrets are stored only as SHA-256 hashes. Sessions are HMAC-signed. Our Content-Security-Policy forbids loading scripts from any third-party host.

7. Children

OpenMD is not directed to children under 13 (or the equivalent minimum age in your jurisdiction) and we do not knowingly collect their data.

8. Changes and contact

We will post any changes to this policy on this page with an updated effective date. Questions or requests: aryamansingha@gmail.com.