CleverReach
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by CleverReach GmbH & Co. KG · www.cleverreach.com
Compare with Mailchimp → Compare with rapidmail → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
CleverReach at a glance
- Vendor
- CleverReach GmbH & Co. KG
- Headquarters
- Incorporated in Germany source, captured 16 Nov 2026
- Data hosting
- Default not stated; pages mention Germany and the EU source, captured 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 16 Nov 2026
- Panel verdict
- The AI panel rates CleverReach 2.5/5, the mean of 6 judges. CleverReach, an email marketing tool from a German company in Rastede, scores 7 on consent and proof and on integrations — double opt-in with automatic dispute-evidence logging, more than 120 named integrations, webhooks documented down to retries, verification and encryption. how scores are made
- As of
- Vendor pages captured 19 Oct 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
CleverReach, an email marketing tool from a German company in Rastede, scores 7 on consent and proof and on integrations — double opt-in with automatic dispute-evidence logging, more than 120 named integrations, webhooks documented down to retries, verification and encryption. Campaign and automation sits at 6-7 and deliverability at 6-7, the deliverability engineer alone at 7 crediting bounce handling in hard numbers — hard bounces blocked a year, soft bounces a month with three retries — and DKIM required before sending. The clearest split is pricing transparency, 4-6: the skeptic's 6 credits the published free, Basic and Enterprise figures, while the judges at 4 cannot compute an invoice for a mid-sized list because no prices are public between 500 recipients and unlimited. Sovereignty splits 5-7: the shop owner's 7 accepts the German core, while the CRM manager's 5 finds the chain unproven end to end given US-hosted Zendesk support and consent-based third-country transfers. List data control sits at 4-5 with the export path unproven, and the data protection officer's scores register as 0 across the board.
Speaks for it
- Double opt-in is the standard and its confirmation is logged automatically, framed by the vendor as evidence in a consent dispute
- More than 120 named integrations across shop, CMS and CRM systems plus webhooks documented with at-least-once retries, a verification header and optional payload encryption
- Bounce handling is documented in hard numbers — hard bounces blocked for a year, soft bounces for a month with three delivery retries — and DKIM is required before sending
- A permanent free tier of 250 recipients and 1,000 emails per month, with no credit card required and monthly cancellation
- A German contracting entity with vendor-stated storage on servers in Germany and the EU, ISO 27001 certified data centres and a digitally signable data processing agreement
Held against it
- The captured pages give no prices for the tiers between 500 recipients and unlimited, so a mid-sized list's invoice cannot be computed
- We found no public information on exporting subscribers with their engagement history, leaving the exit path unproven
- Support requests are processed through Zendesk hosted in the USA, with third-country transfers resting on consent under Art. 49
- We found no public information on warm-up, complaint feedback loops or per-domain reputation reporting
- A/B analysis reports the variant with the higher open rate, and we found no public information on significance reporting or send-time optimisation
Best for
- You run an online shop on Shopify, Shopware or WooCommerce and want cart-abandonment mailings fed by real-time recipient sync
- You must be able to evidence newsletter consent in a dispute and want double opt-in logged automatically
- You want to start small on the permanent free tier of 250 recipients and 1,000 emails per month
- You integrate via API and webhooks and value documentation covering retries, verification and encryption
Avoid if
- You need to compute your invoice from public prices before buying — the captured pages give no figures between 500 recipients and unlimited
- You need a documented exit path for your subscriber data — we found no public information on export with engagement history
- Your compliance review rules out US-hosted processing of support requests — the privacy policy names Zendesk hosted in the USA
- You are a private individual rather than a business — offers are exclusively for businesses within the meaning of §14 BGB
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 3.5 of 5 |
| Deliverability infrastructure | 3 of 5 |
| Consent, proof & tracking limits | 3.5 of 5 |
| List ownership, import & exit | 2 of 5 |
| Integrations & API | 3.5 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 2 of 5 |
Campaigns & automation
panel disagrees
Show reasoningHide reasoning
How this is scored
Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.
0 — Not a campaign tool; mail cannot be composed and sent to a list from the product.
3 — Broadcasts to a list built in an editor with templates, with simple list or tag segmentation; automation and testing are basic or not described.
5 — A drag-and-drop editor with reusable templates, segmentation on subscriber fields or behaviour, automated sequences on common triggers (sign-up, date, click), and A/B testing of campaigns.
8 — A visual journey builder with branching on behaviour and data, dynamic content per segment, send-time optimisation, event triggers from shop or app data, 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
A drag-and-drop editor with responsive templates, segmentation on custom fields and interest tags, and automation triggered by sign-up, birthday, tags or customer behaviour cover a real lifecycle, with cart-abandonment mails and more than twenty automation templates on top. A/B testing exists for subject lines and content splits with a freely chosen distribution and a winner variant sent onward, but the analysis reports which variant achieved the higher open rate rather than significance, and we found no public information on branching journeys or send-time optimisation. 1 3 6 7 12
The Deliverability Engineer
Drag-and-drop editor with responsive templates, segmentation and tagging, visual automation with more than 20 ready-made tracks, and welcome, birthday, behaviour and tag triggers; shop events feed cart-abandonment mailings with real-time recipient sync. A/B testing covers subject lines in the editor and content splits at a freely chosen distribution, the winning variant sent automatically to the remaining recipients. We found no public information on send-time optimisation or on tests reporting statistical significance. 1 3 6 7 12
The Data Protection Officer
A drag-and-drop editor with responsive templates, segmentation, tagging and A/B testing of subject lines and content are all documented, and automations trigger on sign-up, birthday, tags and recipient behaviour in a visual editor with more than twenty ready-made tracks. We found no public information on send-time optimisation, holdout groups, or testing that reports statistical significance rather than open rates, so this sits between the solid mid-level and the advanced journey tooling. 1 3 6 7
The Shop Owner
For a shop like mine the revenue pieces are documented: drag-and-drop editor with responsive templates, segmentation on fields and tags, cart-abandonment mails, behaviour-triggered automations built in a visual drag-and-drop editor with over twenty ready-made tracks, and genuinely deep A/B testing of subject lines and content with a configurable split and winner resend. What keeps it below the top is what the pages do not show: send-time optimisation, significance-based test reporting, and dynamic per-segment content only claimed in general terms. 1 3 6 7
The Integrator
The drag-and-drop automation editor with prepared blocks, behaviour-based triggers and more than twenty automation templates is documented, and shop data reaches it through real-time recipient sync from shop, CMS and CRM systems, including cart-abandonment mailings. A/B testing covers subject lines directly in the editor and content splits via automation with a winner variant sent to the remaining recipients. I found no public information on send-time optimisation or on testing that reports significance rather than raw open rates, which keeps this below the top of the scale. 1 3 6 7
The Skeptic
A drag-and-drop editor with templates, tagging and field-based segmentation, and A/B tests on subject and content with a winner variant are all documented, plus drag-and-drop automation on sign-up, birthday, tag and behaviour triggers with twenty-plus prebuilt flows. The step up to the top level would need branching, send-time optimisation and significance reporting; the captured pages show the A/B analysis naming which subject line won on open rate, and no more. 2 3 6 7
Deliverability infrastructure
panel disagrees
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 — The product does not send mail itself; delivery runs through the customer's own mail server with no sending infrastructure provided.
3 — Sending through the vendor's infrastructure with SPF and DKIM set-up for the sender's domain documented; bounce handling and reputation measures are basic or not described.
5 — SPF, DKIM and DMARC guidance with an authenticated custom sending domain, automatic suppression of hard bounces and complaints, and help-centre guidance on deliverability and list hygiene.
8 — Dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, complaint feedback loops stated, and reputation reporting per sending domain.
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 is mandatory before sending, set up self-service with an automatically generated TXT record and a record check, alongside SPF and DMARC guidance, and soft and hard bounces are excluded automatically with differentiated block durations, three delivery retries, per-mailing bounce reporting and a deliverability dashboard. A dedicated IP appears only as an Enterprise extra on request, and we found no public information on warm-up, complaint feedback loops or per-domain reputation reporting. 2 8 9 12
The Deliverability Engineer
DKIM is mandatory before the first send, set up in the account with an automatically generated TXT record, a record check and selector support, and SPF and DMARC are named alongside it. Bounce discipline is documented in hard numbers — hard bounces blocked for a year after the first failed attempt, soft bounces for a month with three delivery retries and automatic re-activation — plus blocklists matched at import and send, a deliverability dashboard with optimisation tips, a pre-send spam-filter test and a dedicated IP on request in the Enterprise tier. I credit the documented infrastructure, not the advertised inbox-rate figure; on warm-up, complaint feedback loops and engagement-based sunsetting we found no public information. 2 8 9 11 12
The Data Protection Officer
DKIM is a precondition for sending, with automatic TXT-record creation, a record check, and SPF and DMARC named alongside it; bounce handling is documented in unusual detail — hard bounces blocked for a year after the first attempt, soft bounces for a month with three retries, per-mailing bounce rates in the report — plus a deliverability dashboard and a spam-filter test before send. We found no public information on warm-up processes, complaint feedback loops or per-domain reputation diagnostics, and the dedicated IP is only offered on request at the top plan. 2 3 8 9 12
The Shop Owner
DKIM is a documented requirement for sending, with the TXT record generated automatically, a record check and selector support, and bounces are handled in a documented multi-stage system — soft bounces blocked a month with three retries, hard bounces a year — plus a deliverability dashboard, a pre-send spam test and a dedicated IP on request at Enterprise. We found no public information on warm-up, inbox-placement testing, complaint feedback loops or per-domain reputation reporting, and SPF and DMARC appear only named alongside DKIM as important protocols. 2 8 9
The Integrator
DKIM is documented in depth — self-service setup, an automatically generated DNS TXT record, a record check, and DKIM as a prerequisite for sending, with SPF and DMARC named alongside — and bounce handling is staged and concrete: hard bounces blocked for a year after the first attempt, soft bounces blocked for a month with up to three retries and automatic reactivation, bounce rates per mailing, plus a deliverability dashboard and a pre-send design and spam test. I found no public information on complaint feedback loops, dedicated-IP warm-up or per-domain reputation reporting, so the documented level sits a notch above the middle. 2 8 9
The Skeptic
DKIM is documented as a precondition for sending, with an automatically generated TXT record and a record check, and bounce handling is genuinely multi-stage — soft bounces retried three times and blocked a month, hard bounces blocked a year, bounce rates shown per mailing, with a deliverability dashboard in reporting. A dedicated IP appears only as an on-request item in the top plan, and we found no public information on warm-up, complaint feedback loops, seed testing or engagement-based sunsetting. 2 8 9
Consent, proof & tracking limits
panel disagrees
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 — Not built for consent at all: the vendor describes the list as imported addresses, with no sign-up forms and no opt-in confirmation in the product.
3 — Sign-up forms, double opt-in available and an unsubscribe link in every mail; the consent record and tracking controls are basic or not described.
5 — Double opt-in documented with a consent record per subscriber (timestamp and source), one-click unsubscribe, and open or click tracking that can be switched off.
8 — Consent is reproducible as evidence: double opt-in as the default, the confirmation mail and form wording stored per subscriber with IP, unsubscribe honoured across lists, a preference centre, 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 the standard and is logged automatically so consent can be evidenced in a dispute, unsubscribe links sit in every template with immediate effect, three opt-out modes, an optional reason field and recipient self-service profile management, and reporting data can be anonymised on request. That is most of the way to reproducible consent; the captured pages do not show the consent record stored with IP, tracking switched off by default, or unsubscribe honoured across lists. 10 11 12 13
The Deliverability Engineer
Double opt-in is the standard and the successful confirmation is automatically logged so consent can be evidenced in a dispute; every template carries an unsubscribe link that takes effect immediately, with single, confirmed or double opt-out, an unsubscribe-reason field and the unsubscribe date shown in the recipient profile. Reporting can be anonymised on request, which disables recipient-based analysis, and self-service recipient profiles let people manage their own data and preferences. We found no public information on storing the confirmation mail and form wording per subscriber with IP, or on tracking being off by default. 10 11 13
The Data Protection Officer
Double opt-in is the standard and its success is automatically logged so the sender can prove the consent in a dispute; unsubscribe links sit in every template, take immediate effect, offer single, confirmed or double opt-out plus a reason field, and all unsubscriptions are documented with dates visible in the recipient profile. Reporting can be anonymised on request and recipients manage their own data and newsletter preferences, but we found no public information on whether the confirmation mail wording and IP are stored per subscriber, on tracking being off by default, or on a documented process for access and erasure requests. 5 10 11 12 13 5
The Shop Owner
Double opt-in is the documented standard for sign-up forms and the successful confirmation is logged automatically so I can prove the consent in a dispute — the wording a German authority would want to hear. Unsubscribe is immediate with clean documentation and three opt-out variants, recipients manage their own data and preferences in a profile centre, reporting can be anonymised on request, and deletion after a set period is offered. We found no public information on per-subscriber consent detail such as stored IP, or on pixel-free sending as a supported mode. 10 11 13 5
The Integrator
Double opt-in is the standard for sign-up forms and the vendor logs it automatically, explicitly framing the record as evidence for a consent dispute; unsubscriptions take immediate effect with single, confirmed and double opt-out modes, an optional reason field, documentation of every opt-out and the opt-out date on the recipient profile, and recipients manage their own data and preferences. Reporting can be anonymised on request, but I found no public information on consent records carrying IP addresses, on opt-outs honoured across lists, or on tracking switched off by default. 10 11 12 13
The Skeptic
Double opt-in is the documented standard and the successful confirmation is logged automatically so consent can be evidenced in a dispute; opt-out comes in single, confirmed and double variants with immediate effect and a reason field, and recipients self-manage their profile and newsletter preferences. Reporting can be anonymised on request, switching off recipient-based analysis, and deletion after a configurable period is offered — but we found no public information on stored confirmation wording and IP per subscriber, or on handling of access and erasure requests. 10 11 12 13
List ownership, import & exit
panel disagrees
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 — The vendor states that the list cannot be exported; subscriber data stays inside the product.
3 — CSV import and export of subscribers with their fields; engagement history, unsubscribe state and deletion are basic or not described.
5 — Import with field mapping, subscriber export including custom fields and subscription or unsubscribe status, deletion of a subscriber on request, and an API to read and write the list.
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
Import runs from CSV, Excel, text files or an FTP server with up to 45 custom fields per list, records can be edited or deleted at any time, account data is deleted within ten days of withdrawal, and a developer API sits on top. We found no public information on subscriber export, engagement-history export or export throttling, which leaves the exit path unproven rather than poor. 3 5 11 12
The Deliverability Engineer
Import runs from CSV, Excel, text files or an FTP server with up to 45 custom fields, records can be edited or deleted at any time, deleted or replaced recipient lists are backed up automatically, and a developer API is offered. We found no public information on exporting subscribers with their fields and engagement history, so what exit actually looks like stays an open question for a buyer. 11 12
The Data Protection Officer
Import is documented from CSV, Excel, text files and FTP with up to forty-five custom fields, records can be edited or deleted at any time, deleted or replaced lists are backed up automatically, and a developer API with webhooks can read and write the list. We found no public information on bulk export of subscribers with their engagement history in open formats, on export throttling, or on contractual data return at exit, which is what I want to see before entrusting a tool with named people. 5 6 11 12 13
The Shop Owner
Import is richly documented — CSV, Excel, text files or FTP, with up to 45 custom fields — and records can be edited or deleted at any time, deleted lists are automatically backed up, cancellation is monthly with no setup fee, and a documented REST API with webhooks lets me move data myself. We found no public information on exporting subscribers with their engagement history, so the exit story is inferred from the API rather than shown as a feature. 1 11 12 15
The Integrator
Import is documented from CSV, Excel, text files or an FTP server with up to forty-five custom fields, customers can edit or delete records at any time, deleted or replaced lists are backed up automatically, and a developer API exists. I found no public information on exporting subscribers with their engagement history or on exit in open formats — the part I weigh most when I have to unwind a stack — so the documented level stays below the middle. 3 11 12
The Skeptic
Import from CSV, Excel, text files or an FTP server with up to 45 custom fields, automatic backups when lists are deleted or replaced, and editing or deleting records at any time are documented, and a REST API is referenced. We found no public information on exporting subscribers or their engagement history out of the product, which leaves the exit path unproven. 11 12 13 15
Integrations & API
panel disagrees
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 — A closed stand-alone tool: the vendor offers neither an API nor integrations, and the list is maintained by hand or CSV.
3 — A handful of named integrations or embeddable forms, or a basic API; webhooks and API documentation are basic or not described.
5 — Named integrations for common shop and CRM systems, a documented REST API with keys, and webhooks or connector-platform triggers for 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
More than 120 named integrations across shop, CMS and CRM systems — including Shopify, Shopware, WooCommerce, HubSpot and Salesforce — with realtime recipient sync, Zapier and Make, a PHP SDK and an MCP server. Webhooks are documented seriously, with HTTPS POST in JSON, retries with at-least-once delivery, a verification header and optional payload encryption; we found no public information on rate limits, a sandbox, or two-way sync beyond recipient addresses. 3 12 14 15 15
The Deliverability Engineer
More than 120 named integrations span major shop platforms (Shopify, Shopware, WooCommerce), CRM systems (HubSpot, Salesforce, Microsoft Dynamics) and CMS systems, with real-time recipient sync from shop, CMS or CRM, plus Zapier and Make. Webhooks are documented with at-least-once retries, a five-second acknowledgement window, a verification header and optional payload encryption, alongside a PHP SDK and an MCP server. We found no public information on documented rate limits or a sandbox. 3 14 15 15
The Data Protection Officer
More than one hundred and twenty named integrations cover shops (Shopify, Shopware, WooCommerce), CRMs (Salesforce, HubSpot, Microsoft Dynamics) and CMS platforms, with real-time recipient synchronisation, Zapier and Make, a PHP SDK and an MCP server. Webhooks are properly engineered — HTTPS POST with JSON payloads, retries with at-least-once delivery, a call-token verification header and optional payload encryption — though we found no public information on documented rate limits or a sandbox. 3 12 14 15 15
The Shop Owner
This is where the tool earns its keep for a shop: over 120 integrations including Shopify, Shopware 6, WooCommerce and PrestaShop, with recipient addresses synced in real time from shop, CMS and CRM, plus Zapier and Make, a PHP SDK, an MCP server, and webhooks documented with retries, at-least-once delivery, a verification header, optional payload encryption and a full event list. We found no public information on documented rate limits or a sandbox for building against the API. 3 12 14 15 15
The Integrator
This is the surface I judge a stack on: more than 120 integrations with vendor-maintained pages across shop platforms (Shopify, Shopware, WooCommerce), CRM (HubSpot, Salesforce, Microsoft Dynamics) and CMS systems, real-time recipient sync from shop, CMS and CRM, and webhooks documented with HTTPS POST JSON payloads, retries with at-least-once delivery, call-token verification, encrypted fields and a five-second acknowledgement window, plus a PHP SDK and an MCP server. I found no public information on documented rate limits, a sandbox environment, or a versioning and deprecation policy for the API, which is what holds this below the highest level. 12 14 15 15
The Skeptic
More than 120 named integrations across shop, CMS and CRM — Shopify, Shopware, HubSpot, Salesforce among them — with realtime address sync, plus Zapier, Make, a PHP SDK and an MCP server. Webhooks are documented in real detail: HTTPS POST with a JSON payload, at-least-once delivery with retries, a five-second acknowledgement window, a verification header and optional payload encryption; we found no public information on rate limits or a sandbox. 3 12 14 15 15
European sovereignty
panel opinion
panel disagrees
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. Dimensions not proven either way are unknown, not non-European.
0 — Vendor, contracting entity and hosting shown to be outside the EU, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist and one European element is proven (an EU contracting entity or representative, or EU hosting as an option); the rest of the chain is not stated.
5 — An EU contracting entity and EU hosting stated, with a data processing agreement; sending, tracking or support providers are not all shown to be European or are named without a stated safeguard.
8 — EU or DACH hosting on named infrastructure, EU contracting entity, the subprocessor list published with locations including the sending infrastructure, 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 Rastede, an external data protection officer in Hamburg, a self-serve data processing agreement and vendor statements that data sits on servers in Germany and the EU give a European core. Support requests are processed through Zendesk hosted in the USA, third-country transfers rest on consent, and the captured pages name no infrastructure provider or sending infrastructure, so the chain is not proven end to end. 1 4 5 11 5
The Deliverability Engineer
A German contracting entity in Rastede with a published commercial register entry, a data processing agreement that can be signed digitally, a named German data protection officer, and vendor statements that all data is stored exclusively on servers in Germany and the EU in ISO 27001 certified data centres. The privacy policy publishes processor locations and legal bases, but support requests run through Zendesk hosted in the USA and third-country transfers rest on consent. We found no public information naming the hosting infrastructure itself, and the residency claim rests on the vendor's own statements. 1 4 5 11 5
The Data Protection Officer
The contracting entity is a German company in Rastede with a published register entry and external data protection officer in Hamburg, the vendor states all data is stored exclusively on its servers in Germany and the EU, and a data processing agreement can be signed digitally. The chain is not clean end to end: support requests run through a tool hosted in the USA under SCCs, third-country transfers rest on consent under Article 49, and the published privacy policy names website tooling rather than the sending infrastructure on named hardware — so a transfer argument cannot be fully avoided. 1 4 5 11 12 5
The Shop Owner
A German contracting entity in Rastede with register and VAT identification numbers, data stored on servers in Germany and the EU per the vendor's own pages, a self-serve data processing agreement, ISO 27001 certified datacentres and an external data protection officer in Hamburg — as a German shop this is what I pay for. Non-EU processing is named with its basis, including US-hosted Zendesk for support and third-country transfers under Art. 49 consent, but we found no public information naming the hosting or sending infrastructure itself. 1 4 11 5
The Integrator
The contracting entity is a German company registered at the Oldenburg district court, hosting is stated as exclusively on servers in Germany and the EU, the data processing agreement can be concluded digitally, data centres are ISO 27001-certified, and an external data protection officer sits in Hamburg. The privacy policy names subprocessors with locations and legal bases, including support requests processed in the USA by Zendesk under stated safeguards. I found no public information on the named hosting infrastructure or on where the sending infrastructure itself runs, and as a buyer who weighs this heavily that caps the score. 1 4 11 5
The Skeptic
The contracting entity is a German company in Rastede with an external German data protection officer, storage is stated as servers in Germany and the EU for all data, data centres carry ISO 27001 certification, and the data processing agreement is concluded digitally in self-service. The subprocessor list is published with locations and legal bases — including US-hosted Zendesk for support requests under a consent-based third-country transfer — but we found no public information on the named hosting infrastructure or on where the sending infrastructure specifically operates. 1 4 5 11 12 5
Pricing transparency
panel disagrees
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 public "from" price, a free plan or one priced tier; how cost scales with contacts or sends is unclear.
5 — Prices per contact or send tier public for the main plans with the billing period stated and the main limits given; some add-ons (dedicated IP, extra domains, overage) may be unpriced.
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
The free and Lite tiers (250 recipients, 1,000 sends monthly), Basic (500 recipients, unlimited sends) and Enterprise at "449,10 $ / Monat" with a 250,000-email quota are public with limits, billing annually in advance, VAT added on top, and priced add-ons such as premium support at "22,95 € im Monat". We found no public information on the Pro tier's price or on how cost scales across contact tiers between 500 recipients and unlimited, and a dedicated IP is available only on request. 1 2 3 13
The Deliverability Engineer
A permanent free tier of 250 recipients and 1,000 emails per month is fully specified, the billing period is stated — annually in advance, the monthly figure shown only as a calculation, with a 10 percent annual discount — and add-ons carry prices: 29,00 € per onboarding appointment and 22,95 € per month for premium support. The Enterprise tier is priced at 449,10 $ / Monat, with all prices plus the applicable statutory VAT. We found no public information on per-contact prices for the other tiers, so a sender cannot compute the real invoice for their list size. 2 3 13
The Data Protection Officer
The pricing pages state a permanently free tier of 250 recipients and 1,000 emails per month, a 500-recipient tier with unlimited monthly sends, and an Enterprise tier at "449,10 $ / Monat" with a 250,000-email quota, plus individually priced add-ons (Premium Support at 22,95 € per month, onboarding at 29,00 € per appointment), a ten per cent annual discount, annual advance billing and prices excluding statutory VAT. We found no public information on how the mid-tier price scales per contact or on overage rates, so the real invoice for a growing list cannot be computed from the captured pages. 2 3 13
The Shop Owner
Public and priced are the free tier (250 recipients, 1,000 mails a month, no credit card), the Enterprise tier at 449,10 $ per month with its 250,000-mail quota, and add-ons such as Premium Support at 22,95 € a month and onboarding at 29,00 € per appointment, with VAT treatment and annual-in-advance billing stated. But the captured pages show no prices for the middle tiers by list size, a dedicated IP is only on request, and no overage rate is given — so I cannot compute the real invoice for my list from these pages. 2 3 13
The Integrator
Public pages state a permanent free tier of 250 recipients and 1,000 emails per month, an Enterprise tier at 449,10 $ / Monat with 250,000 emails and unlimited recipients, billing annually in advance with a 10% annual discount, all prices plus statutory VAT, and priced add-ons — onboarding at 29,00 € pro Termin and premium support at 22,95 € im Monat. The captured pages give no figure for the Basic and Pro tiers and no per-contact price ladder, and the dedicated IP is on request without a number, so I cannot compute an invoice for a mid-sized list from public pages alone. 2 3
The Skeptic
A free tier of 250 recipients and 1,000 mails, a Basic tier of 500 recipients with unlimited monthly mails, and an Enterprise tier at 449.10 dollars a month for 250,000 mails are public, with annual payment in advance, a 10 percent annual discount, VAT explicitly excluded, and priced add-ons such as 22.95 euro premium support and 29 euro per-appointment onboarding. The contact staircase between 500 and unlimited recipients carries no prices on the captured pages, and we found no public information on overage for the fixed-quota plans; the Enterprise figure is given in dollars while the add-ons are in euros. 2 3
European sovereignty — proven facts
2 of 6 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 | 2/2 pts | 4 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Published, self-serve | 1/1 pts | 11 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about CleverReach
Is CleverReach European?
Yes. whats-best.ai classifies CleverReach as EU-Made. Its vendor, CleverReach GmbH & Co. KG, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.
Where does CleverReach store data?
The default storage location for customer data is not stated on the vendor’s pages as of 16 Nov 2026. The vendor’s pages mention Germany and the EU as hosting locations, per the vendor’s page captured 16 Nov 2026.
Does CleverReach have a free plan?
Yes. CleverReach has a free plan, per the vendor’s page captured 16 Nov 2026.
What are the best alternatives to CleverReach?
As of 18 Nov 2026, the panel rates Brevo (3/5), Dotdigital (3/5) and Mailjet (3/5) highest among the other 35 Email Marketing & Newsletter products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Brevo (EU-Made, France). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: CleverReach alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 19 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. Not confirmed on the vendor’s own pages as captured.
- 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.
- 10 subprocessors 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
- 5 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 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
- 1 compliance 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
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (16)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.cleverreach.com Checked 16 Nov 2026 Details →
- 2 Pricing www.cleverreach.com Checked 16 Nov 2026 Details →
- 3 Features www.cleverreach.com Checked 16 Nov 2026 Details →
- 4 Imprint www.cleverreach.com Checked 16 Nov 2026 Details →
- 5 Privacy policy www.cleverreach.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 6 Campaigns & automation — found from sitemap www.cleverreach.com Checked 16 Nov 2026 Details →
- 7 Campaigns & automation — found from sitemap www.cleverreach.com Checked 16 Nov 2026 Details →
- 8 Deliverability infrastructure — found from sitemap www.cleverreach.com Checked 16 Nov 2026 Details →
- 9 Deliverability infrastructure — found from sitemap www.cleverreach.com Checked 16 Nov 2026 Details →
- 10 Consent, proof & tracking limits — found from sitemap www.cleverreach.com Checked 16 Nov 2026 Details →
- 11 Consent, proof & tracking limits — found from sitemap www.cleverreach.com Checked 16 Nov 2026 Details →
- 12 List ownership, import & exit — found from sitemap www.cleverreach.com Checked 16 Nov 2026 Details →
- 13 List ownership, import & exit — found from sitemap www.cleverreach.com Checked 16 Nov 2026 Details →
- 14 Integrations & API — found from sitemap www.cleverreach.com Checked 16 Nov 2026 Details →
- 15 Integrations & API — found from sitemap developers.cleverreach.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 16 Structured-data backfill: markup only, no text or screenshot www.cleverreach.com Checked 8 Nov 2026 Details →