Privacy Policy

Last updated: 4 August 2026

1. About this Privacy Policy

This Privacy Policy explains how Flagship Dispatcher collects, uses, stores and shares personal information.

It applies to:

• The Flagship Dispatcher public website;
• The Flagship Dispatcher operator platform;
• Free-trial and paid operator accounts;
• The Flagship Dispatcher Driver App;
• Public demonstrations;
• Quote and booking forms powered by Flagship Dispatcher;
• Websites created or connected through Flagship Dispatcher;
• Payment, communication and tracking features;
• Customer support; and
• Other services provided under the Flagship Dispatcher name.

This Privacy Policy applies to website visitors, operator customers, account administrators, staff members, dispatchers, drivers, contractors, passengers, bookers and other people whose information is processed through the Service.

References to “personal information” in this policy mean information relating to an identified or identifiable individual.

2. Who we are

Flagship Dispatcher is a trading name and software service operated by:

Flagship Transfers Limited
Company number: 14615959

Registered office:

98 Parthenon Drive
Liverpool
England
L11 7AQ

Email:

flagshipdispatcher@gmail.com

Website:

Home

In this policy, “Flagship Dispatcher”, “we”, “us” and “our” refer to Flagship Transfers Limited.

3. When we are a controller and when we are a processor

Our legal role depends on why and how the information is being used.

When Flagship Dispatcher is the controller

Flagship Dispatcher normally acts as the data controller for personal information used for our own purposes, including:

• Website enquiries;
• Free-trial registrations;
• Operator account administration;
• Subscription management;
• Billing and payment records;
• Customer support;
• Platform security and fraud prevention;
• Authentication and login records;
• Business communications;
• Product and service announcements;
• Legal and regulatory compliance; and
• Establishing, exercising or defending legal claims.

Acting as controller means we determine why and how this information is used.

When Flagship Dispatcher is the processor

Transport operators use Flagship Dispatcher to manage their own passengers, customers, drivers, vehicles, staff and bookings.

For most operational information entered into the platform, the subscribing transport operator determines:

• Why the information is collected;
• Which information is entered;
• Who can access it;
• How it is used;
• How long it should be retained; and
• Whether it is shared with a driver, subcontractor or another operator.

In those circumstances:

• The subscribing operator normally acts as the data controller; and
• Flagship Dispatcher normally acts as its data processor.

We process that information under the operator’s instructions and in accordance with our Data Processing Agreement.

If you are a passenger, driver or employee and your information has been entered by a transport operator, you should normally contact that operator first about your information. We will assist the operator with valid requests where required.

Information used in both roles

Even where we process operational information for an operator, we may act as controller for limited information needed for:

• Account authentication;
• Platform security;
• Detecting misuse;
• Our own support correspondence;
• Compliance with law; and
• Legal claims.

4. Information we collect

The personal information we collect depends on how you use Flagship Dispatcher.

4.1 Website visitors and enquiries

When you visit our public website or contact us, we may collect:

• Your first and last name;
• Email address;
• Telephone number, where provided;
• Company or business name;
• The content of your message;
• Details about the Service you are interested in;
• Your IP address;
• Browser and device information;
• Website security information;
• Cookie and browser-storage information; and
• Information about how you reached or used the website.

Our current contact form requests a name, email address and message.

4.2 Operator customers and account users

When an operator starts a Trial, creates an Account or purchases a Subscription, we may collect:

• Name;
• Job title or role;
• Business name;
• Business address;
• Email address;
• Telephone number;
• Operator or business details;
• Account username and user ID;
• Password in securely protected form;
• Account permissions;
• Subscription plan;
• Trial and Subscription dates;
• Billing contact details;
• Payment status and transaction references;
• Account preferences and settings;
• Information about drivers, vehicles and users added to the Account;
• Platform activity and audit records;
• Login and security records;
• Support requests;
• Communications with us; and
• Feedback about the Service.

We do not intentionally store passwords in readable form.

4.3 Driver App users

Where an operator provides a driver with access to the Driver App, the Service may process:

