Skip to main content

We use analytics and advertising cookies and similar technologies (Google Analytics, PostHog and the Meta Pixel) to understand how MedMock is used and whether our adverts work. PostHog also records how pages are used, with anything you type hidden. Essential features work without them. See our cookie policy.

MedMock
How it WorksExams and InterviewsPricingAbout Us
Log InSign Up

Cookie Policy

Last updated: 13 November 2026

Please read this cookie policy carefully. It explains how VIRTUALPATIENTS LTD, company number 16303492, incorporated in England and Wales with its registered office at 2 St. Marys Road, Tonbridge, England, TN9 2LB, trading as “MedMock” (“MedMock”, “we”, “us” or “our”), uses cookies and similar technologies on https://medmock.com and the MedMock browser-based platform (together, the “Service”). This policy should be read together with our Privacy Policy, which explains how we collect, use and protect personal data, your rights and how to contact us or a supervisory authority.

1. Cookies

A cookie is a small text file placed on your device (for example, your computer, smartphone or tablet) when you visit or use the Service. We may also use local storage and similar technologies that store or access information on your device. These technologies can recognise your browser or device, remember information about your visit and support the operation, security and improvement of the Service. References in this policy to cookies include these similar technologies where relevant. Our consent banner offers Accept and Decline choices and links to this Cookie Policy before any non-essential cookie or similar technology stores or accesses information on your device.

Cookies help us keep the Service secure, maintain sessions, enable account and sign-in features, remember your choices and understand how users interact with the Service.

For example, with your consent we may use analytics cookies to understand how often the Service is used, which pages and features users visit, how users move around the Service and whether it is functioning properly. Analytics information may be aggregated or statistical, but online identifiers and related usage information can still constitute personal data.

Further information on the categories of cookies and the cookie information is set out below. The live consent tool provides the current choices available on your device.

For further information on cookies generally, including how to control and manage them, visit the guidance published by the UK Information Commissioner’s Office.

2. Consent and changing your settings

We ask for your prior consent before storing or accessing non-essential cookies or similar technologies on your device. Strictly necessary technologies may operate without consent where they are required to provide the Service or a feature you have requested, such as secure sign-in, session management or security. Consent is requested through an affirmative choice: non-essential cookies and similar storage technologies are not enabled by default, there are no pre-ticked consent options, and continued browsing is not treated as consent. Google and Meta code does not load before you accept non-essential cookies. Please see our Privacy Policy for information about the associated processing of personal data.

When first asked, you can accept or reject non-essential cookies, and rejecting them is as easy as accepting them. You can withdraw consent or change your preferences at any time using the “Cookie settings” control available in the footer of our public pages and in Profile & Settings, or here: . Withdrawing consent is as easy as giving it and does not affect the lawfulness of processing before withdrawal. Your updated choice applies from that point. We will stop setting or accessing the relevant non-essential technologies, although you may need to refresh the Service and may delete previously stored cookies through your browser. Strictly necessary technologies cannot be disabled through our settings tool because they are needed to provide the Service or a feature you request. We retain your cookie choice for up to 13 months and will then ask you to choose again; we may ask sooner if our use of cookies or the purposes for which you consented change materially.

3. Our use of cookies

The Service currently uses the following categories of technology:

  • Strictly necessary technologies: These are required for the operation, security and availability of the Service or to provide a feature you have requested. They may support secure sign-in, authentication, session management, account features, security, fraud prevention and recording your cookie choices. They may operate without consent where an exemption under the Privacy and Electronic Communications (EC Directive) Regulations 2003 (PECR) applies. If you block them in your browser, parts of the Service may not work.
  • Analytics technologies: Google Analytics helps us understand how visitors use and interact with the Service, measure performance, identify errors and improve its operation. Google Analytics does not load unless you actively consent through our consent tool. If you actively consent, Google Analytics sets cookies and, for a signed-in user, we send Google Analytics your account’s internal user ID (a random string, not your name or email address) to help us understand use across that user’s devices. PostHog, hosted in the European Union (Frankfurt), also helps us understand how the Service is used, including recordings of how our web pages are used (clicks, scrolling and what is shown on screen, with anything typed into a form field hidden) so that we can find and fix problems. PostHog does not load unless you actively consent through our consent tool, and it does not load in the MedMock iPhone or Android apps. It keeps its identifiers in your browser’s storage rather than in cookies and, for a signed-in user, we send it the same internal user ID. You can later withdraw that consent through the same settings.
  • Advertising technologies: We use the Meta Pixel to measure the effectiveness of our advertising. Meta’s script does not load unless you actively consent through our consent tool. If you actively consent, the Meta Pixel may set or access _fbp for advertising measurement. We also use first-touch attribution information to understand which website, campaign or advertisement brought a visitor to the Service. This may include a referral URL, campaign label or OpenAI advertising click identifier and, if the visitor later creates an account, may be copied to that account. We do not store or access that non-essential attribution information on your device unless you consent.
  • First- and third-party technologies: First-party technologies are set by us. Third-party technologies are set or provided by another organisation whose services are used in the Service. Google provides Google Analytics, PostHog provides PostHog analytics and session recordings, Meta provides the Meta Pixel and Cloudflare provides Turnstile. Those providers may receive information generated by their technologies and process it under their own privacy information. The cookie information below identifies the relevant provider, purpose, category and duration, and the live consent tool provides the available choices. We obtain prior consent before storing or accessing non-essential third-party technologies and review retention periods so that they are no longer than necessary for the stated purpose.
