Privacy Policy

Effective date: 2026-10-18

Summary (plain English)

• EDPro sends limited telemetry to help us ship updates and tune stability/scoring. There is no in-app opt-out. If you do not agree, do not install or use EDPro.
• Miravia Softworks does not sell your data and will never sell your data. We do not receive money, non-monetary compensation, or other valuable consideration in exchange for user data, and we do not share personal data for cross-context behavioral advertising.
• Telemetry is designed to be data-minimized and pseudonymised (random IDs; obfuscated identifiers). Some server logs may still contain IP addresses for short periods for security/abuse prevention.
• When you activate and use Multiplayer, EDPro uses Epic Account Services authentication and Epic Online Services Connect, Lobbies, and Peer-to-Peer for sign-in, pseudonymous multiplayer identity, room membership, and online connectivity.

Who we are

Miravia Softworks (“we”, “us”, “our”) operates this website, our Discord community, and distributes software for EmergencyDispatcherPro (EDPro). Contact: privacy@miraviasoftworks.com.

Scope

This policy covers (i) our website, (ii) our Discord community, and (iii) EDPro software builds and related backend services (including licensing, updates, and EDPro application telemetry).

Definitions

• Personal data means information relating to an identified or identifiable person.
• Pseudonymised means identifiers are replaced/obfuscated (e.g., one-way hashing or random IDs) but the data may still be personal data under GDPR if it could be linkable in any way.
• Telemetry means limited technical and usage event data sent from EDPro to help us maintain and improve EDPro.

Data we process

• Player Portal accounts: your email address, display name and account identifiers; a password hash; encrypted authenticator secrets or your selected email verification factor; recovery-code hashes, sessions, remembered-device records and security events needed to protect your account. Linking EDPro associates your portal account with a verified license entitlement. We record the versions and hashes of the Terms of Use and Privacy Policy you accepted or acknowledged, together with the acceptance time. These records establish which documents applied to your account; they do not enroll you in optional features or marketing. Optional portal features may store the debriefs, achievements, shared operation information or community hospital recommendations that you choose to submit.
• Website: server logs (IP address, user agent, requested URLs, referrer, timestamps) for security, abuse prevention, and operations; essential cookies only. Optional analytics (if enabled by you) is described below.
• Downloads & updater (EDPro builds): when you download EDPro builds from our site or when the in-app updater checks for or downloads an update, our servers may log your IP address, timestamp, requested file or version (e.g. EDPro_1.x_package.zip), and basic HTTP metadata (user agent, status code). This is used to deliver the download, prevent abuse (e.g. automated scraping or excessive download attempts), and diagnose update delivery problems.
• License / key validation (EDPro): when EDPro validates a license, trial entitlement, or access key against our license service, we process:
  • the license or access key you enter
  • a machine identifier in obfuscated/fingerprint form (not a raw MAC address)
  • timestamps and validation results (e.g. valid, invalid, revoked)

  Our servers also receive network metadata in standard server logs (including IP address) for security and abuse prevention. We use this to enforce access rules, prevent key sharing/abuse, and troubleshoot licensing problems.

• Epic Account Services and Epic Online Services multiplayer: when you activate and use Multiplayer, EDPro uses Epic Account Services for Epic Games account authentication and Epic Online Services (EOS) Connect, Lobbies, and Peer-to-Peer, including relay connectivity where needed. This supports account sign-in, pseudonymous multiplayer identity, lobby participation, operation communication, and P2P/relay connectivity. Epic may process:
  • your Epic account identifier and Basic Profile information involved in authentication, such as display name and language preferences;
  • the pseudonymous Product User ID used by EOS Connect;
  • service, session, lobby, and lobby-member identifiers and service data;
  • network and connectivity data, including IP/network metadata inherent in online connectivity; and
  • Epic service, quality-of-service, and technical telemetry.

  EDPro does not intentionally send Epic your detailed patient simulation or treatment history, Aerosoft serial, Miravia account password, or server private signing keys. Epic identity does not authorize EDPro licenses, Miravia account links, mission generation, survivor rosters, or scoring.

  The in-app Multiplayer activation and supplemental terms are separate from this Privacy Policy. This policy describes the processing; it does not itself treat your reading of the policy as consent to processing.