Identity and contact information

• Name;
• Email address;
• Telephone number;
• Driver ID;
• Profile photograph;
• Account username;
• Operator or company association; and
• Emergency-contact information, where entered.

Driver and vehicle information

• Driving-licence information;
• Private hire driver-licence information;
• Licence numbers;
• Expiry dates;
• Driver status;
• Availability;
• Vehicle make, model, colour and registration;
• Vehicle capacity;
• Private hire vehicle plate details;
• Insurance information;
• MOT information; and
• Other information required by the operator.

Documents and uploaded files

The Driver App may allow drivers to photograph or upload:

• Driving licences;
• Private hire licences;
• Insurance documents;
• MOT certificates;
• Vehicle plates;
• Vehicle documents;
• Receipts;
• Profile photographs; and
• Other documents required by the operator.

Work and job information

• Assigned bookings;
• Completed bookings;
• Pickup and destination information;
• Passenger contact details;
• Journey instructions;
• Flight information;
• Job-status updates;
• Arrival and completion times;
• Waiting times;
• No-show records;
• Driver notes;
• Checklists;
• Return journeys;
• Earnings;
• Driver payment information;
• Availability; and
• Job history.

Location information

Depending on the operator’s settings, the function being used and the permissions granted on the device, the Driver App may collect:

• Precise location;
• Approximate location;
• Location timestamps;
• Vehicle or driver position;
• Journey progress;
• Arrival information; and
• Route-related information.

Where background tracking is enabled, location may be processed while the Driver App is not visible on the screen. This may be necessary to provide live job tracking and dispatch updates while a driver is carrying out work.

More information about location processing is provided in section 7.

Device and technical information

The Driver App may process:

• Device type;
• Operating system;
• App version;
• IP address;
• Device or installation identifiers;
• Push-notification token;
• Login history;
• Security events;
• Crash information;
• Error logs;
• Diagnostic information; and
• App-performance information.

4.4 Passengers, customers and bookers

Transport operators may enter or collect passenger and booking information through Flagship Dispatcher.

This may include:

• Passenger or booker name;
• Telephone number;
• Email address;
• Billing or business address;
• Pickup address;
• Destination;
• Intermediate stops;
• Journey date and time;
• Return-journey details;
• Passenger numbers;
• Luggage information;
• Child-seat requirements;
• Vehicle requirements;
• Flight, ferry or train information;
• Booking reference;
• Booking source;
• Fare and payment status;
• Payment-link information;
• Invoice information;
• Booking notes;
• Customer-account details;
• Communication history;
• Tracking information;
• Waiting-time information;
• Cancellation and no-show records;
• Review requests and review history;
• Complaints; and
• Other journey-related instructions.

The relevant transport operator is normally responsible for deciding what passenger information is necessary and lawful to collect.

4.5 Children and vulnerable passengers

Operators may use Flagship Dispatcher for:

• School transport;
• Special educational needs transport;
• Social-care transport;
• Assisted transport;
• Transport involving children; and
• Transport involving vulnerable adults.

Information processed in those circumstances may include:

• A child’s name;
• Parent or guardian details;
• School or care-setting information;
• Passenger assistant details;
• Collection and destination information;
• Accessibility requirements;
• Safeguarding instructions; and
• Necessary health or assistance information.

Flagship Dispatcher does not independently decide that this information should be collected. The relevant operator, council, school, care provider or other organisation is responsible for establishing a lawful basis and applying appropriate safeguards.

4.6 Health, disability and other sensitive information

Booking notes may contain information about:

• Disability;
• Mobility;
• Medical requirements;
• Accessibility;
• Wheelchair use;
• Special assistance;
• Safeguarding needs; or
• Other health-related travel requirements.

Driver records may also contain criminal-offence or background-check information, such as a Disclosure and Barring Service status.

This information receives additional protection under data protection law.

Where Flagship Dispatcher processes this information for an operator, the operator is responsible for identifying an appropriate lawful basis and any additional legal condition required for sensitive information.

