searchHub
How to configure searchHub 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 reflect searchHub's searchCollector in the Consenter Manager. searchHub does not publish configurable privacy settings, so this guide uses a single fixed-behaviour table.
- Implement the service as described below.
- Map the implementation in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.
At a glance
Scope. searchHub's searchCollector, the tracking component for on-site search journeys.
What the service does in this scope. searchCollector captures anonymised customer search journeys to power the searchHub platform. According to the provider, the tracking focuses on anonymised search processes and needs no personal data.
⚠ Research gap. searchHub does not publish which browser storage or identifiers searchCollector uses. "Anonymised" processing can still involve device access under § 25 TDDDG. Load searchCollector after Consenter consent and inspect it in the browser before finalising the mapping.
Step 1 — Implement searchHub
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Improve the service (search optimisation) |
| Tracking | searchCollector |
| Loading | After Consenter consent (see ⚠) |
| Contract | DPA with searchHub |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Improve the service | — |
| Tracking method | First party tracking (single session) | Search journeys; verify |
| Identifier | No identifier | Stated as anonymised; verify |
| Data categories | Browsing and interaction data, Aggregated site statistics | Search journeys |
| Legal role of data recipient | Processor | Provider on behalf of the shop |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Not documented | — |
| Processing location | Per DPA | Check for US sub-processors |
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