This Privacy policy explains how Logivo collects, uses, protects, and retains account, tenant, driver app, integration, billing, and operational transport...
This Privacy policy explains how Logivo collects, uses, protects, and retains account, tenant, driver app, integration, billing, and operational transport data.
Version production-2026-06-15-driver-app
Who we are
Logivo provides transport management software for tenant organisations, their authorised staff, invited drivers, customers, subcontractors, and portal users. Tenant organisations control the transport records they enter into Logivo. Logivo processes those records to provide the service, keep accounts secure, support operations, and meet legal or billing obligations.
Account and tenant data
We collect account details such as names, email addresses, login records, tenant organisation details, role permissions, support details, audit events, billing contacts, subscription state, and acceptance records for legal documents. We use this data for account access, security, tenant administration, billing, support, audit, and service operation.
Transport operation data
Logivo stores customer, subcontractor, fleet, job, planning, container, charge, cost, invoice, report, delivery note, POD, portal, integration, and communication records entered or generated by authorised tenant users. This data is used to run transport workflows, produce documents, support invoicing, provide portals, maintain audit history, and operate tenant-selected integrations.
Driver app data
Logivo Driver may collect driver identity, assigned jobs, job status updates, timestamps, while-in-use location evidence, POD photos or scans, uploaded files, ePOD signatures, notes, offline sync records, vehicle and trailer selections, odometer readings, walkaround check answers, defect notes, and defect photos. This data is linked to the driver, tenant, job, fleet asset, or compliance record so authorised tenant users can manage work, review compliance, and investigate operational issues.
Camera, files, and location
Camera access is used when a driver chooses to capture POD documents, scan delivery paperwork, collect ePOD evidence, or attach photos to vehicle defects. File access is used when a driver chooses to upload an existing POD or evidence file. Location access is used while the app is open to support transport progress updates and compliance evidence. Logivo does not request background location for the driver app.
Integrations and communications
Where a tenant enables integrations, Logivo may process integration credentials, OAuth tokens, accounting data, fleet tracking data, email metadata, webhook records, WhatsApp delivery-note sharing records, API tokens, and sync audit logs. Integration data is used only to provide the selected workflow, troubleshoot the connection, and keep an audit trail. Tenants can configure or disconnect integrations where the product allows it.
AI-assisted features
Optional AI features may process tenant-provided transport documents, job details, POD evidence, planning data, notes, and operational context to suggest draft jobs, planning improvements, document extraction, detention review, or other workflow recommendations. AI outputs are intended for human review unless a tenant explicitly enables an automated workflow. We design AI improvement data to be anonymised or aggregated where used to improve Logivo features.
How we protect data
Logivo uses HTTPS, secure sessions, CSRF protection, hashed passwords, tenant-scoped permissions, audit trails, restricted administrative access, secret redaction, infrastructure monitoring, and backup processes. Sensitive credentials are not exposed to ordinary users. Access to tenant data is limited to authorised users and service providers needed to operate, secure, support, or bill the platform.
Sharing and subprocessors
We do not sell tenant or driver app data and do not use it for advertising. Data may be shared with authorised tenant users, invited portal users according to tenant settings, infrastructure providers, payment providers, email or communication providers, accounting or fleet integration providers, support/security providers, and legal authorities where required. Subprocessor use is governed by the Data Processing Addendum where applicable.
Retention and deletion
Operational records are retained while a tenant account is active and as needed for transport, audit, billing, dispute, tax, legal, backup, and security purposes. Accounts without active subscriptions may be deleted after the period stated in the Billing Terms and Terms of Service. Tenants, drivers, and portal users can request access, correction, or deletion through the tenant administrator or Logivo support, subject to legal and operational retention requirements.
Cookies and device data
Logivo uses essential cookies, session storage, and device/browser metadata for login, security, preferences, CSRF protection, and troubleshooting. The Cookie policy explains cookies and browser storage in more detail.
Contact
Privacy, deletion, data access, and security questions can be sent to Logivo through the published contact and support channels on logivo.ai.