Mailingwork
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by mailingwork GmbH · www.mailingwork.de
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.
Mailingwork at a glance
- Vendor
- mailingwork GmbH
- Headquarters
- Incorporated in France source, captured 11 Nov 2026
- Data hosting
- In the EU; pages mention Germany source, captured 26 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 11 Nov 2026
- Panel verdict
- The AI panel rates Mailingwork 2/5, the mean of 6 judges. MAILINGWORK is an email-marketing and newsletter platform operated by Positive Group Chemnitz GmbH, and the bench scored it strongest on consent and proof, where scores cluster at 4, and campaign and automation, at 4–5. how scores are made
- As of
- Vendor pages captured 15 Sep 2026 to 11 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
MAILINGWORK is an email-marketing and newsletter platform operated by Positive Group Chemnitz GmbH, and the bench scored it strongest on consent and proof, where scores cluster at 4, and campaign and automation, at 4–5. Judges credited documented double opt-in with proof of consent and signup logging of IP address plus date and time, and trigger-based multi-stage campaigns spanning email, SMS and postcard with reusable templates. Sovereignty scored 4–6: German hosting, a Chemnitz commercial-register entry and CSA certification were credited, while the no-third-country-transfer statement covers newsletter-recipient data, and judges found no public information on a data processing agreement or a sending-chain subprocessor list. List data control clustered at 3, with import and export formats and deletion of a customer's own subscribers undescribed on the captured pages, and deliverability ran 3–4, resting on CSA certification with no public information on SPF, DKIM or DMARC set-up. A pricing page exists but its capture carries no figures; the offers shown are a free demo and a free consultation. Persona-weighted verdicts ran 3.7 to 4.1, and the flagged split check flagged none.
Speaks for it
- Trigger-based multi-stage campaigns across email, SMS and postcard are documented, with reusable templates and personalisation
- Double opt-in with proof of consent, consent checkboxes and unsubscribe links are documented, with IP address and timestamp logged at signup
- CSA certification, whitelisting and mailing tests are documented for sending on the vendor's own German-hosted infrastructure
- Servers are stated to be hosted in Germany and the privacy policy states no third-country transfer of newsletter-recipient data
- An open API for CRM, CMS and shop systems plus a Zapier connection is documented
Held against it
- No public information appears on SPF, DKIM or DMARC set-up, bounce suppression or complaint handling
- No public information appears on segmentation, A/B testing or branching journeys
- No public information appears on import and export formats, engagement-history export or documented deletion of a customer's own subscribers
- No public information appears on a data processing agreement, the named hosting provider or a subprocessor list for the sending chain
- The captured pricing page carries no price figures, tiers or contact limits, so no invoice can be computed from public information
Best for
- You send to German recipients and want documented double opt-in with proof of consent plus servers stated to be hosted in Germany
- You run triggered lifecycle campaigns — welcome series, cart reminders, birthday and anniversary mailings — across email, SMS and postcard
- You build your own connections through an open API or Zapier rather than relying on vendor-maintained shop or CRM connectors
Avoid if
- You need segmentation, A/B testing or branching journeys inside your automation tool
- Your procurement requires a data processing agreement and a subprocessor list before signature
- You must see documented SPF, DKIM and DMARC set-up and bounce suppression before adopting a sender
- You need documented import, export and deletion of your subscriber list before you sign
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 2 of 5 |
| Deliverability infrastructure | 2 of 5 |
| Consent, proof & tracking limits | 2 of 5 |
| List ownership, import & exit | 1.5 of 5 |
| Integrations & API | 2 of 5 |
| European sovereignty | 2.5 of 5 |
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 — 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
The campaign manager builds one- and multi-stage campaigns that start automatically on a trigger — welcome series, abandoned-cart reminders, birthday mailings, transactional sends — across email, SMS and postcard, with campaigns reusable as templates and personalization offered. What the captured pages never describe is the part I buy automation for: segmentation, journeys that branch, and split testing of any kind. 5 1
The Deliverability Engineer
Multi-stage, trigger-based campaigns are documented — welcome series, cart reminders, transactional mailings, birthday and anniversary sends across email, SMS and postcard — with reusable templates, personalisation, and campaigns that can be test-run, paused and resumed. We found no public information on segmentation, A/B split testing or branching journeys, so the middle mark is where the evidence stops. 5 1
The Data Protection Officer
The campaign manager builds one- and multi-stage campaigns triggered by subscriber actions — welcome series, cart reminders, birthday and anniversary mailings — with reusable templates, personalisation, channel blocks for email, SMS and postcard, and test, pause and reactivation controls. We found no public information on segmentation, A/B testing or a visual journey builder with branching. 1 5
The Shop Owner
The campaign manager builds one- or multi-stage triggered campaigns — welcome series, abandoned-cart reminders, transactional mailings, product recommendations, birthday mailings — which is precisely the revenue motion my shop runs on, and finished campaigns double as reusable templates. But I found no public information on A/B testing, segmentation on subscriber fields or behaviour, or dynamic content, so I cannot place it higher than mid-tier. 1 5
The Integrator
The campaign manager builds one- or multi-stage automated campaigns that start when a user triggers them — welcome series, cart reminders, transactional mailings, birthday and anniversary sends — with campaigns reusable as templates, a block-based builder spanning email, SMS and postcard, and campaigns that can be tested, activated and paused. We found no public information on segmentation or split testing of campaigns, which the next level of this criterion expects. 5 1
The Skeptic
Triggered, multi-stage campaigns are well documented — welcome series, cart reminders, transactional mailings, birthday and anniversary mailings that start automatically on a trigger, can be tested, paused and saved as reusable templates with personalisation. We found no public information on the editor, segmentation on subscriber fields or behaviour, or A/B testing, which is what separates a campaign tool from a journey builder. 5 1
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 — 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
Sending runs on the vendor's own German-hosted servers, and the security page documents Certified Senders Alliance certification, whitelisting and mailing tests — a real reputation credential in the German market. The pages do not document SPF, DKIM or DMARC set-up, bounce suppression or complaint handling, so I cannot treat this as an operated deliverability programme. 4 3
The Deliverability Engineer
Sending runs on the vendor's own infrastructure, and the security page documents Certified Senders Alliance certification, whitelisting and mailing tests — an auditable reputation signal, not an inbox-rate boast. We found no public information on SPF, DKIM or DMARC set-up for sender domains, on bounce and complaint suppression, or on feedback loops and per-domain reputation reporting, so this sits just above the basic mark. 4 5
The Data Protection Officer
The vendor sends on its own German-hosted infrastructure and documents CSA certification, whitelisting and mailing tests as its trust measures. We found no public information on SPF, DKIM or DMARC set-up for sender domains, on bounce suppression or on complaint feedback, so the picture is own-infrastructure sending plus a certification, with authentication and bounce handling undocumented. 3 4
The Shop Owner
Sending runs on the vendor's own infrastructure with Certified Senders Alliance certification, whitelisting and mailing tests described — a real reputation signal in the German inbox market. I found no public information on SPF, DKIM or DMARC set-up for a sender's domain, bounce and complaint suppression, or per-domain reputation reporting. 4
The Integrator
The vendor sends from its own German-hosted servers and documents Certified Senders Alliance certification, whitelisting and mailing tests as trust markers. We found no public information on SPF, DKIM or DMARC set-up, bounce or complaint suppression, dedicated IPs, or reputation reporting per sending domain. 4
The Skeptic
Certified Senders Alliance certification, whitelisting and mailing tests are documented, a concrete reputation claim rather than an advertised inbox rate. We found no public information on SPF, DKIM or DMARC set-up for the sender's own domain, bounce and complaint suppression, dedicated IP options or warm-up, so the arrival story rests on the certificate. 4
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 — 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
Sign-up with checkboxes, unsubscribe links and double opt-in are documented for the product, explicitly including proof of consent, and the vendor's own newsletter logs IP address and registration date and time at sign-up. The captured pages do not describe a preference centre or any way to limit open and click tracking, which stops this short of consent that is reproducible as evidence. 4 3
The Deliverability Engineer
Double opt-in with checkboxes and unsubscribe links is documented for the product, explicitly with proof of consent, and signup logging stores IP address, date and time — a consent record with substance. We found no public information on switching open or click tracking off, a preference centre, or how unsubscribe is honoured across lists. 4 3
The Data Protection Officer
Double opt-in with proof of consent, consent checkboxes and unsubscribe links are documented as product features, and the vendor's own newsletter practice logs IP address plus date and time at sign-up — the shape of evidence that survives a complaint. We found no public information on switching open and click tracking off, on a preference centre, or on handling of access and erasure requests, and those gaps sit exactly where my sign-off lives. 3 4
The Shop Owner
Double opt-in with proof of consent, consent checkboxes and unsubscribe links are described for subscriber forms, and the signup log stores IP address with date and time of registration — a genuine consent record. I found no public information on switching open or click tracking off, a preference centre, or retention rules for inactive subscribers. 3 4
The Integrator
The product page documents double opt-in with checkboxes, unsubscribe links and proof of consent ("Nachweis der Einwilligung"), and the vendor's own newsletter signup stores the IP address plus date and time of registration. The captured pages do not describe what the consent record contains per subscriber, one-click unsubscribe, a preference centre, or any way to switch off open or click tracking. 4 3
The Skeptic
Double opt-in with proof of consent, checkboxes and unsubscribe links is stated as a product feature, and the vendor practises double opt-in on its own newsletter with IP address and timestamp logged at sign-up. We found no public information on what the consent record stores per subscriber within the product, one-click or cross-list unsubscribe handling, a preference centre, or whether open and click tracking can be switched off. 4 3
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 — 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
The open API is documented to create subscribers, send transactional mail and query data, which gives me a programmatic way in and out of the list. The captured pages do not describe import or export with field mapping, engagement-history export, or deletion of a subscriber as a product feature — the deletion statement I did find concerns the vendor's own newsletter. 5 3
The Deliverability Engineer
An open API creates subscribers, queries data and sends transactional mail — read and write access to the list — and the privacy policy documents recipient data being deleted from the vendor's servers after unsubscribe, though that sentence covers the vendor's own newsletter. We found no public information on import and export formats, engagement-history export, or deletion across a customer's whole account. 5 3
The Data Protection Officer
The open API documents creating subscribers, sending transactional mail and querying data, so the list can be read and written programmatically. We found no public information on import and export formats, engagement-history export, or how deletion of a subscriber is executed, which is what I would need to see before trusting an exit. 5
The Shop Owner
The open API covers creating subscribers and querying data, and the privacy policy shows newsletter-recipient data is deleted from the vendor's servers after unsubscribe. I found no public information on CSV import with field mapping, full export including engagement history and unsubscribe state, or whether export is throttled. 3 5
The Integrator
The API use cases cover creating subscribers and querying data, and the privacy policy's deletion statement — newsletter data removed from both the vendor's and the product's servers after unsubscribe — concerns the vendor's own newsletter recipients. We found no public information on import or export formats, engagement-history export, or documented deletion of a customer's own subscribers. 5 3
The Skeptic
The open API is documented to create subscribers, send transactional mail and query data, which is read and write access to the list. We found no public information on import with field mapping, export including engagement history and unsubscribe state, or deletion of a subscriber across records — for a buyer, the exit route is the part that matters and it is not described on these pages. 5
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 — 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
An open API is offered for connecting CRM, CMS and shop systems, with transactional sending named as a use case, plus a Zapier connection for everything else. No named shop or CRM integrations, webhooks, rate limits or sandbox are described on the captured pages, so this is a workable connection surface without the maintained-integration layer I would want for shop events flowing in. 5
The Deliverability Engineer
An open API aimed at CRM, CMS and shop-system integration, plus a Zapier connector, is documented with subscriber and transactional use cases. We found no public information on named direct integrations with specific systems, webhooks with retries, rate limits or a sandbox. 5
The Data Protection Officer
An open API for CRM, CMS and shop systems and a Zapier connection are documented, with named use cases for subscriber creation, transactional sending and data queries. We found no public information on webhooks, rate limits, a sandbox, or maintained integrations with specific named systems. 5
The Shop Owner
An open API is offered to connect CRM, CMS and shop systems, transactional mail can be sent through it, and Zapier links further apps — the right shape for wiring my shop. The shop connection is named only as a generic category rather than a specific platform my store runs on, and I found no public information on webhooks with retries, documented rate limits, or a sandbox. 5
The Integrator
An open API is offered for CRM, CMS and shop integration, with use cases for subscriber creation, transactional sending and data queries, plus a Zapier connector. We found no public information on named maintained integrations, event webhooks with retries, rate limits, a sandbox, versioning or a deprecation policy — from my desk that is an API claim without the documentation a builder needs, and Zapier coverage I count as outsourced. 5
The Skeptic
An open API positioned for CRM, CMS and shop-system connections, transactional sending through the API, and Zapier as a connector platform are all documented. We found no public information on named shop or CRM integrations the vendor maintains itself, webhooks with retries, documented rate limits or a sandbox. 5
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. 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
The contracting and sending side is provably German: Positive Group Chemnitz GmbH is registered in Chemnitz and named as controller, servers are hosted in Germany, newsletter-recipient data is stated not to be transferred to third countries, and there is an internal data protection officer plus a named external partner. What the pages do not show is a data processing agreement or a subprocessor list with locations for the sending chain; the parent group's legal notice names a French entity, which is European either way but leaves the chain half-documented. 2 3 4 7
The Deliverability Engineer
The operating company is registered in Chemnitz under a French parent, hosting is stated to be in Germany, and the privacy policy states no third-country transfer of newsletter-recipient data, with CSA certification reinforcing the German sending posture. We found no public information on a data processing agreement or a subprocessor list for the sending chain; the subprocessors named on the privacy policy belong to the vendor's own website, including Google Analytics with noted US transfers. 4 3 7
The Data Protection Officer
The operating entity is a Chemnitz company under a French parent, servers are hosted in Germany, the vendor states recipient data undergoes no third-country transfer, and CSA certification with an internal data protection officer are documented. We found no public information on a data processing agreement, on the hosting provider's name, or on a subprocessor list for the sending chain — and the no-transfer sentence covers newsletter-recipient data, while the vendor's own website runs Google Analytics. For the recipient database I get an answer that needs no Schrems II argument; for the behavioural-tracking chain I do not yet. 3 4 2 7
The Shop Owner
The contracting and data-protection controlling entity is Positive Group Chemnitz GmbH with a Chemnitz commercial register entry, servers are stated to be hosted in Germany, the parent Groupe Positive sits in France, and the privacy policy states no third-country transfer of newsletter-recipient data, with a CSA certificate behind it. I found no public information on a data processing agreement, the named hosting infrastructure, or a published subprocessor list covering the sending chain, so this stays a solid mid-tier rather than proven end to end. 3 4 2 7
The Integrator
The contracting entity is a Chemnitz-registered German company under a French parent group, both in the EU; servers are stated to be hosted in Germany with no third-country transfer of newsletter-recipient data, backed by an internal data protection officer, an external data-protection partner and CSA certification. The captured pages stop short of the stronger levels: we found no published product subprocessor list, no data processing agreement, and the hosting infrastructure itself is not named. 4 3 2 7
The Skeptic
A German-registered operating entity with Chemnitz register number and German VAT ID — the captured pages also name the France-based Groupe Positive SAS — plus a stated commitment that servers are hosted in Germany and Certified Senders Alliance certification. The hosting sentence sits in marketing copy naming no infrastructure, and the no-third-country-transfer line covers newsletter-recipient data on the product servers; we found no public information on a data processing agreement or a published subprocessor list covering the sending infrastructure. 4 3 2 7
Pricing transparency
not rated — the vendor publishes no price
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
Every readable page routes me to a free demo or a free consultation rather than a price, and the captured pricing page yielded no readable figures at all. I found no public prices, contact or volume limits, or overage rates that would let a buyer compute an invoice. 1 4 6
The Deliverability Engineer
A prices page exists and a free demo is offered, but no plan, tier or per-contact figure appears on the captured pages, so no invoice can be computed from public evidence. The motion is demo-first, with the numbers behind a conversation. 6 1 5
The Data Protection Officer
The captured pages offer a free demo and a free consultation and show that a pricing page exists, but we found no public information on plan prices, contact tiers or limits in the captured pages. A buyer cannot compute an invoice from what is public here. 1 6
The Shop Owner
The homepage offers a free demo and a free consultation, and a pricing page exists, but the captured pricing page carries no price figures of any kind. I found no public information on tier prices, contact or send limits, overage or how cost scales — so as a buyer who judges price against the channel's contribution, I cannot even begin the calculation. 1 6
The Integrator
The only pricing-related offers in the captures are a free demo and a free consultation, and a pricing page exists on the site but its capture carries no price text. We found no public price per contact or send, no tiers with limits, and no overage or VAT treatment — a buyer cannot compute an invoice from what was captured. 1 6 4
The Skeptic
The captured pricing page yielded no price figures at all, and the commercial motion shown is a free demo plus a free consultation with documents sent on request. A sender cannot compute an invoice for a given list size and send volume from these pages; we found no public information on tiers, contact or volume limits, overage rates or VAT treatment. 6 1 4
European sovereignty — proven facts
3 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 FR | 2/2 pts | 7 Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?The statement sits in marketing copy on the security page and names no subprocessors; the privacy policy's matching no-transfer line refers to newsletter-recipient data. |
4/4 pts | 4 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment |
Not needed, no transfer outside the EU/EEA
unverified
Why unverified?The no-transfer sentence concerns newsletter-recipient data on the product's servers, and the same privacy policy notes US transfers by Google Analytics for the vendor's own website. |
1/1 pts | 3 Report an error |
Questions about Mailingwork
Is Mailingwork European?
Yes. whats-best.ai classifies Mailingwork as EU-Made. Its vendor, mailingwork GmbH, is incorporated in France, per the vendor’s page captured 11 Nov 2026.
Where does Mailingwork store data?
Mailingwork stores customer data in the EU, per the vendor’s page captured 26 Oct 2026. The vendor’s pages mention Germany as hosting location, per the vendor’s page captured 26 Oct 2026.
Does Mailingwork have a free plan?
Not stated on the vendor’s pages as of 11 Nov 2026.
What are the best alternatives to Mailingwork?
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: Mailingwork alternatives.
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 — Transfer impact assessment. The no-transfer sentence concerns newsletter-recipient data on the product's servers, and the same privacy policy notes US transfers by Google Analytics for the vendor's own website.
- Weak sourcing — Hosting location. The statement sits in marketing copy on the security page and names no subprocessors; the privacy policy's matching no-transfer line refers to newsletter-recipient data.
- 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.
- 19 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
- 3 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
- 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 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 (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.mailingwork.de Checked 26 Oct 2026 Details →
- 2 Imprint www.mailingwork.de Checked 26 Oct 2026 +1 earlier capture: 15 Sep 2026 Details →
- 3 Privacy policy www.mailingwork.de Checked 26 Oct 2026 Details →
- 4 Security / trust page — found from the homepage mailingwork.de Checked 26 Oct 2026 Details →
- 5 Campaigns & automation — found from sitemap mailingwork.de Checked 26 Oct 2026 Details →
- 6 Structured-data backfill: markup only, no text or screenshot www.mailingwork.de Checked 8 Nov 2026 Details →
- 7 Parent company legal notice (Groupe Positive SAS) positivegroup.com Checked 11 Nov 2026 Details →
- 8 Parent company history (Positive acquires Mailingwork) positivegroup.com Checked 11 Nov 2026 Details →