Email Marketing & Newsletter
CleverReach
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 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? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
CleverReach, an email-marketing and newsletter tool from CleverReach GmbH & Co. KG in Rastede, scores mid-band: campaign and automation sits at 6, while deliverability, consent and proof, and integrations run 6-7. Judges credited double opt-in with automatic logging said to evidence consent in a dispute, DKIM as a precondition for sending, staged bounce handling, and more than 120 named integrations with a developer API, PHP SDK and webhooks. The weakest criterion is list and data control at 3-4: import and deletion are documented, but no public information was found on exporting subscribers, engagement history or a whole-account exit. Pricing transparency runs 4-5 — the free tier (250 recipients, 1,000 mails per month, no credit card) and Enterprise at 449,10 $ per month are public, the tiers between show no figures. Sovereignty scores 5-6, where the captured pages give different pictures of third-country processing: servers stated in Germany and the EU, while support data is hosted exclusively in the USA via Zendesk on the basis of consent, and no public information names the data-centre provider. No criterion spans more than one point.
Speaks for it
- Double opt-in is the documented standard, with successful confirmation automatically logged so consent can be evidenced in a dispute
- DKIM is a documented precondition for sending, and bounce handling is explicit — soft bounces retried three times and blocked a month, hard bounces blocked a year
- More than 120 named integrations, including Shopify, Shopware, WooCommerce, HubSpot and Salesforce, with realtime recipient sync and a developer API with PHP SDK and webhooks
- The free tier is fully public — 250 recipients and 1,000 mails per month, no credit card required — with add-ons priced to the cent, such as premium support at 22,95 € per month
- A German contracting entity in Rastede, an external data protection officer in Hamburg, and a data processing agreement that can be signed digitally
Held against it
- We found no public information on exporting subscribers, engagement history, campaigns or templates, or on any exit and migration path
- Only Enterprise shows a price (449,10 $ per month); we found no public prices for the tiers between the free tier and Enterprise, no VAT treatment and no overage rates
- We found no public information naming the data-centre provider or a complete subprocessor list for the sending service, and support data is processed on Zendesk servers in the USA on the basis of consent
- A/B analysis reports which subject line achieved the higher open rate; we found no public information on significance reporting, send-time optimisation or branching journeys
- We found no public information on API rate limits, webhook retries or a sandbox
Best for
- You run a shop on Shopify, Shopware or WooCommerce and want realtime recipient sync plus a ready-made cart-abandonment mail
- You need double opt-in with automatic logging so you can evidence consent in an audit or dispute
- You want to start on the free tier — 250 recipients and 1,000 mails per month, no credit card required — before committing to a paid plan
- Your team wants to build against a documented developer API with a PHP SDK and webhooks across more than 120 named integrations
Avoid if
- You need to know your full cost for a mid-size list before signup — ask the vendor: the public pages we read do not show it
- Your purchase hinges on a documented exit path with full export of subscribers and engagement history
- You cannot accept any US-based processing of support data, or you require a complete subprocessor list for the sending chain and a named data-centre provider before signing
- You depend on significance-reported A/B results, send-time optimisation or branching journeys rather than open-rate comparison and trigger-plus-template automations
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 drag-and-drop editor, behaviour-based triggers, twenty-plus ready automation templates and content-split testing with a self-chosen distribution go well past a broadcast tool, and the Pro plan explicitly lifts the cap on automations. What holds it back for lifecycle work: the A/B analysis reports which subject line achieved the higher open rate rather than any significance measure, and we found no public information on branching journeys, send-time optimisation or holdout groups for measurement. 1 2 3 6 7
The Deliverability Engineer
Drag-and-drop editing, segmentation by data fields and tags, multi-step automations on behaviour and event triggers with twenty-plus ready-made tracks, and subject-line and content A/B tests with automatic winner send are all documented. We found no public information on send-time optimisation, on significance-reported test results, on holdout groups, or on journey branching richer than trigger plus template. 1 3 6 7
The Data Protection Officer
A drag-and-drop editor with responsive templates, segmentation by tags and up to 45 custom data fields, a visual automation editor with behaviour and tag triggers, welcome and birthday tracks, cart-abandonment mails, and subject-line A/B testing whose winner goes to the rest of the list — that carries it past the middle anchor. We found no public information on send-time optimisation, significance reporting for tests, or holdout groups, which keeps it short of the higher one. 1 3 6 7 2
The Shop Owner
Drag-and-drop editor, segmentation by attributes and tags, behaviour-triggered multi-step automations, subject-line and content split testing, and a ready-made cart-abandonment mail are all documented — that is the level my shop flows need. We found no public information on send-time optimisation, holdout groups, or testing that reports significance rather than raw open rates, and the only revenue evidence I found is conversion tracking via Google Analytics parameters rather than per-campaign revenue reporting. 1 2 3 6 7
The Integrator
The captures show a drag-and-drop editor, segmentation, a visual workflow editor with behaviour triggers and twenty-plus ready automation tracks, and both subject-line and content split tests with automatic winner send-out. I stop short of the top there: we found no public information on branching automations on data attributes, on send-time optimisation, or on statistical significance in the test analysis — the pages describe which subject line achieved the higher open rate, automatic or manual. 1 3 6 7
The Skeptic
A visual drag-and-drop automation editor, behaviour and tag triggers, twenty-plus prebuilt automation tracks, cart-abandonment and RSS mailings, and subject-line A/B testing with automatic winner send clear the middle of this criterion comfortably. What holds it back is that the A/B analysis reports raw open rates, and we found no public information on branching journeys on behaviour and data, send-time optimisation, or testing that reports significance. 1 3 6 7
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 is documented as a precondition for sending, with an automatically generated DNS record, selector support and a verification check, and bounce handling is unusually concrete — soft bounces blocked for a month with three retries, hard bounces for a year — alongside a deliverability dashboard and pre-send design and spam tests. We found no public information on SPF or DMARC setup guidance beyond naming them as protocols, on complaint-loop handling, on dedicated-IP warm-up, or on engagement-based sunsetting. 2 8 9 12
The Deliverability Engineer
This is documented infrastructure rather than a marketing number: DKIM is a stated precondition for any send, with self-service domain setup, automatically generated TXT record and a record check; hard bounces are blocked for a year after the first attempt, soft bounces retried up to three times and blocked a month, with automatic re-enable, per-mailing bounce rates in reporting and a deliverability dashboard with optimisation tips. We found no public information on complaint-loop handling, dedicated-IP warm-up or per-ISP diagnostics, SPF and DMARC are named without setup documentation, and the advertised inbox-rate benchmark counts for nothing in this score. 1 2 8 9 12
The Data Protection Officer
DKIM is enforced as a prerequisite for sending, with documented self-service setup, automatic DNS record creation and a record check, alongside SPF and DMARC naming, a deliverability dashboard in the reporting, and unusually explicit bounce policy — soft bounces retried three times and blocked a month, hard bounces blocked a year, each mailing's bounce rate reported. Dedicated IPs exist on request; we found no public information on complaint-loop handling, a documented warm-up, or engagement-based sunsetting. 8 9 2 3 12
The Shop Owner
DKIM setup is documented in detail and is required before any send, bounce handling is documented in stages (soft bounces blocked a month after three attempts, hard bounces a year), and there is a deliverability dashboard, a pre-send design and spam test, and a dedicated IP on request in the top tier. We found no public information on SPF or DMARC setup beyond a passing mention, on complaint-loop handling, on IP warm-up, or on engagement-based sunsetting. 2 8 9
The Integrator
DKIM is documented in depth and is a precondition for sending, with an automatically generated TXT record, a record check and selector support; hard bounces are suppressed after the first attempt for a year, soft bounces retried three times with a month's block, and a deliverability dashboard sits in the reporting, with a dedicated IP available on request at the top plan. We found no public information on complaint-loop handling, on warm-up for that dedicated IP, or on seed and inbox-placement testing, so this lands above the middle of the scale and well below the top. 2 8 9 12
The Skeptic
DKIM is documented in unusual depth and made a precondition for sending, with automatic DNS record generation and a record check, and bounce handling is refreshingly concrete: soft bounces blocked a month with up to three retries, hard bounces a year, plus a deliverability dashboard in the reporting. We found no public information on DMARC setup guidance, complaint-loop handling, dedicated-IP warm-up or seed testing — the advertised 90% inbox rate is a third-party benchmark, and the dedicated IP appears only as an on-request item in the Enterprise tier. 2 8 9
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 the documented default for signup forms and the confirmation is logged automatically so consent can be evidenced in a dispute — exactly the proof I want in an audit. Unsubscribes take effect immediately with single, confirmed or double opt-out plus an optional reason field, recipients manage their own data and preferences, and reporting can be anonymised on request. We found no public information on versioned form wording retrievable per subscriber, on tracking that is off by default, or on documented handling of access and erasure requests. 10 11 12 13
The Deliverability Engineer
Double opt-in is the documented standard for signup forms and the successful confirmation is automatically logged so consent can be evidenced in a dispute; unsubscribes take effect immediately with single, confirmed or double opt-out, blocklisted addresses are matched across lists on import and on send, reporting can be anonymised with recipient-based analysis disabled, and deletion after a configurable period is offered. We found no public information on what the stored consent record contains — source, IP or the wording consented to — and tracking is only optionally anonymised rather than off by default or per campaign. 10 11 12 13
The Data Protection Officer
Double opt-in is the documented standard and the confirmation is logged automatically, in the vendor's own words so consent can be evidenced in a dispute — the proof-that-survives-a-complaint posture I look for — with immediate unsubscribe, three opt-out variants, documented unsubscribes, recipient self-service profiles, and retention rules including deletion within three months of ending the newsletter. Reporting can be anonymised on request; we found no public information on whether the stored consent record captures source and wording, on tracking off by default, or on a pixel-free sending mode. 11 10 13 5 12
The Shop Owner
Double opt-in is the documented standard with automatic logging the vendor says proves consent in a dispute, opt-out comes in single, confirmed and double variants with immediate effect, reporting data can be anonymised on request, and there are deletion rules for inactive subscribers. We found no public information on versioned form wording retrievable per subscriber, on unsubscribe being honoured across lists, or on tracking that is off by default rather than merely optional to anonymise. 10 11 12 13
The Integrator
Double opt-in is the documented standard and its success is logged automatically, expressly so the sender can prove consent in a dispute; unsubscribe is immediate with single, confirmed and double opt-out variants, recipients manage their own data and newsletter preferences, and reporting data can be anonymised on request. For the top of the scale I would want retrievable, versioned form wording, tracking off by default and documented handling of access and erasure requests — we found no public information on those. 10 11 12 13
The Skeptic
Double opt-in is the documented standard for signup forms, its confirmation is automatically logged so the sender can prove consent in a dispute, and unsubscribe is immediate with single, confirmed and double opt-out variants, a reason field and full documentation. We found no public information on whether the stored consent record captures the form wording or source, on a per-campaign tracking switch (only a global option to anonymise reporting data is documented), or on handling of access and erasure requests, so this stops short of consent reproducible as evidence. 10 11 13
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
Import from CSV, Excel, text files or FTP with up to forty-five custom fields, an API and webhooks sufficient to sync elsewhere, and documented deletion — account data deleted within ten days of withdrawal where no statutory retention applies. But this criterion lives on exit, and we found no public information on exporting subscribers, engagement history, campaigns or templates, nor on any migration tooling; what is shown is that customers can edit or delete records. 5 11 12 15
The Deliverability Engineer
Import is documented broadly — CSV, Excel, text files and FTP server — into lists enriched with up to forty-five custom fields, records can be edited or deleted at any time, and account data is deleted within ten days of withdrawal. We found no public information on subscriber export in any form, on whether engagement history or unsubscribe state can leave the account, or on a documented exit and migration path. 5 11 12
The Data Protection Officer
Import is well documented from CSV, Excel, text files or FTP with custom attributes intact, and customers can edit or delete records at any time, but we found no public information on export of subscribers with subscription state and engagement history, on throttling, or on any whole-account exit path. One wrinkle an operator should ask about: recipient lists that are deleted or replaced are automatically backed up. 12 11 13
The Shop Owner
Import from CSV, Excel, text files and FTP with up to 45 custom fields is documented, records can be edited or deleted at any time, and account data is deleted within ten days of withdrawal. We found no public information on a full subscriber export including engagement history and unsubscribe state, on export throttling, or on exit pricing; a developer API exists but the captured pages do not show what it can export. 5 11 12 14
The Integrator
Import is properly built — CSV, Excel, text files and FTP, up to forty-five custom attribute fields, realtime sync from shop, CMS and CRM — and deletion is documented: records can be edited or deleted at any time, and account data within ten days of withdrawal. The exit side is where the captures fall silent: we found no public information on subscriber export, engagement-history export or full-account export, and that is the part I price hardest. 5 11 12 13
The Skeptic
Import is well served — CSV, Excel, text files and FTP with 45 custom fields, real-time sync from shop, CMS and CRM, a developer API and webhooks — and deletion is documented both per record ("Datensätze jederzeit bearbeiten oder löschen") and at account level within 10 days of withdrawal. We found no public information on subscriber export, engagement-history export, or any migration or exit tooling, so a buyer cannot see from the captured pages how their list and its history leave the tool. 5 11 12 15
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
More than a hundred and twenty named integrations covering every major shop platform plus deep CRM, CMS and WordPress form-plugin coverage, realtime recipient sync from shop, CMS or CRM, and a documented webhook system with events, endpoint registration, verification and optional encryption, plus a PHP SDK, MCP server, Zapier and Make. We found no public information on documented rate limits, webhook delivery retries, or a sandbox to build against. 3 12 14 15
The Deliverability Engineer
The connection surface is real: Shopify, Shopware 6, WooCommerce, HubSpot, Salesforce and more than a hundred other named systems, real-time recipient sync from shop, CMS and CRM, webhooks with a documented events list, verification and optional encryption, a PHP SDK and an MCP server, plus Zapier and Make. We found no public information on API rate limits, webhook retry behaviour, a sandbox, or an API versioning and deprecation policy. 3 12 14 15
The Data Protection Officer
More than 120 named integrations including Shopify, Shopware, WooCommerce, HubSpot and Salesforce with real-time recipient sync, a developer API with a PHP SDK and even an MCP server, and webhooks that deliver instant POSTs with a documented event list, verification and optional encryption. We found no public information on rate limits, retry behaviour for failed webhook deliveries, or a sandbox, which is what the next anchor up asks for. 14 15 3 12
The Shop Owner
More than 120 named integrations cover every shop platform I might run — Shopify, Shopware, WooCommerce and Magento among them — with real-time recipient sync from shop, CMS and CRM, cart-abandonment mail, event webhooks with verification and optional encryption, a developer API with a PHP SDK, and Zapier and Make as fallbacks. We found no public information on documented rate limits, webhook retries, or a sandbox, so a shop pushing order events would build against unstated limits. 3 12 14 15
The Integrator
This is a genuine developer surface, not a partner form: a documented API with a PHP SDK and an MCP server, webhooks that deliver instant POST requests to your endpoint with a published events list, verification and optional encryption, plus 120-plus named integrations including Shopify, WooCommerce, HubSpot and Salesforce, with Zapier and Make alongside rather than instead. What stops me building on it blind: we found no public information on documented rate limits, webhook retries, a sandbox, or an API versioning and deprecation policy. 3 12 14 15
The Skeptic
More than 120 integrations with named systems across Shopify, Shopware, WooCommerce, HubSpot and Salesforce, real-time recipient sync, a documented developer API with a PHP SDK and an MCP server, and webhooks delivering POST requests with verification and optional encryption. We found no public information on rate limits, webhook retries or a sandbox, which is where this surface stops short of the top band. 3 14 15
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
The contracting entity is a German company in Rastede, hosting is stated on the vendor's own pages as servers in Germany and the EU in ISO 27001-certified data centres, a digital data-processing agreement is offered and an external Hamburg data protection officer is named. Support data is hosted exclusively in the USA via Zendesk, third-country transfers rest on consent, and the data-centre provider is not named, so I cannot confirm the chain is fully European from what is published. 1 4 5 11
The Deliverability Engineer
A German contracting entity acting as controller, ISO-27001-certified data centres, servers stated on the captured pages to stand in Germany and the EU, a digitally signable data-processing agreement and an external data-protection officer in Hamburg are all on the record. Against that, support requests are processed on Zendesk servers in the USA under a consent-based transfer clause, the data-centre provider is not named, we found no complete published subprocessor list, and the independently compiled sovereignty attributes list data residency and ownership as unconfirmed. 1 4 5 11
The Data Protection Officer
The contracting entity is German with full register details, an external data protection officer in Hamburg, servers stated on several pages to stand in Germany and the EU, ISO 27001-certified data centres, and a data processing agreement signable digitally. But support data is processed on Zendesk servers exclusively in the USA with nothing more than consent as the stated transfer basis, the data-centre provider is unnamed, and we found no public information on a complete subprocessor list for the sending service itself. 4 5 1 11
The Shop Owner
The contracting entity is a German company in Rastede, the pages state servers in Germany and the EU in ISO 27001 certified data centres, a data processing agreement can be signed digitally, and the one non-EU link I can see — support data with Zendesk in the USA — is named with a stated legal basis. We found no public information naming the data-centre provider, on the company's ownership, or on a complete subprocessor list covering the sending chain. 1 4 5 11
The Integrator
German legal entity and contracting party in Rastede, servers stated on the vendor's own pages as Germany and the EU, a digitally signable data processing agreement, an external data protection officer, and non-EU processing actually named with a stated basis — Zendesk support data in the USA under Art. 49 Abs. 1 lit. a DSGVO, Reddit under the EU-U.S. Data Privacy Framework. We found no public information naming the data-centre provider, and the subprocessor names in the captures cover the vendor's website rather than a complete list for the newsletter-sending chain — and a consent-based transfer is a thin shield for support data. 1 4 5 11
The Skeptic
The German contracting entity is verifiable down to the commercial register and VAT ID, there is an external data protection officer in Hamburg, a digitally signable data processing agreement, and the claim that all data sits exclusively on servers in Germany and the EU in ISO 27001-certified data centres. But the data-centre provider goes unnamed, we found no public information on where the sending infrastructure runs or on a complete subprocessor list for the service itself, and the captured pages give different pictures of third-country processing: the GDPR page states servers in Germany and the EU with no processing in an unsafe third country, while the privacy policy names support data hosted exclusively in the USA on the basis of consent. 1 4 5 11
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
The free tier's limits, the annual discount, payment annually in advance, the flatrate-versus-fixed-quota billing model, the free-month conditions and add-on prices stated to the cent are public. Beyond one Enterprise plan price we found no public prices for the Basic and Pro tiers on the captured pages, and no overage rates, VAT treatment, or price for the dedicated IP offered on request. 2 3
The Deliverability Engineer
The edges are honest and exact: a permanent free tier of 250 recipients and 1,000 emails per month, unlimited sends on the flatrate model, annual prepayment with a ten-percent discount and the monthly figure expressly labelled as arithmetic, and priced add-ons (premium support 22,95 € im Monat, onboarding 29,00 € pro Termin, spam test 5,00 € pro Test, accessibility test 3,00 € pro Test). The captured pricing pages show a figure only for Enterprise at 449,10 $ per month; Lite and Pro tier prices, VAT treatment and any overage rate for quota plans are not stated, and the dedicated IP is offered on request without a price. 1 2 3 13
The Data Protection Officer
The ends of the ladder are public — a permanent free tier of 250 recipients and 1,000 mails a month, and Enterprise at 449,10 $ / Monat with 250,000 mails — with the billing period stated (annual in advance, monthly figure shown for calculation only), unlimited sends on lower tiers, and priced add-ons such as premium support at 22,95 € im Monat, onboarding at 29,00 € pro Termin, design and spam tests at 5,00 € pro Test and accessibility tests at 3,00 € pro Test. We found no public information on prices for the tiers between free and Enterprise, on VAT treatment, or on overage rates for quota plans, so a mid-sized sender cannot compute their invoice from the captured pages. 2 3 9 1
The Shop Owner
The free tier is fully public (250 recipients, 1,000 mails a month, no card), billing annually in advance with a 10 percent annual discount is stated, and the add-ons carry exact prices. We found no public information on prices for the middle tiers at my list size, on overage rates for the quota plans, or on VAT treatment, and the captured pages give figures in euros for add-ons alongside dollars for the top tier — so I cannot compute the real invoice for my list from what is captured. 2 3 13
The Integrator
The free tier (250 recipients, 1,000 mails monthly, no credit card), an Enterprise tier at 449,10 $ per month with 250,000 mails, priced add-ons — 3,00 € per accessibility test, 5,00 € per design and spam test, 29,00 € per onboarding appointment, 22,95 € monthly premium support — a 10 % annual discount and annual-in-advance billing are all public. But the captures give no price for the middle tiers, no overage terms under the fixed-quota option and no VAT treatment, and they price Enterprise in dollars while the add-ons are in euros — so I cannot compute an invoice for a mid-size list from the public pages alone. 2 3
The Skeptic
The free tier is concrete (250 recipients, 1,000 mails a month, permanent, no credit card) and the add-ons carry real numbers — 22,95 € im Monat premium support, 5,00 € per design-and-spam test, 3,00 € per accessibility test — with billing annual in advance and a stated 10% annual discount. But of the paid tiers only Enterprise shows a figure on the captured pricing page (449,10 $ per month); we found no public information on what the Basic or Pro tiers cost, on VAT treatment, on a price for the dedicated IP offered on request, or on where automation begins below the Pro tier, which lists unlimited automations. 2 3 13
European sovereignty — proven facts
1 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 | 4 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 16 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, Subprocessors. 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.
- 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
- 4 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
- 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 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. 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.cleverreach.com Checked 16 Sep 2026 Details →
- 2 Pricing www.cleverreach.com Checked 16 Sep 2026 Details →
- 3 Features www.cleverreach.com Checked 16 Sep 2026 Details →
- 4 Imprint www.cleverreach.com Checked 16 Sep 2026 Details →
- 5 Privacy policy www.cleverreach.com Checked 16 Sep 2026 Details →
- 6 Campaigns & automation — found from sitemap www.cleverreach.com Checked 30 Sep 2026 Details →
- 7 Campaigns & automation — found from sitemap www.cleverreach.com Checked 30 Sep 2026 Details →
- 8 Deliverability infrastructure — found from sitemap www.cleverreach.com Checked 30 Sep 2026 Details →
- 9 Deliverability infrastructure — found from sitemap www.cleverreach.com Checked 30 Sep 2026 Details →
- 10 Consent, proof & tracking limits — found from sitemap www.cleverreach.com Checked 30 Sep 2026 Details →
- 11 Consent, proof & tracking limits — found from sitemap www.cleverreach.com Checked 30 Sep 2026 Details →
- 12 List ownership, import & exit — found from sitemap www.cleverreach.com Checked 30 Sep 2026 Details →
- 13 List ownership, import & exit — found from sitemap www.cleverreach.com Checked 30 Sep 2026 Details →
- 14 Integrations & API — found from sitemap www.cleverreach.com Checked 30 Sep 2026 Details →
- 15 Integrations & API — found from sitemap developers.cleverreach.com Checked 30 Sep 2026 Details →