Data collection in glimble app

This page describes what data is collected by the glimble app.

User data

The following data are transmitted and subsequently stored by the app:

• Unique identifier: each user of the app is assigned a unique identifier
• The current travel area
• The version number of the glimble app
• The operating system (OS) of the device on which the app is installed
• Type designation of the device on which the app is installed (e.g. iPhone 6)
• The version number of the operating system of the device on which the app is installed
• Advertiser's identification codes
• The app user's email address
• App user's phone number
• The language the app user uses in the app
• Type of external account used to log into the app. This is only known if the user uses it (e.g. Google, Facebook)
• User name
• Password in encrypted form
• Date and time when the user first registered
• Last date and time the user changed their personal data in the app
• Advertisement identifiers
• Date and time when the app was first opened
• Date and time when the app was last opened
• The date and time the app was uninstalled
• The media source if the user installed the app through a referral
• Mobile phone provider
• Number of times the app has been installed

App behaviour

In general, it can be assumed that every action in the app is recorded and stored:

• Date and time when the user did something in the app
• The type of screen the user is on
• What the user clicks on
• What the user types into text fields
• The geographical location of the user during each action in the app
• The last known geographic location of the user

Schedules

• The date and time when a planning is made
• Planning options that are given but not accepted
• The start and arrival location of each schedule
• The start and arrival location of each schedule
• The start and arrival location as entered by the user
• The plan chosen by the user
• The time it takes to generate the plans
• The travel area in which the user is located during the creation of a plan
• The user's preferences for transport options (e.g. bus, train)
• Expected departure and arrival times
• The number of interchanges for each schedule
• Walking distances
• Waiting times
• Reasons for unsuccessful scheduling
• Distances between locations in the planning
• Total travel distance between start and departure times

Tickets and bookings

• The schedules associated with the bookings made by the app user
• The cost of the tickets associated with the bookings

Push notificaties

• The text of the notifications that the user receives from the app
• Whether the user has received the notification or not
• Whether the user clicked on the notification or not
• How long it took before the user clicked on the notification or not
• The time the alert was sent
• The travel area in which the user was located when the notification was sent
• Which target group the user is in
• The subject of the notification
• The source from which the notification was sent
• The duration for which the notification remains valid for the user to continue clicking on it

6 September, 2021