Privacy Policy
Version 2026-11-beta-2. Draft for the free beta. This policy is written to meet India's Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025.
The short version
We collect as little as we can: your email, and the profile you choose to fill in.
Your email, name and college are encrypted in our database with a key unique to you.
We don't store your chat messages with the AI tutor.
We don't sell your data, show ads, or use advertising or analytics trackers.
You can download or delete everything at any time in Settings. Deletion is immediate.
What we collect and why
Email address: to sign you in with a one-time code and to identify your account. Stored encrypted, with a keyed hash so we can look it up.
Name and college (optional): to personalise Osler. Stored encrypted. If you sign in with Google we receive your name but don't store it; you type your profile yourself.
University, MBBS phase and target exam: to tailor content and past-paper analysis. Stored as plain values because they don't identify you on their own.
Google sign-in identifier: if you use Google, we store only a keyed hash of Google's account id, never the id itself or any Google access token.
Sign-in sessions: a random token in a secure cookie (website) or your phone's secure storage (app). We store only a hash of it. A session lasts 30 days and ends after 14 days unused; on a shared device it lasts 12 hours, ends after an hour unused, and ends when you close the browser. You can have up to 10 at once.
Signed-in devices: for each session, a rough device label such as "Chrome on Android" (encrypted, so only your account can read it), how you signed in, and the day you were last active, so you can see and sign out your devices. We don't store your IP address or location.
Before your account exists: after you prove you own your email or Google account, your verified email waits in an encrypted, 15-minute sign-up ticket in your browser (not in our database) until you agree to these terms. If you leave, nothing is kept.
Consent records: which policy versions you accepted and when, and your confirmation that you are 18 or older. You accept once when you create your account, and again only if we change these terms in a way that matters.
Usage counters: how many AI questions you asked per day, to enforce fair-use limits. Counts only, not the questions.
Security log: events such as "signed in" or "deleted account" with a time and your account id. It never contains your email or name.
Your IP address is used briefly for rate limiting and bot protection and is not stored.
Chat messages
When you ask the tutor a question, it is first checked by an automated filter and then answered by an AI model, both running on Cloudflare. We don't keep your message. If the filter finds no personal data in it, the anonymous question and answer may be cached so other students get the same answer faster. Please never type patient details or other personal data into the tutor.
Who processes your data
Cloudflare hosts Osler, its database and its AI models.
Resend delivers sign-in code emails and a few security notices (for example "Google sign-in was connected to your account" or "your account was deleted"). It receives your email address and that message, nothing else.
Google handles "Sign in with Google" if you choose it.
Cloudflare Turnstile checks that sign-in requests come from a person; it sees your IP address.
We never send your chat messages or personal data to any other AI provider.
Your rights
Access: download all your data from Settings → Download my data.
Correction: edit your profile at any time.
Erasure: Settings → Delete account removes your account at once. Your encryption key is destroyed, which makes any remaining encrypted copies (for example in backups) unreadable.
Withdraw consent: during the beta, withdrawing consent works the same as deleting your account.
Grievances: contact us (see below). We will respond within the time limits set by the DPDP Rules.
Children
Osler is only for adults (18+). We don't knowingly process the data of anyone under 18.
Security
We encrypt personal fields with AES-256-GCM using a per-user key, use secure cookies, rate-limit sign-in, and follow the security rules in our engineering handbook. No system is perfectly secure; if a breach affecting you occurs, we will tell you and the Data Protection Board as the law requires.
Changes
If this policy changes in a meaningful way, we'll ask you to accept the new version at your next sign-in.
Contact
Privacy questions and grievances: see
Contact.