Infrastructure transparency
Sub-processors
Principal service providers that process data to deliver MV Fleet Compliance.
Current sub-processors
This list covers principal infrastructure providers used by MV Fleet Compliance at launch. A customer’s own external links/services may involve additional independent controllers or processors selected by that customer.
| Provider | Purpose | Data |
|---|---|---|
| Supabase | Database, authentication, private storage and platform APIs | Customer account and operational data stored in the platform |
| Freeola | Website/application hosting, PHP services, scheduled jobs and email transport | Application requests, operational notification content and limited technical logs |
| Stripe | Secure subscription checkout, recurring billing, one-off setup payments, payment-method management, invoices and customer billing portal | Customer/billing contact details, subscription and invoice information, payment-method and payment-status data required to process payments. Stripe may also process payment data as an independent controller where its terms/privacy information provide. |
| Google Analytics (Google) | Optional analytics on selected public website, pricing, registration and legal pages after the visitor consents. Not loaded inside the secure customer portal, MV Admin or driver app. | Pseudonymous analytics identifiers, public page/path and referrer information, browser/device characteristics and related visit/session data. Query strings are stripped by our implementation before page locations are sent. |
| Device/browser push services | Delivery of operator push notifications where the operator enables them | Push subscription endpoint/keys and notification content required for delivery |
Changes
We may update this list as the service develops. Material changes that significantly affect customer data processing will be communicated where reasonably practicable. Customers can raise a processor/sub-processor question at .