Skip to main content

Data protection and privacy

Booking anonymization

Overview

With this feature you can set a date limit after which, the bookings are anonymized. This means that the system know which object was booked in what time frame, but the user associated with the booking will be permanently detached, so called anonymized. This is a good feature to minimize the personal data stored in Flexopus.


Configuration

To configure the anonymization settings, navigate in Flexopus as an administrator to Dashboard > Settings > Data Privacy Settings > Booking anonymization. Enable the option and decide how many days you want to set for the anonymization interval. The system will anonymize the bookings automatically every day for the past based on your settings.

Anonymization settings
💡
NOTE: Flexopus also collect log data about user activities like (reservations, edit and delete operations or failed log in attempts). The log data regarding the reservation will also be anonymized through this setting, so the reservations can not be tracked in this way. 

EU based customers

Many EU based Flexopus customers are enabling the anonymization settings to prevent user based statistics. The reason is that the work council want to prevent the collection of the office bookings link to the colleagues, since they could be used to track when and where the employees worked. This is usually not the purpose of the application, therefor the work council want to get the past bookings anonymized. The work councils define the purpose of the application to optimize the office utilization, for that the personal bookings do not need to be saved and analyzed in the past. Also, due to GDPR saving, personal related information need to be limited in time and only saved as long they are necessary to fulfill the purpose of the data collection. The purpose is defined to book a resource, which means the purpose is fulfilled after the target day and the data can be anonymized.

However, you may have another valid reason to store the data longer, or you are not under the GDPR jurisdiction, in this case you can store the bookings longer and user the user based statistics. Even if you are an EU based customer, you may have a valid reason to store the data longer.

Statistics

After the data is anonymized, Flexopus still can provide utilization statistics on the building, floor and object level, however we will not know which user was in the office in the past. Learn more about the statistics here:

Building statistics
Overview The building statistics are created without using personal related information. The calculations are made with anonymized reservation based on the data which object is booked and when. To calculate these statistics, it’s not relevant to know which user crated the reservation. This means that the data can be stored
Object heatmap & utilization
Overview The object heatmap and utilization statistics are created without using personal related information, similar to the building statistics. The calculations are made with anonymized reservation based on the data which object is booked and when. To calculate these statistics, it’s not relevant to know which user crated the reservation.
User statistics
Overview The user statistics are created using personal related information. The calculations are made with knowing which user booked what in the past. Please consult internally with your data processing officer to clarify, if you are allowed to collect the user statistics. 💡Note! Many EU based Flexopus customers are disabling