Skip to content
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Cannot retrieve contributors at this time

Privacy Badger enterprise deployment and configuration

System administrators can configure Privacy Badger on managed devices by setting up an enterprise policy.

You can find the full list of available settings in Privacy Badger's managed storage schema. Please let us know if you'd like to set something that isn't yet supported.

⚠️ Note that Privacy Badger currently reads and applies settings from managed storage on startup. To see your policy take effect on a managed device, first restart that device's browser. ⚠️


  1. Locate and if necessary create the managed storage manifests folder. Note that on Windows you need to create a registry key that points to the manifest's location.
  2. Copy the sample managed storage manifest for Firefox to this folder.

If your Privacy Badgers were installed from Privacy Badger's homepage (not from AMO):

  1. Rename the manifest to jid1-MnnxcxisBPnSXQ-eff@jetpack.json.
  2. Similarly, update the "name" property in the manifest to "jid1-MnnxcxisBPnSXQ-eff@jetpack".


Review Chromium's Documentation for Administrators documents, in particular Configuring Apps and Extensions by Policy.

See below for platform-specific tips.

Chrome on Windows

Policy entries live at the following registry path:


Use REG_DWORD for boolean values.

For example, to prevent the new user welcome page from launching upon Privacy Badger installation, create a showIntroPage entry set to a REG_DWORD value of 0.

Chrome on Linux

  1. Locate and if necessary create the managed policies folder for Chrome or Chromium.
  2. Copy the sample managed storage manifest for Chrome to this folder.
  3. Rename the manifest file to whatever you like (perhaps privacy-badger-admin-settings.json).
  4. Update the extension ID inside the manifest if you are not using official Privacy Badger releases from Chrome Web Store.

Chrome OS

The following example JSON policy disables Privacy Badger on This means Privacy Badger will be disabled when you visit any page.

This policy also prevents the new user welcome page from launching upon Privacy Badger installation.

    "disabledSites": {
        "Value": [
    "showIntroPage": {
        "Value": false


Same as Chrome on Windows but with a different registry path: