PushPanda
How to configure PushPanda at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Receive marketing offers
Overview
This guide explains how to reflect PushPanda in the Consenter Manager. PushPanda does not document configurable privacy options, 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. PushPanda web push notifications (Austrian provider).
What the service does in this scope. PushPanda states that web push notifications do not require cookie technology but store two endpoints, that it does not store personal data and that data is managed on servers in Germany. Interests and segments of visitors can be stored, and subscribers can be connected to customer data via the REST API.
⚠ Recommendation — "no personal data" claim. A push subscription endpoint is a device-specific identifier, and the subscription is stored in the browser. Treat the endpoint as a device identifier and load PushPanda only after consent unless your DPO or independent counsel confirms otherwise.
Step 1 — Implement PushPanda
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Receive marketing offers |
| Loading | Consenter script blocking until consent; then browser permission prompt |
| Segments / interests | Store only if disclosed |
| CRM connection | Via REST API only if disclosed |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Receive marketing offers | Push marketing |
| Tracking method | First party tracking (cross-session) | Stored push subscription |
| Identifier | Device identifiers | Push endpoint |
| Data categories | Device identifiers, Browsing and interaction data | Subscription and interests |
| Legal role of data recipient | Processor | Provider on behalf of the operator |
| Personalisation model | Group based (properties) | Interests and segments; "Profile based" if connected to customer data |
| Maximum storage duration | For the duration of the subscription | — |
| Processing location | 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