As part of its business, hubtobee collects personal data.
The data collected by hubtobee is collected and stored in accordance with the provisions of the Data Protection Act of 6 January 1978 in the version currently in force, as well as with the provisions of the General Data Protection Regulation (GDPR) .
hubtobee collects the surnames, first names, emails of the representatives and employees of its customers, with whom it is brought to work.
The processing of this data is necessary to provide the services mentioned on our website.
hubtobee also acts as a processor within the meaning of Article 4 of the GDPR as regards the collection of data relating to its customers’ employees.
The customer remains sole controller under the meaning of Article 4 of the GDPR, for the processing of personal data of its employees, as well as the processing performed for statistical purposes accessible from the platform set up by hubtobee.
The data is stored for the time necessary to provide the services offered by hubtobee.
The data is then stored for archiving purposes and processed solely for litigation purpose during the term of the legal prescription.
Each data subject has the right to access, modify, rectify, erase and, where applicable, a right of portability of his/her personal data, in accordance with the provisions of the French Data Protection Act Liberties of January 6, 1978 in its version currently in force, and in accordance with GDPR.
The right of access, modification, correction and deletion provided for in the preceding paragraph is exercised by contacting Customer Service at the following email address: email@example.com
When the request for access, modification, rectification or erasure is addressed to hubtobee acting as a processor, hubtobee shall apply the terms and conditions provided by its customer (controller), subject to their compliance with the applicable regulations and their prior notification.
In case of difficulty related to the management of your personal data, you have the right to lodge a complaint with the CNIL or with any competent supervisory authority.
There are two types of cookies: session cookies and persistent cookies. Session cookies are created in your browser when you visit a website. Once you leave the site, the session cookie is deleted.
Persistent cookie files remain in your browser’s subfolder and are reactivated once you visit the website that created this specific cookie. A persistent cookie remains in the browser subfolder for the duration defined in the cookie file.
In general, the validity period of a cookie is 13 months maximum.
Can I refuse to store cookies on my computer?
You do not have to accept the deposit of cookies on you device. However, we can not guarantee an identical user experience if you delete cookies.
How to set up and delete cookies?
The main issuers of cookies used by hubtobee are as follows.
|Name of the Cookie||Aim||Deactivation link||Consequence on the navigation on the site|
|Google Analytics||Navigation information: time spent, browser used, words entered to find the site, number of times you visited the site||See the information here (1)||None|
Google Agenda Add-On
Why does the add-on hubtobeeflex for Google Calendar needs access to some of your data as a Google user?
hubtobeeflex' add-on aims to assist people at looking for available meeting rooms.
In the search process in this add-on, you have to fill 3 elements : first the building in which you want to find a room, second a list of participants to the meeting, and third a timeslot. Then the add-on aggregates all the availabilities to provide you a list of possible meeting timeslots.
What king of data do we concretely use?
In order to provide this list of possible meeting timeslots, the add-on needs:
- to get the list of your Google domain building and rooms
- to be able to read on the rooms' calendar
- to be able to read on the meeting participants' calendar
We also use information about your Google account : your country, your language, and your timezone.
How do we use these data?
About the buildings, we only use their name and unique identifier. This is used to let the Google user selecting the building in which she/he wants to find the meeting rooms.
About the rooms, we only use their name, the floor in the building (if mentioned), and their unique identifier. This is used to display those rooms in the list of possible meeting timeslots at the end of the search.
About the rooms' and meeting participants' calendars, we only use the timeslots of the events found inside those calendars: we don't need more! This is used to aggregate the availabilities between the rooms and the participants.
About the rest (your country, your language, and your timezone), we only use the language. This is used for the add-on to adapt its displayed content translation.
What else does the add-on do?
hubtobeeflex' add-on for Google Calendar also aims to be bind with our complete hubtobeeflex' application.
In order to establish this connection between your Google Calendar domain and hubtobeeflex, the add-on needs to control the account on which the Google user is connected. We do control this via the following application: addon-googlecalendar.hubtobee.com.
Concretely, the add-on communicates with addon-googlecalendar.hubtobee.com to determine whether the Google user domain who is using our add-on will have access to all the features (from hubtobeeflex) or not.
How are your data saved?
We do not save any Google data.
The few data saved are those you filled on the application addon-googlecalendar.hubtobee.com.
How do you delete any data related to your account or your domain?
To delete them, you can just send an e-mail to firstname.lastname@example.org or email@example.com, by providing us your email and all the associated domains you want to delete.
06 50 24 24 92