GPC Privacy Choice is a Chromium browser extension for researching the usability of privacy choices, especially, opting out from web tracking with Global Privacy Control (GPC). Our goal is to strike a balance between giving people sufficient options to make their privacy choices on one side and not overburdening them with too many or too complicated choices on the other. Enabling opting out by default for all websites proved to be a major roadblock for the adoption of Do Not Track (DNT). We take the learnings from DNT to improve GPC.
Once installed, our GPC Privacy Choice extension injects a privacy choice scheme, for example, a banner asking whether a user wants to enable GPC on the current website they visit. Data about the user's choices as well as details about the visited websites are then transmitted to a backend for analysis. The focus of this extension is on researching user interface design. However, the extension is fully functional and is sending header-based GPC signals. Thus, it serves as a working prototype for all privacy choice schemes we implement.
GPC Privacy Choice is maintained by Sebastian Zimmeck (@SebastianZimmeck) of the privacy-tech-lab.
It was developed by former privacy-tech-lab members Eliza Kuller (@ekuller), Chunyue Ma (@chunyuema), Isabella Tassone (@bella-tassone), Joe Champeau (@JoeChampeau), Kuba Alicki (@kalicki1), Daniel Knopf (@dknopf) and Abdallah Salia (@asalia-1).
1. Research Publications
2. Quick Developer Set-Up Guide
3. Privacy Choice Schemes
4. Data Collection
5. Full Developer Set-Up Guide to Implement GPC Privacy Choice
6. GPC Privacy Choice Architectural Overview
7. Files and Directories in this Repo
8. Third Party Libraries
9. Known Issues
10. Thank You!
Sebastian Zimmeck, Eliza Kuller, Chunyue Ma, Bella Tassone and Joe Champeau, Generalizable Active Privacy Choice: Designing a Graphical User Interface for Global Privacy Control, 24th Privacy Enhancing Technologies Symposium (PETS), Bristol, UK and Online Event, July 2024, BibTeX.
If you are using code or schemes from this repo, please cite the above paper.
You can find a complete list of our GPC research publications in the GPC OptMeowt repo.
In order to set up the environment for our extension, you should have Git installed.
-
Clone this repo:
git clone https://github.com/privacy-tech-lab/gpc-privacy-choice.git
-
In the
srcfolder, create aconfig.jsfile. If you not wish to set up a Firebase backend and only want to observe the frontend UI, you can copy the following information into the required config file and use the provided password (12345).export const PASSWORD = "12345"; export const firebaseConfig = { apiKey: "AIzaSyC08Bt3IUPn_6Sn469x-M1VwIb4KTXHYNo", authDomain: "gpc-example.firebaseapp.com", projectId: "gpc-example", storageBucket: "gpc-example.appspot.com", messagingSenderId: "403632222995", appId: "1:403632222995:web:6f72eb626ff4214ba060e6", };
Alternatively, if you wish to set up your own Firebase backend, we recommend looking at our Full Developer Set-Up Guide to Implement GPC Privacy Choice for more in-depth instructions.
-
To test the extension from a local repo, open the browser (Chrome, Brave, etc) and find the Manage Extension options from settings.
-
Turn on developer mode, and then click the
Load unpackedbutton. Select the foldergpc-privacy-choice/src. -
The extension should now be loaded and you should see the registration page pop up on the browser. We signed up participants for our usability study to test the different schemes via Prolific. In order to access the extension, supply a string formatted as a valid Prolific ID (you may use 5a123456xyz12u123v123456 for testing purposes). You also need to supply the password you created above. The registration process should start.
-
You may switch between schemes by manually setting it in line 741 of the
background.jsfile of the repository, where there is a list of what number corresponds to which scheme. See Privacy Choice Schemes for full descriptions of each scheme.
The GPC Privacy Choice extension includes nine schemes for enabling GPC signals on websites. Which scheme a user is assigned upon installation of the extension is intentionally set within the extension (see background.js).
Here are the main features of each scheme:
SB-Base is the base scheme. Users are presented a GPC Privacy Choice Banner on each new site they visit. Users can select to which domains they want to send GPC signals via a domain list on the Options Page.
Users are presented a GPC Privacy Choice Banner on each new site they visit. There is a Snooze button that, upon being selected, will prevent the banner from popping up on new sites for a few hours. Users can select to which domains they want to send GPC signals via a domain list on the Options Page.
In S1-Apply-All the GPC Privacy Choice Banner is presented on every new site, however, with an Apply-all option but no Snooze button. Users can select to which domains they want to send GPC signals via a domain list on the Options Page.
S2-Snooze+Apply-All is a combination of schemes 0 and 1. The GPC Privacy Choice Banner contains both the Apply-all option as well as the Snooze button. Users can select to which domains they want to send GPC signals via a domain list on the Options Page.
S3-Profile makes use of Privacy Profiles. Upon running the extension for the first time, users are prompted to choose a privacy profile. Their choice will then determine which sites will receive GPC signals. We use the disconnect-tracking-protection list to identify sites that should receive signals under a certain Privacy Profile. Users can select to which domains they want to send GPC signals via a domain list on the Options Page. The GPC values for domains on the domain list depend on in which category, if any, the domain is included in the disconnect-tracking-protection list as well as the choices a user makes on the domain list.
S4-Website makes use of Website Categories. Upon running the extension for the first time, users are prompted to select the categories that they would like to opt out from. We use the disconnect-tracking-protection list to identify sites that should receive signals under a certain Website Category. Users can select to which domains they want to send GPC signals via a domain list on the Options Page. The GPC values for domains on the domain list depend on in which category, if any, the domain is included in the disconnect-tracking-protection list as well as the choices a user makes on the domain list.
S5-Learn is a combination of schemes 1 and 3 and makes use of a simple technique to Learn Privacy Profiles. The user is presented with GPC Privacy Choice Banners on the first 10 websites they visit. Their choices are recorded and then used to select a Privacy Profile that suits the user best. No GPC Privacy Choice Banners are shown beyond the initial 10. Users that choose to enable GPC signals on 8 or more of the first 10 websites will be assigned a High-Sensitivity Privacy Profile. 4-7 enables (inclusive) will yield a Medium-Sensitivity Privacy Profile and 3 or fewer will give users a Low-Sensitivity Privacy Profile. Users can select to which domains they want to send GPC signals via a domain list on the Options Page. After the learning period is over a user may change their privacy profile on the Options Page.
S6-Universal is the simplest of all schemes. Upon running the extension for the first time, users are prompted as to whether they would like to send GPC signals to all websites they visit or not. They may change this preference on the Options Page. Users can select to which domains they want to send GPC signals via a domain list on the Options Page.
S7-Data makes use of Data Categories. Upon running the extension for the first time, users are prompted to select the types of data that they would not like to be shared with or sold to advertisers. Users should not rely on being opted out with S7-Data, as our extension is not a full implementation of the described functionality. Users can adjust their categories on the Options Page. In S7-Data users are not able to select individual domains to which they want to send GPC signals.
Although – to some extent – it depends on what you want, there are certain generalities when it comes to developing schemes. These are listed below.
- You'll need a registration page. You can either make use
registration.jsandregistration.html, which are used for the banner schemes, or you'll have to create your own files, which are necessary for category schemes. Seequestionnaire.jsandquestionnaire.htmlfor examples. - You'll have to create a corresponding Options Page. For this, you would be working in
domainlist-ui.js. - In order to set the browser extension to your scheme, you'll need to link it to a scheme number in
background.js. - You will also need to create a collection for your scheme in firebase. You can do this by working in
background.jsto change the collection name, and then developing your firebase security rules to accept that collection name.
NOTE: Please make sure that you have your users' consent to collect their data. If you are at a university, you may need IRB approval or a determination that your research is exempt.
The GPC Privacy Choice browser extension records how users interact with the sites they visit and which privacy choices they make in a Firestore database. In the database each user is represented by a unique ID (e.g., uDMVrtzy7lxf1sQqsmd8) and all their interactions are recorded under that ID. In addition, each user is requested to enter their unique Prolific ID upon installing the extension. The Prolific ID allows us to correlate the collected data with data from surveys about the use of our extension, which we administer via Prolific.
The browser extension collects the following data types from users, but data is never disclosed to any third-party. We never disclose any identifiable information.
Below is the list of data types that the browser extension generally collects from users of the GPC Privacy Choice extension:
General:
- Prolific ID
- Browser (e.g. Google Chrome)
- Whether you have HTTP cookies enabled (true or false)
- Whether you have Do Not Track enabled (true or false)
- Whether you have JavaScript enabled (true of false)
- Operating system language (e.g. en-US)
- Geographic location (e.g., your latitude/longitude coordinates)
- Whether you have Local Storage enabled in your browser (true or false)
- Operating system (e.g. Mac/iOS)
- Browser plugins (e.g. Chrome PDF Plugin)
- Browser's rendering engine (e.g., WebKit)
- Whether you have Session Storage enabled (true or false)
- Time zone
- UI scheme of your browser
- User agent of your browser
Browser history and Interaction with Our Extension:
- The website URLs you visit (e.g. https://www.cnbc.com/finance/)
- A timestamp when you visited a website
- The GPC status you selected for the current website you are on (true or false)
- Whether you have GPC globally enabled for all websites you visit
- Referer (i.e., the previous website you visited before coming to the current site)
- The TabIDs of the different tabs in your browser
- Whether you click on an ad on a website
- The website URL that your browser goes to when you click on an ad
- The website URLs of the ad networks integrated in the sites you visit
Here is how we categorize the data that the extension collects:
Browser History covers site-specific information that is collected for every site while a user is using the extension.
Ad Interactions cover a users interaction with an ad, specifically, the timing of the interaction, the source of the ad, and the domain that was initially navigated to after the Ad Interaction. Characteristics that cause an event to be flagged as an Ad Interaction are the following: if the event causes a new tab to open and if either the click that initialized the event occurred in a subframe or if the navigation involved the domain of a network identified in the disconnect-tracking-protection list, which we use to identify different types of websites. As it cannot be determined with certainty that such interaction is, in fact, an Ad Interaction, the reason that the interaction is recorded is noted.
Data on third party requests are stored in two collections: Third Party Requests (first 50) and Third Party Requests Summary. Instances of both collections are found under the Browser History documents that correspond to the website on which the documented requests occur.
Third Party Requests (first 50) documents hold specific data for the first 50 third party requests that occur upon visiting a site. This data includes the url that the request is sent from, the url's domain and network, any categories that the domain is listed under in the Disconnect List, the timestamp of the request, the request type, and the site to which the request is sent.
Third Party Requests Summary documents record how many requests are sent by each third party domain that sends requests during a visit to a certain site. This data is recorded in firebase once a user navigates away from a site or closes the tab on which the site was visited.
The Privacy Configuration Interaction History covers the privacy choices users make for schemes 3, 4, 5, 6 and 7. It covers the initial choice upon registration as well as later modifications, e.g., the initial Privacy Profile choice and its later modification for scheme 3.
Domain Interaction History covers any privacy choices made via the GPC Privacy Choice Banner on schemes 0, 1 or 2. It also covers changes made on the Options Page for all schemes that include it.
The Mute Interaction History covers schemes where the Snooze button is present, that is, schemes 0 and 2. It records when users choose to use the Snooze button.
NOTE: In order to create a Firebase project, you need 'Cloud Resource Manager project creation' to be enabled. This may be disabled if you are using an institutional account.
Follow the instructions to implement the GPC Privacy Choice browser extension for your own projects.
-
Clone this repo:
git clone https://github.com/privacy-tech-lab/gpc-privacy-choice.git
-
Create a Firebase Cloud Firestore project. Here are detailed instructions on how to set up a Firebase server for data collection. Before proceeding, make sure that you have created a Firebase account, a Cloud Firestore database and a web app within the database, and selected Test Mode as the starting mode for your Cloud Firestore Security Rules. Do not worry about installing the SDK; we have already added the required dependencies, client libraries, and initialized an instance of Cloud Firestore.
-
In the
srcfolder, create aconfig.jsfile and add in the following code. Be sure to update the fields based on the Firebase Cloud Firestore project you have set up. The information should be in Project Settings, under the General tab. Make sure you have your web app selected, then switch the SDK setup and configuration fromnpmtoconfigto see all the necessary information. You can pick any password you like. Upon installing the extension users will be asked for the password. If users do not enter a password or enter a wrong password, no data will be collected on Firebase. If you are running a study with multiple schemes one after another, it is recommended to change the password between schemes. Otherwise, data from study participants running a previous scheme may continue to be collected inadvertently.export const PASSWORD = "*******"; export const firebaseConfig = { apiKey: "********", authDomain: "******", projectId: "******", storageBucket: "******", messagingSenderId: "******", appId: "******", };
-
To test the extension from a local repo, open the browser (Chrome, Brave, etc) and find the Manage Extension options from settings. In Google Chrome, this can be done by clicking on the puzzle icon on the top right corner and then clicking
Manage Extensions. -
Turn on developer mode, and then click the
Load unpackedbutton. Select the foldergpc-privacy-choice/srcfrom your files. -
The extension should now be loaded and you should see the registration page popping up on the browser. In order to access the extension and start writing to your database, supply a string formatted as a valid Prolific ID (you may use 5a123456xyz12u123v123456 for testing purposes). You also need to supply the password you created above. The registration process should start.
-
Reviewer may switch between schemes by manually setting it in line 741 of the
background.jsfile of the repository, where there is a list of what number corresponds to which scheme. -
The best way to deploy GPC Privacy Choice, for example, to participants in a research study, is via the Chrome Web Store.
The extension makes use of Manifest V3.
Here are the most important files and directories:
assets: Image assets that can be used on the Chrome Web Store listing for the extension.scripts/writerules.py: This script is used to render the rulesets for appropriately attaching the GPC signal by privacy sensitivity (scheme 3) and third party category (scheme 4). It generates the files insrc/rulesetsand is not run in the browser or on the backend.src/firebase: Contains all the Firebase related configurations/scriptssrc/firebase/firebase.json: The Firebase (Firestore) configuration file.src/firebase/firestore.json.indexes: Contains the indexes used by the extension to sort and filter the Firestore database.- Background scripts for connecting to the Firestore database and adding data to it.
src/firebase/firebase-app.jssrc/firebase/firebase-auth.jssrc/firebase/firebase-firestore.js
src/firebase/firestore.rules: This file contains the rules for reading and writing to the Firestore database.
src/img: Contains all image resources.src/json:src/json/headers.json: Contains the JSON configuration files for the extension's Do Not Sell and Do Not Track headers.src/json/services.json: Contains the third party services and their categories used in some of the schemes.
src/libs-css: Contains all CSS libraries used in the browser extension.src/libs-js: Contains all JS libraries used in the browser extension.src/options: Contains the UI elements and scripts for the supplemental Options Page.src/registration: Contains all user registration scripts relevant for performing the research.- HTML files for different user schemes:
src/registration/oneQuestion.htmlsrc/registration/profile.htmlsrc/registration/questionnaire.htmlsrc/registration/registration.html
- JavaScript files for registering users:
src/registration/profile.jssrc/registration/questionnaire.jssrc/registration/registration.js
- HTML files for different user schemes:
src/rulesets: This file contains the rule sets for different categories of sites (e.g., advertising or analytics).src/background.js: This is the main service worker running the extension. It controls all of the major backend regarding whether the extension is on/off, sending Do Not Sell signals, etc.src/contentScript.js: This is the main supplemental script that passes data tobackground.jsand runs on every webpage loaded.src/editRules.js: Takes care of any changes to the rule sets that are responsible for adding GPC to domain requests.src/manifest.json: Provides the browser with metadata about the extension regarding its name, permissions, etc.src/updateSignal.js: Updates the status of whether a GPC signal is sent or not on any given site.src/util.js: Provides utility functions forbackground.js.
The GPC Privacy Choice extension uses the following third party libraries. We thank the developers.
The Dolphin logo is used under the CC-BY 4.0 license copyright Twitter, Inc.
- Only header-based GPC signals: Our extension is sending header-based GPC signals. However, we did not implement DOM-based GPC signals.
- The GPC choice banner UI may not display well on certain sites: Due to lack of control on the styling of injected HTML, the banner UI may vary on certain sites. We have tried our best to ensure UI consistency. Based on our testing during the development phase, the UI consistency is only not well maintained on a small set of sites, and the functionalities of the banner are not affected.
- In rare instances the extension may unexpectedly stop working: During our study we had rare incidents where users reported to us that the extension stopped working and we were no longer receiving data at the Firebase backend. We investigated this issue, however, could not replicate the behavior. It may be related to service workers in Manifest V3 or that a browser update or other software interaction causes the breakage.
- Incorrect recording or missing of a user clicking on an ad: Because of the ambiguity of Ad Interactions, our method of recording them is not fool-proof. While a vast majority of Ad Interaction data is correct, the extension may in individual cases incorrectly record or miss a user clicking on an ad. Ad Interaction is also based on a heuristic, especially, a click event occurring in a subframe, that may not always correctly identify an ad.
- Random assignment of schemes seems to perform poorly: The library for randomly assigning each user a scheme seems to perform poorly. To get a uniform distribution of schemes among users, it may be necessary to hardcode the scheme number and sign up the desired number of users for that scheme. This process can then be repeated for each scheme. In that case the Firebase password in the
config.jsshould be changed for each new scheme. Otherwise, users from a previous scheme may keep writing to Firebase as the Google Chrome Web Store pushes the updated extension with the new scheme to all current users. - GPC Current Site Status, i.e., whether GPC is enabled on a site or not does show a result on Firebase when the site is visited the first time. It shows "N/A." The reason is that at the moment the site is visited the first time, the user has not yet made a GPC choice. The GPC Current Site Status corresponds to the GPC status in the domain list.
- The domain list on Firebase updates on leaving a site: So, when a user visits site A and then site B, site A will show up in the domain list at the time the user opens site B.
- In rare instances browser updates may require re-registration: For already registered users, upon browser updates, the extension may display the user registration page again. No data may be collected on Firebase until the user re-registers. If the user re-registers, a second Firebase ID will be created and data will be collected from that moment on under that Firebase ID. Data for the same user under different Firebase IDs can be combined in the post-processing stages.
- Scheme 7 does not send GPC Signals. It is a front-end implementation only.
- Errors in the Chrome Manage Extensions tab If you have successfully installed the GPC Privacy Choice extension, you may have noticed that the extension has multiple documented errors on the Manage Extensions page. As far as we can tell, none of these errors have ever inhibited the functionality of our extension, and as such, we have not yet addressed them.
- Available only on Chromium browsers Although our extension is generally available on Chromium browsers (Chrome, Brave, etc.) it cannot be installed on other browsers, such as Firefox.
We would like to thank our supporters!
Major financial support provided by the Alfred P. Sloan Foundation.
Additional financial support provided by the National Science Foundation, Wesleyan University, and the Anil Fernando Endowment.
Conclusions reached or positions taken are our own and not necessarily those of our financial supporters, its trustees, officers, or staff.
