Security
Health data, kept where it belongs.
Each company's rows are kept apart by the database itself. Every change has a name on it. Sign-in takes two steps where you say so, and you can take all of your data out any time.
trips, as storedone database, a company on every row
| company | rider | pickup | |
|---|---|---|---|
| Inland Care Transit | Gloria Ibarra | 07:12 | R-4 |
| Another provider | A. Reyes | 07:30 | N-1 |
| Inland Care Transit | Dolores Vega | 09:16 | R-2 |
| Another provider | B. Chen | 09:45 | N-3 |
| Another provider | C. Patel | 10:10 | N-1 |
| Inland Care Transit | Kenji Sato | 10:25 | R-9 |
Policy: company = session.company
what a dispatcher at Inland Care Transit gets3 of 6 rows returned
| company | rider | pickup | |
|---|---|---|---|
| Inland Care Transit | Gloria Ibarra | 07:12 | R-4 |
| Inland Care Transit | Dolores Vega | 09:16 | R-2 |
| Inland Care Transit | Kenji Sato | 10:25 | R-9 |
Sample data: Inland Care Transit, its people, riders and settings are made up. Network addresses are documentation addresses.
Audit log
Every change has a name on it.
Who changed what and when, in a sentence, with the record linked. Imports, API calls, the driver app and the nightly jobs are in the same log.
- A forced assignment keeps the rule it broke and the reason.
- Filter by date, person and source; download it as CSV.
Who, what, and why.
app.milecall.com/settings/audit
Audit logLast 7 days · Everyone · All sources
Imports, API calls, the driver app and the nightly jobs are in it too.Download CSV
Roles and sign-in
Checked on the server, for every request.
Owner, Dispatcher, Biller, Driver and Read-only, with custom roles in between. Two-step sign-in with backup codes, required for the roles you choose.
- Several roles add up; only owners manage users.
- Backup codes work once each; wrong passwords lock the account for a while.
app.milecall.com/settings/users
What each role can doThe four built-in roles are fixed. Add a role for anyone in between.
| Area | ||||
|---|---|---|---|---|
| Dispatch board | Edit | Edit | No access | View |
| Trips and riders | Edit | Edit | View | View |
| Fleet | Edit | View | View | View |
| Billing and payers | Edit | View | Edit | View |
| Reports | View | View | View | View |
| Revenue and margins | View | No access | View | No access |
| Settings | Edit | View | View | View |
Drivers: the driver app only. Every request is checked on the server against the signed-in person’s roles, not just hidden in the menu.
Two-step sign-in
Company policy: required for owners. Optional, or required for all office users, are the other settings.
6-digit code from your authenticator app
The code changes every 30 seconds.
Verify and sign inNo phone with you? Use a backup code
Sessions
See who is signed in. End it from your desk.
Every live sign-in, office and driver, with its device and network. Sign one out, or everyone but you.
- An office network list is checked against your own before it saves, so a typo can’t lock you out.
- Sign-in history: who, when, from where, and whether it worked.
Signed out in one click.
Signed in now3 devicesSettings › Security
- Dana Price · OwnerMac, Chrome · nowThis device
- Maria Lopez · DispatcherWindows, Edge · 2 min agoSign out
- Rosa Martinez · DriveriPhone, MileCall Driver · 1 min agoSign out
Keeping and removing
Kept as long as you decide, encrypted while it’s here.
app.milecall.com/settings/data
Data retentionAnything older is removed every night at 02:00 company time.Purge now
| Kind of record | Keep for | Older now |
|---|---|---|
| Trips, proof of service, charges and claimsInvoices and invoiced trips are never removed. | 10 years | 0 |
| GPS breadcrumbsProof-of-service points on performed legs stay on the leg. | 3 years | 1,204 |
| Rider texts and driver messages | 2 years | 318 |
| Audit log | 10 years | 0 |
| Webhook delivery log | 90 days | 2,960 |
| Expired sessions and device receipts | 30 days | 41 |
Every purge, nightly or by hand, is written to the audit log with what it removed.
- Encrypted at rest
- Signatures, photos and uploaded documents are encrypted before they are saved. The database and its backups are encrypted where they are stored, and everything between your browser, the driver app and the server travels over TLS.
- Backed up nightly
- A database snapshot every night, and a restore we have run, not just written down.
- Yours to take
- Every table as CSV and JSON, signatures and photos included, from Settings, any time.
The rider's page
The ride page shows little, for a short time.
Where's My Ride needs no login. It shows the rider's first name, the ETA on the pickup window, the driver's first name and the van. Nothing else about the rider is on it.
- The link stops showing the ride 1 to 72 hours after the drop-off; 4 by default.
- Each ride has its own link. Your name is on the page; MileCall is the credit at the foot.
Inland Care Transit
Your ride today
Rosa is 6 min away
Arriving about 11:22 AMOn time
Your pickup window
11:1011:40
ETA 11:22
R
Call Inland Care TransitRosa · Van 12
White van, wheelchair lift
Updated 11:16 AM
Inland Care Transit
Your ride today
Rosa is 6 min away
Arriving about 11:22 AMOn time
Your pickup window
11:1011:40
ETA 11:22
R
Call Inland Care TransitRosa · Van 12
White van, wheelchair lift
Updated 11:16 AM
Questions from your compliance team?
Health plans, brokers and counties often send a security questionnaire. We fill it in with the facts on this page and can walk your compliance lead through each control on a call. Write to info@milecall.com.
Bring your security questionnaire to the demo.
We’ll show the audit log, the roles and the export on a live workspace, and answer the questions your payers and brokers ask, in writing if you need it.