epoq
How to configure epoq at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Personalise the website, Receive personalised marketing offers
Overview
This guide explains how to implement different privacy configurations for epoq 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. epoq Search, Advise, Inspire and Connect (epoq internet services GmbH, Ettlingen, Germany).
What the service does in this scope. epoq uses between 0 and 5 cookies, depending on which services are in use, to display product suggestions in the shop or newsletter and to report on the success of the services. The cookies can only be read from the shop domain or a customer-specific subdomain at arc.epoq.de. epoq uses pseudonymised data, hosts in Germany and offers a data processing agreement on request.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | epoq Search only; after consent. |
| Configuration B — Higher risk | Recommendations (Advise, Inspire) in shop and newsletter (Connect); after consent. |
No configuration without prior consent. epoq sets cookies for recommendations and success reporting; no consent-free configuration is documented.
Step 1 — Configure epoq
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Personalise the website | Personalise the website; Receive personalised marketing offers |
| 2 | Services in use | epoq contract / integration | epoq Search | epoq Advise, Inspire, Connect |
| 3 | Loading | Consenter script blocking | After consent | After consent |
| 4 | Contract | Data processing agreement | Conclude | Conclude |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Germany; epoq is a German company, so no CLOUD Act flag is added unless the DPA lists US sub-processors.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Personalise the website | Personalise the website, Receive personalised marketing offers |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers |
| Data categories | Browsing and interaction data, Device identifiers | Browsing and interaction data, Device identifiers, e-commerce Activity, Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | Group based (behaviour) | Profile based |
| Maximum storage duration | Per cookie documentation | Per cookie documentation |
| Processing location | Germany | Germany |
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