APP TRACKING TECHNOLOGIES POLICY

OUR USE OF APP TRACKING TECHNOLOGIES

In this App Tracking Technologies Policy you will find information on what tracking technologies may be set when you use our app and the purposes for which we use those technologies.  The app is owned and operated by Premier Inn Hotels Ltd in the UK or its applicable group company in Germany (“we”, “us”, “our”).
  

WHAT ARE APP TRACKING TECHNOLOGIES? 

App tracking technologies include software development kits (SDKs), device and app identifiers, analytics tools and similar technologies that collect information about how our app is used.

These technologies help us: 
 

  • keep the app functioning correctly;
     
  • monitor and improve app performance;  
     
  • remember preferences and settings;
     
  • understand how customers use the app; and 
     
  • where you provide consent, support analytics, personalisation and advertising activities.

We use the term "tracking technologies" in this policy to describe all technologies that collect information in this way. 
   

  • Strictly necessary tracking technologies. These technologies are required for the operation, security and reliability of our app. They cannot be switched off because the app cannot function properly without them. 
      
  • Analytical tracking technologies. They allow us to recognise and count the number of visitors and to see how visitors move around our app when they are using it. This helps us to improve the way our app works, for example, by ensuring that users are finding what they are looking for easily. 
      
  • Functionality technologies. These are used to recognise you when you return to our app and to embed functionality from third party services. This enables us to remember your preferences and to integrate useful services provided by third party providers into our app.
      
  • Advertising technologies. These technologies record your visit to our app, the pages you visited on our app and others and the links you followed. We will use this information to make the advertising displayed to you more relevant to your interests. We may also share this information with third parties for this purpose. 

 

THIRD PARTY TRACKING TECHNOLOGIES

We may also use and work with third-party suppliers and partners who set or read tracking technologies on our app.  We do not have any control over these. Whilst we provide a summary of the third-party tracking technologies used in this Policy, you should also check the relevant third party’s privacy policy for more information about how these are used.

 

MANAGING YOUR TRACKING PREFERENCES 

You can provide your tracking preferences by using the banner presented to you when you first joined the app. 

You can change your non-essential tracking preferences at any time in My Account by using the Allow Optional Tracking toggle. This option is available on app versions v4.58.1 or later for iOS and 4.37.1or later for Android.

 

TRACKING TECHNOLOGIES USED ON OUR APP
  
Details of the tracking technologies used on our app are outlined in the table below:
  

Essential
Show more
Show less

Technology

Premier Inn app and booking services

Why we use it

Enables the app to operate and provides the services requested by customers, including searching for hotels, viewing hotel and room information, signing in, making a booking and managing an existing booking.

Information that may be processed

App-session information, searches, hotel and room selections, booking details, account information where a customer signs in, and technical information required to provide the service.

What this means for customers

These technologies are required to provide the app and booking services and cannot be switched off.

Technology

Google Firebase Remote Config - essential configuration

Why we use it

Allows us to deliver technical settings required for the app to operate correctly without requiring customers to download a new version of the app.

Information that may be processed

App and package information, app version, operating-system information, installation or app-instance identifiers, configuration-request information and
technical tokens required to retrieve the configuration.

What this means for customers

Essential app configuration remains active because it is required for the app to operate. This does not permit optional performance measurement,
experimentation or personalisation.

Technology

Google Firebase Crashlytics - critical crash diagnostics

Why we use it

Helps us identify, investigate and resolve serious crashes and technical failures that could prevent the app or a requested service from working
correctly.

Information that may be processed

Information about the crash or error, app version, device model, operating-system information, installation and session identifiers, timestamps,
process information and technical information about the circumstances in which the failure occurred.

What this means for customers

Limited crash diagnostics required to maintain app availability and resolve critical failures remain active. This information is not used for advertising
or personalisation.

Technology

Dynatrace - availability and critical incident monitoring

Why we use it

Helps us monitor whether the app and supporting services are available, identify serious errors, manage incidents and diagnose critical technical
failures.

Information that may be processed

Error information, network timing, technical-request information, app and device information, operating-system information, diagnostic or correlation
identifiers, and IP-derived technical information.

What this means for customers

Limited monitoring required for service availability, security and critical fault diagnosis remains active. Optional performance and customer-journey
measurement is addressed separately in the Non-Essential table.

Technology

3CInt payment technology

Why we use it

Provides the hosted payment journey and enables customers to securely pay for a booking.

Information that may be processed

Payment-session and transaction information, tokenised or encrypted payment information, device and technical information, and payment-security information.

What this means for customers

This technology is activated when a customer chooses to make a payment and is required to process that payment.

Technology

Jscrambler - payment security

Why we use it

Helps protect the payment journey against code tampering, misuse and other technical security threats.

Information that may be processed

Technical security signals, application and payment-page integrity information, and device or runtime information required to identify security threats.

What this means for customers

This technology may operate during the payment journey because it is required to protect the payment service. It is not used for unrelated advertising or personalisation.

Non-Essential 
Show more
Show less

Technology

Google Firebase Performance Monitoring

