Your operation runs on this. Here is how we protect it.
Murphey OS holds your reservations, customers, chauffeurs, invoices and payroll. This page explains, plainly, how those records are kept separate, who can see them, how changes are tracked, and how you can take your data with you.
1 companyPer sign-in
5 roles11 permission areas
You approveSupport access
0 card numbersTyped on our pages
Your company only
| Separate records | Every reservation, customer, invoice and setting belongs to one company. Each request is answered only with the signed-in company's records. |
| Separate control room | The Murphey team's own administration (Master Control) uses its own accounts and its own sign-in, separate from every company's users. |
Sign-in and passwords
| Passwords | At least 12 characters, stored only as a salted scrypt hash. Nobody, including us, can read a password. |
| Two-step sign-in | Anyone can add a 6-digit code from an authenticator app to their sign-in, and the owner can require it for owners and administrators or for everyone. One-time recovery codes cover a lost phone. |
| Lockout | Wrong passwords lock that account for 15 minutes after the number your company sets (five unless you change it). Many failed sign-ins from one network pause sign-in from there. |
| Sessions | Sign-ins end after a period without activity that your company chooses (30 minutes unless you change it). Session cookies can't be read by page scripts, and browsers are told to reach Murphey OS only over secure connections. |
| Changing a password | Changing your password signs you out on every other device. |
| Removing someone | Deactivating a user or changing their access signs them out everywhere at once. |
| Stored credentials | The passwords and keys you connect (email, texting, payment processors, phone system, partners) and uploaded staff and partner documents are encrypted with AES-256-GCM. |
Who sees what
roles and permissions| Roles | Owner, administrator, reservationist, dispatcher and chauffeur. |
| Permission areas | Quotes and reservations, communications, dispatch, customers, fleet, reports, pricing, team and HR, payroll, and user permissions are switched on per person. |
| Owner protection | The owner account can't be removed or downgraded. Only the owner creates administrators or grants full access. |
| Chauffeur privacy | You can hide customer contact details and pay estimates from chauffeurs, and allow them back for individual employees. |
| Developer API keys | Read-only or read-and-add, one company each, shown once, removable at any time. |
Support access
when the Murphey team helps you| You approve it | To look inside your account, the Murphey team must request access with a reason, a level (view, operational or full) and a time limit. Your owner approves or denies it in Administration › Support access. |
| It runs out | Access ends automatically when the time is up, and you can cut it off at any moment. |
| It's recorded | Every request, approval, sign-in and change made by support is written to your audit history. |
| Emergencies | For an urgent outage the team can open emergency access for up to 60 minutes without waiting. You are emailed straight away, it is recorded, and you can end it immediately. |
Audit history
who changed what| Recorded actions | Payments and invoice changes, payroll actions, customer deletions, settings changes, imports, employee documents, support access, API changes and more are recorded with the person and the time. |
| See it yourself | Owners and administrators open Reports › Audit & staff activity to see who changed what in any period. |
| Locked periods | Settled trips and approved payroll are locked so earlier figures can't quietly change. |
| How long it's kept | You choose how many months of audit history to keep (seven years unless you change it). Customers, trips and invoices are never deleted automatically. |
Payments
| Hosted checkout | Customers pay on Square, Stripe or PayPal's own secure checkout pages. Card numbers are never typed into Murphey OS or stored by us. |
| Your processor | You connect your own payment account. Money goes straight to you, with no Murphey markup. |
Backups
| Managed database | Your records live in a managed PostgreSQL database at our cloud provider, reachable only by the Murphey OS application. |
| Point-in-time recovery | The database keeps backups that can restore it to any moment in the past seven days. |
| Careful restores | A restore is made into a separate copy first and checked before anything replaces live data. |
Getting your data out
your records are yours| Everything at once | The owner can download all company records in one ZIP: a spreadsheet for each kind of record. Passwords, keys and sign-in codes are never included, and every download is recorded. |
| Customers | Export your customer list to a spreadsheet, choosing the fields: contact details, addresses, contact permissions, tags and notes. |
| Accounting | QuickBooks Online files for customers, invoices and payments, and a year-end package for your accountant (payments, invoices, expenses, payroll, partner settlements, mileage). |
| Payroll | Payroll provider files, journal entries, timesheets and contractor reports. |
| Live connection | Zapier and the developer API send your trips, customers and invoices to your other systems as they happen. |
When the network drops
| Fallback pages | If a chauffeur's or client's phone loses its connection, the app shows your company's name and a tap-to-call dispatch number saved on the device. |
| Live data needs a connection | Trips and changes are always read live, so nobody acts on an old copy. |
Client privacy
| Your clients' controls | Clients can close their own portal account. Their saved profile and password are erased, while the trip and invoice records your business needs are kept. |
| Deleting a customer | Only the owner can permanently delete a customer, after typing a confirmation and their password. Marking a customer inactive keeps the history instead. |
Questions about security or your data? Contact the Murphey OS team.