Operators should enter only information genuinely necessary to provide the transport service safely and appropriately.

4.7 Payments and financial information

Flagship Dispatcher may process financial information relating to:

• Subscription payments;
• Passenger fares;
• Driver earnings;
• Driver payments;
• Expenses;
• Invoices;
• Refunds;
• Payment status;
• Transaction references;
• Payment links; and
• Payment-provider account identifiers.

Full card information is normally collected directly by the relevant payment provider, such as Stripe.

Flagship Dispatcher does not intentionally store:

• Full payment-card numbers;
• Card security codes; or
• Online-banking passwords.

We may receive limited information from the payment provider, such as:

• Payment status;
• Transaction identifier;
• Payment amount;
• Payment date;
• Card type or limited card details;
• Billing contact information; and
• Fraud or verification results.

4.8 Communications

The Service may process communications sent through or in connection with the platform, including:

• Booking confirmations;
• SMS messages;
• Emails;
• Push notifications;
• Tracking links;
• Payment links;
• Review requests;
• Customer messages;
• Driver messages;
• Delivery status;
• Support messages; and
• Communication history.

The operator remains responsible for deciding which communications are sent and ensuring that it has a lawful basis for using the recipient’s information.

4.9 Marketplace and subcontracting information

Where an operator uses marketplace or subcontracting functions, the Service may process or share:

• Operator or company details;
• Contact information;
• Journey details;
• Vehicle requirements;
• Proposed driver pay;
• Booking status;
• Acceptance or interest information;
• Business-performance indicators;
• Passenger information necessary to complete awarded work; and
• Communications between participating operators.

Information is made available according to the operator’s actions, account settings and instructions.

Passenger information should only be disclosed to another operator or driver where it is reasonably necessary and lawful to fulfil the booking.

4.10 AI-assisted features

Flagship Dispatcher may offer optional artificial-intelligence or automated features, including booking-information extraction.

Where an operator uses these features, the Service may process:

• Text pasted into the feature;
• Emails or booking messages submitted by the user;
• Passenger names;
• Contact details;
• Pickup and destination addresses;
• Journey dates and times;
• Flight details;
• Booking notes;
• Uploaded content; and
• The structured result produced by the feature.

The information may be sent to an approved AI service provider solely to provide the requested function.

Operators must review AI-extracted information before using it. Automated extraction may produce incorrect, incomplete or misplaced information.

5. How we obtain personal information

We may obtain personal information:

• Directly from you;
• From the operator that created your account;
• From an account administrator;
• From a driver;
• From a passenger or booker;
• Through a public quote or booking form;
• From a website powered by Flagship Dispatcher;
• From another transport operator through subcontracting or marketplace functions;
• From payment providers;
• From mapping, navigation or flight-information providers;
• From mobile devices and browsers;
• From email, SMS and push-notification providers;
• From app stores;
• Through platform-security and audit systems; and
• From another organisation that is lawfully using the Service.

6. How and why we use personal information

Where Flagship Dispatcher acts as controller, we may use personal information for the following purposes.

To provide the Service

We use information to:

• Create and administer Accounts;
• Provide Trials and Subscriptions;
• Authenticate users;
• Provide the operator dashboard and Driver App;
• Respond to enquiries;
• Provide support;
• Process subscription payments; and
• Deliver requested platform functions.

Depending on the circumstances, we rely on performance of a contract, steps requested before entering a contract, or our legitimate interests in providing and administering a business software service.

To manage business relationships

We use information to:

• Communicate with operator customers;
• Manage subscriptions;
• Send important service information;
• Respond to questions;
• Record agreed changes;
• Resolve complaints; and
• Maintain contractual records.

We rely on contract and our legitimate interests in managing customer relationships.

To protect the Service

We use information to:

• Prevent unauthorised access;
• Authenticate users;
• Detect fraudulent or abusive activity;
• Investigate incidents;
• Protect Customer Data;
• Maintain audit records;
• Test security;
• Enforce our Terms; and
• Protect our legal rights.

