On this page
1. Who we are and what this covers
MedicalOS is an anatomy learning application for medical students. This policy explains what we collect, why, who else handles it, and what you can do about it. It is written to meet the Digital Personal Data Protection Act, 2023 (India) and the UK General Data Protection Regulation (UK GDPR) with the Data Protection Act 2018.
It covers every way of using MedicalOS:
- the mobile apps for iPhone and iPad (App Store) and for Android (Google Play);
- the web application;
- MedicalOS for Windows, the desktop app, whether you installed it from the Microsoft Store or with the installer downloaded from GitHub.
MedicalOS is operated by CLOUDZZY LTD, 320 Firecrest Court, Centre Park, Warrington, WA1 1RG, United Kingdom. In this policy “we” means CLOUDZZY LTD, which is the controller under the UK GDPR and the data fiduciary under the DPDPA. Because we are a United Kingdom company, UK data protection law applies to everything in this policy, wherever you use MedicalOS from; if you are in India, the DPDPA applies as well.
Email: nihal@cloudzzy.co.uk
CLOUDZZY LTD, 320 Firecrest Court, Centre Park, Warrington, WA1 1RG, United Kingdom
CLOUDZZY LTD acts as the Grievance Officer. Write to this address for any request or complaint about your data.
2. What we collect
MedicalOS is invitation-only. Everything below is linked to your account unless it says otherwise.
2.1 Your account
| Data | Why | Required |
|---|---|---|
| Email address | To create your account, sign you in, send your sign-in link, and match an email invitation to a class | Required |
| Account identifier | A random identifier that attaches your progress and settings to your account | Required |
| Display name | Shown to you, and to the lecturer of any class you join; supplied by you, or by Google or Apple at sign-in | Optional |
| Role and access record | Whether you are a student, lecturer or administrator, whether the account is active, and when and how you were let in (an invitation code or a class invitation) | Required |
| Invitation codes | The code you used to join (we record which code each account used), and the personal invitation code the app gives you to share, which counts how many times it has been used | Required |
| Sign-in sessions | Our sign-in provider records each session: when it started, the IP address it came from, and a description of your browser or app. It is how sessions are kept secure and ended | Required |
2.2 Your study
| Data | Why | Required |
|---|---|---|
| Study progress | Lessons and cases completed, how far you are through each lesson, concepts you have seen, saved terms, your daily study log (counts and minutes), streak and frozen days, your daily goal, and your exam date and exam pause dates if you set them. It lets the app resume where you stopped and keep your phone, web and computer in step | Required |
| Review cards | Your revision cards and their schedule | Required |
| Your answers | The text you type, or the option you pick, for knowledge checks and case steps, with your score, the feedback you were given, and whether it was marked automatically or by AI. We keep your answers so you can see your history and so lecturers can review marking (section 5) | Required |
| Mastery | An estimate of how well you know each concept, worked out from your answers | Required |
| Activity records | That you opened a lesson, answered a check or finished a case step, with the score, the time taken and a session identifier. These hold identifiers, scores and timings, not text you typed | Required |
Study progress is the product. It is what lets the app resume where you stopped, schedule your revision, and show your streak.
2.3 Classes, institutions and live lectures
| Data | Why | Required |
|---|---|---|
| Institution membership | Every student account is placed in a MedicalOS institution so that classes can be offered to it. Lecturers may belong to others | Required |
| Class membership | The classes you have joined or asked to join, when, and whether you are active, pending or removed, and who approved you | If you join a class |
| Class invitations by email | A lecturer can invite you by typing your email address. We keep that address, the invitation’s status and its 30-day expiry, and you join the class when you sign in with that address after confirming it | If you are invited |
| Lecture attendance | When you joined a live lecture, when you were last seen in it, when you left, and for how long you were there | If you join a lecture |
| Questions and poll answers | The questions you ask in a lecture and the options you choose in polls. The lecturer sees your question without your name; we keep it linked to your account so the lecturer can mute you and abuse can be dealt with | If you take part |
2.4 Messages and notifications
| Data | Why | Required |
|---|---|---|
| Inbox | Messages from your lecturers and notices from the app, and whether you have read them | Required |
| Notification settings | Whether you want notifications about messages from lecturers | Optional |
| Push notification token | If you turn on notifications on a phone, Apple or Google issues a token, via Expo, that lets us send you a notification. We keep the token, the platform, the device name or model, whether it is switched on, and when it was last used, and we record each notification we queue or send to it. It is used to tell you that a lecture has started and that a lecturer has sent you a message. The notifications are generic (“Lecture started”, “New faculty message”) and carry no names and none of the message text | Optional |
The Windows app does not use push tokens. It shows a Windows notification itself when it learns a lecture has started, if you allow it.
2.5 Your devices and installations
| Data | Why | Required |
|---|---|---|
| Signed-in devices | A student account may be limited to a small number of devices at a time (two), so that one login is not shared among many people. For each sign-in we keep a random device identifier made by the app, the platform, a device name (the phone model, your Windows computer name, or a description of your browser), when it first and last signed in, and whether and why it was signed out. Your Windows computer name can contain your own name if you gave it one. You can see your devices and sign one out in the app | Required |
| App installation record | A random installation identifier, the platform, the app version, the update and release channel, and when the app was first and last seen. It tells us which versions are in use, so that we can fix problems and retire old versions | Required |
| Screenshot reports | When an app notices that you took a screenshot or started a screen recording (on iPhone and iPad, on Android 14 and later, and when the Print Screen key is pressed on the web and in the Windows app) it tells us the kind, the platform, the screen you were on (for example “a lesson”, never its content), the device and the time. We never receive the image. Where the operating system allows it, the apps also block or blank the capture of lessons | Automatic |
| Lesson watermark | Lessons shown to students carry faint text made of the start of your email address and a short code from your account identifier, so that a lesson that is shared can be traced. It is drawn on screen; it is not collected | Automatic |
2.6 AI marking
| Data | Why | Required |
|---|---|---|
| Written answers sent for AI marking | The answer you type to a knowledge check or case step may be sent to our AI provider, with the question, to be marked. Your name, email and account identifier are not sent | Automatic |
| AI usage records | For each AI call: the provider, model, purpose, cost, response time, and a short fingerprint (not the text) of what was sent and returned, linked to your account. We also keep a running monthly total of your AI spend, which caps how much AI marking one account can use | Automatic |
There is no AI chat in MedicalOS, and we do not keep conversation transcripts. We do keep your answers and the feedback you received (section 2.2).
2.7 Technical data
- IP address and request logs. Our servers log each request: the time, the address it was made from, the path, and the result. Some security and audit entries include your account identifier. We use them to keep the service secure, to limit abuse, and to find faults.
- Rate limits. To stop abuse and runaway AI spend, counters keyed on your account identifier or IP address are kept for short periods.
- Update checks. The mobile apps ask Expo for app updates, and the installer version of the Windows app asks GitHub for new versions. Both see your IP address and the version you run, as any download does. Neither receives your account details.
2.8 If you are a lecturer or contributor
If you write teaching content or send messages to classes, we also keep what you author (topics, figures, edits and their history), your public byline (display name, affiliation and honorific, if you set them), the comments you leave on colleagues’ topics, the messages you send to classes (students see them as from “Your instructor”, and we keep the message and who sent it), the classes you run and their rosters, and a record of who changed or approved what, because other people’s learning depends on that record. Lecturers also see the other people’s data described in section 5.
2.9 What stays on your device
- Phone. Your sign-in session, a copy of your progress, the lessons downloaded for offline study (removed when you sign out), your random installation identifier, and your push token.
- Web. The same kinds of data in the browser’s own storage: your sign-in session, a random device identifier, your progress and the lessons you are reading, which are removed when you sign out. We do not set cookies.
- Windows. Your sign-in session is stored in an encrypted file in the app’s data folder. The key that encrypts it, your device identifier and your installation identifier are kept in Windows Credential Manager. Signing out deletes the encrypted session. Uninstalling the Microsoft Store version removes its files and the web data it keeps. Uninstalling the installer version removes the program and its shortcuts; its uninstaller also offers a “Delete the application data” box, which is unticked unless you tick it, and which deletes the app’s data folders (the encrypted session and the web data). Neither uninstall removes the three Credential Manager entries (named
org.medicalos.desktop.storefor the Store version andorg.medicalos.desktopfor the installer version); once the files are gone they protect nothing, and you can delete them in Windows Credential Manager.
3. What we do not collect
So that there is no ambiguity, and because app stores ask us to be specific:
- No location data. The apps do not ask for location permission. Our servers see your IP address (section 2.7) but we do not use it to work out where you are.
- No advertising identifier. MedicalOS contains no advertising and no advertising SDK.
- No analytics or crash-reporting SDK, and no cross-app or cross-site tracking. (Apple and Google run the push services that deliver notifications to your phone, and Expo delivers app updates; section 7.)
- No camera, microphone, photo or contact access on the mobile apps, and no access to your calendar. On the web and in the Windows app, a lecturer can choose a file to upload (for example a Word document or an image) and only that file is read.
- No health or fitness data. What you study is education, not a record about your body.
- No financial or payment information. MedicalOS is free to use.
4. How we use it, and why
- To run the app — signing you in, storing your progress and answers, scheduling your revision, and keeping your phone, web and computer in step.
- To run classes and lectures — letting lecturers manage a class, run a live lecture, take attendance and send messages, and letting you receive them.
- To mark your work — checking your answers and working out your mastery of each concept, with AI where an answer cannot be marked by matching alone.
- To protect the service and its content — limiting each account to a few devices, spotting a shared login or a shared screenshot, limiting abuse and AI spend, and investigating faults.
- To keep the app current — knowing which versions are installed so that we can fix problems and retire versions that are no longer supported.
- To meet legal obligations — and to answer your requests and grievances.
Under the DPDPA we process your data with your consent, which you give by creating an account and using the features described here, and which you can withdraw at any time by deleting your account. We also process some data where the DPDPA allows it without consent, such as keeping the service secure and meeting legal obligations.
We do not use your data for advertising, profiling unrelated to study, or automated decisions with legal effect.
4.1 Legal bases and your rights under the UK GDPR
Under the UK GDPR we need a legal basis for each use of your personal data. These are ours. None of the data in section 2 is special category data.
| What | Legal basis (Article 6) |
|---|---|
| Your account and sign-in (section 2.1) | Performance of our contract with you: giving you the account you asked for |
| Study progress, review cards, mastery, activity records and your answers (section 2.2), and AI marking (section 2.6) | Performance of our contract: providing the study service |
| Institution and class membership, invitations and live lectures (section 2.3) | Performance of our contract: letting your lecturer run the class you joined |
| Inbox and lecturer messages (section 2.4) | Performance of our contract |
| Push notification token (section 2.4) | Your consent, which you give by switching notifications on in your phone and withdraw by switching them off or signing out |
| Devices, installation records, screenshot reports and the lesson watermark (section 2.5) | Our legitimate interests in keeping each account to one person, protecting our lessons from being passed on, and fixing or retiring app versions |
| Request logs, rate limits, AI usage records and spend limits (sections 2.6 and 2.7) | Our legitimate interests in security, preventing abuse and controlling cost |
| Lecturer and contributor records (section 2.8) | Performance of our contract with you, and our legitimate interest in a record of who changed or approved teaching content |
| Answering your requests and complaints, and meeting legal duties | Legal obligation |
Where we rely on legitimate interests, you may object by emailing us; we will stop unless we have a compelling reason to continue.
Your rights. Under Articles 15 to 22 of the UK GDPR you may ask us for access to your personal data and a copy of it (15); to correct it (16); to erase it (17); to restrict its use (18); to be told when we have passed a correction, erasure or restriction on to anyone we shared the data with (19); to receive the data you gave us in a portable form (20); to object to processing based on legitimate interests (21); and not to be subject to a decision based solely on automated processing with legal or similarly significant effect (22), which MedicalOS does not make. AI marking gives you a score and feedback that you and your lecturer can see; it does not decide anything about your course or career. Email nihal@cloudzzy.co.uk; we reply within 30 days, and deletion needs no request (section 11).
Complaints. If you are unhappy with how we use your data, please tell us first. You also have the right to complain to the Information Commissioner’s Office, the UK data protection authority, at ico.org.uk, or to the Data Protection Board of India under the DPDPA.
5. Who can see your data
| Who | What they can see |
|---|---|
| You | Everything in your account, in the app. You can also see your signed-in devices and sign one out. |
| Other students | Nothing. No student can see another student’s name, email, answers or progress. |
| The lecturer of a class you have joined | Your display name or email address and when you joined, in that class’s roster; the attendance record of a lecture they run, which they can download with your name, email, join and leave times and time present; the questions you ask (without your name); and your answers to check questions and how they were marked, which they may review and adjust. This covers questions in the topics they wrote and in MedicalOS’s built-in lessons, and only for students who are active members of one of their classes. The app does not show lecturers your overall study progress, review cards or devices. |
| A lecturer who invites you by email | The address they typed, and whether you have joined. |
| MedicalOS administrators | The list of accounts (email, display name, role, whether active, how and when admitted), an account’s signed-in devices and screenshot reports, usage statistics and AI costs. Administrators use these to run the service, to help you if you are locked out of a device, and to investigate a shared login or shared content. |
| Our service providers | What section 7 says each handles. |
| Authorities | Only where the law requires it. |
6. Sign-in
Depending on the app you can sign in with Google, with Apple, or with a one-time link sent to your email address. There is no password to set or forget. When you use Google or Apple, they tell us your email address and, if you allow it, your name; our sign-in provider may also hold other details the provider shares, such as a profile picture address, that MedicalOS does not use. We do not receive your password.
If you use Apple’s Hide My Email, Apple gives us a relay address instead of your own. That works normally, but it is a different address from your Google or email sign-in, so it creates a separate account with separate progress.
7. Who processes your data
We use service providers who process data only to run the service. We do not sell your personal data and we do not share it with advertisers or data brokers.
| Provider | What it does for us | Your data it handles | Where |
|---|---|---|---|
| Supabase | Authentication (including sending your sign-in links by email), the database, file storage, live-lecture messaging, and delivery of queued notifications | All the account data in section 2, and your email address and sign-in link when it emails you | Ireland (EU West) |
| Railway | Runs the MedicalOS server (API) | Everything that passes through a request, and request logs | Netherlands (EU West, Amsterdam) |
| Netlify | Serves the web application | IP address and request details when you load the web app | A global content delivery network, from the location nearest you |
| Upstash | Short-lived rate-limit and AI-spend counters | Your account identifier or IP address | Europe (London) |
| Anthropic | Marks written answers with AI | The text of the answer and the question, without your name, email or identifier. Anthropic deletes it within 30 days and, by default, does not use it to train its models | United States and other regions Anthropic operates in (we do not restrict the region) |
| OpenAI | Draws anatomical figures when a lecturer asks for one | The figure description the lecturer typed. No student data. OpenAI keeps API requests for up to 30 days for abuse monitoring and does not use them to train its models | United States and other regions OpenAI operates in (we do not restrict the region) |
| Expo | Delivers app updates to the mobile apps, and relays push notifications | Push token, notification text, IP address, app version | Mainly the United States |
| Apple and Google | Deliver push notifications to your phone; provide sign-in with Apple and with Google; distribute the mobile apps | Push token and notification text; the email and name you allow at sign-in | Their own global systems |
| Microsoft | Distributes MedicalOS for Windows through the Microsoft Store, under its own privacy statement | None from the app | Their own global systems |
| GitHub | Hosts the Windows installer and its update files, and these policy pages | IP address when you download or check for an update. No account data | Their own global systems |
8. Transfers outside the UK and India
We are a United Kingdom company. Your data is stored in Ireland, our server runs in the Netherlands, and our rate-limit store is in London. The UK treats Ireland and the Netherlands (the EEA) as adequate for personal data. Some providers also handle data in the United States and other countries, as the table in section 7 shows. When personal data is sent from the UK to a provider in a country without an adequacy decision, we rely on one of these safeguards, and we send only what each provider needs:
| Provider | Safeguard for transfers from the UK |
|---|---|
| Supabase | Standard contractual clauses approved by the European Commission, with the UK Information Commissioner’s addendum |
| Railway | The UK Addendum to the EU standard contractual clauses, in its data processing addendum |
| Netlify | The UK Extension to the EU–US Data Privacy Framework, and standard contractual clauses |
| Upstash | Its data processing agreement; the data is held in London |
| Anthropic | Standard contractual clauses with the UK Addendum, in its data processing addendum |
| OpenAI | Standard contractual clauses with the UK Addendum (no student data is sent) |
| Expo | The UK Extension to the EU–US Data Privacy Framework, which Expo self-certifies to |
| Apple, Google, Microsoft, GitHub | Each acts under its own privacy statement and transfer safeguards |
You can ask us for a copy of the safeguards that apply. For users in India, the DPDPA allows transfers abroad except to countries the Government of India restricts by notification. As of the date of this policy, none has been notified. If a country is restricted, we will stop sending data there.
9. How long we keep it
| Data | How long |
|---|---|
| Your account, progress, answers, classes, messages, devices, installation record, push token, screenshot reports and AI usage records | While your account exists. We delete them when you delete your account (section 11). We do not currently delete an account because it is unused. We will review this when MedicalOS opens beyond invited students, and tell you in the app before we adopt any inactivity period. |
| Devices you signed out | Kept, marked as signed out, until you delete your account. The record is what lets us apply the device limit fairly |
| Push notification tokens | Deleted when you sign out. A token that Apple or Google report as no longer valid is deleted about a week later. Records of notifications queued for you are kept until you delete your account; the records of their delivery go with the token |
| Sign-in links | Valid for one hour |
| Class invitations | Open for 30 days. An invitation that expires or is withdrawn is deleted 7 days later. One that is accepted is deleted 7 days after you accept it, once the app has told you that you have joined, and in any case within 30 days. The clean-up runs nightly, so each deletion happens within about a day of these dates |
| Rate-limit counters | Seconds to a day; the monthly AI-spend counter for up to 40 days. Neither is deleted when you delete your account; both expire by themselves, and hold only your account identifier or IP address |
| Server request logs | 7 days, the retention of our hosting plan with Railway |
| Sign-in provider event log | Our sign-in provider records sign-in events with the email address and IP address. They are kept while your account exists. When you delete your account we remove, as far as we can, the entries that contain your account identifier or email address; anything missed is removed by a nightly clean-up, as far as we can. Its platform logs are kept for a limited time set by its plan, no longer than 28 days |
| Backups | Encrypted backups may retain remnants of a deleted account until their normal rotation expires, which is within 30 days. They are isolated from ordinary use and are not used to restore a deleted account. |
10. Your rights
Your rights under the UK GDPR, which apply to everyone, are in section 4.1. Under the DPDPA you may ask us for a summary of the personal data we hold about you and who we share it with, ask us to correct or complete it, ask us for a copy of it, ask us to erase it, withdraw your consent, use our grievance process, and nominate another person to exercise these rights for you if you die or become unable to. Deletion is available in the app at any time and needs no request — see section 11 and the deletion page. For anything else, email nihal@cloudzzy.co.uk from the address on your account. We respond within 30 days.
You can also see and sign out your own devices from inside the app, switch lecturer-message notifications off, and turn off push notifications in your phone’s settings. If you are not satisfied with our answer, you may complain to the Information Commissioner’s Office (ico.org.uk) or, under the DPDPA, to the Data Protection Board of India.
11. Deleting your account
Delete your account from the app (phone: More, then Delete account; web and Windows: Profile, then Delete account). Deleting removes your sign-in and profile, your progress, review cards, answers, mastery and activity records, your class and institution memberships, your lecture attendance, questions and poll answers, your inbox and notification settings, your push tokens and notification records, your devices, installation records and screenshot reports, your invitation records, and every class invitation sent to your email address. If you are a lecturer, the classes you own are removed with you, and your authored topics are withheld while rights over them are resolved.
Some records survive without your name. AI usage records stay with the link to your account removed. Records of who edited or approved teaching content stay with your name removed. Our access-audit log, which records class and institution actions, keeps its entries but loses your account identifier when you delete your account. If you authored teaching content, a restricted record of ownership and permissions is kept for up to 90 days, then deleted unless the law requires us to keep it. Backups, server logs and the sign-in provider’s event log are covered by section 9. The deletion page lists what is removed in full.
12. Children
MedicalOS is built for medical students aged 18 and over and is not directed at children. We do not knowingly collect data from anyone under 18. If you believe a child has created an account, email us and we will remove it.
13. Security
Data is encrypted in transit. Access to the database is restricted by row-level security and by the checks our server makes on who is asking, so that a student can read only their own data and a lecturer only what section 5 describes. On Windows, your sign-in session is encrypted on the computer with a key held in Windows Credential Manager. No system is perfectly secure. If a breach puts personal data at risk, we will tell affected users, the Information Commissioner’s Office and the Data Protection Board of India as the law requires.
14. Changes
If we change this policy we will update the date at the top and, for material changes, tell you in the app. Continuing to use MedicalOS after a change means the updated policy applies.