Medceptor Privacy Policy
Effective Date: September 7, 2026
Entity: IDK Studios, Inc., a Texas corporation (operating as Medceptor)
Registered Office: 262 Fawn Trail, Lake Jackson, TX 77566
Contact: admin@medceptor.com
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. See Section 7.
When you register and use Medceptor (the "Services"), we collect:
- Account information: name, email, display name, optional phone number, optional avatar, 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 and how you heard about us. 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.
- 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. 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).
- Payment information: processed by Stripe (website purchases) or Apple (in-app purchases in the Medceptor iOS app). We never see or store your card number. For Stripe purchases we store the Stripe customer and subscription identifiers and your subscription state (plan, status, billing period). 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. 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 or organization you provide, along with the page you were on and your browser type) and by email.
- Technical information: log data, browser and device information, IP addresses, session metadata, and session recordings of your interactions with the application (with the form inputs you type and account identifiers such as your name and email masked) — see Section 7.
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.
- 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.
- Respond to your support and contact requests.
- 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 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 when DeepSeek is unavailable.
Conversation and study-assistant requests are routed through Vercel AI Gateway, which forwards them to the provider under our own API credentials or, if ours fail, under Vercel's. Vercel states that the gateway does not retain prompts or responses and does not use them for training.
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. 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.
4. Data Storage and Sub-Processors
We rely on the following sub-processors, each under a data-processing agreement:
- 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.
- 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.
- 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.
- Inngest — durable function execution for the grader pipeline and billing reconciliation.
- Langfuse — tracing of the AI calls behind scenario conversations and grading. 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.
- 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 described in Section 2.
- Formspree — delivery of messages you submit through the in-app and website contact forms.
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 | Life of account; deleted when you delete your account |
| Scenario transcripts, grading results, and other educational data | Life of account; deleted when you delete your account |
| Payment records (via Stripe or Apple) | 7 years (tax and accounting compliance) |
| 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 on request |
| Support messages | Until your request is resolved and the message is no longer needed, or deleted on request |
| 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 is how you remove it. Deletion is immediate and permanent: your profile, scenario attempts and transcripts, grading results, charting entries, question-bank and practice-exam history, and bookmarks are removed from our database at once. Copies held by our processors — analytics events at PostHog, AI-call traces at Langfuse, email delivery records at Resend — are deleted on those processors' own schedules or on request (Section 6). Payment records remain with Stripe or Apple as required by law.
5. Data Sharing
- We do not sell personal data to third parties.
- We share personal data only with the trusted sub-processors listed in Section 4 to operate and maintain the Services.
- 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
Depending on your jurisdiction (including California, Texas, Virginia, Colorado, Connecticut, Utah, Oregon, Montana, Iowa, Tennessee, Indiana, Florida, Delaware, EU/EEA, and UK), you may have rights 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.
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.
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, and other account data are removed from our database at once and cannot be recovered. Copies held by our processors (for example analytics events at PostHog and AI-call traces at Langfuse) are deleted on those processors' own schedules or, on request, within 45 days. We retain only: (a) payment and transaction records, which remain with Stripe or Apple and in our billing records for 7 years for tax compliance; (b) records necessary to defend legal claims, resolve disputes, or enforce agreements; and (c) de-identified, aggregated analytics that cannot be linked to you. 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).
7. Cookies, Analytics, 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, holding a random identifier for your browser. 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. We do not use advertising cookies, and we do not share this identifier with third parties for advertising or track you across websites we do not operate.
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; 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 account identifiers such as your name and email in recordings.
- Error monitoring — automatic capture of application errors and diagnostic context.
This data is processed by PostHog on our behalf and is not used for cross-site advertising. It is retained per the schedule in Section 4.
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 analytics or session recording for your session, on the application or on our public website. Many privacy-focused browsers and extensions can send these signals on your behalf. 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. 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. 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 operate.
For any transfers from the EEA, UK, or Switzerland that may occur, we rely on appropriate safeguards, including the European Commission's 2021 Standard Contractual Clauses (Module 2, controller-to-processor), the UK International Data Transfer Addendum, or other lawful transfer mechanisms.
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)
- Customer records (account profile, certification track, school or program name)
- Commercial information (subscription state, payment history)
- Internet or network activity (log data, session metadata, session recordings)
- 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)
- Inferences (learning progress derived from rubric performance)
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); 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.
Categories of third parties with whom we share personal information: the sub-processors listed in Section 4.
Do Not Sell or Share. We do not sell or share personal information as those terms are defined under the CCPA/CPRA, including for cross-context behavioral advertising. We have not done so in the preceding 12 months. We honor opt-out preference signals, including the Global Privacy Control, as described in Section 7.
Sensitive personal information. We do not collect or process sensitive personal information for the purpose of inferring characteristics about consumers.
Verifiable consumer requests. To exercise your CCPA rights (access, deletion, correction, portability, opt-out, 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. You may also designate an authorized agent to make requests on your behalf, subject to verification.
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.
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.
13. Changes to This Policy
Material changes trigger a re-acceptance flow; 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.