• EDPro application telemetry (required for EDPro use): EDPro sends limited telemetry to Miravia Softworks as part of normal operation for quality, stability, tuning, and update planning. Telemetry is limited to EDPro and is designed to be data-minimized and pseudonymised. It may include:
  • Random IDs: randomized session identifiers and/or randomized installation identifiers (not your name/email).
  • App usage: time in app, missions started/completed, feature usage, and coarse performance diagnostics.
  • Mission/scoring metrics: mission type, generator seed/variant, phase timings, scoring breakdowns and outcomes (for tuning/balancing).
  • Compatibility: spawn and asset success/failure (e.g., object titles that failed to spawn), and version info (app/OS/runtime).
  • Diagnostics: limited error/exception information relevant to EDPro stability (we avoid collecting unnecessary content).

  What we do not intentionally collect in EDPro telemetry:

  • your name, email address, or account credentials (unless you separately contact us for support)
  • precise real-world location (street address or GPS coordinates)
  • message/chat content, keystrokes, microphone audio, or unrelated files
  • payment card data (we do not request it through EDPro telemetry)
  • special category/sensitive data (e.g., health, religion, political opinions)

  Obfuscation & minimization measures:

  • Telemetry identifiers are randomized; we do not require you to create an account to send telemetry.
  • Machine identifiers used for licensing and anti-abuse are stored in obfuscated/fingerprint form (e.g., one-way transformation). These may still be personal data under GDPR.
  • IP addresses may appear in server logs for endpoints (downloads, licensing, telemetry ingestion) for security/abuse prevention, and are retained for a limited period (see Retention).

  No telemetry opt-out: EDPro telemetry is part of using the software. If you do not agree with this processing, do not install or use EDPro.

• Discord: your Discord username/ID/avatar, roles, messages, reactions; support content you submit (logs/screens/specs); and moderation records. Discord is a separate service provider with its own privacy policy.

Purposes & legal bases (GDPR Art. 6)

• Provide and secure services (Art. 6(1)(f) legitimate interests) – operating the website, Discord community, and EDPro backend services; serving downloads; handling in-app updates; enforcing license and trial access; preventing fraud and abuse; and securing systems.
• Operate EDPro and improve quality/stability (Art. 6(1)(f) legitimate interests) – processing limited EDPro telemetry to improve stability, performance, mission/scoring balance, and compatibility. We apply data minimization and pseudonymisation and retain telemetry for a limited period.
• License/key enforcement and access control (Art. 6(1)(b) contract and/or Art. 6(1)(f) legitimate interests) – validating keys and enforcing access rules required to deliver EDPro, trials, updates, and related services while preventing abuse.
• Multiplayer connectivity (Art. 6(1)(b) contract and/or Art. 6(1)(f) legitimate interests) – providing requested multiplayer identity, private lobby participation, peer/relay connectivity, and operation communication, and protecting those services from abuse.
• Support (Art. 6(1)(b) contract / pre-contract steps) – responding to support requests and diagnosing issues you report.
• Optional website analytics (Art. 6(1)(a) consent, if used) – if we run non-essential analytics on the website where consent is required, we will only do so when enabled/accepted by you.
• Legal compliance (Art. 6(1)(c) legal obligation) – where we must retain or disclose data under applicable law.

Retention

