Security
How mBurse protects your program data.
Encryption, access, hosting, and data handling, explained in plain terms. Everything your IT and security teams need to start a vendor review.
Data protection
Encrypted in transit and at rest.
Driver locations, trips, and reimbursements are sensitive. They're encrypted whether they're moving between systems or stored.
TLS 1.2 or higher
Data moving between the mLog app, the mBurse web platform, and our servers is encrypted with TLS 1.2 or higher.
AES-256
Databases, file storage, and backups are encrypted at rest with AES-256. mBurse manages the encryption keys.
Daily mLog backups
The mLog app backs up each driver's trip and mileage data to Amazon S3 every day, starting with the first recorded trip, so it can be restored to a new or replacement phone.
Access and permissions
People see only what their role needs.
Your administrators add users and assign roles. Each role limits what a person can see and do.
| Role | What they can see |
|---|---|
| Driver | Their own trips, mileage, and reimbursements |
| Manager | Their own team, plus everyone downstream in their reporting line, including the teams of managers who report to them |
| Administrator | Your company's program, users, and roles |
| Driver/Manager and Driver/Admin | Combined roles for people who drive and also approve or administer |
Driver privacy
Business mileage. Driver control.
mLog records the business driving your program needs and keeps personal trips private. mBurse doesn't sell your data.
Business trip records are shared for review.
Personal trips aren't accessible to managers.
Driving isn't visible unless it's business-related. Business driving outside normal hours can be shared for review.
- Route, recorded by GPS
- Addresses
- Dates
- Times
- Mileage
- Notes, if used
- Tags, if used
- Pause tracking when they need to
- Keep trips personal by classifying them as personal or private
- Delete trips in the app until they're approved or rejected
What mLog needs on the phone
Location, including in the background
So mLog can record trips automatically during the business hours a driver sets. The phone may show that mLog uses location while the app is closed.
Notifications
mLog sends in-app push notifications. Emails and text messages are optional.
A choice of tracking modes
Fully automatic, semi-automatic, semi-manual, or manual tracking, so trips are recorded the way your program works.
Infrastructure
Built on AWS. Responsible for our own controls.
AWS secures the data centers. mBurse secures everything we build and run on top of them. Here's how that responsibility is split.
The physical infrastructure
- Data centers, hardware, and networking
- The core cloud services mBurse runs on
- AWS's own certifications and audit reports, including ISO 27001 and SOC 1, 2, and 3
AWS's reports are available from AWS Artifact →. They cover AWS, not mBurse's application.
Everything we build and run
- The mBurse platform and the mLog app
- Configuration, encryption, and key management
- Who can access your data, and how
- Our internal processes and the service providers we use
Data lifecycle
Clear rules for keeping and deleting data.
We keep data while your account is active or as your agreement requires, and delete it when it's no longer needed, unless the law requires us to keep it longer.
Access ends, records stay
Your administrator deactivates the driver, and their access ends. Their trip, mileage, and reimbursement records stay available to your administrators for tax and recordkeeping. The IRS asks employers to keep employment tax records for at least four years.
Business records stay with your company
Drivers can delete a trip in the app until it's approved or rejected. After that, trip, mileage, receipt, and reimbursement records are your company's business records, so drivers can't delete them. Your company decides when they're removed.
Other personal data, such as website and contact details, can be deleted on request at data@mburse.com. Deleted data may stay in backups until those backups expire.
Service providers
The companies that help us run mBurse.
We use a small number of providers to host the platform, map trips, and send notifications.
| Provider | What it does |
|---|---|
| Amazon Web Services | Hosts the mBurse platform, databases, file storage, and mLog backups. mLog backups are stored in one of five locations: Oregon, Virginia, Ireland, Australia, or Singapore. |
| Map geocoding and route comparisons in the mLog app | |
| Messaging providers | In-app push notifications, and optional emails and text messages |
| HubSpot | Website and forms |
| Google Analytics | Website analytics |
Assurance and security reviews
SOC 2 audit scheduled to begin in February 2027.
mBurse’s SOC 2 audit is scheduled to begin in February 2027. We expect to receive the report approximately 2–6 weeks after the audit begins, subject to the auditor’s process and findings. The examination has not yet been completed, and an mBurse SOC 2 report is not currently available. This is a planned assurance milestone, separate from the safeguards described on this page.
Service provider list
Our current list of service providers, with what each one does.
Security questionnaires
Help completing your security questionnaire, in your format.
Security and privacy questions
Know what's shared.
Quick answers for drivers, managers, and the teams reviewing mBurse.
Can managers see personal trips?
No. Personal trips and personal driving outside business hours aren't accessible to managers.
What about a business trip after hours?
Business driving outside normal working hours can be shared with managers for review, so drivers are reimbursed for it.
Who can see a driver's business trips?
The driver, their manager, managers above them in the reporting line, and your company's mBurse administrators. Managers see everyone downstream from them, including the teams of managers who report to them.
Can drivers delete trips?
Yes, until a trip is approved or rejected. After that it's part of your company's business records, which substantiate reimbursements under an accountable plan.
Who owns the trip and reimbursement records?
They're your company's business records. Your company decides when they're removed, and your administrators keep access when a driver leaves.
Does mBurse sell driver or company data?
No. mBurse doesn't sell your data.
Do managers see the route I drove?
For business trips, yes. mLog records the actual route by GPS so mileage and reimbursements are accurate. Personal trips stay private.
Why does mLog need location access all the time?
Background location lets mLog record trips automatically during your business hours, without you opening the app. With manual tracking, you start trips yourself.
Where is customer data hosted?
On Amazon Web Services. Data is encrypted in transit with TLS 1.2 or higher and at rest with AES-256.
How do I report a security concern?
Email security@mburse.com with what you saw, when, and how to reach you. If you think your account was compromised, also tell your company's mBurse administrator.
Report a concern
See something? Tell us right away.
To report a suspected security issue or data breach, email security@mburse.com. Include what you saw, when, and how to reach you. If you think your account was compromised, also tell your company's mBurse administrator.