At Next Logistics, we believe the future can be better if we make supply chains better.
At Next Logistics, we believe the future can be better if we make supply chains better.
Effective Date: September 21, 2026
NextLogistics (“we”, “our” or “us”) provides the NextLogistics website, the NextLogistics Driver Companion mobile application (“App”) and related transport management system services (“TMS”).
This Privacy Policy explains what personal information is processed through these services, why it is used, who receives it, how retention periods are determined and how individuals can exercise their privacy rights.
This policy applies to website visitors, people contacting NextLogistics, authorised App and TMS users, drivers and other operational personnel, and delivery recipients or pickup contacts whose information appears in transport records.
The App is intended for professional and authorised operational use. It does not provide public or self-service account registration.
Companies using NextLogistics services are referred to as “TMS Customers”. They may include your employer, contractor or the logistics operator responsible for a shipment.
For operational transport information, the relevant TMS Customer generally acts as the data controller. It determines the purposes and legal bases for processing, authorised access, retention requirements and the handling of privacy requests. NextLogistics generally acts as a data processor, handling that information under the TMS Customer’s instructions and applicable data-processing arrangements.
NextLogistics may act as a separate data controller when operating its website, responding to inquiries, managing customer relationships, protecting its infrastructure, meeting legal obligations or handling legal claims.
Requests about a shipment, driver account or operational record should normally be directed to the relevant TMS Customer. NextLogistics assists where required. If you are unsure whom to contact, email hello@nextlogistics.tech.
The information processed depends on the services, permissions and workflows used.
Website and inquiries: names, email addresses, telephone numbers, company information, messages, IP addresses, browser and device information, and website usage or cookie information where those technologies are enabled.
Accounts and authentication: usernames, account identifiers, authentication information, assigned roles and permissions, company associations, account status, session information and device identifiers needed to operate the service. Accounts are administered by the TMS Customer or its authorised administrators.
Transport operations: routes, shipments, orders, vehicles, packages, pallets, barcodes, delivery instructions, loading and unloading records, delivery and collection outcomes, returns, refusals, inspections, manifests, comments and timestamps.
Recipients and pickup contacts: names, addresses, telephone numbers, delivery instructions and shipment details supplied by the TMS Customer or entered during an authorised workflow.
Cash-on-delivery and settlement: collection amounts and methods, handover and settlement status, contracting-authority and manifest information, and related evidence.
Location: approximate or precise coordinates, reading accuracy and time, device identifiers and the username or user identifier associated with a report. Location may also accompany an operational event when available. See section 7.
Photos, signatures and evidence: delivery, collection, assembly, inspection and transport photographs; manifest images or scanned pages; recipient signatures; barcode scans; and associated comments, outcomes, stamp confirmations, timestamps and location. Images and documents may contain personal information visible within them.
Technical information: App and operating-system information, authentication and notification status, network and synchronisation status, identifiers used to prevent duplicate submissions, and limited error or diagnostic information needed to operate, secure or troubleshoot the service.
Information may come directly from you, the relevant TMS Customer, authorised operational personnel, your device where access is permitted, transport workflows, or service providers involved in delivering the service.
Recipient and pickup-contact information is usually supplied by the TMS Customer rather than collected directly from the individual concerned.
Information is used to:
We do not sell personal information or use operational App information for third-party advertising.
Where NextLogistics acts as controller, the applicable legal basis depends on the activity. It may be:
You may withdraw consent without affecting the lawfulness of processing carried out before withdrawal.
For operational information processed on behalf of a TMS Customer, that customer determines the applicable legal basis. Accepting an in-app disclosure or granting an Android permission does not replace the TMS Customer’s responsibility to establish a lawful basis for its processing.
When tracking starts
Delivery tracking begins after you select the Deliveries workflow, accept the in-app location disclosure and grant the required Android location permissions. Where required, background location permission is requested separately.
What happens during tracking
While tracking is active, the App collects and sends location reports to the TMS infrastructure used by your logistics operator, including in the background when the App is minimised, closed or not actively in use.
Reports include coordinates, location accuracy, the time of the reading, a device identifier and your signed-in username. Location may be approximate or precise depending on permissions and available device readings. Reporting frequency varies with movement and the availability of reliable readings.
Location supports delivery-progress tracking, fleet and dispatch coordination, estimated arrival times, proof of service, delivery and refusal verification, return-to-depot verification and investigation of operational disputes. Available location may also be attached to individual operational events. An event may still be saved when current location is unavailable.
Who receives location
The relevant TMS Customer and its authorised personnel receive location information for these purposes. Limited shipment-related location may also be shown through a valid tracking link where configured, as explained in section 10.
When an on-demand route estimate is requested, origin and destination coordinates may be sent to Google Routes or another configured routing provider to calculate travel time and distance.
When tracking stops and your choices
Tracking stops when you log out. The App is also configured to stop tracking at 21:00 (9:00 PM), using your device’s local time.
You can decline the disclosure or revoke location access in Android settings. Revoking location permission stops access to device location. The Deliveries workflow requires location permission and may be unavailable until the required access is restored.
Location retention is explained in section 15.
The App requests camera access when you initiate a feature that needs it, such as barcode scanning, taking proof photographs or photographing a manifest. It does not request broad permission to read your device’s photo or video library.
Recipient signatures are entered on the device screen to document the delivery, collection, refusal or other outcome shown in the workflow.
Submitted photos, signatures, documents and associated information are sent to the TMS infrastructure and linked to the relevant order, transport or operational action. The TMS Customer controls authorised access to these records.
Include only information needed for the task when photographing goods or documents or entering comments. Retention and deletion are explained in sections 15–17.
You can revoke camera permission in Android settings. This may prevent camera-based scanning and evidence capture.
To support work without a reliable connection, the App may store route and order information, recipient details, vehicles, packages, manifests, pending actions, comments, timestamps, coordinates, signatures, photos and synchronisation information in private App storage.
Pending signature and proof-image files in current App versions are encrypted using keys protected by Android Keystore. Related operational metadata is stored in private App databases or files and separated according to the signed-in user. Android backup is disabled for App data.
Abandoned delivery-proof drafts normally expire after seven days. Once the server confirms successful synchronisation, associated pending evidence files are removed from the device.
Failed or interrupted submissions may remain until synchronised, resolved, explicitly abandoned or removed by clearing App data. Pending work may remain after logout so that the same authorised account can resume it.
Clearing App storage or uninstalling the App removes local App information, including unsynchronised work. It does not delete records already sent to the TMS infrastructure.
TMS Customers and authorised personnel: Operational information is available to the relevant TMS Customer and personnel it authorises, which may include drivers, dispatchers, warehouse staff, planners, customer-service staff, finance staff, managers and administrators.
Shipment-tracking links: A recipient or another person with a valid shipment-tracking link may see limited shipment information. Where configured and relevant, this may include a recent driver location and its reporting time, for example when the shipment is the driver’s next scheduled stop.
Mapping and routing providers: Google Maps, Google Play Services, Google Routes or another configured provider may process location, origin, destination or route information needed for location, map, navigation or route-estimation features.
Service providers: Providers of hosting, storage, infrastructure, communications, notifications, monitoring, security and technical support may process information needed to provide their services, subject to applicable contractual and data-protection requirements.
Legal and protective purposes: Information may be disclosed where necessary to comply with law or a valid official request, investigate fraud or abuse, protect the service or individuals, or establish, exercise or defend legal claims.
Service providers may process information outside the country where you are located.
Where applicable law requires safeguards for an international transfer, including transfers of protected personal data outside the European Economic Area, appropriate transfer mechanisms are used. These may include an adequacy decision, approved Standard Contractual Clauses or another legally recognised mechanism, with additional safeguards where required.
The App may show notifications for background-location status, synchronisation and enabled operational features. You can manage notification permissions in Android settings.
Turning off notifications does not itself revoke location permission or stop tracking. It may prevent you from seeing tracking-status information or operational alerts.
In-app dispatch messaging, messaging photo attachments, push call alerts and voice calls are not enabled in the current release. This policy will be updated as necessary if those features are introduced.
The website may use cookies or similar technologies needed to operate and secure it.
Where analytics or other non-essential technologies are enabled, information about their purposes and available choices is provided as required by law. Technologies requiring consent are not activated until that consent is obtained.
Further information and choices may be available in our Cookie Policy or cookie-management interface.
We use technical and organisational measures designed to protect personal information from unauthorised access, disclosure, alteration, loss or destruction. Depending on the processing, these include encrypted network transport, role-based access, private App storage, encryption of pending signature and proof-image files, user-scoped offline information and security monitoring.
No security measure can guarantee absolute protection. Users should protect their devices and credentials and report suspected unauthorised access to their TMS administrator or NextLogistics.
Information is retained only while needed for its stated purpose or an applicable legal requirement. Retention depends on the type of record and the relevant TMS Customer’s lawful processing requirements.
Continuous location audit logs: These are normally kept for one month from collection and then permanently removed through scheduled retention processes.
On-device evidence: Abandoned delivery-proof drafts normally expire after seven days. Pending evidence files are removed following successful server-confirmed synchronisation. Unresolved submissions follow the handling described in section 9.
Delivery and operational evidence: Photos, signatures, delivery-event locations, comments and related records are retained while needed to complete the delivery or return, settle associated payments and resolve related complaints. Further retention for legal claims is limited to evidence necessary for that purpose, taking account of the applicable claim limitation period and any ongoing proceedings.
Accounting, tax and legally required transport records: Stamped manifests, cash-settlement evidence and other documents forming part of these records are kept for the statutory period applicable to the record and the responsible TMS Customer. The period runs from the starting event specified by the applicable law. Only information needed for the relevant obligation is retained for that purpose.
Website inquiries and support correspondence: These are kept while needed to handle the inquiry or support matter, maintain necessary customer records, resolve related disputes or meet legal obligations.
Security and technical records: These are kept while needed to investigate security incidents, maintain service reliability or meet an applicable legal requirement.
Records relevant to an unresolved dispute, investigation or legal obligation may be retained until that need ends. Once the applicable retention requirements and any necessary retention for unresolved claims end, the information is deleted or irreversibly anonymised.
Where NextLogistics acts as processor, server-side retention and deletion follow the relevant TMS Customer’s lawful instructions and applicable obligations. The customer can provide the retention period or criteria for a particular record.
The App does not offer public or self-service account creation. Accounts are created and managed by the TMS Customer or its authorised administrator.
To request account removal, contact your employer, contractor or TMS administrator. You may also email hello@nextlogistics.tech for help identifying the responsible customer or directing your request.
Account removal does not automatically erase every associated business record. Delivery evidence, financial records and other information may need to be retained for the specific purposes and periods explained in section 15. Retention is limited to information for which a lawful need remains.
Uninstalling the App or clearing its storage does not itself submit an account-deletion request or delete information already stored in the TMS infrastructure.
Depending on applicable law, you may have the right to:
For operational information controlled by a TMS Customer, direct your request to that customer. NextLogistics assists where required. For information NextLogistics controls, or help identifying the responsible customer, contact hello@nextlogistics.tech.
Where available, include the relevant account, shipment, order or transport reference. We may request information needed to verify your identity and locate the records.
Rights may be subject to legal exceptions. If requested information must be retained, the responsible controller will explain the reason and the applicable retention period or criteria. Requests are handled within the time limits required by applicable law.
The App is intended for professional and authorised operational users. It is not intended as a service for children.
Our services may interact with mapping, routing, operating-system, infrastructure or other third-party services and may contain links to external websites.
Where a provider acts independently, its own privacy terms apply to its processing. Providers acting on our behalf remain subject to the applicable arrangements described in this policy.
We may update this policy when our services, processing practices, providers or legal obligations change. The revised policy will be published here with an updated effective date. Additional notice will be provided where required, including through the App where appropriate.
NextLogistics
Website: nextlogistics.tech
Email: hello@nextlogistics.tech
For requests about operational information controlled by a TMS Customer, contact that customer first where possible. We can help identify the appropriate contact.