• Player Portal accounts and terms records: maintained for the account and the services you request, subject to applicable erasure rights and any necessary legal retention. We retain the accepted document versions so that acceptance can be checked accurately. You can contact our privacy address to request account erasure or further information about retained records.
• Server logs (website, downloads, license/update/telemetry endpoints): typically up to 90 days (longer only if needed for security, abuse investigations, or debugging).
• EDPro application telemetry: typically 30 days in pseudonymised form. We may keep aggregated statistical reports longer where they no longer relate to an identifiable person.
• License/key records: retained while a key is active and for a reasonable period thereafter to enforce access rules, investigate abuse, and maintain auditability (machine identifiers are stored in obfuscated form).
• Multiplayer records: live lobby/member and connectivity identifiers are used for the session. Our operation-control and security records are retained only as needed to provide the operation, enforce access, investigate abuse, and meet the server-log periods above. Epic controls retention of data in EOS under its applicable terms and privacy materials.
• Moderation records: up to 12 months after action or while relevant.
• Support tickets: up to 24 months.
• Website analytics (if enabled): retained per the analytics configuration (e.g., GA4 user-/event-level data up to 14 months; aggregated reports may persist).

We do not sell user data

Miravia Softworks does not sell your data and will never sell your data. We do not receive money or other monetary compensation for user data, and we do not receive non-monetary compensation or other valuable consideration in exchange for user data. We do not share personal data for cross-context behavioral advertising.

We disclose limited data to service providers only so they can provide contracted services to Miravia, such as hosting, licensing, security, telemetry, and Epic Account Services and Epic Online Services. Miravia does not receive compensation or valuable consideration for these disclosures, and those providers are not being sold the data. The “Sharing & processors” section below explains these processing relationships.

Sharing & processors

We use service providers for hosting, email, error/uptime monitoring, and moderation bots (“processors”). They process data on our instructions and under contract. When Multiplayer is activated and used, Epic Games and its service providers receive the limited Epic account, Product User ID, lobby/member, network, and technical data described above to provide Epic Account Services and Epic Online Services. We do not sell personal information and we do not share it for cross-context behavioral advertising.

International transfers

If data is transferred outside the EEA/UK (for example, to the US), we use appropriate safeguards such as the EU Standard Contractual Clauses (plus the UK Addendum where applicable) and technical/organizational measures. Epic Account Services and EOS may involve processing in countries where Epic or its service providers operate; applicable transfer safeguards and user rights remain subject to the relevant legal requirements and Epic service documentation.

Your rights

Under GDPR/UK GDPR you may request access, rectification, erasure, restriction, portability, or object to processing. Where we rely on legitimate interests, you may object based on your particular situation. If you object to processing that is necessary to operate EDPro (such as required telemetry, licensing, and security measures), we may be unable to provide EDPro to you.

Important practical note: EDPro telemetry is designed to be pseudonymous and may not be directly linkable to you by name. This can limit our ability to locate or delete specific telemetry records unless you provide helpful identifiers (e.g., a session ID shown in logs, timestamps, or support references).

You may lodge a complaint with your local authority (e.g., Der Hessische Beauftragte für Datenschutz und Informationsfreiheit).

California & certain US state rights

California residents (CCPA/CPRA) can request to know, access, correct, or delete personal information and to opt out of “sale” or “sharing.” We do not sell personal information and we do not share it for cross-context behavioral advertising. You may designate an authorized agent by written permission. We do not discriminate for exercising rights.

Children

Our services are not directed to children under 13. We do not knowingly collect data from children under 13.

Security

We implement reasonable technical and organizational measures (least-privilege access, encryption in transit where applicable, audit logs). No method is 100% secure, but we aim to keep risks proportionate and reasonable.

Data we don’t want

Please avoid posting sensitive personal data (e.g., precise addresses, health data, financial info) in public channels. Redact such data from logs/screenshots before sharing.

Changes

We may update this policy; the effective date will change. If we materially change what we collect or how we use it (for example, new telemetry categories), we will notify you (e.g., server announcement or in-app notice).

Contact

Privacy: privacy@miraviasoftworks.com • General: contact@miraviasoftworks.com