We rely on our legitimate interests in securing the Service, protecting users and preventing fraud or misuse. We may also rely on legal obligations where applicable.

To maintain and improve the Service

We may use technical, diagnostic and usage information to:

• Identify errors;
• Investigate performance problems;
• Improve reliability;
• Understand how functions are used;
• Develop improvements;
• Test updates; and
• Provide technical support.

We rely on our legitimate interests in maintaining and improving the Service. Where non-essential cookies or tracking require consent, we will request consent before using them.

To manage payments and records

We use billing and transaction information to:

• Take Subscription payments;
• Record invoices;
• Handle failed payments;
• Prevent payment fraud;
• Maintain accounting records; and
• Comply with tax and company-law obligations.

We rely on contract, legitimate interests and legal obligations.

To send marketing

We may send information about Flagship Dispatcher features, offers or updates where permitted.

Depending on the recipient and communication method, we may rely on consent or legitimate interests.

You can opt out of marketing at any time. Service messages relating to an active Account are not marketing and may still be sent where necessary.

To comply with law and protect legal rights

We may use or disclose information where necessary to:

• Comply with a legal obligation;
• Respond to a valid court or regulatory request;
• Prevent or investigate crime;
• Obtain legal advice;
• Establish, exercise or defend a legal claim;
• Cooperate with regulators; or
• Protect a person’s vital interests in an emergency.

The applicable basis may be legal obligation, legitimate interests, recognised legitimate interests or vital interests, depending on the circumstances.

Processing on behalf of an operator

Where we act as processor, we use passenger, driver, booking and operational information only to:

• Provide the Service;
• Follow the operator’s documented instructions;
• Protect and maintain the platform;
• Provide requested support;
• Comply with law; and
• Carry out the processing described in our Data Processing Agreement.

The operator is responsible for determining its own lawful basis.

7. Driver location and live tracking

Location information can be particularly sensitive, so it should only be processed for clear operational purposes.

The Driver App may use location information to:

• Show an operator where an active driver or vehicle is located;
• Provide live job progress;
• Confirm arrival at a pickup;
• Support passenger tracking links;
• Assist with job allocation;
• Record journey-status information;
• Support navigation;
• Investigate an operational or security issue; and
• Provide other location-enabled functions selected by the operator.

Depending on device permissions and the function being used, location may be collected:

• While the Driver App is open;
• While an assigned job is active;
• While the driver is marked available or on duty;
• While live tracking is enabled; and
• In the background where background location is necessary and permission has been granted.

Location access can normally be controlled through the device settings. Disabling location may prevent live tracking, arrival confirmation, job-allocation or other location-dependent functions from working correctly.

The operator is responsible for:

• Informing drivers about tracking;
• Establishing a lawful basis;
• Deciding when tracking should be active;
• Limiting access to authorised users;
• Avoiding unnecessary monitoring; and
• Setting a suitable retention period.

Flagship Dispatcher does not intend location tracking to be used for unrelated or excessive monitoring.

We retain location information only for as long as reasonably necessary to:

• Provide live tracking;
• Maintain relevant journey records;
• Investigate disputes or incidents;
• Protect platform security; or
• Follow the operator’s lawful instructions.

8. App permissions

The Driver App may request access to certain device functions.

Location

Used for live tracking, journey progress, arrival information, dispatch functions and navigation-related features.

Camera, photographs and files

Used where a driver chooses to photograph or upload a licence, vehicle document, receipt, profile photograph or another permitted file.

Notifications

Used to deliver assigned-job alerts, booking changes, document reminders and other operational notifications.

Telephone and external communication links

The Driver App may allow a driver to open the device telephone function, messaging service or WhatsApp to contact a passenger or operator.

Opening an external communication app does not mean that Flagship Dispatcher records the content of the telephone call or external conversation. The relevant external provider may process information under its own privacy policy.

Navigation

The Driver App may open an external mapping or navigation service. The navigation provider’s own privacy terms apply to its processing.

Device permissions can be changed through the device settings, although disabling a permission may prevent the relevant feature from working.