The cookies we useNamePurposeWhether the cookie is essential for us to provide you with a service that you have requested and whether we will seek your consent before we place the cookie
MedMock essential and functional first-party technologies; Google Firebase Authentication; Cloudflare Turnstile__session; Google Firebase authentication browser storage; mm_cookie_consent; Turnstile tokens; other MedMock browser-storage items: mm_examiner_mode, mm_show_mood, mm_autosend_mode, mm_send_delay_ms, mm_delayhint_seen, mm_frcsct_subspecialty, mm_frcsto_drill_view, mm_lounge_game, mm_defib_best, mm_oncall_best, selectedExamId, mm_station_resume_v1, mm_live_station_v1, mm_live_station_scenario_v1, mm_live_station_draft_v1, cons_full_panel_v1, fullmock_<exam> items and medmock-referral-draft-v1

__session supports session management and enables candidates to view case images in their sessions. Google Firebase authentication browser storage maintains sign-in until the user signs out. mm_cookie_consent records your cookie choice. Cloudflare Turnstile tokens help detect bots and protect sign-up, sign-in, password reset, contact and report-a-problem forms. The other MedMock items remember interface settings, game scores and the exam you last chose, keep practice in progress so that you can carry on after a refresh, and keep a referral code typed into the sign-up form.

These technologies may process a session identifier, authentication information, consent choice, security and bot-detection signals, interface preferences, game-score information, practice-in-progress information and a referral code.

__session: 30 days for candidates and 12 hours for organisation, reviewer and staff logins. Google Firebase authentication browser storage: until the user signs out. mm_cookie_consent: up to 13 months. Turnstile tokens: up to five minutes. Interface settings, game scores and the exam you last chose: until the relevant setting or score is replaced, or you clear the information through your browser or device settings. Practice in progress: until the browser tab is closed or, for a full mock exam, until the mock ends. medmock-referral-draft-v1: until the browser tab is closed.

For information about Cloudflare’s processing, see https://www.cloudflare.com/privacypolicy/.

__session, Google Firebase authentication browser storage, mm_cookie_consent and Turnstile tokens are essential, so we do not request consent before using them. We request consent for other items unless they are strictly necessary to provide a setting or feature you requested.
Google Analytics (Google); PostHog (PostHog); Meta Pixel (Meta); MedMock first-touch attribution and analytics markers_ga; _ga_<id>; ph_<project key>_posthog and other ph_ and __ph_ browser-storage items; _fbp; mm_first_touch; mm_activated; mm_purchase_<id>; mm_score_recorded_<id>

Google Analytics measures visits, use across pages and features, performance and, for consenting signed-in users, use across devices by reference to the account’s internal user ID (a random string, not the user’s name or email address). _ga and _ga_<id> remain for up to two years. See https://policies.google.com/privacy.

PostHog measures visits and use across pages and features and records how our web pages are used (clicks, scrolling and what is shown on screen, with anything typed into a form field hidden), and for consenting signed-in users links that use to the account’s internal user ID. Its browser-storage items remain until you withdraw your consent, your cookie choice runs out, or you clear them through your browser; PostHog keeps session recordings for 30 days and other analytics data for up to one year. See https://posthog.com/privacy.

Meta Pixel measures advertising effectiveness; _fbp remains for about three months. See https://www.facebook.com/privacy/policy/.

mm_first_touch records the referring website, campaign label and, where applicable, an OpenAI advertising click identifier; it may be copied to an account at sign-up. mm_first_touch remains for up to 13 months.

mm_activated, mm_purchase_<id> and mm_score_recorded_<id> are our own markers that stop an analytics event (a first completed station, a purchase or a recorded score) being counted twice. They remain until you withdraw your consent, your cookie choice runs out, or you clear them through your browser.

No. We request your consent before storing or accessing these technologies on your device.

4. Browser controls and consequences of turning off cookies

In addition to using our consent-management settings, you can usually configure your browser or device to block, limit or delete cookies and local storage. Controls vary, so consult the help or settings pages for your browser or device. Blocking or deleting cookies, especially strictly necessary ones, may prevent secure sign-in, session management, account features or other parts of the Service from working properly. Browser settings do not replace the choices available through our consent-management settings and may not communicate a withdrawal of consent to us, so please also update your choice through the “Cookie settings” control.

5. Changes to this policy

We may change this cookie policy from time to time, including where the technologies used by the Service, the law or regulatory guidance change. We will publish the updated policy and, where a change materially affects your choices, provide an appropriate notice and request fresh consent where required. If you have questions about this policy or our use of cookies, or wish to exercise data-protection rights, please contact us through the contact form on https://medmock.com, by email at contact@medmock.com or by post at VIRTUALPATIENTS LTD, 2 St. Marys Road, Tonbridge, England, TN9 2LB. Further information about how we process personal data is available in our Privacy Policy at https://medmock.com/privacy.

MedMock

© 2026 VirtualPatients LTD. All rights reserved.

  • YouTube
  • LinkedIn
  • Instagram
  • TikTok
  • About Us
  • Contact
  • Privacy Policy
  • Terms of Service
  • Cookie Policy
  • Website Terms
  • Accessibility