Jelbi logo

TRACKING AND ANALYTICS.

How we analyse our offer

How many users are currently in our app? Which means of transport do our users particularly like to use?  Can our users find the optimal connection of different means of transport with the help of our routing suggestions? Answering such questions is important for us in order to improve and further develop our offer on a technical level.

1. Google Analytics for Firebase and Google Analytics

In order to be able to analyse our offer for the above-mentioned purposes, we use the analysis service Google Analytics for Firebase and Google Analytics. Of course this requires your prior consent. Google acts as a data processor on our behalf.

The Google Firebase SDK is implemented in our app. At the app level, a so-called App Instance ID is generated here (pseudonymised). This works similar to cookies in a web browser. It is a randomly generated ID, which is recorded the first time the app is used. For this purpose, general device information such as model and operating system as well as interactions with our app, such as clicks to search for nearby means of transport or views of different screens, are recorded.

When using Google Anaytics for Firebase, the following data about your use of the app is used and transmitted to Google pseudonymously:

In the standard implementation of Google Analytics for Firebase, the following data types are collected:

  • Number of users and sessions
  • Session duration
  • Operating systems
  • Device models
  • Region
  • First-time starts
  • App versions
  • App updates
  • In-app purchases
You can find a complete overview of data acquisition
Events screen_open element_tab modal_show item_show
Parameter
travel_class x x x x
index x x x x
content x x x x
content_type x x
source x
item_name x x x x
item_id x x x x
item_category x x x
group_id x x x x
Score x x x
Achievement ID x x x
Origin x
Booking_ID x x x x
shedule_id x x x x
label x x
Destination x x
Track_id x x
Ticket_type x
screen_name x x x x

Anonymization of IP addresses is always enabled via the Firebase SDK. This does not allow us to assign the above-mentioned data to a specific person. For more information about data processing and IP address anonymization with Google Firebase SDK please visit: https://support.google.com/analytics/answer/2763052.

The collected data is usually transferred to US servers and stored there. However, Google must first truncate IP addresses in member states of the European Union or in other states that are parties to the Agreement on the European Economic Area. You can find an overview of IP anonymisation here.

The above-mentioned data is transferred to the USA under the EU-US Privacy Shield on the basis of the adequacy decision of the European Commission. You can download the certificate here.

The legal basis for the use of Google Analytics for Firebase is your consent according to Art. 6 para. 1 p.1 lit. a GDPR.

You can find more information on the terms of use and data protection at Google Analytics at https://www.google.com/analytics/terms/de.html or https://policies.google.com/?hl=de.

Only the data collected in Google Analytics for Firebase is forwarded to Google Analytics for a simplified view. The data we collect and link to App Instance ID is automatically deleted after 14 months. Data that has reached its retention period is automatically deleted once a month. Of course you can revoke your consent to data analysis at any time with effect for the future by adjusting your consent in the app in the “Legal” > “Jelbi” section.

2. Batch

When using Batch, the following data about your use of the app is used and transmitted:

Data Purpose Retention
Installation ID Default data captured by the Batch SDK 12 months after the end of the contract
Advertising ID (can be deactivated: iOS / Android) Default data captured by the Batch SDK 12 months after the end of the contract
Identifier for Vendor (IDFV), on iOS (can be deactivated). Default data captured by the Batch SDK 12 months after the end of the contract
API level of the SDK (on Android) Default data captured by the Batch SDK 12 months after the end of the contract
IP address Default data captured by the Batch SDK 12 months after the end of the contract
Bundle ID Default data captured by the Batch SDK 12 months after the end of the contract
OS version Default data captured by the Batch SDK 12 months after the end of the contract
App version Default data captured by the Batch SDK 12 months after the end of the contract
Batch SDK version Default data captured by the Batch SDK 12 months after the end of the contract
Push token Default data captured by the Batch SDK After the app has been uninstalled
Push notifications opt-in status Default data captured by the Batch SDK 12 months after the end of the contract
MLVL (Mobile Landing Version) Default data captured by the Batch SDK 12 months after the end of the contract
Transaction tracked Default data captured by the Batch SDK 12 months after the end of the contract
Locale (language and region) Default data captured by the Batch SDK 12 months after the end of the contract
Device time zone Default data captured by the Batch SDK 12 months after the end of the contract
Country Default data captured by the Batch SDK 12 months after the end of the contract
City (if user is connected to a Wifi network) Default data captured by the Batch SDK 12 months after the end of the contract

First SDK start date

Default data captured by the Batch SDK 12 months after the end of the contract

Last SDK start date

Default data captured by the Batch SDK 12 months after the end of the contract
List of the campaigns that targeted the install Default data captured by the Batch SDK 12 months after the end of the contract

List of the campaigns that targeted the install and clicked by the user

Default data captured by the Batch SDK 12 months after the end of the contract
Smart Segment Default data captured by the Batch SDK 12 months after the end of the contract
Send date of the most recent campaign that targeted the install Default data captured by the Batch SDK 12 months after the end of the contract
Number of push sent to the install Default data captured by the Batch SDK 12 months after the end of the contract
Consent to marketing communcation Marketing 12 months after the end of the contract
Consent to analytics & tracking Marketing & Analytics 12 months after the end of the contract
First name Marketing 12 months after the end of the contract
First login/registration date Marketing & Analytics 12 months after the end of the contract
Login status Marketing & Analytics 12 months after the end of the contract
Payment method added Marketing & Analytics 12 months after the end of the contract
ID added Marketing & Analytics 12 months after the end of the contract
Driver’s license added Marketing & Analytics 12 months after the end of the contract
In-app purchases Marketing & Analytics 12 months after the end of the contract
Information on added vouchers/account credits

Marketing & Analytics

 

12 months after the end of the contract
Location Marketing & Analytics 12 months after the end of the contract
Gender Marketing & Analytics 12 months after the end of the contract
Age range Marketing & Analytics 12 months after the end of the contract
Email address Marketing 12 months after the end of the contract

The legal basis for the use of Google Analytics for Firebase is your consent according to Art. 6 para. 1 p.1 lit. a GDPR.

You can find more information on the terms of use and data protection at Batch at https://batch.com/privacy-policy. 

You can revoke your consent to data analysis at any time with effect for the future by adjusting your consent in the app in the “Legal” > “Jelbi” section.