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: August 19, 2026
NextLogistics (“NextLogistics”, “we”, “our”, or “us”) provides the NextLogistics website and the NextLogistics Driver Companion mobile application (the “App”).
This Privacy Policy explains how personal data is collected, used, stored, shared, and otherwise processed through our website, the App, and the related NextLogistics transport management system infrastructure.
This Privacy Policy applies to:
The App is intended for professional drivers and other authorized operational personnel. It does not support public account registration.
The NextLogistics platform is provided to companies using the NextLogistics transport management system (“TMS Customers”).
For operational transport data processed through the App and TMS, the relevant TMS Customer generally determines:
For this processing, the TMS Customer acts as the data controller, and NextLogistics generally acts as a data processor, processing personal data on the TMS Customer’s instructions.
Drivers, delivery recipients, pickup contacts, and other individuals should normally contact the relevant TMS Customer — for example, the driver’s employer, contractor, or the company responsible for the shipment — regarding processing purposes, legal bases, access to data, correction, deletion, retention, or other privacy rights.
NextLogistics assists TMS Customers with such requests where required and where the relevant data is held within NextLogistics infrastructure.
NextLogistics may separately act as a data controller where we determine our own purposes for processing, including where appropriate for:
The information processed depends on the services and features used by the TMS Customer.
When individuals interact with the NextLogistics website, we may process:
For authorized App and TMS users, we may process:
Accounts are created and administered by the relevant TMS Customer or its authorized administrators.
Depending on the user’s role and assigned workflow, we may process:
Information supplied by the TMS Customer may include:
This information will normally have been provided to NextLogistics by the relevant TMS Customer rather than directly by the recipient.
Where cash-on-delivery functionality is enabled, we may process:
For users assigned to workflows that require location functionality, the App may process precise or approximate device location depending on the permissions granted by the user and the location available from the device.
Location information may include:
Location may also be recorded in connection with specific operational events, including delivery, collection, refusal, return, inspection, or other workflow actions.
An operational event may still be saved when current location is unavailable.
Depending on the workflow configured by the TMS Customer, we may process:
To operate, secure, synchronize, and troubleshoot the App, we may process limited technical information including:
Depending on the circumstances, personal data may be obtained:
Operational information may be processed to:
Website and business information may also be used to:
NextLogistics does not sell personal data.
NextLogistics does not use operational App data for third-party advertising.
Where NextLogistics acts as a data controller, personal data is processed only where an appropriate legal basis applies.
Depending on the circumstances, processing may be based on:
Where processing is based on consent, consent may be withdrawn at any time, without affecting processing that occurred before withdrawal.
For operational information processed on behalf of a TMS Customer, the TMS Customer determines the applicable legal basis. NextLogistics processes that information according to the TMS Customer’s instructions and applicable data-processing arrangements.
Location tracking applies to users using the Delivery Driver workflow or another workflow for which location tracking has been enabled.
Before background tracking begins, the App provides an in-app disclosure explaining the use of location and requires the user to proceed affirmatively before the relevant Android location permissions are requested.
Where required by the Android operating system, background location permission is requested separately.
When the required permission has been granted, the App may collect and transmit location while the App is minimized, closed, or otherwise not actively in use.
Background location is used to support:
While the driver is moving, the App sends location reports to NextLogistics infrastructure no more frequently than once every 30 seconds.
A new location report is normally suppressed when movement is less than 50 metres, unless approximately five minutes have passed since the previous report.
Background tracking stops when the user logs out.
Tracking also ends automatically at 21:00 (9:00 PM) each day.
When an on-demand route estimate is requested, precise origin and destination coordinates may be transmitted to Google Routes or another configured routing provider to calculate estimated travel time and distance.
Continuous location audit logs are normally retained for one month from collection and are then permanently removed through scheduled retention processes.
Location recorded as part of a specific delivery, collection, refusal, return, inspection, or other operational event may form part of the corresponding business record and may therefore be retained for longer according to the TMS Customer’s operational, contractual, legal, security, audit, and dispute-resolution requirements.
Users can revoke location permissions through Android system settings.
If required location permission is revoked, background location tracking stops. Features or workflows that require location, including the Delivery Driver workflow, may become unavailable or restricted.
The App accesses the camera only when a user initiates functionality requiring the camera, such as:
Camera access requires the relevant device permission.
Recipient signatures are captured through the device screen where signature functionality is required as proof of delivery, collection, refusal, or another operational action.
Photos, signatures, comments, manifests, timestamps, location information, and related evidence are transmitted to the NextLogistics TMS infrastructure and become part of the applicable operational record.
The relevant TMS Customer controls access to these records.
These records may be retained according to the TMS Customer’s:
They may be deleted or anonymized when those requirements no longer apply.
Users can revoke camera permission through Android system settings. Doing so may prevent camera-based barcode scanning, proof-photo capture, and other workflows that require the camera.
The App is designed to support field work where internet connectivity may be unreliable or unavailable.
For this purpose, the App may temporarily store information in app-private device storage, including:
Pending signature and proof-image files created by current App versions are encrypted using keys protected by the Android Keystore.
Related operational metadata is stored in private App databases or files and is isolated according to the signed-in user.
Android backup is disabled for App data.
Abandoned delivery-proof drafts normally expire after seven days.
After the server confirms successful synchronization, associated pending evidence files are removed from the device.
Failed, interrupted, disputed, or authentication-blocked work may remain on the device until it is:
Pending work may remain after logout where necessary to allow it to resume only for the same authorized account.
Users can remove locally stored App data using Android system settings or by uninstalling the App.
Removing local App data does not delete operational records that have already been transmitted to and retained within the TMS infrastructure.
Operational data is made available to the relevant TMS Customer and personnel authorized by that TMS Customer.
Depending on the customer’s organization and configuration, authorized users may include:
Information may also be processed or disclosed in the following circumstances.
A shipment recipient or another person possessing a valid shipment-tracking link may receive limited information concerning the shipment.
Where configured and operationally relevant, this may include a recent driver location and the time at which the location was reported, for example when the shipment is the driver’s next scheduled stop.
Google Maps, Google Play Services, Google Routes, or another configured mapping or routing provider may process location, origin, destination, map, or routing information where required to provide device-location, map, navigation, or route-estimation functionality.
We may use service providers for functions such as:
Such providers may process personal data only as necessary to provide their services and subject to applicable contractual, confidentiality, data-protection, and security requirements.
Information may be disclosed where reasonably necessary:
Some technical or service providers used in connection with NextLogistics may process information in countries outside the country in which the individual is located.
Where personal data protected by European data-protection law is transferred outside the European Economic Area or another jurisdiction requiring transfer safeguards, appropriate mechanisms will be used where required by applicable law.
Depending on the destination and provider, these safeguards may include:
Additional technical, contractual, or organizational safeguards may be used where appropriate.
The App may use notifications for:
Users can manage notification permissions through Android system settings.
Disabling notifications may prevent users from seeing the visible notification indicating that background location tracking is active or may prevent receipt of other operational alerts.
In-app dispatch messaging, photo attachments in messaging, push call alerts, and voice-call functionality are not enabled in the current release.
If additional communication features are introduced, this Privacy Policy will be updated as necessary to reflect the associated processing.
The NextLogistics website may use cookies or similar technologies necessary to provide and secure the website.
Where analytics or other non-essential technologies are enabled, information about their use and available choices will be provided as required by applicable law.
Where consent is legally required before using a particular category of cookies or similar technology, those technologies will not be activated until the required consent has been obtained.
Additional information may be provided through a separate Cookie Policy or cookie-management interface.
NextLogistics uses administrative, technical, and organizational measures designed to protect personal data against unauthorized access, disclosure, alteration, loss, or destruction.
Depending on the type of information and processing, these measures include:
No technical or organizational security measure can guarantee absolute security.
Users are responsible for protecting their devices and login credentials and should report suspected unauthorized access to their employer, TMS administrator, or NextLogistics support.
Personal data is retained only for as long as reasonably necessary for the relevant processing purpose, subject to contractual, operational, legal, accounting, security, and dispute-resolution requirements.
Current retention practices include:
Deletion may be delayed or restricted where information must be retained for purposes including:
Where NextLogistics acts as processor, server-side retention and deletion are generally performed according to the instructions and requirements of the relevant TMS Customer.
The NextLogistics Driver Companion App does not provide public or self-service account creation.
User accounts are created, assigned, managed, disabled, and removed by the relevant TMS Customer or its authorized administrator.
Users who wish to have their account disabled or removed should normally contact their employer, contractor, or other relevant TMS Customer.
Users may also contact NextLogistics at [email protected] for assistance identifying or contacting the relevant TMS Customer.
Removing an App account does not necessarily require deletion of all business records associated with that user.
Transport records, delivery evidence, signatures, location associated with completed operational events, financial records, audit records, and other business information may continue to be retained where the relevant TMS Customer has a lawful operational, contractual, accounting, security, dispute-resolution, or legal reason to retain them.
Deleting the App or clearing its local storage deletes locally stored App information but does not itself delete records already transmitted to the TMS infrastructure.
Depending on applicable law and the circumstances of the processing, individuals may have rights concerning their personal data, including the right to:
These rights may be subject to exceptions or limitations provided by applicable law.
Where the relevant TMS Customer acts as controller, requests concerning:
should normally be directed to that TMS Customer.
NextLogistics will assist the TMS Customer with such requests where required.
Where NextLogistics acts as controller, privacy requests can be submitted to [email protected].
We may need to request sufficient information to identify the individual and verify that the person making a request is entitled to do so.
The NextLogistics Driver Companion App is intended for professional and authorized operational users and is not intended for children.
NextLogistics does not knowingly design the App for use by children as a consumer service.
The App or website may interact with third-party services such as mapping, routing, operating-system, hosting, infrastructure, and notification providers.
Those providers may process information under their own privacy terms where they act independently from NextLogistics.
Users may also interact with third-party websites or services through links made available through NextLogistics. NextLogistics is not responsible for independent data-processing practices of third parties that are not acting on our behalf.
We may update this Privacy Policy when:
Where a material revision is made, the revised Privacy Policy will be published with an updated effective date.
Where appropriate, additional notice may also be provided through the App or other relevant communication channels.
For questions about this Privacy Policy, the NextLogistics infrastructure, or assistance with a privacy request, contact:
NextLogistics
Website: https://nextlogistics.tech
Email: [email protected]
Individuals requesting access to or deletion of operational information should normally contact the relevant TMS Customer first, as described above.
© 2026 NextLogistics. All rights reserved.
