rapidmail
How to configure rapidmail 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 rapidmail in the Consenter Manager. On the website, rapidmail is used for newsletter sign-up forms; email open and click tracking is governed by the newsletter consent, not the cookie banner. This guide therefore 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. rapidmail sign-up forms on the website (rapidmail GmbH, Freiburg, Germany).
What the service does in this scope. rapidmail processes address data on behalf of the customer to send newsletters as a processor under a data processing agreement; processing takes place in Germany or another EU/EEA member state. Website operators must obtain newsletter consent and conclude the agreement.
Step 1 — Implement rapidmail
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Receive marketing offers |
| Sign-up form | Double opt-in; inform about email tracking in the consent text |
| Website cookies | None documented for the form; verify in the browser |
| Contract | Data processing agreement |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Entry needed | Optional — only to disclose form data processing | Website footprint limited to forms |
| Processing purposes | Receive marketing offers | Newsletter |
| Tracking method | No tracking | No website tracking in scope |
| Identifier | Direct identifier | Email address on sign-up |
| Data categories | User-provided data, direct identifier | Form data |
| Legal role of data recipient | Processor | — |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Until unsubscribe | — |
| Processing location | Germany / EU | ; 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