9. Automated processing and AI

Flagship Dispatcher may use automation to:

• Extract booking fields from submitted text;
• Produce administrative alerts;
• Highlight expired or missing documents;
• Calculate figures;
• Display acceptance or activity indicators;
• Organise bookings;
• Suggest operational information; and
• Identify possible technical or security issues.

These functions are intended to assist human users.

Flagship Dispatcher does not intend these features to make solely automated decisions about an individual that produce legal or similarly significant effects.

Operators and authorised users remain responsible for reviewing information and making operational, employment, licensing, safeguarding and financial decisions.

10. Who we share information with

We may share information only where necessary for the purposes described in this policy.

The subscribing operator

Information may be available to authorised administrators, dispatchers, staff members and other users belonging to the operator Account.

Drivers

Passenger and booking information may be shared with an assigned driver where required to complete a journey.

This may include:

• Passenger name;
• Contact number;
• Pickup and destination;
• Journey time;
• Flight information;
• Passenger requirements; and
• Relevant booking notes.

Subcontractors and other operators

Information may be shared with another operator or driver where the subscribing operator chooses to subcontract or award work.

Cloud and infrastructure providers

We use service providers for hosting, storage, databases, backups, security and email delivery. This may include Amazon Web Services.

Mobile and notification providers

We may use:

• Google and Firebase services;
• Apple Push Notification Service;
• Mobile-app infrastructure providers; and
• Diagnostic or error-reporting services.

Communications providers

We may use providers such as Twilio or email-delivery providers to send SMS messages, email messages and delivery notifications.

Payment providers

Stripe or another payment provider may process Subscription or passenger-payment information.

Payment providers may act as our processor, the operator’s processor or an independent controller for some fraud-prevention, verification and regulatory purposes.

Mapping and flight-information providers

Addresses, route searches, coordinates or flight details may be sent to mapping, geocoding, navigation or flight-information providers where those functions are used.

AI service providers

Information deliberately submitted to an AI-assisted feature may be processed by the approved provider configured for that feature.

Professional advisers and insurers

Information may be shared with accountants, solicitors, auditors, insurers and other professional advisers where reasonably necessary.

Authorities and legal recipients

We may disclose information where required by:

• Law;
• A court order;
• A regulator;
• A licensing authority;
• Law enforcement;
• A tax authority; or
• Another organisation with lawful authority to request it.

Business transactions

If Flagship Dispatcher or the relevant business is sold, merged, reorganised or transferred, information may be disclosed to genuine prospective purchasers and advisers under appropriate confidentiality arrangements.

We do not sell personal information to data brokers or advertisers.

Where a provider acts as our processor, we require it to protect the information and process it only for authorised purposes.

11. International transfers

Some service providers may process information outside the United Kingdom.

Where personal information is transferred to a country not covered by UK adequacy regulations, we will use an appropriate safeguard where required, such as:

• The UK International Data Transfer Agreement;
• The UK Addendum to approved Standard Contractual Clauses;
• Another approved contractual mechanism;
• Binding corporate rules; or
• Another lawful transfer safeguard.

We may also assess the destination country and apply supplementary technical or organisational safeguards where appropriate.

You may contact us for more information about the safeguards applying to a particular transfer.

12. How long we keep information

We keep personal information only for as long as reasonably necessary for the purpose for which it was collected, subject to legal, contractual, security and dispute-resolution requirements.

Our normal retention approach is as follows.

Website enquiries

Contact-form and general-enquiry information may normally be retained for up to 24 months after the last meaningful contact, unless a longer period is required for a contract, complaint or legal claim.

Trial Accounts

Where an operator does not activate a paid Subscription, Trial Account information may be deleted or anonymised approximately 30 days after the Trial ends.

Active operator Accounts

Customer Data is normally retained while the operator Account remains active.

Cancelled or terminated Accounts

Following cancellation or termination, Customer Data will normally remain available for export for up to 30 days.

After that period, it may be deleted or anonymised from active systems.

Backups

Deleted information may remain in protected backups for up to 90 days before being overwritten through the normal backup cycle.

