MyEZToll handles vehicle, driver and payment data for rental and fleet operators. This page describes how that data is protected, where it lives, who else touches it, and what happens when something goes wrong — in enough detail that most security reviews can be completed without a call.
Last updated August 16, 2026
We state where we actually are rather than implying more. Two of the four rows below are inherited from our infrastructure provider and are in force today; the other two are programmes we are running.
Readiness work underway against the Security, Availability and Confidentiality Trust Services Criteria. Observation window targeted for Q2 2027. Gap-assessment findings and the remediation plan are available under NDA today.
ISMS scoping follows SOC 2 certification, reusing the same control set and evidence pipeline. Stage 1 audit targeted for Q4 2027.
All production infrastructure runs on Microsoft Azure, which maintains SOC 1/2/3, ISO/IEC 27001, 27017, 27018, FedRAMP High and PCI DSS attestations. Physical security, hypervisor isolation, hardware lifecycle and datacentre operations are inherited from that programme; the controls described on this page are the ones we own on top of it.
Card data is never transmitted to or stored on our servers. Payment credentials are captured directly by Stripe (PCI DSS Level 1 Service Provider) and we hold only opaque Stripe references, so our environment is out of PCI scope for cardholder data.
SOC 2 Type II is in progress, with the observation window targeted for Q2 2027. Until the report is issued we can share our readiness assessment, control matrix and remediation plan under NDA, and we will accept contractual security commitments in the meantime.
A single multi-tenant application, a managed relational database, and a set of background workers that talk to external toll, telematics and rental systems. There are no customer-managed servers and no on-premise components.
Browser applications for owners and renters, plus native mobile apps. Clients hold no secrets: they authenticate against the API and receive a short-lived signed token.
A .NET API on Azure App Service, behind Azure’s managed TLS termination and platform firewall. Instances are stateless, so scaling out and redeploying carry no data risk.
Azure SQL Database with Transparent Data Encryption, automated backups and point-in-time restore. Azure Blob Storage holds documents and images, encrypted at rest.
Separately deployed services handle telematics ingestion, toll retrieval and scheduled billing. They share the data tier but are isolated from inbound internet traffic.
Per-agency and per-vendor connectors are loaded as isolated modules with their own credentials, so a failure or credential rotation in one integration cannot affect another.
One logical database, strict row-level ownership. Every record is bound to an owning organisation and every query is constrained to the caller’s organisation.
This is the complete list. Each vendor is engaged under a data processing agreement, receives only the data its function requires, and is reviewed before onboarding. Customers on an active agreement are notified before a new subprocessor is added.
| Vendor | Purpose | Data processed | Region | Assurance |
|---|---|---|---|---|
| Microsoft Azure | Application hosting, managed database, object storage, telemetry | All platform data | United States / Canada | SOC 2 Type II, ISO 27001, FedRAMP High |
| Stripe | Card processing, ACH, payouts to owners and partners | Payment credentials, billing contact, transaction amounts | United States | PCI DSS Level 1, SOC 2 Type II |
| Twilio | SMS notifications and inbound message handling | Mobile number, message body | United States | SOC 2 Type II, ISO 27001 |
| Twilio SendGrid | Transactional email delivery and inbound relay | Email address, message body, attachments | United States | SOC 2 Type II |
| Plaid | Bank account verification for ACH billing | Bank account tokens, account holder name | United States | SOC 2 Type II, ISO 27001 |
| Anthropic | Document understanding, classification and text extraction | Document images and extracted text submitted for processing | United States | SOC 2 Type II, ISO 27001; zero data-retention terms for API traffic |
| Google Cloud (Document AI, Vision) | Optical character recognition of driver licences and documents | Document images | United States | SOC 2 Type II, ISO 27001 |
| Managed network egress providers | Reaching toll and violation agency portals from a stable regional address on the customer’s behalf | Agency portal session traffic | United States | Contractual confidentiality; traffic is TLS-encrypted end to end |
Every incident is triaged against a fixed severity scale and follows the same four stages. Notification is a commitment, not a judgement call.
Automated alerting, customer reports and the disclosure address all feed the same intake. An incident is assigned a severity and an accountable owner at intake.
Affected credentials are rotated, affected access paths are closed, and the blast radius is established before remediation begins.
Affected customers receive written notice describing what happened, what data was involved, what we have done, and what — if anything — they need to do. Notification is not delayed pending root-cause analysis.
Root cause is documented, corrective actions are tracked to completion, and a written post-incident summary is made available to affected customers on request.
Send findings to security@myeztoll.com. We acknowledge reports within two business days and will keep you updated until the issue is closed. We will not pursue legal action against researchers who act in good faith, stay within their own account’s data, avoid degrading the service, and give us a reasonable window to remediate before disclosing.