The spirit of the FDVT is to be a privacy-preserving browser extension that wants to preserve the identity of the users installing it. We refer to this as No-Identification principle
At the same time the FDVT aims to provide users with an accurate estimation of the revenue they generate for Facebook out of their activity in this system. This requires to obtain some personal information from FDVT users without violating the no-identification principle.
The FDVT is a social tool that aims to create awareness among Internet Users of the actual value of their personal online information. The long-term goal is to create informed Internet Users that increase their demand of transparent online services that clearly reveal how they manage personal information and how they create value out of it.
The FDVT has been designed as a social tool that aims to create awareness in the society. Therefore, the FDVT can be installed at no cost.
The FDVT is being currently maintained using research funding coming from public and private sources. Therefore, in order to use the FDVT we request the user to grant us permission to store the information listed below and use it for research purposes. This is useful for two purposes. First, it will serve to advance science in the area of online advertising and try to reveal what are the practices of Facebook to deliver ads to their users. Second, we will be able to attract new research funding that help us to sustain the FDVT in the medium-term.
Therefore, for all the reasons exposed above we inform the user that the FDVT will collect and store in a database the following information that will be used for research purposes and eventually for commercial purposes:
1. An FDVT ID computed as the hash of the user Facebook ID:
- The hash operation creates a random and non-reversible random string. This operation is known as pseudonymization.
2. The parameters filled during the registration process:
- Location refers to the country where the user is living and it is compulsory because it is the only compulsory parameter that Facebook requests to configure an audience.
- Gender: Male or Female.
- Age + Birthday: We ask users to provide us their age. The reason we also need the birthday is because we need to update the age of the user every year in order to create an accurate audience including the actual age of the user.
- Relationship Status: Single, In a Relationship, Married and Engage.
3. Information related to all Facebook sessions of the FDVT user. In particular we store for each session:
- Pseudonymized Facebook account ID associated to ads.
- Initial and final timestamp of the session. This is used to compute the duration of the session.
- Auntonomous System from which the user has established the connection.
- Currency FB associates to your account.
- Number of newsfeed posts (different than ads) printed during the session but not content of them.
- Number of friends/pages/groups printed during the session but not content of them.
- Facebook economical estimations (min, median and max values) such as CPC, CPM and CPA.
- Facebook Ad Id for all the ads displayed in the session. This is a unique ID Facebook assigns to each ad.
- URLs associated to each ad displayed during the session.
- Timestamp for each ad displayed during the session.
- Location of each ad displayed during the session. The location could be either the newsfeed or the right side of the wall.
- Timestamp of each ad click happening during the session.
- Pseudonymized IP address from which the user has established the connection with the central server.
- AS IP from which the user has established the connection with the central server.
- Pseudonymized IP city from which the user has established the connection with the central server.
- IP country from which the user has established the connection with the central server.
- IP region from which the user has established the connection with the central server.
- IP timezone from which the user has established the connection with the central server.
- Pseudonymized IP zip code from which the user has established the connection with the central server.
- Preferences ID associated to the user account.
- Timestamp of creation and delete of preferences.
- Name, topic, type and description of user preferences.