Set up your bannerConfigure Your ToolsMonitoring and Performance

BugSnag (Insight Hub)

How to configure BugSnag (Insight Hub) at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Improve the service

Overview

This guide explains how to implement different privacy configurations for the BugSnag JavaScript notifier (now SmartBear Insight Hub) 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. BugSnag browser JavaScript error monitoring.

What the service does in this scope. By default BugSnag records the user's IP address as the user ID; collectUserIp prevents this. It generates an anonymous device ID, which can be prevented via generateAnonymousId. User agent and locale are also captured and can be modified in a callback.

Configurations included.

ConfigurationSummary
Configuration A — Lower riskcollectUserIp: false, generateAnonymousId: false.
Configuration B — Higher risk (default configuration)IP address and anonymous device ID collected.

⚠ Recommendation. Whether error monitoring in A can run without consent is a legal assessment. Have your DPO confirm the legal basis before running A without a consent entry.

Step 1 — Configure BugSnag

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Higher risk (default configuration)
1Processing purposesOperator decisionImprove the serviceImprove the service
2Client IPcollectUserIpfalsetrue
3Device IDgenerateAnonymousIdfalsetrue

Step 2 — Map the configuration in the Consenter Manager

Processing location. SmartBear is a US enterprise; list the United States.

Consenter Manager fieldConfiguration A — Lower riskConfiguration B — Higher risk (default configuration)
Entry neededPer DPO assessment (⚠)Yes
Processing purposesImprove the serviceImprove the service
Tracking methodNo trackingFirst party tracking (cross-session)
IdentifierNo identifierDevice identifiers, IP address
Data categoriesDevice characteristicsDevice characteristics, Device identifiers, IP address
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage durationPer BugSnag retentionPer BugSnag retention
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