Security, stated plainly.
Delivery records are business records: proofs, addresses, customers. This page describes how we protect them, in concrete practices rather than badges.
Encryption in transit
All traffic between browsers, the driver app and our servers runs over TLS. There is no unencrypted path into the platform.
Access control
Web users have role-based permissions; drivers see only their own routes. Customer portal accounts are scoped to their own orders.
Cloud hosting
The platform runs on a major cloud provider with managed infrastructure, network isolation and audit logging.
Backups
Operational data is backed up on a regular schedule, and restores are tested as part of routine operations.
Data separation
Each customer’s operational data is logically separated. Your orders, proofs and reports are yours alone.
Responsible disclosure
Found a vulnerability? Report it to support@mlogtech.com and we will respond quickly. We appreciate coordinated disclosure.
Data protection.
MLogTech processes personal data (names, addresses, signatures, locations) on behalf of the operations that use it. We take that role seriously: data is processed for the delivery operation and nothing else, and our commitments are set out in the privacy policy and in data processing terms available to customers.
We operate under UK GDPR obligations: lawful basis for processing, data subject rights, breach notification duties and retention limits. Questions about data protection go to support@mlogtech.com.
On certifications: we describe here what we actually do. As formal certifications are completed, they will be listed on this page with their scope, not as logos without context.
Questions security teams ask, answered directly.
Bring your security questionnaire to the demo. We answer it with the engineers.
- From login to a published route in under a minute
- Import orders from CSV or API
- Per-driver or per-order pricing