Subprocessor List | Apollo EMS

1. Overview

This page lists the third-party service providers that Apollo EMS may use to operate, secure, support, deliver, or improve the Apollo EMS service.

This type of list is commonly called a subprocessor list. It may also be described as a list of third-party processors, service providers, or external recipients.

Apollo EMS is operated by Apollo Health Group Pty Ltd. Most customer tenant data is controlled by the customer organisation using Apollo EMS. Apollo EMS processes that information on the customer's behalf and may use the providers below to deliver the service.

2. How to Read This List

Core means the provider is used to operate the platform or website.
Optional means the provider is used only when a customer enables, configures, or uses the relevant feature.
Website only means the provider is used for the public Apollo EMS website rather than customer tenant workflows.
Processing locations are indicative. Some providers use global infrastructure, support teams, backup locations, content delivery networks, or routing that may involve additional countries.

Customers should also consider third-party systems they choose to connect to Apollo EMS, recipients they send data to, and any external tools they use outside Apollo EMS.

3. Core Platform Subprocessors

Provider	Services used	Purpose	Data that may be processed	Use
Amazon Web Services	EC2, RDS, ElastiCache, S3, SES, SQS, CloudWatch, Secrets Manager, MediaConvert, CloudFront, Amazon Bedrock, related AWS infrastructure	Hosting, database storage, object storage, email delivery, queues, logs, secrets, backups, file delivery, video processing, and AI-assisted case summaries via Amazon Bedrock where enabled	Customer tenant data, account data, clinical records, rostering data, incident data, uploaded files, email content, logs, diagnostics, secrets, backups, video attachments, and case-summary prompt/Amazon Bedrock model response data	Core and optional case-summary workflow
Cloudflare	DNS, proxy/security services, Turnstile challenge verification	DNS, traffic routing, security, bot protection, contact form protection, and certificate validation support	IP addresses, request metadata, browser and device information, challenge tokens, and limited interaction metadata	Core and website
Sentry	Error monitoring, performance monitoring, session replay, diagnostics	Detecting, diagnosing, and resolving application errors and performance issues	User identifiers, email addresses, IP addresses, device and browser details, URLs, errors, stack traces, API or request metadata, console output, and limited session replay context	Core diagnostics
Google	Google Places API, Firebase Cloud Messaging, Google Fonts, Google Analytics, Google Play services	Address autocomplete, Android push notifications, fonts, public website analytics, and mobile app distribution	Address search input, selected place details, approximate location data, push tokens, push notification metadata and content, IP addresses, browser/device data, website analytics events, and app distribution metadata	Core, mobile, and website
Apple	Apple Push Notification service and App Store services	iOS push notifications, Live Activities, and mobile app distribution	Device push tokens, push notification metadata and content, app distribution metadata, and device/platform information	Mobile

4. Communication, Billing, and Customer-Enabled Integrations

Provider	Services used	Purpose	Data that may be processed	Use
Twilio	Programmable Messaging and Verify	SMS notifications, SMS fallback, bulk SMS, and SMS-based verification where used	Phone numbers, SMS message content, verification metadata, delivery status, timestamps, and related account metadata	Optional communications and authentication
Stripe	Checkout, Billing, Customer Portal, invoices, subscriptions, billing API	Subscription management, invoices, payments, billing portal access, and payment status	Billing contacts, organisation details, subscription details, invoice records, payment status, Stripe customer IDs, and payment details entered directly into Stripe	Billing
Xero	Connected account authorisation and Xero Payroll AU services	Payroll, accounting, earnings rate, payroll calendar, employee, client, and timesheet synchronisation	Organisation connection details, Xero tenant identifiers, employee names and email addresses, employee IDs, earnings rates, payroll calendars, timesheet hours, payroll line details, client billing references, and sync logs	Optional integration
Slack	Connected app authorisation, Slack messaging services, interactive messages	Event and shift notifications and Slack actions	Slack workspace identifiers, access tokens, channel IDs, event and shift details, staff names and email addresses and EOI interaction data	Optional integration
Mapbox	Mapbox GL maps, styles, and map tile services	Map rendering for addresses, CAD, event maps, telematics, and other geospatial workflows	IP addresses, browser/device data, map tile requests, map viewport data, coordinates, and location-related operational context shown on maps	Optional map features
OpenAI	OpenAI services	AI-assisted document parsing for drug protocol PDF import where enabled.	Extracted PDF text, prompts, model responses and related processing metadata	Optional drug protocol and drug reference workflow
MXroute	Email hosting services, mailbox management, IMAP/SMTP hosting, webmail access	Hosted email domains, mailboxes, forwarders, external email client setup, and webmail access	Domain names, mailbox addresses, forwarder addresses, mailbox credentials or provisioning metadata, email headers, email content, attachments, delivery metadata, and webmail access metadata	Optional email hosting

5. Website and Public Contact Providers

Provider	Services used	Purpose	Data that may be processed	Use
Google	Google Analytics and Google Fonts	Website analytics and web font delivery	IP address, browser and device metadata, approximate location, page activity, referrer, and font request metadata	Website only
Cloudflare	Turnstile	Contact form abuse prevention	IP address, browser and device metadata, challenge token, and challenge result	Website only
Amazon Web Services	SES and backend infrastructure	Contact form handling and email delivery	Contact form name, email address, organisation, message content, delivery metadata, and diagnostic logs	Website only

6. Supporting Providers With Limited Customer Data

Some providers support security or delivery but do not normally receive customer tenant records.

Provider	Purpose	Data that may be processed	Use
Internet Security Research Group / Let's Encrypt	TLS certificate issuance and renewal	Domain names, certificate validation metadata, and technical connection metadata	Infrastructure
App store operators	Distribution of mobile applications	App download metadata, platform account metadata, device metadata, and crash or store analytics controlled by the app store operator	Mobile distribution

7. Customer-Directed External Recipients

Apollo EMS customers and authorised users can choose to send or export information to external recipients. These recipients are not always Apollo EMS subprocessors because they may be selected, configured, or controlled by the customer.

Examples include:

email recipients;
SMS recipients;
connected Xero organisations;
connected Slack workspaces;
organisations receiving reports, PDFs, bookings, timesheets, or incident records;
customer-selected mailbox users and email forwarder destinations;
any external systems a customer uses after exporting data from Apollo EMS.

Customers are responsible for ensuring they have the required authority, notice, consent, and legal basis for those disclosures.

8. Self-Hosted Components and Open-Source Software

Apollo EMS also uses self-hosted infrastructure and open-source software that does not, by itself, disclose customer data to the software maintainers.

These are not listed as external subprocessors unless they are operated as a separate hosted service by a third party that receives personal information.

9. Changes to This List

Apollo EMS may update this list when providers are added, removed, replaced, or materially changed.

For privacy questions about subprocessors or third-party processing, contact [email protected].