Email Marketing & Newsletter
rapidmail
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by rapidmail GmbH · www.rapidmail.de
Compare with Mailchimp → Compare with Inxmail → Compare with CleverReach → Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
rapidmail is the newsletter tool of Positive Group Deutschland GmbH, Freiburg, and the judges' picture is even rather than sharp. It is strongest on sovereignty at 6 to 7 — a German contracting entity, a data processing agreement assuring server location Germany, an ISO 27001-certified datacenter, daily encrypted backups on German servers — on campaign and automation at 6 to 7, and on list data control, which sits at 6 with no spread, its recipient lists exporting as CSV or Excel with the double opt-in record included. It is weakest on integrations, a flat 4 for a documented surface of Shopware 6 and Plentymarkets, and on deliverability at 4 to 5: authentication is documented, and we found no public information on bounce suppression, complaint loops, dedicated IP or warm-up. No material disagreement was computed on any criterion; the 4-to-6 spreads on consent and proof and on pricing transparency come from the same facts weighted differently: a tracking pixel documented in every mailing, prices shown only at the 500-contact step.
Speaks for it
- Sovereignty scores 6 to 7 on a German contracting entity, a data processing agreement assuring server location Germany, an ISO 27001-certified German datacenter and daily encrypted backups on German servers
- Double opt-in is applied automatically, with IP address, date and time stored for both the signup and the confirmation and exportable per contact
- Recipient lists export as CSV or Excel with the double opt-in record included, and per-mailing opens, clicks, bounces and unsubscribes export from the statistics area
- Automations are genuinely multi-step — if/then branching, signup, activity and date triggers, unlimited mailings per workflow, over 250 templates and free test sends
- Authentication is documented in depth — DKIM, SPF as a CNAME, DMARC with its policy options explained, plus setup guides for five named webhosters
Held against it
- Integrations sit at a flat 4: the documented connections are a Shopware 6 plugin and Plentymarkets interfaces via SOAP and REST, and we found no public information on webhooks, rate limits, a sandbox or a named CRM integration
- Deliverability scores 4 to 5: we found no public information on bounce suppression, complaint-loop handling, dedicated IP options or warm-up, and the vendor states it can only check whether a DNS entry exists, not whether it is correctly configured
- A tracking pixel and tracking links are documented as present in every mailing, and we found no public information on switching tracking off per campaign or a pixel-free sending mode
- Prices are shown only at the 500-contact step — Essential 15,00 € / Monat, Performance 25,00 € / Monat, Unlimited 35,00 € / Monat — and we found no public information on prices above 500 contacts, send limits for the lower tiers, overage rates or VAT treatment
- We found no public information naming the datacenter operator or a complete subprocessor list, and the Google and HubSpot entries under standard contractual clauses concern the vendor's own website
Best for
- You need consent evidence that survives a complaint: automatic double opt-in with IP address, date and time recorded for both the signup and the confirmation, exportable per contact
- German data residency is a hard requirement: a German contracting entity, a data processing agreement assuring server location Germany, an ISO 27001-certified datacenter and daily encrypted German backups
- You run a shop on Shopware 6 or Plentymarkets and want multi-step newsletter automations with clean, exportable recipient lists
- You send occasionally and want to avoid a term: a Versand von 1 x 500 E-Mails at 20,00 € / Gesamt with no contract term is listed
Avoid if
- You need mailings without tracking — the captured privacy policy describes a tracking pixel and tracking links in every mailing, and we found no public information on switching them off
- You must budget a list above 500 contacts before signing — the captured pages show prices only at the 500-contact step
- Your stack needs CRM or event-driven connections — the documented integrations are Shopware 6 and Plentymarkets, and we found no public information on webhooks or rate limits
- You depend on documented deliverability operations — the captured documentation covers authentication setup, and we found no public information on bounce suppression, complaint loops, dedicated IP or warm-up
The scores
Campaigns & automation
Show reasoningHide reasoning
How this is scored
Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.
0 — One-off broadcasts from a fixed template; no segmentation and no automation of any kind.
3 — A drag-and-drop editor and simple list segmentation, but automation is a single welcome mail and there is no testing.
5 — Reusable templates, attribute and behaviour segmentation, multi-step automations on common triggers, and subject-line A/B testing.
8 — A visual journey builder with branching on behaviour and data, dynamic content per segment, send-time optimisation, and testing that reports significance rather than raw counts.
10 — Journeys treat the whole lifecycle: event-driven entry from other systems, branching on any attribute or event, holdout groups for measurement, and automations a marketer can read months later without a diagram.
The CRM Manager
The functions pages show a real journey tool: if/then branching, triggers on signup, recipient activity and date, unlimited steps, workflow templates and a visual overview — plus per-email automation statistics. What I cannot find is any A/B testing with significance reporting, dynamic content per segment or send-time optimisation, and segmentation leans on tags and signup-interest questions rather than behavioural filters, so it is a solid multi-step programme short of measured experimentation. 6 7
The Deliverability Engineer
There is a visual workflow builder with drag-and-drop editing, if/then branching, triggers on signup, recipient activity and date, unlimited steps per automation, free test sends before activation, and documented use-case templates. We found no public information on subject-line A/B testing, send-time optimisation or holdout groups, which keeps this short of the top band. 6 7 2
The Data Protection Officer
The visual workflows branch on if/then conditions, trigger on signup, recipient activity or a date, run an unlimited number of mails, and come with workflow templates, per-mail statistics and free test sends — a serious automation build. I found no public information on subject-line A/B testing, dynamic content per segment or send-time optimisation, which is what separates this from the top tier. 6 7 2
The Shop Owner
Automations are genuinely multi-step: sign-up, recipient-activity and date triggers, as many mailings per workflow as I like, if/then branching, a visual workflow view with templates, and free test sends before activation. But I found no public information on A/B testing, dynamic content or send-time optimisation, and nothing on event entry from a shop — no abandoned-cart or post-purchase journeys and no revenue attribution per campaign, which is what I'd actually buy this for. 6 7
The Integrator
The visual workflow builder with if/then branching, triggers on signup, recipient activity or date, and documented use cases from welcome mailings to reactivation of inactive contacts is a real automation engine, not a single welcome mail. I found no public information on subject-line A/B testing, dynamic content per segment or send-time optimisation, so it stops short of the higher rungs. 6 7 2
The Skeptic
A visual workflow with if/then branching, triggers on signup, recipient activity and date, unlimited mailings per automation, 250-plus templates and tagging are all documented — that clears the journey-builder bar, and per-tier automation counts are stated. We found no public information on subject-line or content A/B testing, send-time optimisation, dynamic content per segment or holdout measurement, which is what separates a competent automation tool from a complete one. 6 7 2
Deliverability infrastructure
Show reasoningHide reasoning
How this is scored
Whether the mail arrives — authentication, sending reputation, bounce and complaint handling — judged on what the vendor documents rather than the inbox rate it advertises.
0 — No documentation of authentication or bounce handling; deliverability appears only as a marketing number.
3 — SPF and DKIM setup documented, but no DMARC guidance, no stated bounce policy and shared sending only.
5 — SPF, DKIM and DMARC documented with a custom sending domain, automatic hard-bounce suppression, and complaint-loop handling stated.
8 — The above plus dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, and published guidance on list hygiene.
10 — Deliverability is operated as a service: reputation monitoring surfaced to the customer, per-domain and per-ISP diagnostics, enforced authentication before first send, and postmaster or blocklist handling the vendor documents doing on the customer's behalf.
The CRM Manager
DKIM, SPF and DMARC are documented in real depth — policy options explained, SPF set as a CNAME, advice for sends above 5,000 recipients, status indicators and timing expectations. I found no public information on hard-bounce suppression, complaint-loop handling, dedicated-IP options or inbox-placement testing, so the operational half of deliverability rests on the vendor's Zustellbarkeit claims rather than documented process. 2 8 9
The Deliverability Engineer
Authentication is documented properly: SPF via CNAME, DKIM for mailings and signup forms, and DMARC with policy guidance plus a status display and realistic verification timing — this is setup documentation, not a delivery-rate boast, so I count it. Beyond a list-quality review before accounts are activated and exportable bounce records, we found no public information on automatic hard-bounce suppression, complaint-loop handling, dedicated IP options with warm-up, or inbox-placement testing. 8 9 5 13 2
The Data Protection Officer
Authentication is documented unusually well — SPF, DKIM and DMARC each with setup guidance, status indicators and walk-throughs for named webhosters — and bounce and unsubscribe counts are exportable per mailing. I found no public information on a stated hard-bounce suppression policy, complaint-loop handling, dedicated IP options or warm-up, so I cannot move this above mid-table. 8 9 2 13
The Shop Owner
The authentication side is documented properly: DKIM and SPF (set as a CNAME to their record), DMARC with explained policy options, guides for five named webhosters, validation status indicators and a partner service to do the setup, plus account release only after a review of list quality. I found no public information on bounce suppression, complaint-loop handling, or dedicated-IP and warm-up options, so only the setup half of deliverability is documented. 8 9 5
The Integrator
Authentication is properly documented — DKIM, SPF as a CNAME, DMARC with its policy options explained, and per-webhoster setup guides — but that is where the documentation ends. I found no public information on automatic bounce suppression, complaint-loop handling, dedicated IP options or warm-up, and deliverability otherwise appears mainly as an advertised rate. 8 9 2 5
The Skeptic
Real authentication documentation exists — DKIM for mailings and forms, SPF set up as a CNAME, and DMARC policies explained with a recommendation above 5,000 recipients — rather than only the advertised "höchste Zustellbarkeitswerte", plus account activation gated on a list-quality review. We found no public information on a stated bounce-suppression policy, complaint-loop handling, dedicated IP options or warm-up, and the vendor itself states it can only check whether a DNS entry exists, not whether it is correctly configured. 9 8 2 5
Consent, proof & tracking limits
Show reasoningHide reasoning
How this is scored
How subscribers arrive and what the sender can prove afterwards: double opt-in, logged consent, unsubscribe handling, and whether open and click tracking can be limited or switched off.
0 — Single opt-in with no consent record; tracking is always on and cannot be disabled.
3 — Double opt-in available but not the default, and the consent record is a timestamp without the source, IP or the wording consented to.
5 — Double opt-in as the documented default with a stored consent record including source and timestamp, one-click unsubscribe, and tracking that can be turned off per campaign.
8 — Consent is reproducible as evidence: the confirmation mail and form wording versioned and retrievable per subscriber, unsubscribe honoured across lists, tracking off-by-default available, and retention rules for inactive subscribers.
10 — Built for the burden of proof: a per-subscriber consent history an authority would accept, documented handling of Art. 15 access and Art. 17 erasure requests, pixel-free and link-tracking-free sending as a supported mode, and preference-centre granularity rather than all-or-nothing.
The CRM Manager
Double opt-in is applied automatically, and the consent record is genuinely exportable — IP address, date and time for both the signup and the confirmation, plus current status. Tracking, however, is documented as always present (tracking pixel and tracking links for every mailing), and I found no public information on switching tracking off per campaign, a pixel-free mode, versioned form wording or preference-centre granularity. 4 5 10 11
The Deliverability Engineer
Double opt-in is applied automatically, the duty-of-proof requirement is addressed, and the consent record exports with IP address, date and time for both signup and confirmation — that is a usable evidence trail. Against that, the privacy policy describes a tracking pixel and tracking links in every mailing, and we found no public information on a mode to switch tracking off, on versioned consent wording, or on documented access and erasure-request handling. 10 5 11 4
The Data Protection Officer
Double opt-in is the documented default, and the exportable record — IP address, date and time for both the signup and the confirmation, plus current status — is exactly the kind of proof that survives a complaint. What holds it back is tracking: the captured pages present the tracking pixel and click-counting links as built into the mail, and I found no public information on switching tracking off per campaign, on a pixel-free sending mode, or on preference-centre granularity. 10 5 11 4
The Shop Owner
Double opt-in is applied automatically, and the proof is real: IP address, date and time are stored for both the sign-up and the confirmation, saved automatically with their sign-up forms and included in the list export; every mailing carries an unsubscribe link by default and contact deletion is documented. I found no public information on switching the tracking pixel or tracking links off, which the captured privacy policy describes as present in the mails. 5 10 11 4
The Integrator
Double opt-in is applied automatically and the proof is exportable per contact — IP address, date and time for both the signup and the confirmation — a consent record I could actually hand to a lawyer. The privacy policy describes a tracking pixel and tracking links in every mailing, though, and I found no public information on turning tracking off per campaign. 5 10 4 11
The Skeptic
Double opt-in is documented as automatically applied, and the consent record is unusually deep — IP address, date and time for both the signup and the confirmation, exportable per contact — which is close to evidence-grade. The captured privacy policy describes a tracking pixel and tracking links in every mailing, and we found no public information on turning tracking off per campaign, on versioned and retrievable form wording, or on unsubscribe effect across lists. 5 10 4 11
List ownership, import & exit
Show reasoningHide reasoning
How this is scored
Whether the list and its history remain the sender's: import with attributes intact, full export including engagement history, deletion that executes, and no metering that prices leaving out of reach.
0 — Export is addresses only; engagement history, segments and automations cannot leave.
3 — CSV import and export of subscriber fields, but engagement history and unsubscribe state are not exportable.
5 — Full subscriber export including custom attributes, subscription status and unsubscribe state, plus API access sufficient to sync elsewhere.
8 — Everything exportable in open formats — subscribers, engagement history, campaigns and templates — with documented deletion of a subscriber across all records, and no export throttling.
10 — Exit is a documented feature: full-fidelity export of the whole account, contractual data return, deletion that is evidenced rather than asserted, and migration tooling in both directions.
The CRM Manager
Recipient lists export as CSV or Excel with subscription status and the double-opt-in record, and per-mailing recipient activity — opens, clicks, bounces, unsubscribers — is exportable in selectable categories, so my engagement history can leave with the list; list duplicate, merge and restore-from-backup operations are documented too. I found no public information on exporting campaigns or templates, on a full-account export, or on deletion being evidenced rather than asserted; no export throttling is mentioned either way. 10 12 13 14
The Deliverability Engineer
Recipient lists export as CSV or Excel including the opt-in record, per-recipient activity — opens, clicks, bounces and unsubscribes — is exportable per mailing, an API manages recipients for syncing elsewhere, and list backups can be restored. We found no public information on exporting campaigns or templates, on import with attributes intact, or on deletion that is evidenced rather than stated as GDPR-compliant. 12 13 10 14 5
The Data Protection Officer
Subscribers export to CSV or Excel with the double-opt-in record included, opens, clicks, bounces and unsubscribes export per mailing, lists can be merged, duplicated, restored from backup and deleted, and GDPR-compliant contact deletion is a documented feature. I found no public information on exporting campaigns and templates, on a full-account export for leaving, or on migration tooling in both directions. 12 10 13 5
The Shop Owner
The list leaves when I want it to: recipient lists export as CSV or Excel with sign-up status and the double-opt-in data included, per-mailing recipient activity — opens, clicks, bounces, unsubscribes — exports in a few clicks, and deletion, backup and restore of lists are documented. I found no public information on importing a list with attributes intact, or on exporting campaigns and templates, so a full exit is not a documented feature. 12 13 10
The Integrator
Recipients export as CSV with the double opt-in proof included, per-mailing recipient activity — opens, clicks, bounces, unsubscribes — exports from the statistics view, and lists can be duplicated, merged and restored from backup. I found no public information on exporting campaigns and templates, on a documented whole-account exit, or on import with custom attributes intact. 12 13 10 5
The Skeptic
Recipient lists export as CSV or Excel with a documented path and retrievable files, per-mailing opens, clicks, bounces and unsubscribes export from the statistics area, backups are restorable, and the API covers recipient management. We found no public information on exporting campaigns and templates, and contact deletion is asserted as GDPR-compliant deletion without a documented process or evidence of execution. 12 13 5 14
Integrations & API
Show reasoningHide reasoning
How this is scored
The connection surface a newsletter lives on: shop and CRM systems, events in and out, webhooks, and an API somebody can build against without a partner agreement.
0 — No API and no named integrations; the list is maintained by CSV upload.
3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.
5 — Named integrations for common shop and CRM systems, a documented REST API with keys, and webhooks for the core subscriber events.
8 — Maintained bidirectional integrations with named systems including at least one major shop platform, event webhooks with retries, documented rate limits, and a sandbox.
10 — The tool is a component rather than a destination: transactional and marketing sending on one API, events flowing both directions, versioned API with a deprecation policy, and integrations the vendor maintains rather than lists.
The CRM Manager
There is a documented API with its own developer site that can send mailings and manage recipients, plus native Shopware 6 and plentymarkets connections — decent coverage of the German shop stack. But the captured pages name no CRM integration, and I found no public information on webhooks, rate limits or a sandbox, which is precisely the event surface I build lifecycle triggers on. 2 7 14 15
The Deliverability Engineer
There is a publicly documented API with a developer site that can send mailings and manage recipients — a write-capable surface, not a read-only one — plus native Plentymarkets and Shopware 6 connections. We found no public information on webhooks, documented rate limits, a sandbox, or CRM integrations beyond the two shop platforms. 14 15 2 3
The Data Protection Officer
There is a documented API for sending mailings and managing newsletter recipients, plus named shop connections to Shopware 6 and Plentymarkets over SOAP and REST. I found no public information on webhooks, documented rate limits, a sandbox or CRM systems beyond those, which keeps this below the level a connected stack needs. 14 15 2
The Shop Owner
There are two real shop connections — a Shopware 6 plugin and Plentymarkets interfaces via SOAP and REST — plus a documented developer API for sending mailings and managing newsletter recipients. I found no public information on webhooks, documented rate limits or a sandbox, and none on CRM connectors or order and cart events flowing in, which is what my shop would actually need. 14 15 2
The Integrator
There is a public developer documentation URL and an API that both sends mailings and manages recipients, plus a Shopware 6 plugin and a Plentymarkets interface — a write-capable surface rather than a read-only one. But I found no public information on webhooks, documented rate limits, a sandbox, a versioned API with a deprecation policy, or any named CRM integration, which is precisely the surface I need before wiring this into an existing stack. 14 15 2 3
The Skeptic
Two named shop integrations — Shopware 6 and Plentymarkets via SOAP and REST — plus an API that sends mailings and manages recipients, with a developer documentation site. We found no public information on webhooks, documented rate limits, a sandbox, or any named CRM integration, so the connection surface reads as shop-only. 14 15 2 3
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where subscriber data and behavioural tracking live, who the contracting entity is, and which subprocessors touch the send. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily.
0 — US vendor and contracting entity, US hosting, subprocessors unnamed; subscriber behaviour leaves the EU with no stated basis.
3 — EU hosting offered as an option or for storage only, while sending, tracking or support access remains non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — sending infrastructure, analytics, support tooling — are non-EU without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, complete subprocessor list published, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, sending and every subprocessor in the EU, certification published, and no transfer that needs a Schrems II argument to survive.
The CRM Manager
A German contracting entity in Freiburg, German hosting stated with an online-signable data processing agreement, an ISO 27001-certified datacenter and an external data protection partner — the operation reads sovereign on its face. But the datacenter operator goes unnamed, a complete subprocessor list for the send chain is not published, and the broadest all-data-in-Germany wording sits on the marketing page, while the vendor's own website runs Google, HubSpot and Mixpanel tooling — as a buyer who weights this heavily, I cannot verify the chain end to end from public pages. 3 4 5 11
The Deliverability Engineer
The contracting entity is a German GmbH in Freiburg, hosting is in a German datacentre assured by the data-processing agreement and backed by an ISO 27001 certificate, backups are daily, encrypted and stored in Germany, and an external German data-protection officer is named. The data-centre operator itself is not named, a complete subprocessor list is not published, and the vendor's own website runs Google and HubSpot under standard contractual clauses — non-EU processing named with a legal basis, but not a fully evidenced chain. 3 5 11 4
The Data Protection Officer
The contracting entity is German, the data-processing agreement is signed online and assures a Germany server location, the datacenter holds ISO 27001, daily backups are encrypted on German servers, and the pages state no third-country transfer — for the newsletter data itself, the where-question has a clean answer without a Schrems II argument. But the datacenter operator is not named, a complete subprocessor list is not published, and the vendor's own web pages show Google and a US-parented HubSpot processing under standard contractual clauses, so the picture is strong rather than airtight. 3 5 11 4
The Shop Owner
German legal entity in Freiburg, all data on servers in Germany in an ISO 27001 certified data centre, daily encrypted backups on German servers, a data-processing agreement to conclude online that assures the Germany server location, and an external data protection officer. Two things hold it back: the captured pages do not name the data-centre operator, and I found no complete subprocessor list for the sending chain. 3 5 11 4
The Integrator
The contracting entity is Positive Group Deutschland GmbH in Freiburg, the data processing agreement confirms server location Germany, and the vendor states no third-country transfer, backed by an ISO 27001 certified datacenter and daily encrypted backups on German servers. I found no public information on the datacenter operator's name or a complete subprocessor list, so the chain rests on the vendor's own statements rather than a verifiable register. 3 5 11 4
The Skeptic
The core is genuinely DACH: a German contracting entity in the commercial register, a German datacenter with ISO 27001, a data processing agreement available in the customer account that assures the server location Germany, and daily encrypted backups on German servers. The datacenter operator is not named and a complete subprocessor list is not published, and we found no public information on where the sending infrastructure or the authentication service partner Entri sit — the Google and HubSpot entries with standard contractual clauses concern the vendor's own website, not the sending chain. 3 5 11 9
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a sender can compute the real invoice for their list size and send volume — including overage, extra domains and automation limits — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A headline price per contact tier exists, but send limits, overage rates or the tier where automation begins are not stated.
5 — Contact-tier prices public with the billing period stated and send limits given, but at least one commonly needed capability sits in an unpriced tier or add-on.
8 — Every tier priced publicly with contact and volume limits, overage rates, feature boundaries and VAT treatment stated; only genuinely custom volume lacks a number.
10 — Complete price computability: a calculator producing the annual invoice for a given list size and send frequency, including overage, additional domains and dedicated IPs.
The CRM Manager
Three tiers are priced per month at 500 contacts with the feature boundaries spelled out — one, five or unlimited automations, sender addresses and recipient lists per plan — plus a pay-per-send option and a free start. I found no public information on overage rates, VAT treatment or prices for contact counts above 500, so the real invoice for a growing list is not computable from the captured pages alone. 2 3
The Deliverability Engineer
Three tiers are priced publicly at up to 500 contacts with the monthly period stated, per-tier limits on automations, lists, sender addresses and users are spelled out, and a pay-as-you-go option of 1 x 500 emails for a total of 20,00 € with no contract term is listed. We found no public information on overage rates, VAT treatment, or prices for contact volumes beyond 500, so the invoice for a bigger list is not computable from these pages alone. 2
The Data Protection Officer
Three tiers are priced publicly per month at up to 500 contacts with per-tier limits on automations, recipient lists, sender addresses and users stated, and a no-term option at 20,00 € per send of 1 x 500 E-Mails exists. I found no public information on send limits for the lower tiers, overage rates or VAT treatment, so the real invoice for a larger list is not computable from the captured pages alone. 2
The Shop Owner
Three tiers are public with the monthly period stated at up to 500 contacts — Essential 15,00 € / Monat, Performance 25,00 € / Monat, Unlimited 35,00 € / Monat — automation counts per tier are spelled out, and a pay-as-you-go Versand von 1 x 500 E-Mails costs 20,00 € / Gesamt. But only the 500-contact level is evidenced; I found no public information on send limits for the lower tiers, higher contact levels, overage rates or VAT treatment. 2
The Integrator
Three monthly tiers are public — "15,00 € / Monat bis zu 500 Kontakte" for Essential, "25,00 €" Performance, "35,00 €" Unlimited — plus a pay-as-you-go "20,00 € / Gesamt" send of 500 emails with no contract term, and the feature boundaries per tier such as automation counts and sender addresses are stated precisely. Only the 500-contact price point is shown, however, and I found no public information on send limits for the lower tiers, overage rates, VAT treatment or a price calculator. 2 3
The Skeptic
Three tiers are priced at the 500-contact step — "Essential 15,00 € / Monat bis zu 500 Kontakte", "Performance 25,00 € / Monat", "Unlimited 35,00 € / Monat" — with the tier boundaries for automations, recipient lists, sender addresses and users stated, and a no-term "20,00 € / Gesamt" send of 500 emails. The captured pages show prices only at that bottom rung, and we found no public information on higher contact tiers, send limits below Unlimited, overage rates or VAT treatment. 2
European sovereignty — proven facts
3 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in DE | 3/3 pts | 3 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | EU only ⚠ unverified | 3/3 pts | 4 Report an error |
| Subprocessors | EU only ⚠ unverified | 2/2 pts | 5 Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 15 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency. Die zitierte Aussage steht im Newsletter-Abschnitt der Datenschutzerklärung; die weitergehenden Formulierungen („Alle Daten werden auf Servern in Deutschland gespeichert“) stehen nur auf der Marketing-Seite, ohne dass ein DPA-Auszug oder Subprozessoren-Liste den Standort belegt.
- Weak sourcing — Subprocessors. Der Betreiber des Rechenzentrums wird nicht namentlich genannt und eine vollständige Subprozessoren-Liste ist in den Auszügen nicht enthalten.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 15 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 7 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.rapidmail.de Checked 15 Sep 2026 Details →
- 2 Pricing www.rapidmail.de Checked 15 Sep 2026 Details →
- 3 Imprint www.rapidmail.de Checked 15 Sep 2026 Details →
- 4 Privacy policy www.rapidmail.de Checked 15 Sep 2026 Details →
- 5 Security / trust page www.rapidmail.de Checked 30 Sep 2026 Details →
- 6 Campaigns & automation — found from sitemap help.rapidmail.de Checked 30 Sep 2026 Details →
- 7 Campaigns & automation — found from sitemap www.rapidmail.de Checked 30 Sep 2026 Details →
- 8 Deliverability infrastructure — found from sitemap www.rapidmail.de Checked 30 Sep 2026 Details →
- 9 Deliverability infrastructure — found from sitemap help.rapidmail.de Checked 30 Sep 2026 Details →
- 10 Consent, proof & tracking limits — found from sitemap help.rapidmail.de Checked 30 Sep 2026 Details →
- 11 Consent, proof & tracking limits — found from sitemap help.rapidmail.de Checked 30 Sep 2026 Details →
- 12 List ownership, import & exit — found from sitemap www.rapidmail.de Checked 30 Sep 2026 Details →
- 13 List ownership, import & exit — found from sitemap www.rapidmail.de Checked 30 Sep 2026 Details →
- 14 Integrations & API — found from sitemap www.rapidmail.de Checked 30 Sep 2026 Details →
- 15 Integrations & API — found from sitemap help.rapidmail.de Checked 30 Sep 2026 Details →