Backup information is restricted and is not normally restored except for disaster recovery, security or legal reasons.

Billing and accounting records

Billing, payment, tax and accounting records may be retained for up to six years after the relevant financial period, or longer where legally required.

Contract and support records

Important contractual, complaint and support records may be retained for up to six years after the relationship ends where reasonably necessary to manage disputes or legal claims.

Security logs

Security and authentication records may normally be retained for up to 12 months.

They may be kept for longer where connected to a security incident, fraud investigation, legal claim or regulatory matter.

Marketing records

Marketing contact information is retained until:

• You opt out;
• Consent is withdrawn;
• The information is no longer accurate; or
• We determine that it is no longer necessary.

We may retain a minimal suppression record to ensure that an opt-out continues to be respected.

Operational, booking and driver information

Where we process information for an operator, the retention period is normally determined by that operator.

Information may also be deleted in accordance with the Account closure and backup periods described above.

Location information

Location is retained only for the period reasonably required for tracking, journey records, incident investigation, security or the operator’s documented purposes. It is not intended to be retained indefinitely without a defined need.

We may retain information for longer where required by law, court order, regulatory obligation or the establishment, exercise or defence of legal claims.

13. Data security

We use reasonable technical and organisational measures designed to protect personal information.

These may include:

• Encrypted transmission using HTTPS and TLS;
• Access controls;
• User authentication;
• Secure password protection;
• Role-based permissions;
• Restricted administrative access;
• Cloud security controls;
• Private or controlled document storage;
• Logging and monitoring;
• Backups;
• Security updates;
• Incident-response procedures; and
• Confidentiality requirements.

No online service can guarantee complete security. Users and operators must also protect passwords, devices, accounts and access permissions.

Operators should remove user access promptly when an employee, contractor or driver no longer requires it.

Please do not send highly sensitive documents through ordinary email unless we have specifically asked you to use that method.

14. Cookies and browser storage

Our website and operator platform may use cookies, session storage, local storage and similar technologies for:

• Account sign-in;
• Authentication;
• Security;
• Session management;
• Essential preferences; and
• Other necessary website and platform functions.

More information is available in our Cookie Policy:

https://flagship-dispatcher.co.uk/cookie-policy/

Where we introduce non-essential analytics, advertising or tracking technologies that require consent, we will provide appropriate information and controls before they are activated.

15. Marketing communications

We may send service information and operational communications to Account users.

These may include:

• Security alerts;
• Subscription information;
• Trial updates;
• Important changes;
• Planned maintenance;
• Account notices; and
• Support responses.

These are not necessarily marketing and may be required to administer an Account.

We may also send promotional information about Flagship Dispatcher where permitted.

You can opt out of promotional marketing by:

• Using the unsubscribe link in the message; or
• Contacting us at flagshipdispatcher@gmail.com.

Opting out of marketing does not prevent us from sending essential Account or security communications.

16. Your data protection rights

Depending on the circumstances and our legal role, you may have the right to:

• Be informed about how your information is used;
• Request access to your personal information;
• Request correction of inaccurate or incomplete information;
• Request deletion of information;
• Request restriction of processing;
• Receive certain information in a portable format;
• Object to particular uses of your information;
• Withdraw consent where processing is based on consent; and
• Raise concerns about automated decision-making.

These rights are not absolute and may depend on:

• Our lawful basis;
• Whether Flagship Dispatcher or the operator is the controller;
• Legal record-retention requirements;
• The rights of another person;
• Security requirements; and
• Applicable legal exemptions.

We may request information to verify your identity before responding.

17. Your right to object

You have the right to object at any time to the use of your personal information for direct marketing.

You may also object to processing based on legitimate interests.

Where you object to direct marketing, we will stop using your information for that purpose.

For other objections, we will consider your request and stop processing unless we have a lawful and compelling reason to continue or the information is required for legal claims.

18. Passenger and driver requests

Where information was entered by a transport operator, that operator is normally the controller.

Passengers