Why we use it

Helps us understand app speed, loading times, network performance and technical issues so that we can improve the app's reliability and performance.

Information that may be processed

App version, device model, operating-system information, network type, technical request information, request duration, response information,
installation or session identifiers and performance measurements.

What happens if it is not allowed

We will not use Firebase for optional app and network-performance measurement. Essential configuration and critical crash diagnostics may continue separately.

Technology

Dynatrace - optional performance and journey monitoring

Why we use it

Helps us understand detailed app performance and how customer journeys perform beyond the monitoring required to maintain service availability.

Information that may be processed

App and device information, operating-system information, network requests, timing information, screen or user-action names, session or correlation
identifiers and IP-derived information.

What happens if it is not allowed

We will not use Dynatrace for optional performance or journey measurement. Monitoring strictly necessary for availability, security and critical fault
diagnosis may continue.

Technology

Adobe Analytics

Why we use it

Helps us understand how customers use the app, which screens and features are used and where customers may experience problems. We use this information to measure and improve the app and booking journey.

Information that may be processed

App and device information, operating system, screen names, interactions, selected app events, session information, login status and an analytics
identifier.

What happens if it is not allowed

We will not use Adobe Analytics to measure the customer's app journey. The customer will still be able to use the app and make a booking.

Technology

Adobe Target - feature testing

Why we use it

Helps us test different versions of app features or content and understand which version provides a better customer, business or technical outcome.

Information that may be processed

App and device information, session and visitor identifiers, test assignments, interactions and information about how a version performs.

What happens if it is not allowed

The customer will not be included in optional Adobe Target tests and will receive the standard version of the app experience.

Technology

Adobe Target - personalisation

Why we use it

Helps us provide tailored content or app experiences based on information about how the app is used.

Information that may be processed

App and device information, session and visitor identifiers, interactions, experience assignments and information used to select personalised content or experiences.

What happens if it is not allowed

We will not use Adobe Target to personalise the customer's app experience. Standard content will be displayed instead.

Technology

Contentsquare - experience analytics

Why we use it

Helps us understand how customers navigate and interact with the app and identify areas where the app experience could be improved.

Information that may be processed

App and device information, session identifiers, screen names, navigation, interactions, selected app events and technical experience information.

What happens if it is not allowed

We will not use Contentsquare to analyse the customer's app journey. The customer will still be able to use the app and make a booking.

Technology

Contentsquare - session replay

Why we use it

Helps us investigate usability and technical issues by recreating interactions within an app session.

Information that may be processed

Session identifiers, screen names, taps and interactions, selected app events and representations of content displayed in the app. We use masking and other controls designed to protect sensitive information.

What happens if it is not allowed

We will not record or recreate the customer's app session. The customer will still be able to use the app and make a booking.

Technology

AppsFlyer - installation and campaign attribution

Why we use it

Helps us understand whether an app installation resulted from an advertising campaign and identify the campaign that contributed to the installation.

Information that may be processed

App and device information, advertising identifiers where available, attribution and installation identifiers, campaign and referral information, timestamps, IP address and privacy-preserving advertising-measurement information.

What happens if it is not allowed

We will not use device-level information for optional app-install attribution. The customer will still be able to use the app and make a booking.

Technology

AppsFlyer - selected app-event and conversion measurement

Why we use it

Helps us understand whether selected activities in the app resulted from an advertising campaign and measure campaign effectiveness.

Information that may be processed

Attribution identifiers, campaign information, selected app events, event timestamps, app and device information, advertising identifiers where available and IP address.

What happens if it is not allowed

We will not use or share selected app-event information for optional advertising conversion measurement.

Technology

Google Ads - advertising attribution and measurement through AppsFlyer

Why we use it

Helps us understand whether advertising on Google services contributed to an app installation or selected activity and helps us measure campaign
effectiveness.

Information that may be processed

Where configured, AppsFlyer may send Google Ads installation-attribution information, campaign information, selected app events, timestamps, consent information and advertising identifiers or privacy-preserving measurement information.

What happens if it is not allowed

We will not send optional advertising-attribution or selected app-event information to Google Ads. Customers may still see adverts, but we may be less able to measure their effectiveness.

Technology

Microsoft Advertising - advertising attribution and measurement through AppsFlyer

Why we use it

Helps us understand whether advertising on Microsoft services, including Bing, contributed to an app installation or selected activity and helps us measure campaign effectiveness.

Information that may be processed

Where configured, AppsFlyer may send Microsoft Advertising installation-attribution information, campaign information, selected app events, timestamps, and app or device information.

What happens if it is not allowed

We will not send optional advertising-attribution or selected app-event information to Microsoft Advertising. Customers may still see adverts, but we may be less able to measure their effectiveness

CONTACT US

If you have any questions or concerns about tracking technologies or your privacy when using our app in the UK, please contact us by email at: privacyofficer@whitbread.com. 

If you have any questions or concerns about tracking technologies or your privacy when using our app in Germany, please email our data protection officer in Germany, Dr. Sebastian Kraska, at skraska@iitr.de.
Show more
Show less