FleetFlow
Privacy & Data Protection

FleetFlow Privacy Policy

This policy explains what personal data the FleetFlow driver app collects, why, and how it is protected — for drivers and operations staff of New Line for Logistics.

Location only on trip events
No ads or analytics
Encrypted connections
Internal workforce app
Android & iOS
|
sa.newline.fleetflow.driver
|
New Line for Logistics

1. Who we are and who this policy is for

FleetFlow is an internal workforce application operated by New Line for Logistics. It is not a consumer app. It is used solely by our own drivers and our own operations staff, using accounts we issue. There is no public sign-up, and the app cannot be used by anyone outside the organisation.

New Line for Logistics is the data controller for all personal data described in this policy. We decide what is collected, why, and how long it is kept.

This policy covers two kinds of account, both served by the same application:

Account Signs in with
Driver IQAMA (national/residency ID) number and password
Staff Work email address and password

Because this is a workplace system, some of the processing described here is a condition of your employment or service contract rather than something you opt into. Where that is the case we say so.

2. Summary

We collect what is needed to dispatch, execute and prove delivery of freight trips.

The app contains no analytics, advertising, attribution, crash-reporting or tracking software — none at all.

We do not track your location continuously. Location is read only at specific moments: when you tap to record a trip status, and — if you switch on location sharing — when dispatch requests your position during an active trip. That request can arrive while the app is in the background or closed. There is no timer and no continuous location watching, and you can switch location sharing off at any time.

We do not sell or share personal data with third parties for their own purposes, and we do not use it for advertising or profiling.

3. Information we collect

3.1 Account and identity

Collected when you sign in, and returned by our platform to display your profile:

Data Driver Staff
IQAMA (national/residency ID) number✅ used to sign in
Work email address✅ used to sign in
Password
Full name
Mobile phone number
Nationality, joining date, employee code
Bank name and IBAN
Assigned vehicle (plate number, serial number)
Role and permissions

Your password is never stored on the device in any form. It is sent once over an encrypted connection to sign you in and is then discarded. The app has no "remember password" feature and disables autofill saving on the ID field.

Your bank name and IBAN are shown to you inside the app so you can check your settlement figures. They come from our payroll records — the app never asks you to enter them and cannot change them.

3.2 Location

We collect a single precise location reading each time you record a trip status (for example "Trip Started", "Loading Completed", "Delivered"). Nothing is recorded between those moments.

For each status update the app sends:

  • Precise coordinates (latitude and longitude) of your device at that moment;
  • a street address and city, derived from those coordinates by your phone's own operating system (this look-up happens on your device, not on our servers);
  • the status you selected and the time.
Only when something happens. The reading is taken while the app is open and you are submitting a status, or — if you enabled location sharing — when dispatch requests your position during an active trip, which may reach the app in the background.
Event-driven, not continuous. There is no timer and no location watching. A typical trip produces a handful of readings — one per milestone.
Required for a status update. A status update cannot be submitted without a location reading, as it proves the milestone happened where it was supposed to.
Readings that are too imprecise (worse than about 1 km) are rejected rather than sent.

These locations are visible to our operations team, and the most recent one is shown against your assigned vehicle on the operations dashboard. We do not use this to monitor you outside working activity.

3.3 Photographs, documents and signatures

The app uploads the following to the trip record:

  • Photographs you capture with the camera — including a photograph of yourself (a selfie) where driver verification is required at a trip milestone, plus photographs of cargo loading and offloading, vehicle temperature displays, and the vehicle load area.
  • Scanned receipts, captured with the device's document scanner and combined into a PDF.
  • Handwritten signatures captured on screen from the sender or recipient of the shipment at pickup and delivery.

Please note: signatures and contact details you capture belong to other people — the shipper's or consignee's representative. Collect them only where the delivery process requires it, and tell the person what the signature is for.

About location data embedded in photographs. The app resizes most photographs before upload, which removes embedded EXIF/GPS data. However, on Android this removal is not guaranteed for every photograph. You should assume an uploaded photograph may carry the coordinates of where it was taken.

3.4 Trip and customer information

To do your job the app displays information about each trip, which includes the name, phone number, company and address of the shipper and consignee contacts. Staff users can also create and edit these customer location records. This is information about third parties, held by us as part of our commercial records. It is shown to you solely for the purpose of completing the delivery. Do not use it for any other purpose and do not disclose it outside the company.

3.5 Push notifications

If you allow notifications, the app registers a push notification token — an anonymous device-specific identifier issued by the Expo push service — and stores it against your account so that trip assignments and updates can be delivered to your device. This token identifies your device installation, not you personally, but because it is stored against your account it is treated as personal data. It is the only thing sent during registration — no device model, operating system version, advertising identifier, or app version is transmitted with it.

3.6 Technical information

As with any internet-connected application, our servers and our service providers receive your IP address and basic connection information when the app communicates with them. This is inherent to how the internet works and is used for delivering the service and for security.

4. What we do not collect

