Set up your bannerConfigure Your ToolsSocial Media and Sharing

Disqus

How to configure Disqus at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features, Customise online ads

Overview

This guide explains how to implement different privacy configurations for the Disqus comment widget and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. The Disqus comment embed (Disqus Inc. / Big Heads Labs Inc., San Francisco, US).

What the service does in this scope. The Norwegian DPA found that Disqus collected data through cookies placed on visitors' devices and passed it to third-party advertising partners and its parent company, and announced a fine. Publishers can disable data tracking for their forum via the Tracking setting under Settings > Advanced; users can opt out on the Data Sharing Settings page. Ads within and below comments can be switched off under Settings > Ads; removing ads entirely requires a paid plan.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskTracking disabled in Settings > Advanced; ads off (paid plan); widget after Consenter consent.
Configuration B — Higher risk (default configuration)Default tracking and ads; widget after consent.

Step 1 — Configure Disqus

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk (default configuration)
1Processing purposesOperator decisionUnlock additional website featuresUnlock additional website features; Customise online ads
2TrackingSettings > Advanced > TrackingDisabledEnabled
3AdsSettings > AdsOff (paid plan)On
4LoadingConsenter script blocking / click-to-loadAfter consentAfter consent

Step 2 — Map the configuration in the Consenter Manager

Processing location. Disqus is a US enterprise subject to the US CLOUD Act; list the United States.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk (default configuration)
Processing purposesUnlock additional website featuresUnlock additional website features, Customise online ads
Tracking methodThird party tracking (crosssession, cross-website)Third party tracking (crosssession, cross-website)
IdentifierDevice identifiers, Authentication-derived identifiersDevice identifiers, Authentication-derived identifiers
Data categoriesBrowsing and interaction data, Device identifiers, IP address, User-provided data, Authentication-derived identifiersAs A, plus Users' profiles
Legal role of data recipientJoint ControllerJoint Controller; ad partners as Individual Controller
Personalisation modelNo personalisationProfile based
Maximum storage durationPer Disqus cookie policyPer Disqus cookie policy
Processing locationUnited StatesUnited States

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page