What we store, and what we deliberately do not
Most courier software asks you to trust it with patient data. We built this one so you never have to hand us any.
The short version
Your client labels a specimen with a reference. That reference is opaque: it means something in their system and nothing at all in ours. We track it through pickup, transport and delivery, and we never receive, request or resolve the person behind it.
If a member of your staff types a patient name into a note field, that is a mistake we try to prevent rather than a feature. The apps warn against it at the point of typing.
What we hold
| We store | We never store |
|---|---|
| Opaque specimen reference | Patient name |
| Pickup and delivery site addresses | Date of birth |
| Custody events (who held it, and when) | Medical record number |
| Signatures from facility staff | Diagnosis or test type |
| Temperature readings | Any other patient identifier |
| Driver identity and route history during shifts | Driver location outside an active route |
Driver location
Reported only while a driver is on an active route, and visible to them the whole time it is happening. There is no configuration that turns it on outside working hours, because we did not build one.
Where your data lives
Every customer gets their own database rather than a row in a shared table. A query cannot reach another operator's data because that data is somewhere else entirely, and not because somebody remembered to write the filter correctly.
What we do not claim
- We are not certified against SOC 2 or HITRUST, and "HIPAA certified" is not something any vendor can truthfully be.
- We do not support controlled substances. If your work includes them, we are not the right fit yet and would rather say so now.
- The no-PHI position is an architectural decision, and we will walk your compliance contact through it in detail rather than asking them to take a web page's word for it.