Privacy Policy
This policy explains how FreightTasks handles personal data: driver and account information, job and operational records, documents and proof-of-delivery files, and location information used while a driver is actively working a job. It is written for UK data protection law (UK GDPR and the Data Protection Act 2018, as updated by the Data (Use and Access) Act 2025) and describes what FreightTasks actually does, not a generic template.
Last updated: 28 September 2026.
Who we are
FreightTasks is operated by FreightTasks Ltd. FreightTasks is a transport management product used by UK haulage companies to plan jobs, manage drivers and vehicles, and capture proof of delivery. For any privacy question, or to exercise any of the rights described below, contact support@freighttasks.com.
Most FreightTasks accounts are business accounts: the company that subscribes to FreightTasks (the “operator”) controls which of its staff and drivers have access. See “Our role: controller and processor” immediately below for who is actually responsible for your data, and “Your rights” and “Complaints” for who to contact.
Our role: controller and processor
UK data protection law distinguishes between a controller (the organisation that decides why and how personal data is processed) and a processor (an organisation that processes data on a controller's instructions). FreightTasks holds both roles, depending on the data:
- Operational data — controlled by the operator. For job, driver, staff, location and document/POD data belonging to a haulage operator's workforce and operation, the operator (the company that subscribes to FreightTasks) is normally the data controller. FreightTasks acts as their processor, processing that data on the operator's instructions to provide the service. As controller, the operator is responsible for identifying its own lawful basis, giving its staff and drivers the required transparency information, and handling their data protection rights requests — matters this notice cannot decide on the operator's behalf. If you are a driver or member of staff, your employer or the operator you work through is usually your first point of contact.
- FreightTasks' own purposes — controlled by FreightTasks Ltd. FreightTasks Ltd is the controller for data it processes for its own purposes: administering an operator's FreightTasks subscription (billing and support contacts), keeping the platform secure and preventing misuse across all customers, and handling enquiries sent directly to us (for example, a demo or support enquiry). This notice speaks in our own voice for that data.
We have not formally documented a data-processing agreement position for every operator in this public notice — where a specific FreightTasks–operator agreement exists, its terms take precedence over the general description here. This notice otherwise uses conservative, general wording rather than asserting a controller/processor position we have not confirmed for a specific relationship.
What data we collect
FreightTasks collects only the data needed to operate transport workflows:
- Account and profile data: name, email, role (planner, admin or driver), company association, active/inactive status, and authentication status needed to identify who is using the system.
- Job and operational data: job references, collection and delivery addresses, scheduled timings, assigned driver and vehicle identifiers, status updates, and notes entered by planners or drivers.
- Documents and PODs: uploads such as delivery notes, proof-of-delivery images or files, signatures, and metadata that links documents back to jobs and users.
- Location data: device position information recorded while a driver is signed in and actively working a job. Full detail, including how background tracking works on Android and iOS and when it stops, is set out under “Driver and location data” below.
- Audit and history data: a record of significant changes to jobs (such as edits, status and reassignment) and of driver device changes, kept so operational records stay accurate and reviewable.
- Customer, import and integration data: where a job originates from a spreadsheet import, email/PDF import, or a connected third-party transport platform, we hold the job and reference data provided through that route, together with the connection status of the integration itself.
Source of your data
Most job, driver and vehicle data is entered directly into FreightTasks by your company's planners and administrators as part of running their operation, or is provided by drivers themselves through the Driver app (for example, location while working a job, and proof-of-delivery documents). Where a job is imported from a spreadsheet, email/PDF, or a connected third-party transport platform, the data originates from that source rather than from the individual it describes.
How we use data
As the operator's processor, we use operational data (jobs, driver, location, document and audit data) only to run the FreightTasks workspace on the operator's behalf and on their instructions: assigning work, tracking job progress, storing documents, and keeping an accurate operational and audit record.
As controller for our own purposes, FreightTasks Ltd also uses data (which may include operational data, where necessary) to keep accounts and the platform secure, to detect and prevent misuse across all customers, and to provide support and respond to enquiries. We do not use your data for advertising, and we do not sell it.
Lawful bases for processing
Because FreightTasks acts as a processor for the operational data described in this notice (see “Our role” above), the operator, as controller, normally determines the purposes and lawful basis for processing its workforce and operational data under UK GDPR — not FreightTasks Ltd. FreightTasks processes that data on the operator's instructions. The operator is responsible for identifying, documenting and communicating its own lawful basis to its staff and drivers; this notice does not speculate about what that basis is, and does not conduct any assessment (such as a Legitimate Interests Assessment) on the operator's behalf. If you are a driver or member of staff, please consult the privacy information your employer or the operator provides you for that basis, not this notice.
For the data FreightTasks Ltd itself controls (see “Our role” above), we rely on:
- Legitimate interests: for proportionate business-to-business account administration — including billing and support contacts for an operator's subscription — to keep the platform secure across all customers, detect and prevent misuse, and respond to enquiries sent directly to us, such as a demo or support request. Where we rely on this basis, we weigh it against the impact on individuals and reduce that impact through measures such as role-based access, private document storage, and the retention limits described below.
- Performance of a contract: only where an individual is themself a party to the contract with FreightTasks Ltd, or has personally asked us to take steps before entering into one — for example, an individual who asks for a demo or trial in their own capacity. An operator being under contract with FreightTasks Ltd does not, by itself, put that operator's staff, admins or other contacts on this basis for their own personal data; where we hold billing or support contact details for someone because of their employer's contract, that is covered by legitimate interests above, not this basis.
We do not rely on consent as the lawful basis for the data described in this notice, and FreightTasks Ltd does not rely on legal obligation either: any such obligation (for example, transport or employment record-keeping law) generally falls on the operator as controller of that data, not on FreightTasks Ltd.
Driver and location data
Device position information is recorded while the driver is signed in and the driver account is active, used to show progress and record journey evidence. In web browsers, tracking is foreground-only and stops when the page is hidden. On the native Android and iOS Driver apps, while the driver has an active operational job, tracking can continue when the app is in the background or the screen is off. Android uses a location foreground service and iOS uses Core Location background updates; in both cases background-capable tracking is started while the app is visible and is limited to active operational work. With no active operational job there is no native background continuation. Signing out, account deactivation, or the end or reassignment of the job stops it. When a driver has an active operational job, samples may be associated with that job; otherwise they have no job association.
As explained under “Our role” and “Lawful bases” above, the operator you work for is normally the controller for this location data, and determines and communicates its own lawful basis for it — FreightTasks provides the platform and technical safeguards (the 90-day automatic deletion described under Retention, foreground-only browser tracking, and role-based access) that support that processing, but does not itself decide why your location is tracked or state that basis here. If you have questions about why your location is tracked, consult the privacy information your employer or the operator provides you.
Data sharing and sub-processors
Operational data is visible to authorised users within the same company workspace, scoped by role: for example, a driver only sees their own assigned jobs. To deliver FreightTasks, we share data with a small number of categories of infrastructure providers who process it for us — acting as our sub-processors where the underlying data is operational data controlled by an operator — under contractual instructions that limit their use of it to that purpose:
- Cloud hosting, database and file storage providers, who store operational data and documents.
- Error-monitoring providers, used to help us find and fix technical problems (see “Cookies and diagnostics” below for how this is limited).
- Connected transport-platform providers, only where your company has enabled a specific integration, and only for the job data that integration is set up to exchange.
We do not name individual providers here because the set of infrastructure we use may change; the categories above and the controls in “How we protect your data” describe how that processing is limited. This notice does not confirm a specific data-processing agreement or sub-processor list for any individual operator — where such an agreement exists, it takes precedence over this general description.
International transfers
Some of our infrastructure providers may process data outside the United Kingdom. Where that happens, UK data protection law requires the transfer to be protected by an appropriate safeguard, such as an applicable adequacy decision or standard contractual clauses. We have not independently audited the specific contractual safeguards each provider has in place as part of writing this notice, and confirming and documenting those arrangements is an ongoing part of our supplier due diligence, not something we assert is already complete here. We do not claim that all data is stored exclusively within the UK.
Retention
Raw driver GPS points are retained for 90 days and are then automatically removed. Other retention periods have not been fixed in this policy: data is kept for as long as the account or job record is needed for operational, support or legal reasons, and may be retained for longer where a business or regulatory obligation requires it. We aim to keep no more than is needed for those purposes. Specific retention schedules for other data categories may be published separately once finalised. For operational data, how long records are kept beyond FreightTasks' own automated processes (like the 90-day GPS window) is primarily a decision for the operator, as controller, and for our processing agreement with them; FreightTasks Ltd does not unilaterally set retention for operator-controlled data beyond what is instructed or automated as described here.
How we protect your data
FreightTasks is built as a multi-tenant system with controls enforced at the database level, not only in the application interface:
- Company-level data isolation: every operational record belongs to one company, and access is enforced by PostgreSQL row-level security policies on the database itself, not only by checks in the application — so one customer's data cannot be read through another customer's session.
- Role-based access: planners, admins and drivers have different, server-enforced permissions. A driver account can only read and update the jobs and locations assigned to it; only planners and admins can create, assign or edit jobs.
- Private document storage: proof-of-delivery images and job documents are stored in a private storage bucket with no public URL. Every access uses an individually signed link that expires automatically.
- An audit trail that ordinary accounts cannot alter: significant job changes are written to a separate audit record. No user account, including administrators, has permission to edit or delete it directly.
- Trusted-device protection for drivers: a driver account can have only one active signed-in device at a time, verified on our servers on every session; moving to a new device requires explicit re-verification.
- Server-side validation: job status changes and assignment rules are checked and recorded on the server, not only on a phone or in a browser, so a client on its own cannot force an invalid state.
- Protected integration credentials: where FreightTasks connects to a third-party transport platform, the credentials for that connection are held in an encrypted secrets store that ordinary application access cannot read, not in a plain database column.
- Automated checks on every change: changes are checked through automated CI including tests, database validation, dependency auditing and secret scanning.
- Encrypted connections: data sent between your browser or the Driver app and FreightTasks travels over an encrypted HTTPS connection.
No system is completely secure, and we cannot guarantee against every possible attack. What we can commit to is that these controls are real, specific and independently testable, not just a policy statement, and we continue to invest in them as the product grows. If you believe you have found a security issue, please tell us at support@freighttasks.com.
Your rights
Under UK data protection law, you have the right to:
- request access to the personal data we hold about you;
- request correction of inaccurate data;
- request erasure of your data, where applicable;
- request that we restrict processing in certain circumstances;
- object to processing we carry out on the basis of legitimate interests; and
- request a copy of your data in a portable format, where applicable.
These rights are not absolute and may not apply in every case — for example, we may need to retain certain records for the legal or operational reasons described under Retention above. Who handles your request depends on our role, described under “Our role: controller and processor” above: for operational data (job, driver, location and document records), the operator you work for is normally the controller and the right party to contact first, since they are best placed to action the request; FreightTasks will assist them as processor. For data FreightTasks Ltd controls itself (see “Our role”), contact support@freighttasks.com directly. If you are unsure who to contact, email support@freighttasks.com and we will point you in the right direction.
Automated decision-making
FreightTasks does not currently use your personal data to make decisions about you solely by automated means that would have a legal or similarly significant effect on you, without human involvement. If this changes, we will update this notice and, where the law requires it, explain the logic involved and your right to request human review.
Cookies and diagnostics
The FreightTasks public website does not use cookies, analytics or advertising trackers of any kind.
Inside the FreightTasks application, we use browser storage (and, for the Driver app's offline queue, on-device storage) for a small number of specific purposes. We classify each deliberately against the exceptions to the UK's electronic communications rules (PECR), rather than treating all storage as automatically exempt:
- Strictly necessary, to deliver the service you have asked for: signing you in and managing your session (including password-recovery, invite and registration flow state); reliably handling a job you are actively creating across browser tabs; remembering that you have already been shown a required location-permission explanation so we do not repeatedly interrupt an active job; and, in the Driver app, queuing job updates while temporarily offline and managing a push-notification subscription once you have opted into notifications. None of this could be removed without breaking the specific feature you are using, so it does not require consent.
- Security: the trusted-device check that limits a driver account to one signed-in device at a time, and technical-fault detection through error monitoring where enabled (see below). PECR recognises storage for detecting and preventing security threats and technical faults as a purpose that does not require consent.
- Preferences (theme and saved table/column view settings): we store your theme (light/dark/system) and saved table/column view choices on your device so the interface reflects them the next time you use FreightTasks. PECR has a narrower exemption for exactly this kind of low-impact appearance/functionality choice, introduced alongside the Data (Use and Access) Act 2025, but it requires both clear information about the storage (which this notice provides) and a simple, free means of objecting to the storage itself — not merely changing the stored value. Today, switching between theme or view options changes what is stored, but FreightTasks does not yet offer a way to opt out of the storage happening at all. We are not relying on this exemption as fully satisfied, and we treat adding a genuine objection mechanism for this preference storage as a compliance gap to close before wider production/public launch, not as already resolved.
None of this is used for advertising, to build a profile of you, or to track you across other websites. Where error monitoring is enabled within the application, it is configured to exclude personal details, cookies, page content and request data before any report is sent, and is used only to help us find and fix technical problems.
The strictly-necessary and security storage described above does not require consent. We have not concluded the same for the preference storage described above, for the reason given there, and we are not adding a cookie banner as part of this notice while that gap remains open — this is a narrow, specific position about low-impact interface preferences, not a general claim that a banner is never needed. We will revisit this once the objection mechanism described above is in place.
Changes to this notice
This policy describes the current product. As features evolve, the wording may be updated, and the “Last updated” date above will change accordingly. Where legal wording is not yet final for a feature, we use conservative language rather than making unverified promises.
Complaints
If you are unhappy with how your personal data has been handled: for operational data (job, driver, location and document records), please raise this with the operator you work for first, since they are normally the controller responsible for that data and FreightTasks assists them as processor; for anything FreightTasks Ltd handles directly as controller (see “Our role: controller and processor” above), contact us first at support@freighttasks.com so we can try to resolve it. In either case, you also have the right to complain to the UK's data protection regulator, the Information Commissioner's Office (ICO), at ico.org.uk/make-a-complaint or by calling 0303 123 1113.
Account deletion
Drivers can request account deletion through the dedicated deletion page. Support handles verification, deactivation, and confirmation. Driver account deletion
Contact
For privacy questions, account deletion requests, or support, contact support@freighttasks.com.