To be explicit, the application contains no:

Analytics or usage-measurement software
Crash or performance reporting software
Advertising software, ad identifiers, or advertising tracking
Attribution, marketing or audience-measurement software
Access to contacts, calendar, microphone, call logs, SMS, health data, or installed-app list
Access to your photo library
Continuous or always-on location tracking
Device fingerprinting or cross-app tracking of any kind

We do not sell or rent personal data, we do not share it with data brokers, and we do not use it to build advertising or behavioural profiles.

5. Why we use your information

Purpose Data used
Signing you in and keeping you signed in securelyID/email, password, session token
Showing you your assigned trips and vehicleName, employee code, vehicle, trip data
Recording and proving trip milestonesLocation, status, timestamp
Providing proof of pickup and delivery to our customersPhotographs, scanned receipts, signatures
Showing your settlement and payment figuresBank name, IBAN, settlement amounts
Sending you trip assignments and updatesPush notification token
Showing the app in your languageLanguage preference
Keeping the service secure and diagnosing faultsIP address, error information

The lawful basis is the performance of your employment or service contract with us, our legitimate interest in verifying that freight movements occurred as recorded and in evidencing delivery to our customers, and compliance with our legal and contractual obligations.

6. How information is stored on your device

Stored where What Protection
Secure hardware-backed storage (iOS Keychain / Android Keystore) Your session token Encrypted by the operating system
Application storage A cached copy of your profile (including name, ID number, phone, bank name and IBAN), settlement figures, and reference data, kept for up to 7 days so the app works offline Protected by the operating system's app sandbox; not separately encrypted by the app
Application storage Your language and theme preference Not personal data
Temporary cache Photographs, scanned receipts, signatures awaiting upload, and trip documents you have downloaded Protected by the app sandbox; managed by the operating system

Signing out deletes your session token and clears the cached profile and trip data. Note that documents you have downloaded (trip PDFs and previously uploaded attachments) remain in the app's temporary cache after sign-out until the operating system reclaims that space or the app is uninstalled. Uninstalling the app removes all of it.

Your device's own screen lock is the primary protection for data held on the device. Use one.

7. Who we share information with

Your information is sent to our own FleetFlow platform at fleetflow.newline.com.sa. All communication uses encrypted HTTPS connections.

We use the following service providers, and no others. Each processes data only on our instructions:

Provider What they process Why
Google Firebase Cloud Messaging (Android) and Apple Push Notification service (iOS) Push notification delivery To deliver notifications to your device. Only Firebase's messaging service is used — no Firebase Analytics, Crashlytics or advertising products are present in the app.
Expo Push notification token issuance and delivery relay To route notifications to the correct device
Netlify Hosting of application updates The app checks for improved versions on launch. This request carries no user identifier, but Netlify's servers will see your IP address and device type.

Beyond these, we disclose personal data only to our customers, where proof of delivery forms part of the service we contracted to provide, and to law enforcement, regulators or courts where legally required.

8. International transfers

FleetFlow platform data is held on our infrastructure. The push notification and update-hosting providers listed in §7 operate global networks, so limited technical data (such as your IP address and a notification token) may be processed outside the Kingdom of Saudi Arabia. Where that happens we rely on the providers' contractual safeguards.

9. How long we keep information

  • Trip records, including locations, photographs, receipts and signatures — retained for as long as our operational, contractual, tax and statutory obligations require. These form part of our commercial delivery records.
  • Your account and profile — for the duration of your employment or service contract, and afterwards only for as long as employment and financial record-keeping obligations require.
  • Session token on your device — until you sign out or your session expires.
  • Cached profile and trip data on your device — a maximum of 7 days, and cleared when you sign out.
  • Downloaded documents in the device cache — until the operating system reclaims the space or you uninstall the app.

10. Your rights

Under the Saudi Personal Data Protection Law (PDPL) — and equivalent laws where they apply to you — you have the right to be informed about how your data is used, to access it, to request correction of inaccurate data, to request destruction of it, and to complain to the competent supervisory authority.

Accounts are created and removed by us, not by you — there is no self-registration and no in-app account deletion. To exercise any of these rights, contact us using §12 or speak to your line manager or HR.

Some data cannot be deleted on request while it forms part of a completed commercial delivery record or an employment record we are obliged to retain — for example proof-of-delivery signatures, trip milestones, and payroll data.

11. Children

FleetFlow is a workplace application intended solely for adults in professional employment. It is not directed at children and we do not knowingly collect data from anyone under 18.

12. Contact us

New Line for Logistics
Data protection contact: fazal@new-line.sa
Registered address: Riyadh - Saudi Arabia

To request access to, correction of, or destruction of your personal data, write to the address above. We will respond within the timeframe required by applicable law.

13. Changes to this policy

We will update this page when the application's data practices change, and revise the "Last updated" date above. Material changes will be communicated to staff and drivers directly.

© 2026 New Line for Logistics. FleetFlow is an internal platform. All rights reserved.