Manage Consent in the Privacy Center

The Fides Privacy Center provides configurable consent settings for regulatory compliance, allowing users to access and edit their data use preferences.

To learn more about configuring your Privacy Center for DSR enforcement, see the DSR automation guide.

Configuration#

The Fides Privacy Center's text and actions are managed by a config.json file, which should be located in your project’s /clients/app/config directory. More information on configuration options can be found in the Privacy Center guide.

{
  "title": "Take control of your data",
  "description": "When you use our services, you’re trusting us with your information. We understand this is a big responsibility and work hard to protect your information and put you in control.",
  "description_subtext": [],
  "server_url_development": "http://localhost:8080/api/v1",
  "server_url_production": "https://<$YOUR_SERVER_URL>/api/v1",
  "logo_path": "/logo.svg",
  "actions": [
    {
      "policy_key": "default_access_policy",
      "icon_path": "/download.svg",
      "title": "Access your data",
      "description": "We will email you a report of the data related to your account.",
      "identity_inputs": {
        "name": "optional",
        "email": "required",
        "phone": "optional"
      }
    },
    {
      "policy_key": "default_erasure_policy",
      "icon_path": "/delete.svg",
      "title": "Erase your data",
      "description": "We will delete all of your account data. This action cannot be undone.",
      "identity_inputs": {
        "name": "optional",
        "email": "required",
        "phone": "optional"
      }
    }
  ],
  "includeConsent": true,
  "consent": {
    "button": {
      "title": "Manage your consent",
      "description": "Manage your consent preferences",
      "description_subtext": [
        "In order to opt-out of certain consent preferences, we may need to identify your account via your email address. This is optional."
      ],
      "icon_path": "/consent.svg",
      "identity_inputs": {
        "email": "optional"
      }
    },
    "page": {
      "title": "Manage your consent",
      "description": "Manage your consent preferences, including the option to select 'Do Not Sell or Share My Personal Information'.",
      "description_subtext": [
        "When you use our services, you're trusting us with your information. We understand this is a big responsibility and work hard to protect your information and put you in control."
      ],
      "policy_key": "default_consent_policy",
      "consentOptions": [
        {
          "fidesDataUseKey": "marketing.advertising",
          "name": "Data Sales and Sharing",
          "description": "We may use some of your personal information for behavioral advertising purposes, which may be interpreted as 'Data Sales' or 'Data Sharing' under regulations such as CCPA, CPRA, VCDPA, etc.",
          "url": "https://example.com/privacy#data-sales",
          "default": {
            "value": true,
            "globalPrivacyControl": false
          },
          "highlight": false,
          "cookieKeys": ["data_sales_and_sharing"],
          "executable": false
        }
    }
  }
}

Actions#

To learn more about configuring your Privacy Center for DSR enforcement, see the DSR automation guide.

Each action object supports the following:

Consent#

To provide compliance with local and internal regulations, you may define a series of data uses in your Privacy Center configuration. The consent object of your config.json file contains a list of consentOptions which represent the data uses (e.g. Data Sales, Data Sharing) that you would like to let your users opt in or out of.

The consent object supports the following:

The consent.button object is identical to other actions and supports the following:

The consent.page object can be configured with the desired text and consent options:

Each consent.page.consentOptions object supports:

Server-side Consent Enforcement#

Most consent solutions generally focus on user consent in the browser by suppressing third-party cookies. Along with browser consent enforcement, Fides supports server-side enforcement of user consent. Fides communicates the user's consent to third-party vendors via API calls or email. This type of consent propagation can be considered more comprehensive and enduring.

How to configure Server-side consent#

When configuring consent options in the privacy center, you need to mark the executable tag as true for one of the consent options. When users change their preference (opt-in, opt-out) for the consent option marked as executable, all the SaaS connections with consent as an option are triggered to make consent requests. Connections internally will make API calls or email third-party vendors to notify user's preference changes.

"consent": {
    "cookieName": "fides_consent",
    "consentOptions": [
      {
        "fidesDataUseKey": "advertising",
        "name": "Advertising / Data Sharing",
        "description": "We may use some of your personal information for advertising performance analysis and audience modeling for ongoing advertising which may be interpreted as 'Data Sharing' under some regulations.",
        "url": "https://example.com/privacy#advertising",
        "default": true,
        "highlight": false,
        "cookieKeys": ["data_sales_and_sharing"],
        "executable": true
      },
    ]
  }

Ethyca recently launched three new SaaS connectors to propagate user's consent to third-party vendors. After setting the executable flag to true for a consent option, please follow the configuration guide to set up the connectors.

1. Wunderkind Consent Connector
2. Universal Analytics Consent Connector
3. Sovrn Consent Connector