ProvenExpert
How to configure ProvenExpert 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
Overview
This guide explains how to implement different privacy configurations for ProvenExpert rating seals 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. ProvenExpert rating seals, widgets and Google rich snippets (Expert Systems AG, Berlin, Germany).
What the service does in this scope. ProvenExpert states that integrated features (rating seals, widgets, rich snippets) do not use cookies and do not store website visitors' data, and that users generally do not need a DPA. Seals are available in several formats; some (e.g. the landing-page widget) include script or link tags that make third-party requests. An integration can fetch seals via the ProvenExpert API and cache the images on your own server.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Seal fetched via API and served from your own server (image only). |
| Configuration B — Medium risk | ProvenExpert seal/widget code loaded directly from ProvenExpert. |
⚠ Recommendation — Configuration B without consent. ProvenExpert sets no cookies, but loading the seal from its servers transmits the visitor's IP address. Have your DPO decide whether this can run without consent; otherwise use A or load B after Consenter consent.
Step 1 — Configure ProvenExpert
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | — | Unlock additional website features |
| 2 | Seal delivery | ProvenExpert API / widget code | API, cached locally | Widget code (Reputations-Boost > Bewertungssiegel) |
| 3 | Loading | Consenter (see ⚠) | — | Per DPO decision |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk |
|---|---|---|
| Entry needed | No | Yes |
| Processing purposes | — | Unlock additional website features |
| Tracking method | No tracking | No tracking |
| Identifier | No identifier | IP address |
| Data categories | — | IP address, Device characteristics |
| Legal role of data recipient | Self-hosted | Individual Controller |
| Personalisation model | — | No personalisation |
| Maximum storage duration | — | No visitor data stored |
| Processing location | Your server | Germany (German company; no CLOUD Act flag) |
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