Set up your bannerConfigure Your ToolsLive Chat and Messaging

Smartsupp

How to configure Smartsupp 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, Support marketing analytics

Overview

This guide explains how to implement different privacy configurations for the Smartsupp chat box 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 Smartsupp chat box (Smartsupp.com, s.r.o., Brno, Czech Republic). Smartsupp states that its data is stored only within the EU.

What the service does in this scope. ssupp.vid identifies visitors so that a conversation can be paired with the visitor on reload; ssupp.visits and its local-storage equivalent are marketing information that should not be stored without marketing consent. Cookie consent is enabled in Settings → Security and privacy → Cookie consent; when enabled, only necessary cookies are stored, and analytics and marketing cookies are stored only after smartsupp('analyticsConsent', true) / smartsupp('marketingConsent', true). Smartsupp is the processor under its DPA.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskCookie consent mode on; chat box after Consenter consent; analytics and marketing consent not passed.
Configuration B — Higher riskCookie consent mode on; analytics and marketing consent passed from Consenter; visitor recordings used.

⚠ Recommendation — chat box before consent. Smartsupp states that no consent is needed for basic Flow (formerly chatbots) only, and its consent mode still stores ssupp.vid before consent. Load the chat box after Consenter consent unless your DPO or independent counsel confirms ssupp.vid is strictly necessary.

Step 1 — Configure Smartsupp

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionUnlock additional website featuresUnlock additional website features; Support marketing analytics
2Cookie consent modeSettings → Security and privacy → Cookie consentOnOn
3Consent signalssmartsupp('analyticsConsent', …), smartsupp('marketingConsent', …)falseMapped from Consenter
4Visitor recordingsSmartsupp recordingsOffOn
5LoadingConsenter script blockingAfter consentAfter consent

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesUnlock additional website featuresUnlock additional website features, Support marketing analytics
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers
Data categoriesBrowsing and interaction data, Device identifiers, User-provided dataAs A, plus Device characteristics, Privacy choices, Users' profiles
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationGroup based (behaviour)
Maximum storage durationUntil deleted (persistent storage)Until deleted
Processing locationEUEU; check the DPA for the recordings sub-processor

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