Back to Home
EM
EMERGE MEDICAL
Legal & Compliance Documentation

Privacy Policy

Emerge Medical Simulation • Owned & Operated by Emerge Medical (Published via ExeDev) • Effective Date: October 26, 2026

Zero Patient Data

We never collect, process, or store real-patient PHI. All casualties are 100% simulated.

Anonymous Access

No personal registration or passwords. Access is granted via temporary Exercise Session Codes.

UK / EU GDPR Compliant

Fully adheres to the UK Data Protection Act 2018 and Apple / Google developer guidelines.

1. Introduction & Overview

Emerge Medical (“we”, “us”, or “our”) is the exclusive owner and operator of the Emerge Medical Simulation platform and associated clinical management tools (collectively, the “Platform”). ExeDev serves solely as the authorized technical distribution and publishing partner on public mobile app stores.

The Platform is engineered strictly as an educational and simulation training ecosystem for first responders, emergency services, medical personnel, and military responders (including event first aiders, law enforcement tactical units, Hazardous Area Response Teams (HART), and Helicopter Emergency Medical Services (HEMS)). We are firmly committed to safeguarding user privacy and complying with all applicable statutory data protection requirements, including the UK Data Protection Act 2018, UK GDPR, and mobile application store compliance frameworks (Apple App Store Review Guidelines and Google Play Developer Policies).

2. Strict Non-Collection of Live Patient Health Data (PHI)

The Platform is exclusively a simulation system. We do not collect, process, host, or transmit any live patient Protected Health Information (PHI) or personal medical records. All casualty scenarios, physiological curves, vital signs, injury descriptions, and medical histories displayed or calculated within the application are synthetic, fictitious parameters created solely for emergency drill education.

3. Anonymous Participant Access Architecture

To protect user privacy and eliminate operational hurdles during tactical drills:

  • Mobile participants connect via ephemeral Firebase Anonymous Authentication paired with an authorized Exercise Session Code.
  • No permanent personal account registration, email address, password, or credit card information is required to run the mobile application.
  • Operational tags entered by participants (e.g. callsigns like Medic-1 or staff initials) are ephemeral session identifiers used exclusively to synchronize real-time telemetry and directing staff logs during an active exercise. Participants and directing staff must never submit classified operational codenames, military service numbers, police badge credentials, or real-world tactical intelligence into session fields.

4. Information We Collect & How It Is Used

A. Simulation Telemetry

Simulated clinical actions (tourniquets, needle chest decompressions, TXA administration, triage category selections), timestamps, and Directing Staff (DS) notes. Used strictly for real-time exercise orchestration and post-exercise After-Action Review (AAR) debrief reports.

B. Device & Diagnostic Data

Operating system type/version, device model, and crash traces processed via Google Firebase Crashlytics to resolve memory leaks and application crashes. Crash reports do not contain personal identifiers.

C. Hardware Sensors & Permissions

NFC hardware is utilized exclusively to scan simulation casualty tags and wristbands (reading tag UIDs/NDEF payloads). Microphones and live biometric sensors are never accessed or recorded.

5. Data Sharing & Third-Party Infrastructure

We do not sell, rent, monetize, or trade any exercise or user data. Cloud services are hosted securely on Google Cloud Platform / Firebase located in secure European/UK data centers meeting ISO/IEC 27001 standards. Telemetry is accessible only to authorized instructors and coordinators managing the specific Exercise Session Code.

6. In-Memory Decryption & Data Retention

Proprietary scenario curves and clinical algorithms are transmitted via TLS 1.3, decrypted strictly in device volatile memory (RAM), and zeroed out upon session exit. Exercise telemetry on the cloud may be archived or deleted by authorized organizational instructors upon conclusion of debrief analytics.

7. User Rights & Contact Information

Under the UK GDPR and Data Protection Act 2018, participants and organizations have the right to access, rectify, or request deletion of data associated with their simulation exercises.

Platform Owner & Operator: Emerge Medical

App Store Publishing Partner: ExeDev (Distribution Only)

Clinical Governance Team: governance@emergemedical.co.uk

Privacy Inquiries: privacy@emergemedical.co.uk