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.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- 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.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | collectUserIp: 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 area | Where to configure it | Configuration A — Lower risk | Configuration B — Higher risk (default configuration) |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service |
| 2 | Client IP | collectUserIp | false | true |
| 3 | Device ID | generateAnonymousId | false | true |
Step 2 — Map the configuration in the Consenter Manager
Processing location. SmartBear is a US enterprise; list the United States.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Higher risk (default configuration) |
|---|---|---|
| Entry needed | Per DPO assessment (⚠) | Yes |
| Processing purposes | Improve the service | Improve the service |
| Tracking method | No tracking | First party tracking (cross-session) |
| Identifier | No identifier | Device identifiers, IP address |
| Data categories | Device characteristics | Device characteristics, Device identifiers, IP address |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Per BugSnag retention | Per BugSnag retention |
| Processing location | United States | United 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