For IT and procurement
Everything your IT/MDM and procurement reviewers ask for, in one place, so a deal doesn’t stall in review over a question nobody could find the answer to.
IT / MDM
One app, one rollout
Every hazard module (UVDose today, NoiseDose alongside it, HeatDose later) ships inside the one worker app your crew already installs. One consent flow, one HealthKit permission set, ever.
No new deployment per module
Licensing a new module is a server-side entitlement flip against your account, not a new app, a new MDM push, or a new device enrolment.
Server-side entitlements
Which modules a worker's app can read from is enforced by the policy engine on our servers, not by a flag inside the client. Nothing to audit on-device beyond the one app you already approved.
AWS Sydney, always
All exposure data is hosted on Amazon Web Services in Sydney (ap-southeast-2). Nothing crosses a border. This is a hosting fact, not a policy promise: it's where the infrastructure runs.
Legal / procurement
Our Privacy and Terms pages cover the full detail. The three questions procurement asks in every SaaS review, answered directly:
Data ownership
Your organisation owns the exposure records your workforce generates. Exposia is the system that stores and computes against them, not the owner.
Retention
Records are retained for as long as your WHS record-keeping obligations require, and no longer than a worker's own deletion rights allow. See the full detail in our Privacy policy.
Exit and export
Your ledger exports with you. If you leave Exposia, you take a complete export of your organisation's exposure records with you, in a usable format, on request.
Unions and worker representatives
The worker-owns-data privacy model is documented in full on the Platform page, with a direct link you can send to a delegate or a workplace consultative committee.