This page lists the data that are collected by the Glimble app.

User data transmitted and stored by the app:

• unique identifier (each user in the app is assigned a unique identifier);

• the geographic area of travel;

• the version of the Glimble app;

• the operating system of the device on which the app is installed;

• the type of the device on which the app is installed (e.g., iPhone 6);

• the operating system version of the device where the app is installed;

• the user's email address;

• the user's phone number;

• the language used by the user in the app;

• the type of external account, if any, used by the user to identify himself/herself (when, for example, a user identifies with Google or Facebook);

• the user's name;

• the password in encrypted form;

• the date and time of first registration;

• the date and time of the last time the user changed their personal information in the app;

• any advertising identifiers;

• the date and time of the first opening of the app;

• the date and time of the last opening of the app;

• the date and time the app was uninstalled;

• the mobile operator used by the user;

• the number of times the app has been installed.

In general, any activity in the app is recorded and stored:

• date and time when the user performed an activity in the app;

• the object or area the user clicks on;

• the textual content typed by the user;

• the user's geographic location while performing each activity;

• the last known geographic location of the user.

Whenever a trip is planned, its activities are stored:

• the date and time when a planning is carried out;

• the planning options given and, if any, not accepted;

• the start and arrival location of each trip;

• the origin and destination entered by the user;

• the trip options chosen by the user;

• the time required to generate the schedule;

• the geographic area in which the user is located during trip planning;

• the user's travel mode preferences (e.g., bus, motorboat, bicycle, train);

• the scheduled departure and arrival times;

• the number of interchanges for each trip;

• the distances traveled on foot;

• the average waiting times;

• the reasons for any unsuccessful planning;

• the distances between trip origins and destinations;

• the time spent traveling;

• the times associated with reservations made by the user;

• the cost of tickets purchased by the user.

The Glimble app can send the user a series of push notifications, of which the app stores certain elements:

• the text of the notifications the user receives from the app;

• whether or not the user has received the notification;

• whether or not the user clicked on the notification;

• how long it took before the user clicked on the notification;

• the time at which the notification was sent;

• the geographic area in which the user was located at the time the notification was sent;

• user profiling (why the user received the notification);

• the subject of the notification;

• the origin from which the notification was sent;

• the duration for which the notification remains valid for the user.