A clear account of the information we use.

Last updated: 5 September 2026

About this page

This notice covers the Tanker Docket website, driver app, cloud docket service, and customer reporting portal. It explains what information the service handles, why it is needed, and the choices available to drivers and customer organisations.

Information on this website

Visiting the public website does not require an account. We may receive basic technical information needed to deliver and protect the site, such as request timestamps, browser details, and security logs.

Optional Google Analytics is loaded only after you choose “Accept analytics” in the consent prompt. We use it to understand page visits, app-download clicks, and contact-link clicks. We do not send form contents, passwords, or docket details to analytics.

External contact forms

When configured, the “Talk to the team” link opens an external form provider. Information submitted there is handled under that provider’s privacy notice and the terms shown on the form. Do not submit sensitive delivery or payment information through a public contact form.

Customer portal accounts

The customer portal uses account, session, and authentication information, including your name and email address, to provide access to an approved organisation. Passwords are entered only on the secure website. The driver app signs in through the system browser and stores encrypted session credentials in the device keychain or secure storage; it does not collect or save your password.

Driver app and cloud docket information

The app works without an account and stores delivery records on the device. If a driver signs in and enables cloud use, completed dockets can be uploaded to their approved organisation. Draft dockets are not uploaded. Older local records are uploaded only after the driver confirms that action.

An uploaded docket may contain the driver name, truck number, docket and order numbers, delivery date and time, customer and site codes, site name, delivery address and postcode, products, quantities, tank numbers and dip readings, operational notes, and print result. We also store record identifiers, revision and audit timestamps, the account that created the record, its organisation, and print-attempt status.

How cloud information is used and shared

Cloud information is used to synchronise completed delivery records, show a driver their own history, provide authorised organisation owners, administrators, and viewers with operational reports, resolve sync errors, secure the service, and meet support or legal obligations. A driver is limited to records created by that account. Organisation managers can access records belonging to their organisation. We do not use delivery records for advertising and do not sell them.

Storage, security, and retention

Local records remain on the device until removed through the product or device-management process. Cloud records are stored with contracted infrastructure providers and protected by account, organisation, and role checks. Access credentials and full docket payloads must not be written to analytics or application error logs. The final customer agreement and retention schedule will state how long cloud records and security logs are kept and when they are deleted or de-identified.

Choices and requests

You can decline optional analytics or reopen the privacy choices control in the footer. Drivers may sign out without losing local records; signing out clears the cloud cache and session credentials from that device. Unsent records are not deleted. Access, correction, export, and deletion requests may be made through the privacy contact that will be published before launch. Some records may need to be kept for legal, safety, accounting, or dispute-resolution purposes.

Changes

We may update this notice when the website, app, portal, or data practices change. The effective date at the top will be updated with each published revision.