Passengers should normally contact the operator that accepted or managed the booking.

The operator’s contact details may be found on:

• The booking confirmation;
• Payment receipt;
• Email or SMS message;
• Tracking page; or
• Operator website.

Drivers

Drivers should normally contact the operator that created or manages their Driver App Account.

The operator is responsible for decisions concerning:

• Driver records;
• Job history;
• Earnings records;
• Licence documents;
• Employment or contractor information;
• Location retention; and
• Account access.

If you contact Flagship Dispatcher directly, we may forward the request to the relevant operator or ask for its instructions.

19. Account and data deletion

Operator administrators may request closure of their Flagship Dispatcher Account by using any Account cancellation or deletion function made available or by contacting us.

Drivers may request deletion of their Driver App Account through the available account-deletion process or by contacting:

flagshipdispatcher@gmail.com

We may need to verify:

• Your identity;
• The Account involved;
• Your relationship with the operator; and
• Your authority to request deletion.

Where the operator controls the relevant data, we may refer the request to that operator.

Deleting a login Account does not necessarily require immediate deletion of every booking, payment, safety or legal record connected with that individual. Some information may need to be retained because:

• The operator has a lawful reason to retain transport records;
• The information relates to another person;
• It is needed for accounting or tax;
• It is required for security or fraud prevention;
• It is required for a complaint or legal claim; or
• Retention is required by law.

Where deletion applies, information will normally be removed from active systems and then overwritten through the backup cycle described in section 12.

20. Children

The Flagship Dispatcher operator platform and Driver App are intended for business users and authorised adult drivers.

They are not intended for children to create their own operator or driver Accounts.

However, operators may process children’s passenger information for legitimate transport purposes. In those circumstances, the relevant operator is responsible for:

• Providing age-appropriate privacy information where required;
• Informing parents or guardians;
• Establishing a lawful basis;
• Applying safeguarding controls;
• Limiting information to what is necessary;
• Restricting access; and
• Applying an appropriate retention period.

21. Links and third-party services

Our website, platform and Driver App may link to services operated by other organisations, including:

• Payment services;
• Mapping and navigation apps;
• Flight-information services;
• App stores;
• WhatsApp;
• Telephone services;
• Review platforms; and
• Operator websites.

Those organisations may collect information independently under their own privacy policies.

We are not responsible for the privacy practices of an independent third-party service.

22. Public demonstration

The Flagship Dispatcher public demonstration is intended only for testing sample functions.

Users must not enter:

• Real passenger information;
• Real driver information;
• Driver documents;
• Payment details;
• Confidential business information;
• Health information; or
• Other sensitive personal information.

Demonstration data may be reset or deleted without notice.

23. Data protection complaints

You can make a complaint about how Flagship Dispatcher has used your personal information by contacting:

flagshipdispatcher@gmail.com

Please include:

• Your name;
• The relevant operator or Account;
• A description of your concern;
• Relevant dates or messages; and
• The outcome you are seeking.

We will:

• Provide a clear way for you to complain;
• Acknowledge a data protection complaint within 30 days;
• Investigate it without undue delay;
• Keep you reasonably informed; and
• Tell you the outcome.

You also have the right to complain to the UK data protection regulator:

Information Commissioner’s Office

Website:

https://ico.org.uk

We would appreciate the opportunity to investigate your concern first, but you are not required to contact us before approaching the ICO.

24. Changes to this Privacy Policy

We may update this Privacy Policy when:

• The Service changes;
• We add or remove features;
• Our providers change;
• Our processing activities change;
• App-store requirements change; or
• Data protection law or regulatory guidance changes.

The latest version will be published on this page.

Where a change materially affects how we use personal information, we will take reasonable steps to bring it to the attention of affected users before the new use begins.

25. Contact us

Questions, requests and complaints about this Privacy Policy can be sent to:

Flagship Dispatcher
Flagship Transfers Limited

Registered office:

98 Parthenon Drive
Liverpool
England
L11 7AQ

Email:

flagshipdispatcher@gmail.com

Website:

Home