Medceptor Privacy Policy
Effective Date: November 4, 2026
Entity: IDK Studios, Inc., a Texas corporation (operating as Medceptor)
Registered Office: 262 Fawn Trail, Lake Jackson, TX 77566
Contact: admin@medceptor.com
What's new in version 2.1. For accounts created on or after the Effective Date and set up on our website, our servers also tell Meta the first time you finish a practice scenario on our website, within 7 days of creating your account. Meta learns only that it happened: never which scenario, your score, or anything you said or answered. For the same accounts, they also tell Meta when you start an App Store subscription in the Medceptor iOS app within 7 days of creating your account. To match that purchase to our ad, we keep the Meta cookie value and ad-click identifier your browser had when you set up your account on our website. Accounts created before the Effective Date are never sent these events. If you install the iOS app from one of our ads on Facebook or Instagram, Apple may also tell Meta, without identifying you, that the install came from that ad.
Since version 2.0 (October 19, 2026), we use Meta's advertising tools on our public website and on the application's sign-up and onboarding pages, and, for accounts created on or after October 19, 2026 and set up on our website, our servers tell Meta when you register, open checkout, or subscribe. The iOS app uses Apple's attribution service to learn which App Store ads bring students. Our servers never send Meta anything about accounts created before October 19, 2026, and you can opt out at any time at https://medceptor.com/privacy-choices or in Settings.
1. Information We Collect
Before you register. When you visit our public website (medceptor.com), we collect limited analytics about the visit: pages viewed, the website or link that brought you to us, approximate location derived from your IP address, and device and browser type. This does not include your name, email, or any account data, because you do not have an account yet. If you later register, that earlier visit is linked to your account so we can understand which sources bring students to Medceptor. Our public website also runs the Meta Pixel, a tool from Meta Platforms, Inc. ("Meta", which operates Facebook and Instagram) that collects information about your visit for advertising (see "Advertising information" below). Section 7 describes both.
When you register and use Medceptor (the "Services"), we collect:
- Account information: name, email, display name, optional phone number, your self-reported certification track (currently EMT-B, AEMT, Paramedic, CNA, LPN, RN, CCRN, CEN, CRT, RRT, FNP-C, or FNP-BC), and whether you are a student or an instructor. We also ask, optionally, for your school or program name, how you heard about us, and a few study questions (such as when your exam is, what worries you about it, and a weekly practice goal). If you sign in with Google or Apple, that provider supplies your name and email address (and, for Google, your profile picture) to create your account. If you are an instructor, we also collect the email addresses you enter to invite students to a class.
- Educational data: scenario attempts, in-scenario chat transcripts, grading results and written feedback, scenario state, per-attempt timing, tutorial-mode coaching events, nursing charting entries, question-bank answers, practice-exam sessions and responses, bookmarks, and learning progress. If you used the earlier version of Medceptor, this includes the conversation and question history we imported from it. Your conversations with the question-bank study mentor and the preceptor study assistant are not saved to your account; the questions you ask them are recorded in our product analytics (Section 7).
- Feedback: ratings and comments you give on scenarios, chat messages, and grading results, your answers to in-app surveys (such as a 0 to 10 score and a comment), and your answers to in-app quizzes.
- Payment information: processed by Stripe (website purchases) or Apple (in-app purchases in the Medceptor iOS app). We never see or store your full card number. For Stripe purchases we keep a copy of Stripe's records for your account: your billing name, email, phone number, and address, your card's brand, last four digits, and expiry date, your subscription identifiers and state (plan, status, billing period), and your invoices, payments, refunds, disputes, and checkout records. When you open checkout on our website, we also give Stripe your IP address, browser user agent, and Meta cookie values (unless an opt-out in Section 6 applies to that browser), and they are kept with the checkout record so that a purchase can be reported to Meta as described in Section 7. For App Store purchases we store Apple's signed transaction and renewal records for your subscription — the product, purchase and expiry dates, price, currency, storefront, any offer applied, and any revocation — and we pass Apple an opaque account identifier (your Medceptor account ID) so the purchase can be matched to your account. Apple does not share your payment details with us.
- Voice recordings: if you use push-to-talk dictation — in the scenario player, the preceptor study assistant, or the question-bank chat — the audio clip is sent to our speech-to-text provider (Deepgram, Section 4) to be transcribed, and the resulting text is inserted as your message. We do not store the audio; it is transcribed and discarded, and we opt out of Deepgram using it to improve its models. Dictation is optional; typing is always available.
- Communications: messages you send us through the in-app or website contact form (name, email, subject, message, and any phone number, organization, or number of students you provide, your browser type, and, for the in-app form, the page you were on) and by email.
- Consent records: when you accept our Terms of Service and this Policy, we record which versions you accepted, when, your IP address, and your browser's user agent.
- Technical information: log data, browser and device information, IP addresses, session metadata, and session recordings of your interactions with the application (with what you type into form fields, email addresses shown on screen, and the places where the application displays your name, masked) — see Section 7.
- Advertising information: on our public website, and on the application's sign-up and onboarding pages, the Meta Pixel collects information about your visit, such as the pages you view, your IP address and browser details, and advertising cookie identifiers, including an identifier for your click if you arrived from one of our ads on Facebook or Instagram. For accounts created on or after October 19, 2026 and set up on our website, we may also send Meta your email address and Medceptor account ID in hashed form (converted into a fixed-length code) when you finish setting up your account, open checkout, or start a subscription on our website, and, for accounts created on or after the Effective Date, the first time you finish a practice scenario on our website or start an App Store subscription in the iOS app. For those accounts we also keep the Meta cookie value and ad-click identifier your browser had when you set up your account. Hashing hides the readable address, but Meta can still match it to a Facebook or Instagram account that uses the same email. We share this information with Meta for advertising. Section 7 has the details and the exceptions, and Section 6 explains how to opt out.
- Apple Ads attribution (iOS app only): a random identifier for each install of the Medceptor iOS app and, from Apple, whether the install came from one of our ads in the App Store and, if so, which campaign and ad, and your country or region (the full list is in Section 7). We link this to the first account that signs in on that install. It does not use your device's advertising identifier or need your permission to track.
Important — Do Not Enter Real Patient Information. Medceptor is an educational training tool, not a clinical system. Do not enter real patient information of any kind into the Services, including names, dates of birth, addresses, medical record numbers, or any other Protected Health Information ("PHI") as defined under HIPAA. All Medceptor scenarios are synthetic. We are not a HIPAA covered entity or business associate, and we do not sign Business Associate Agreements. Accounts found entering real PHI may be suspended and the data deleted.
2. How We Use Information
We use collected data to:
- Provide and operate the Services.
- Process payments and manage subscriptions.
- Improve training quality and product performance, including by re-running our grader on stored scenario transcripts to test and improve its accuracy.
- Conduct analytics on anonymized, aggregated rubric and timing data to enhance educational outcomes.
- Send transactional emails (account, billing, security) and a small number of service emails about your account and subscription lifecycle — for example a welcome email when you first sign in, a check-in a few days after you subscribe, and a note if your subscription ends. We do not currently send marketing email.
- Send class invitations to the email addresses an instructor enters.
- Respond to your support and contact requests, and follow up on feedback you give us.
- Advertise Medceptor on Facebook and Instagram: measure how our ads perform, and help Meta show our ads to people likely to be interested in Medceptor (see Sections 5 and 7; you can opt out as described in Section 6).
- Measure which of our Apple Ads campaigns in the App Store bring students to the iOS app (Section 7).
- Publish anonymized, aggregated metrics (such as rubric pass rates and average attempt length) in marketing or research materials to demonstrate educational effectiveness.
3. AI Processing
Parts of the Services are powered by third-party large-language-model providers. We send them the content needed to produce a response:
- Scenario conversations — your in-scenario messages and the conversation so far, to generate the simulated patient's and preceptor's responses.
- Grading and feedback — the completed scenario transcript (and, for nursing scenarios, your charting entries), to determine what you did and to write your feedback.
- Study assistants — your messages to the question-bank study mentor, together with the question you are working on, and your messages to the preceptor study assistant.
- Tutorial coaching — the scenario context needed to phrase a coaching hint.
As of this version:
- DeepSeek (DeepSeek V4.1 Flash) is the default model for scenario conversations and the two study assistants, and writes the feedback for attempts that did not pass.
- Google Gemini runs grading, writes the feedback for attempts that passed, phrases tutorial coaching hints, and is the fallback model for conversations and the study assistants when DeepSeek is unavailable.
Conversation and study-assistant requests are routed through Vercel AI Gateway. It forwards them to DeepSeek using our own API credentials; when DeepSeek is slow or unavailable, to independent companies that host the same DeepSeek model (currently DeepInfra, Modal, and Wafer), using Vercel's credentials; and, if those fail, to Google Gemini. If our own credentials fail, Vercel may use its own, in which case Vercel may send the request to another company that hosts the same model. Vercel states that the gateway does not retain prompts or responses and does not use them for training. Grading, feedback, and coaching requests go directly to Google and DeepSeek.
These providers process your content to generate a response and may retain it for a limited period for abuse monitoring and to comply with law. We do not permit them to use your content to train their models where their terms give us that choice: Google's API terms for paid use provide that Google does not use prompts or responses to improve its models. DeepSeek's platform terms do not contain an equivalent commitment or a stated retention period; DeepSeek is based in the People's Republic of China, and content sent to it may be processed there. Model providers can change as we improve the product; we will update this Section and the list in Section 4 when they do.
Medceptor itself does not train AI models on identifiable user data, and we do not collect, use, or sell personal data to train large language models. We may use de-identified, aggregated metrics derived from scenario performance (such as rubric-item pass rates and average attempt length) for product improvement and educational research; no identifiable student transcript is used as training data. Re-running our grader on stored transcripts to check its accuracy (Section 2) is testing, not training.
4. Data Storage and Sub-Processors
We rely on the following service providers. Where a provider offers a data-processing agreement, we have one in place; the others process data under their own terms.
- Supabase (Postgres, Auth) — primary application database, hosted in the United States.
- Stripe — payment processing for website purchases.
- Apple (App Store) — payment processing for in-app purchases made in the Medceptor iOS app, under Apple's own privacy policy. Apple is also the source of the Apple Ads attribution data described in Section 7.
- Vercel — application hosting and edge runtime, and the AI Gateway that routes conversation requests to the model providers (Section 3).
- DeepSeek — large-language-model inference, as described in Section 3.
- DeepInfra, Modal, and Wafer — host the same DeepSeek model and receive conversation and study-assistant requests when DeepSeek is slow or unavailable (Section 3).
- Google — large-language-model inference (Gemini), as described in Section 3.
- Deepgram — speech-to-text for optional push-to-talk dictation. Audio is sent only to be transcribed, and we opt out of Deepgram using it to improve its models.
- Inngest — durable function execution for the grader pipeline (which passes your scenario transcript between steps), billing reconciliation, and passing account deletions on to our other providers.
- Langfuse — tracing of the AI calls behind scenario conversations, grading, feedback, and tutorial coaching. These traces contain the content of those calls (the prompts and transcript sent to the model and the model's output), not just timing and cost, but not your name, email, or account ID. Study-assistant traces record timing and cost only.
- PostHog — product analytics, session recording (application only), error monitoring, and feature-flag / experiment delivery, hosted in the United States.
- Resend — delivery of the transactional and service emails and class invitations described in Section 2.
- Formspree — delivery of messages you submit through the in-app and website contact forms.
- Discord — our internal team chat, where we receive error and outage alerts and in-app survey responses (your score and comment, with your account ID so we can follow up).
Advertising partner (not a sub-processor). Meta is not on the list above: it receives the advertising information described in Section 7 as an independent third party, not as our service provider (see Section 5).
Data retention. We retain personal data only as long as necessary for the purposes for which it was collected and as required by applicable law:
| Data type | Retention period |
|---|---|
| Account profile and onboarding answers | Life of account; deleted when you delete your account |
| Consent records | Life of account; when you delete your account we keep only which versions were accepted and when, with your account ID, IP address, and user agent removed |
| Scenario transcripts, grading results, and other educational data | Life of account; deleted when you delete your account |
| AI-call traces at Langfuse (the prompts, transcripts, and model output behind scenarios, grading, feedback, and coaching) | Life of account; deleted when you delete your account |
| Stripe billing records (at Stripe and our copy of them) | As long as needed for tax, accounting, fraud-prevention, and legal obligations |
| App Store purchase records in our database | Life of account; deleted when you delete your account (Apple keeps its own records) |
| Server and authentication logs | Short-term, under our hosting providers' standard log retention |
| Session recordings | 30 days from creation, then deleted |
| Product analytics events | Up to 7 years, held by PostHog; deleted when you delete your account or on request |
| Support messages | Until your request is resolved and the message is no longer needed, or deleted on request |
| Survey responses in our team chat (Discord) | Up to 12 months, then deleted; deleted sooner on request |
Advertising cookies (_fbp, _fbc, mc_fbc) in your browser | Until they expire (mc_fbc after 90 days) or you clear your cookies |
| Meta cookie value and ad-click identifier saved when you set up your account on our website | Life of account; deleted when you delete your account |
Privacy cookies (mc_pixel_geo, mc_ads_opt_out) in your browser | mc_pixel_geo for 6 hours; mc_ads_opt_out for 2 years or until you opt back in or clear your cookies |
| Advertising information sent to Meta | Held by Meta under its own terms and privacy policy, which we do not control |
| Apple Ads attribution records in our database (iOS app) | Up to 24 months after we record them; records linked to your account are deleted when you delete it |
| Aggregated, de-identified analytics | Indefinite |
Where a period above says "life of account," we do not delete that data on a timer while your account is open; deleting your account removes it, as described in Section 6.
5. Data Sharing
- We do not sell personal data for money. Some state laws define "sale" to include sharing for other things of value, and our advertising sharing with Meta may meet that definition. Under those laws, Meta Platforms, Inc. is the only third party to which we sell or may sell personal data, and the opt-outs in Section 6 cover it.
- We share personal data with the trusted service providers listed in Section 4 to operate and maintain the Services.
- Advertising. Beginning on October 19, 2026, we share limited personal data with Meta through the Meta Pixel and the Meta Conversions API. We do this to measure how our ads on Facebook and Instagram perform and to help Meta show them to people likely to be interested in Medceptor. Meta is a third party, not a sub-processor or service provider: it uses this data under its own terms and privacy policy. Section 7 describes what is shared and on which pages. Under the CCPA/CPRA this is "sharing" for cross-context behavioral advertising, and under other US state privacy laws it is "targeted advertising". You can opt out as described in Section 6.
- Accounts created before October 19, 2026. If your account existed before October 19, 2026, we never send Meta your email address or account ID, in any form, and our servers send Meta nothing about your account. The first-scenario and App Store purchase events in Section 7 are sent only for accounts created on or after the Effective Date shown at the top of this policy. The Meta Pixel can still record your visits to the pages listed in Section 7 unless you opt out.
- The iOS app. If you set up your account in the iOS app, nothing about it is sent to Meta, including App Store purchases, and we never send Meta your email address or account ID, even if you later subscribe on our website. If you set up your account on our website on or after the Effective Date, our servers tell Meta when you start an App Store subscription in the iOS app within 7 days of creating your account (Section 7). Apart from that purchase, nothing from the iOS app is sent to Meta. Apple's own install reports to Meta, described in Section 7, do not identify you.
- We do not share your educational data with Meta, except that our servers may tell Meta that you finished your first practice scenario, without saying which one or how you did (see "What we do not send" in Section 7).
- Apple Ads attribution (Section 7) is not sharing: Apple tells us about its own ads for our app, and apart from exchanging Apple's token with Apple, we send Apple Ads nothing about you.
- If you are enrolled through an institutional plan, we may share relevant training data (such as performance, progress, and account information) with that institution for educational purposes.
- We do not share private user information with schools or instructors outside of institutional plans, and never without explicit consent.
6. Your Rights
Wherever you live in the United States, you can ask us to:
- Access a copy of your personal information.
- Correct inaccurate or incomplete information.
- Delete your personal information.
- Receive your data in a portable format.
- Object to certain processing.
- Opt out of the sale or sharing of personal information, targeted advertising, or profiling for decisions that produce significant effects.
- Appeal any denial of these rights.
If you live outside the United States, you may have similar rights under your local law, and you can use the same contact below.
Opting out of sharing and targeted advertising. You can opt out of our sharing of personal data with Meta for advertising (Sections 5 and 7) in any of the following ways. You do not need an account, and we do not ask you to verify your identity to opt out.
- Your Privacy Choices page: visit https://medceptor.com/privacy-choices. It saves an opt-out cookie in your browser. While the cookie is there, we do not load the Meta Pixel on our public website or the application, and our servers do not send Meta events about a registration, checkout, purchase or finished practice scenario made from that browser. The choice applies only to that browser and device, and clearing your cookies removes it.
- Global Privacy Control or Do Not Track: if your browser sends either signal, we treat it as a request to opt out for that browser (see Section 7). If you are signed in when we receive the Global Privacy Control signal, we also apply the opt-out to your account, so it covers every browser and device where you sign in.
- Settings or email: turn on "Don't share my activity with advertising partners" in Settings on our website (the setting is not shown in the iOS app), or email admin@medceptor.com from the address on your account and we will turn it on for you within 15 business days. While it is on, we do not load the Meta Pixel on any page where you are signed in, and our servers send Meta nothing about your account, on any browser or device. On pages where you are not signed in, such as our public website, also use Your Privacy Choices or the Global Privacy Control in each browser.
To exercise these rights, contact admin@medceptor.com. We will respond within 45 days (extendable by an additional 45 days where permitted by law). We do not discriminate against users who exercise these rights.
Appeals. If we decline a request, we will tell you why. To appeal, reply to our decision or email admin@medceptor.com with "Privacy appeal" in the subject. We will answer in writing within 45 days. If we deny your appeal, you may contact your state attorney general.
Deleting your account. You can delete your account yourself at any time from Settings, or by emailing admin@medceptor.com. Deletion is immediate and permanent: your profile, scenario attempts and transcripts, grading results, charting entries, question-bank and practice-exam history, bookmarks, App Store purchase records, Apple Ads attribution records linked to your account, and other account data are removed from our database at once and cannot be recovered. We also automatically ask PostHog to delete your analytics data, including events and session recordings, and Langfuse to delete the traces of your scenario conversations, grading, and feedback. Other copies held by our providers (for example email delivery records at Resend and contact-form messages at Formspree) are deleted on those providers' own schedules or, on request, within 45 days. We retain only: (a) billing records: Stripe keeps its records of your website payments, and we keep our copy of Stripe's records, for as long as needed for tax, accounting, fraud-prevention, and legal obligations; (b) records necessary to defend legal claims, resolve disputes, or enforce agreements; (c) de-identified, aggregated analytics that cannot be linked to you; and (d) anonymized records of which policy versions were accepted and when. Deleting your account cancels a subscription purchased on our website; it does not cancel a subscription purchased through the App Store, which you must cancel in your device's Settings (see the Terms of Service, Section 13). Once your account is deleted, our servers send Meta nothing more about it. Information already sent to Meta for advertising (Section 7) is held by Meta under its own privacy policy, and we cannot make Meta delete it; to ask Meta to delete information it holds about you, use the options in Meta's Privacy Policy (https://www.facebook.com/privacy/policy).
7. Cookies, Analytics, Advertising, and Session Recording
Authentication uses strictly necessary cookies for session management.
Analytics cookie. We set one first-party analytics cookie, scoped to medceptor.com and its subdomains. It holds a random identifier for your browser and, once you sign in, your account ID, along with details of your current visit and the website that first referred you. Our analytics tool also keeps similar data in your browser's local storage. Its purpose is to recognize that a visit to our public website (medceptor.com) and a later visit to the application (app.medceptor.com) come from the same browser, so we can measure how many visitors go on to create an account and which sources they came from. It is set on your first visit, including before you register. This analytics cookie is for our own analytics only: we do not send its contents to Meta or any other advertising partner. Our advertising cookies are separate and are described under "Advertising cookies and the Meta Pixel" below.
Product analytics and session recording. We use PostHog (a sub-processor listed in Section 4, acting on our behalf under a data-processing agreement) to understand how the Services are used, to diagnose errors, and to deliver feature experiments. This includes:
- Usage analytics — pages viewed, features used, and product events such as starting or completing a scenario. On the application this is associated with your account and includes the questions you ask the study assistants and the feedback and survey answers you give; on our public website it is collected before any account exists, and is linked to your account only if you later register.
- Referral information — the website or link that brought you to us (for example a social media post), so we can understand which sources reach students.
- Session recordings — recorded on the application only, never on our public website. A replay of your interactions with the application (such as mouse movement, clicks, scrolling, navigation, and on-screen content) used to diagnose usability problems and errors. The text you type into form fields is masked and not recorded, and we mask names and email addresses shown on screen. A message you send in a scenario or chat then appears on screen, and is recorded like other on-screen content. Recordings also capture console messages and network timing to help us diagnose errors.
- Heatmaps — where people click and scroll on application pages, combined across users.
- Error monitoring — automatic capture of application errors and diagnostic context.
This data is processed by PostHog on our behalf, and we do not send it to Meta or any other advertising partner. It is retained per the schedule in Section 4.
Advertising cookies and the Meta Pixel. We advertise Medceptor on Facebook and Instagram, which are operated by Meta. To measure how those ads perform, and to help Meta show our ads to people likely to be interested in Medceptor, we send Meta information about a small number of events through two Meta tools: the Meta Pixel, which runs in your browser, and the Meta Conversions API, which sends events from our servers. We do not load the Meta Pixel, set advertising cookies, or send Meta server events for visits whose IP address indicates the European Economic Area, the United Kingdom, or Switzerland.
- Where the Meta Pixel runs. On our public website (medceptor.com), except blog articles and the Your Privacy Choices page, and on the application (app.medceptor.com) only on the sign-up and onboarding pages. It never runs on scenario, practice, question-bank, or study pages, and never in the Medceptor iOS app.
- Advertising cookies. Where the Meta Pixel runs, it sets two
cookies:
_fbp, a random identifier for your browser, and_fbc, which stores an identifier for your click when you arrive by clicking one of our ads. When an ad brings you to one of the application's public pages (such as sign-up, sign-in, or onboarding), our servers also store the same click identifier in a cookie of our own,mc_fbc, for up to 90 days, so that a sign-up or purchase you make later can still be matched to the ad. We do not set it when your browser sends Global Privacy Control or Do Not Track or has the Your Privacy Choices cookie, or for visitors in the European Economic Area, the United Kingdom, or Switzerland, and the Your Privacy Choices page removes it. Our public website does not set it. Our public website also setsmc_pixel_geo(your country code, for 6 hours) to decide whether the Meta Pixel may load, and the Your Privacy Choices page setsmc_ads_opt_out(for 2 years) to remember your opt-out. - Events. We send Meta: a page view for each of the pages listed above; "complete registration" when you finish setting up your account on the web; "initiate checkout" when you open checkout to subscribe on our website; "purchase" when you pay to start a subscription there, or start an App Store subscription in the iOS app; and "first session complete" the first time you finish a practice scenario on our website. The initiate checkout, purchase and first session complete events are sent only from our servers, as described below.
- From your browser (Meta Pixel). With each event, the Meta Pixel
sends Meta information including the page address and the page that
referred you, your IP address, your browser's user agent and basic
device details such as screen size, the time, the
_fbpand_fbcvalues above, and, for a registration, a random event code that lets Meta match it to the same event from our servers. Your browser may also send Meta its own Facebook or Instagram cookies, which can let Meta connect the visit to your Facebook or Instagram account. - From our servers (Meta Conversions API). For accounts created on or after October 19, 2026 and set up on our website, our servers may also send Meta the registration, the opening of a checkout, and a new subscription started on our website. For accounts created on or after the Effective Date shown at the top of this policy and set up on our website, they may also send Meta the first time you finish a practice scenario on our website, and an App Store subscription you start in the iOS app, each only if it is within 7 days of creating your account. Each event is sent with: the event, its time and the page it happened on (for a finished scenario, our scenarios page, never the scenario's own address); an event code (for a registration, the same random code your browser sends; for a checkout or purchase, our payment processor's ID for that checkout; for an App Store subscription, Apple's ID for its first purchase; for a finished scenario, a random code); your email address and your Medceptor account ID, each hashed before it leaves our servers; your IP address and browser user agent (not for an App Store subscription); the Meta cookie values and click identifier from your browser (for an App Store subscription, the ones saved when you set up your account); and the price of the plan for a checkout, or the amount paid for a purchase (after discounts, before sales tax), with its currency. An App Store subscription is sent as a purchase made in our app, marked as one for which you have not allowed tracking. The iOS app does not ask for Apple's tracking permission. Meta does not receive your email address in readable form, but it can match the hashed value to a Facebook or Instagram account that uses the same email address. We never send these server events for accounts created before October 19, 2026 or set up in the iOS app, for subscription renewals, for a scenario finished in the iOS app, or after you opt out (Section 6). An App Store subscription is not made in a browser, so only the opt-out in Settings, which covers your account, stops it; if an opt-out applied to your browser when you set up your account, we keep no cookie values and send no App Store subscription.
- What we do not send. Apart from the fact that you finished your first practice scenario, we do not send Meta your educational data (which scenarios you take, scenario transcripts, scores and grading results, question-bank or practice-exam answers, study-assistant messages), your certification track, or voice recordings. From the Medceptor iOS app we send Meta only the App Store subscription described above; if you set up your account in the iOS app, we never send Meta anything about it.
- Installs from our ads (Apple's SKAdNetwork). If you install the Medceptor iOS app after seeing or tapping one of our ads on Facebook or Instagram, the app lets Apple's SKAdNetwork tell Meta that an install came from that ad. Apple sends this report itself, after a delay, without your name, your account, or any identifier for you or your device, and it may include a broad value we set about early use of the app, such as whether you started a subscription.
Meta receives this information as an independent third party, not as our service provider. Third parties, including Meta, may use cookies, web beacons, and similar technologies to collect or receive information from our websites and elsewhere on the internet, and use that information to provide measurement services and to target ads. The Meta Business Tools Terms and Meta's Privacy Policy (https://www.facebook.com/privacy/policy) govern how Meta uses and retains it.
Opting out of advertising. To stop us sharing your information with Meta, use any of the options in Section 6, including our Your Privacy Choices page (https://medceptor.com/privacy-choices). To control how Meta uses information from other websites and apps to show you ads, use the ad preferences in your Facebook or Instagram account (https://www.facebook.com/adpreferences). You can also opt out of interest-based advertising from participating companies at https://www.aboutads.info/choices or, in Europe, at https://www.youronlinechoices.eu.
Apple Ads attribution (iOS app). We also advertise the Medceptor iOS app in the App Store through Apple Ads. To learn which of those ads bring students, the iOS app uses Apple's attribution service:
- When it runs. On a full page load after you install the app, retried on later page loads up to five attempts in total, then never again. If you already have the app, it runs the same way the first time you open a version that includes it. It never runs on our website.
- What is collected. The app sends our servers an attribution token from Apple and a random identifier it creates for that install (not your device's advertising identifier); the identifier is also kept in the app on your device until you delete the app or your device clears its stored data. Our servers exchange the token with Apple, which returns whether the install came from one of our ads on Apple Ads and, if it did, the campaign, ad group, keyword and ad, the type of install (for example, a first download or a redownload), whether you tapped the ad or only saw it, where in the App Store it appeared (for example, search results or the Today tab), and your country or region. We store Apple's answer as it was sent, which also includes Apple's identifier for our ad account and, when Apple provides it, the date you tapped or saw the ad. Your IP address is used only briefly to limit repeated requests and is not stored with the record.
- How it is used. We store the result and link it to the first account that signs in on that install. For installs that came from an ad, we also record in our product analytics (PostHog), against your account, the campaign, ad group, keyword and ad, your country or region, whether you tapped the ad or only saw it, whether it was a first download or a redownload, and whether your account existed before the ad, so we can see which campaigns lead to students who stay and subscribe.
- What it is not. It does not track you across other companies' apps or websites and does not ask for or need your permission to track. Apart from exchanging Apple's token with Apple, we send Apple Ads nothing about you, and we send nothing to any other advertiser. It is not a sale or sharing of personal information.
We keep the attribution records in our database for up to 24 months after we record them, and delete the records linked to your account when you delete it. The campaign details in our product analytics follow the product analytics retention in Section 4 and are deleted with your account. To ask us to delete them sooner, email admin@medceptor.com.
Your choices. We honor the Global Privacy Control ("GPC") and browser "Do Not Track" signals: when your browser sends either signal, we do not load the Meta Pixel or start our analytics or session recording in your browser, and our servers send Meta nothing about a registration, checkout, purchase or finished practice scenario made from that browser. If you are signed in when we receive the GPC signal, we also apply the opt-out to your account (Section 6). We still record some product events on our own servers while you use the application, such as completing a scenario or a question you ask a study assistant, to run and improve the Services; apart from the first finished practice scenario described in Section 7, these are never sent to Meta. Many privacy-focused browsers and extensions can send these signals on your behalf. The iOS app cannot send them, and they do not cover Apple Ads attribution; to delete that data, email us as described above. You may also request deletion of analytics data associated with you by contacting admin@medceptor.com (see Section 6).
8. Security
We protect user data with encryption in transit and at rest, access controls, and regular security review. No system is completely secure, and we cannot guarantee absolute security of your data.
Breach notification. In the event of a confirmed personal data breach affecting your information, we will notify you without undue delay and in any event within 60 days of confirmation, or sooner where required by law (for example, within 72 hours to EU supervisory authorities under GDPR Article 33). Notice will describe the nature of the breach, the categories of data involved, the likely consequences, and the remediation steps taken.
9. Children's Privacy
The Services are intended for adults aged 18 and older. We do not knowingly collect personal information from anyone under 18. If we discover we have inadvertently collected data from a user under 18, we will delete it within 30 days, and we will stop sending information about that person to advertising partners as soon as we discover it. Instructors are encouraged to supervise students using the Services in classroom settings.
10. International Transfers
The Services are operated in the United States and are intended for users located in the United States. We do not target or actively market the Services to users in the European Economic Area, the United Kingdom, or Switzerland, and we do not load the Meta Pixel or send Meta server events for visits whose IP address indicates those places. If you access the Services from outside the United States, your information will be transferred to and processed in the United States and, for the AI processing described in Section 3, in the countries where our model providers and the companies that host their models operate.
Where our service providers offer Standard Contractual Clauses or similar safeguards for international transfers, we rely on them.
11. California Residents (CCPA / CPRA)
This section applies to California residents and supplements the rest of this Privacy Policy.
Categories of personal information we collect (under the CCPA's classifications):
- Identifiers (name, email, phone, IP address, account ID, advertising cookie and ad-click identifiers, advertising event codes, a random identifier for each install of the iOS app, and the email addresses instructors enter to invite students)
- Customer records (account profile, certification track, school or program name, onboarding answers, billing name and address, and consent records)
- Commercial information (subscription state, payment history, and your card's brand and last four digits)
- Internet or network activity (log data, session metadata, session recordings, the page views and events collected for advertising described in Section 7, and the Apple Ads campaign, if any, that led to your iOS app install)
- Audio information (voice clips, if you use optional dictation — transcribed and not stored)
- Geolocation data (coarse location inferred from IP)
- Professional information (self-reported certification track, student or instructor status)
- Education information (scenario attempts, grading results, question-bank and practice-exam history)
- Feedback (ratings, comments, and survey and quiz answers)
- Inferences (learning progress derived from rubric performance)
- Sensitive personal information: account login credentials, used only to sign you in and secure your account
All categories above are disclosed to the service providers in Section 4 as needed to operate the Services.
Categories of sources: directly from you; automatically from your device; from Google or Apple if you sign in with them (your name, email, and, for Google, profile picture); from Apple, for Apple Ads attribution in the iOS app (Section 7); from an instructor who invites you to a class (your email address); and from your institutional administrator if you are enrolled through an institutional plan.
Business purposes: providing and operating the Services, processing payments, security and fraud prevention, analytics, session recording for diagnostics, speech-to-text transcription, and AI-generated scenario responses, tutoring, and grading.
Commercial purposes: advertising Medceptor on Facebook and Instagram, including cross-context behavioral advertising through Meta (Sections 5 and 7).
Who receives personal information: the providers listed in Section 4, to operate the Services. Those with a data-processing agreement receive it as our service providers or contractors; the others receive it as third parties under their own terms, only for the business purposes above and never for advertising. Meta Platforms, Inc. receives the information described in Section 7 as a third party, for advertising.
Do Not Sell or Share. We do not sell personal information for money. Beginning on October 19, 2026, we "share" personal information, as the CCPA/CPRA defines that term, for cross-context behavioral advertising, and this may also count as a "sale" under the CCPA because Meta gives us ad measurement and delivery in return. Before that date, we did not sell or share personal information. We sell or share the following categories, and only with Meta Platforms, Inc.:
- Identifiers: IP address, advertising cookie and ad-click identifiers, advertising event codes, and, for accounts created on or after October 19, 2026 and set up on our website, your email address and Medceptor account ID in hashed form
- Internet or network activity: your visits to the pages where the Meta Pixel runs, your browser's user agent and basic device details, and the events described in Section 7, with their times
- Commercial information: that you opened checkout or paid to start a subscription on our website, or started an App Store subscription in the iOS app (Section 7), the plan's price or the amount paid, and its currency
We share this information to measure how our ads perform and to help Meta show our ads to people likely to be interested in Medceptor. You can opt out at any time, without verifying your identity: use our Your Privacy Choices page (https://medceptor.com/privacy-choices), enable the Global Privacy Control in your browser (which we treat as a valid request to opt out for that browser and, if you are signed in, for your account), turn on the setting in Settings, or email admin@medceptor.com. Section 6 explains each option. We do not have actual knowledge that we sell or share the personal information of consumers under 16 years of age; the Services are for adults 18 and older (Section 9).
Sensitive personal information. We do not collect or process sensitive personal information for the purpose of inferring characteristics about consumers. The only sensitive personal information we collect is your account login credentials, used only to sign you in and secure your account.
Verifiable consumer requests. To exercise your CCPA rights (access, deletion, correction, portability, limit use of sensitive PI, no retaliation), email admin@medceptor.com. We will verify your identity using your account credentials and respond within 45 days. Requests to opt out of sharing do not require verification; see "Do Not Sell or Share" above. You may also designate an authorized agent to make requests on your behalf, subject to verification. You can appeal a decision as described in Section 6.
Non-discrimination. We do not discriminate against consumers who exercise their CCPA rights. We do not offer financial incentives in exchange for personal information.
12. Texas Residents (TDPSA)
This section applies to Texas residents and supplements the rest of this Privacy Policy.
We do not sell sensitive personal data or biometric personal data.
Targeted advertising. We process personal data for targeted advertising: we share limited personal data with Meta Platforms, Inc. so that our ads on Facebook and Instagram can be measured and shown to people likely to be interested in Medceptor (Sections 5 and 7). You can opt out at any time through our Your Privacy Choices page (https://medceptor.com/privacy-choices), the Global Privacy Control or Do Not Track, the setting in Settings, or by emailing admin@medceptor.com (Section 6).
To exercise your rights under the Texas Data Privacy and Security Act (access, correction, deletion, portability, opt-out of sale, opt-out of targeted advertising, opt-out of profiling), email admin@medceptor.com. We will respond within 45 days and provide an appeal mechanism if any request is denied (Section 6).
13. Changes to This Policy
When we make a material change, the app will ask you to accept it before you keep using the Services. We will not apply a material change to personal information we collected before the change unless you agree to it. Continued use after a non-material revision does not constitute acceptance of the new policy.
14. Contact
For questions about this Privacy Policy, contact admin@medceptor.com.