Intercom
How to configure Intercom 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, Receive marketing offers
Overview
This guide explains how to implement different privacy configurations for the Intercom Messenger 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. The Intercom Messenger (including Fin) on the website. Intercom, Inc. is a US company.
What the service does in this scope. The Messenger sets intercom-id-[app_id] (anonymous visitor identifier, 9 months), intercom-session-[app_id] (1 week) and intercom-device-id-[app_id] (270 days, refreshed on each ping). The cookies are unique to the customer's domain and cannot be read by Intercom on other sites. Intercom documents booting the Messenger with disabled: true and calling Intercom('boot', { disabled: false }) once consent is given. Intercom offers EU data hosting in Dublin; app.eu.intercom.com indicates EU hosting.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Messenger for anonymous visitors after consent; EU data hosting. |
| Configuration B — Higher risk | Messenger with identified users (user ID, email via boot), outbound messages and product tours; US hosting. |
No configuration without prior consent. The 9-month visitor cookie is set regardless of whether the visitor interacts with the Messenger.
Step 1 — Configure Intercom
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Unlock additional website features | Unlock additional website features; Receive marketing offers |
| 2 | Consent handling | intercomSettings.disabled / Intercom('boot', …) | Boot after Consenter consent | Boot after Consenter consent |
| 3 | User identification | boot with user_id / email | Not passed | Passed |
| 4 | Data hosting | Workspace region | EU (Dublin) | US |
| 5 | Outbound messages | Intercom Outbound | Off | On |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Intercom is a US enterprise subject to the US CLOUD Act; list the United States in all configurations.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Unlock additional website features | Unlock additional website features, Receive marketing offers |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers, Authentication-derived identifiers, Direct identifier |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, IP address, User-provided data | As A, plus Authentication-derived identifiers, direct identifier, Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | Profile based |
| Maximum storage duration | 9 months | 9 months |
| Processing location | EU; 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