In this section, you can configure how the collection of customer consent refects into the related data processing activities. Using the settings in this page you can define what are the minimum opt-ins to be collected from a customer in order to perform certain data processing activities.
We defined two main categories of Data Processing that you can control:
- Processing of Personal Data (both in Compass and Splash)
- Profiling (available only in Compass)
Processing of Personal Data refers to the collection and storage of certain data provided directly by the customer (zero-party data) as part of the registration process, or other metadata collected directly from his activities (for example location where he sign-up form, type of device, etc..).
If, according to the settings, there are not all the required consents to perform this processing, the system automatically deletes most of the relevant personal data collected during the interaction with the guest WiFi (data minimization).
The only personal data that remain registered in the system is the MAC address of the device used by the customer to register. This data is collected leveraging the legal ground of legitimate interest, with the purpose of monitoring over time the amount of traffic and duration of all connections in order to allow you to identify abuses of the service in contrast with fair usage policies. For this purpose, the system keeps the connection logs and run aggregated analytics of all the connections to make it easier to identify location and hotspot where these abuses occur.
The Profiling processing activity has been defined as a collection of operations aims to profile the customer with attributes that allow, eventually, to personalize his experience. In particular, we include in the Profiling processing activity the following processes:
- Detection of customer in-store interactions using passive WiFi tracking technology. This activity relies on the passive collection and further classification of the WiFi probing signals broadcasted by all WiFi devices independently form their connection status. The system collects all these signals and processes them using sophisticated algorithms to identify meaningful interactions in the stores.
- Store Visits elaboration. By observing all the data related to the customer interactions in the store, the system identifies specific events called "Visits", that represent the event of a customer staying inside the store long enough to be considered a shopper instead of a walk-by visitor.
To extract the Visits, the system considers both on the in-store interactions collected with passive WiFi tracking technology (as described above) and the WiFi Connections. The history of the Visits is then reported in a timeline on the customer profile page.
- Elaboration of behavioral metrics. Based on the history of the Visits the system extrapolates statistical metrics that describe in summary how a customer interacts with the organization (for example date of the last visit, most visited store, average visit time, etc..)
If, according to the settings, there are not all the required consents to perform this processing, the system won't track the in-store interactions using the passive presence/location capabilities, won't process the Visit events and won't compute profiling attributes based on them. As a result, the customer profile page and its data won't contain the history of its Visits and some of the metrics and attributes will be empty.
Note that the WiFi Connection logs are collected and stored anyway, independently from any consent, for the purpose of service assurance based on the legal ground of legitimate interest. At this time, the zero-party data and first-party data provided directly by the customer during the sign-up process (for example gender and age) are not considered "profiling" data.
Using this feature you have the possibility to reflect the consent collected from your customer into actual rules of data processing, using the two categories defined above.
By default, the system saves and process certain personal data to ensure the proper functioning of the product. In particular, the system store all the WiFi Connection logs, with the MAC Address of the device that generated the record, with the purpose of generating aggregate network reports that allow you to monitor the usage of the network and possibly spot abuses and anomalies. Keep in mind that most likely this information is stored and processed anyway, independently form Cloud4wi, also on your WiFi network management system.
How to configure it
Note that for both processing activities, the condition is satisfied if ALL the listed opt-ins are accepted by the customer.
If you have multiple Login Profiles and you defined different custom opt-ins for each of them you can select all of them in this menu (for example if you defined an opt-in named Profiling_A used in Venue_A and another one named Profiling_B used in Venue_B). All the opt-ins not published to the customer during his registration won't be considered required (in the example above, customer registering in the Venue_A won't be required to have the Profiling_B opt-in)