Set up your bannerConfigure Your ToolsMarketing Automation and CRM

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.

  1. Implement the service as described below.
  2. Map the implementation in the Consenter Manager.
  3. 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 areaFixed behaviour / required action
Processing purposesReceive marketing offers
Sign-up formDouble opt-in; inform about email tracking in the consent text
Website cookiesNone documented for the form; verify in the browser
ContractData processing agreement

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldValue to selectBasis and conditions
Entry neededOptional — only to disclose form data processingWebsite footprint limited to forms
Processing purposesReceive marketing offersNewsletter
Tracking methodNo trackingNo website tracking in scope
IdentifierDirect identifierEmail address on sign-up
Data categoriesUser-provided data, direct identifierForm data
Legal role of data recipientProcessor—
Personalisation modelNo personalisation—
Maximum storage durationUntil unsubscribe—
Processing locationGermany / 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

On this page