Privacy
What stays on the phone, what's shared, what's sealed
Doorside records drives so a practice can bill travel and pay mileage. That means location data, and health information from the practice's diary. Here's where each piece goes, and who can see it.
A plain-English summary of how Doorside is being built. The full privacy policynames every service we use.
Three places trip data lives
1 · On the phone
Stays on the clinician's phone
- Raw location points, in encrypted storage, deleted soon after the day is confirmed
- Trips that don't match a diary visit, and stops
- Anything the clinician marks private
These leave the phone only if the clinician says a trip was work.
2 · Shared
Shared with the practice, as totals
- Trips that match a diary visit: start and end times, km, and how they were recorded
- No map and no trace of the route
- Mileage and the travel billed
- Changes an admin makes, with their reasons
These sync as soon as they're recorded, so the practice can bill an overdue day. If the clinician later marks part of a trip private, the totals are corrected.
3 · Sealed
Sealed as evidence
- The route of each work trip, once the clinician confirms the day
- Encrypted on the phone with the practice's key before it's uploaded
- Opening one (Open work route) needs a reason and a fresh email code
- Every opening is logged, and the clinician is told who opened it and why
Home and other clients' locations at either end are masked.
Who can see what
| Data | Clinician | Practice owner and admin |
|---|---|---|
| Live location, speed, driving | On their phone | Never |
| Raw location points | On their phone | Never |
| Stops, unmatched and private trips | On their phone | Only trips the clinician says were work |
| Trips matched to visits (totals) | Yes | Yes |
| Work route of a confirmed trip | Yes | Only by opening it with a reason. The clinician is told |
| Clinician's home address | Yes | No. It's encrypted and used only to estimate trips |
A billing partner (for example, a bookkeeper) sees only the practices that have given them access. Referring a practice to Doorside gives a partner no access to its data.
What Doorside doesn't do
- It doesn't show anyone a clinician's live location or a full-day trace.
- It doesn't measure speed, driving, attendance or productivity. Times between visits can still show a gap, so clinicians can mark anything private before they confirm the day.
- It doesn't send raw location to its servers, logs or analytics.
- It doesn't write anything to Cliniko. It only reads.
- It doesn't put client names on the phone's lock screen.
The clinician stays in control
- Before anything is recorded, each clinician reads what the practice will see and agrees to it, separately from the phone's location prompt. Saying no means trips are estimated from the diary instead.
- Recording only runs in their work hours, and they can pause it at any time without giving a reason.
- They can see a history of who has opened their work routes, and why.
Practice and client data
The practice connects its Cliniko account once. Doorside reads practitioners, clients, appointments and invoices on a schedule, so it knows who each visit was for and which scheme pays. An OT appointment is health information, and Doorside handles it as such.
Client names, funding and travel terms are readable by the practice. Client street addresses are encrypted; only the zone or area needed for the travel rule is readable. The phone holds only today's and tomorrow's visits, encrypted.
A client-facing travel note never names another client, and never shows a route or anyone's home.
Where it's kept
Data is stored in Australia (Sydney). Addresses and work routes are encrypted with keys held separately, in a key service that keeps its own record of every use. Someone with access to the database alone can't read them.
Address lookups and route estimates go to Mapbox. Every service that handles data for Doorside will be named in the privacy policy.
How long records are kept (for example, the 7 years NDIS providers must keep certain records) is part of a legal review that happens before the beta.
Questions
Ask us anything about how Doorside handles data: privacy@doorside.app.