Email Marketing & Newsletter
Moosend
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Moosend · www.moosend.com
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
Moosend is an email marketing and automation platform whose strongest showing is campaigns and automation, where scores cluster at 7: the rationales document a visual workflow builder with branching logic and multiple triggers, segmentation, dynamic content, A/B testing and 130+ templates, held back by no public information on send-time optimisation or A/B results reported with significance. The weakest band is consent and proof, with scores clustered at 3: double opt-in appears only as an available function, and cookie-based tracking of individual users is promoted as a capability with no public information on limiting it. Two criteria split. Deliverability spans 4 to 6 — the documented SPF, DKIM, DMARC and BIMI plus a free DMARC checker and pre-send testing earn the top, while the lower scores weigh no public information on bounce suppression, complaint-loop handling, dedicated IPs or warm-up. List data control spans 2 to 4, higher scores crediting inbound paths (a MailChimp importer, an API) against an unevidenced exit path. Sovereignty and pricing transparency hold at 4, with "$7 $9 Per month" public but no contact-tier boundaries.
Speaks for it
- Documented visual workflow builder with branching logic, multiple triggers, conditions and actions, plus segmentation, dynamic content insertion and A/B testing over 130+ templates.
- Pre-made automation recipes for cart abandonment, user onboarding, upsell/cross-sell and thank-you email.
- Authentication documented across SPF, DKIM, DMARC and BIMI, with a custom sending domain and a free DMARC checker offering policy analysis and DNS recommendations.
- Forty-two native integrations including WooCommerce, Magento and OpenCart, plus Zapier access to 1,000+ apps and a developer surface with an SMTP service and a transactional API.
- Headline pricing of "$7 $9 Per month" is public with monthly, biannual (15% off) and annual (20% off) periods and unlimited email campaigns/sents.
Held against it
- Double opt-in is documented only as an available function said to help with GDPR, with no public information on whether it is the default or what the stored consent record contains.
- Cookie-based tracking that links specific users to page visits, carts and purchase details is promoted as a core capability, and we found no public information on limiting or switching it off.
- We found no public information on what a subscriber export contains, whether engagement history or unsubscribe state can leave, or on documented deletion — list data control scores span 2 to 4.
- We found no public information on bounce suppression, complaint-loop handling, dedicated-IP options or warm-up, and the 98% delivery guarantee and 0.02% spam rate appear as advertised figures.
- The EU-hosting statement covers only "customer's contact data" on AWS, a US-headquartered provider, the parent is named as Constant Contact without a stated jurisdiction, and we found no published subprocessor list.
Best for
- You run an online shop and want cart-abandonment, upsell and thank-you journeys wired to WooCommerce, Magento, OpenCart or Zen Cart.
- You are moving lists in from MailChimp or Segment and need documented inbound import paths and two-way contact syncs.
- You want a published headline price of "$7 $9 Per month" with 15% and 20% discounts for longer periods and unlimited email campaigns/sents.
- You send authenticated mail and value a free DMARC checker with policy analysis alongside SPF, DKIM, DMARC and BIMI documentation.
Avoid if
- You must evidence per-subscriber consent for a regulator or complaint — consent and proof scores cluster at 3, and we found no public information on what the stored consent record contains.
- You need a documented exit for your list — we found no public information on export contents, engagement history, unsubscribe state or deletion, and list data control scores span 2 to 4.
- You must pre-compute your invoice for a given list size — the pages give the $7 and $9 per month figures and we found no public information on the contact counts covered, overage rates or VAT treatment.
- You require a named, complete EU processing chain — ask the vendor: the public pages we read do not show it
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 visual workflow builder with branching logic, multiple triggers, conditions and actions covers real lifecycle work — cart abandonment, onboarding, upsell and cross-sell recipes — driven by browsing and purchase behaviour rather than opens alone, with segmentation and dynamic content that goes beyond the first name. What holds it back for a lifecycle programme: we found no public information on send-time optimisation, and A/B testing is documented only as testing variations of emails, with nothing showing results reported with statistical significance. 1 4 5 10
The Deliverability Engineer
A visual workflow builder with branching logic, multiple triggers, real-time behaviour entry, segmentation and dynamic content, backed by 130-plus templates and A/B testing — that is a genuine journey builder, not a welcome mail. We found no public information on send-time optimisation or testing that reports significance, so it stays short of the top band. 4 5 10 1
The Data Protection Officer
The captured pages document a visual workflow builder with branching logic, multiple triggers and behaviour-based entry, dynamic content with segmentation, and pre-made recipes plus A/B testing — most of what the upper mid band describes. We found no public information on send-time optimisation or on A/B results reporting significance rather than raw variation testing. 1 4 5
The Shop Owner
The visual workflow builder with branching logic, multiple triggers, and ready-made recipes for cart abandonment, upsell and thank-you mail is exactly what my shop's revenue flows run on, and A/B testing, segmentation and dynamic content insertion are all documented. I found no public information on send-time optimisation or on testing that reports significance rather than raw counts, which is what holds this back from the top band. 4 5 10 1
The Integrator
The workflow pages document a visual builder with branching logic, conditions and actions, multiple triggers, and behaviour-based entry from website tracking, alongside segmentation, dynamic content and A/B testing — most of what I need a journey engine to do. We found no public information on send-time optimisation or on testing that reports significance rather than raw variation counts. 4 5 10 1
The Skeptic
A visual workflow builder with branching logic, conditions, actions and multiple triggers is documented, alongside segmentation, dynamic content insertion, behaviour-triggered sends and A/B testing over 130+ templates. What holds it below the top band: we found no public information on send-time optimisation, or on A/B results reported with significance rather than raw counts. 1 4 5
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
SPF, DKIM, DMARC and even BIMI are documented alongside a custom sending domain, plus a free DMARC checker with policy analysis and DNS recommendations — the authentication layer is genuinely written up. But the 98% delivery guarantee and 0.02% spam rate are marketing numbers, and we found no public information on a stated bounce-suppression policy, complaint-loop handling, dedicated-IP options with warm-up, or inbox-placement testing; M3AAWG and CSA membership is listed without operational detail. 6 7
The Deliverability Engineer
SPF, DKIM, DMARC and even BIMI are documented, a custom sending domain is stated, there is a public DMARC policy checker with DNS recommendations, and M3AAWG and Certified Senders Alliance membership is claimed. But we found no public information on a bounce or hard-bounce suppression policy, complaint-loop handling, dedicated IP options or warm-up, and the 98% delivery guarantee and 0.02% spam rate are advertised numbers I disregard on principle. 6 7 3
The Data Protection Officer
SPF, DKIM, DMARC and BIMI are documented alongside a custom sending domain, a free DMARC checker with policy analysis and DNS recommendations, pre-send testing, and M3AAWG/CSA membership. We found no public information on a bounce-suppression policy, dedicated IP options with warm-up, or published list-hygiene guidance, and the 98% delivery rate and 0.02% spam rate appear only as marketing figures. 6 7
The Shop Owner
SPF, DKIM, DMARC and BIMI are documented alongside a custom sending domain and a free DMARC checker that reads the policy and suggests fixes, which is the documented baseline I need. I found no public information on bounce suppression, complaint-loop handling, dedicated-IP options or warm-up, and the 98% delivery figure is an advertised number rather than documentation. 6 7
The Integrator
SPF, DKIM, DMARC and BIMI are documented together with a custom sending domain, and the free DMARC checker with policy analysis is more authentication documentation than most vendors publish. We found no public information on bounce suppression, complaint-loop handling, dedicated-IP options or warm-up, and the 98% delivery figure is a marketing number rather than a stated policy. 6 7
The Skeptic
SPF, DKIM, DMARC and BIMI are documented, a custom sending domain is offered, and the free DMARC checker with policy analysis is real tooling rather than a badge. But we found no public information on bounce suppression, complaint-loop handling, dedicated IPs or warm-up, and the 98% delivery "guarantee" is a marketing number while the Postmaster reference sends the customer to Google's own tool rather than documenting monitoring performed on the customer's behalf. 3 6 7
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 documented as available and GDPR-relevant, but nothing states it is the default, and we found no public information on what the consent record stores — source, wording, IP — or on one-click unsubscribe and whether it is honoured across lists. Website tracking via cookies, linking specific users to their behaviour, is described as a core capability, and we found no public information on limiting or switching off open and click tracking; the GDPR pages cover compliance history rather than reproducible per-subscriber proof. 6 8 9 10
The Deliverability Engineer
Double opt-in is documented as available with GDPR relevance, and a GDPR addendum page exists, but nothing shows it is the default or what the consent record stores. We found no public information on unsubscribe mechanics, consent logging, or any way to limit open, click or website tracking — the cookie-based tracking that identifies individual users is promoted as a feature, never as something a sender can switch off. 6 9 10
The Data Protection Officer
Double opt-in is mentioned once as a GDPR-compliance function, but I found no public information on whether it is the default, what a stored consent record contains — source, wording, IP — or how unsubscribe is honoured across lists. The tracking pages promote cookies that link specific identified users to page visits, carts and purchase details with no documented off-by-default or pixel-free mode, so nothing here proves consent to the standard a complaint would demand. 6 9 10
The Shop Owner
Double opt-in is documented only as a function that helps with GDPR, and I found no public information on what the consent record stores, whether double opt-in is the default, how unsubscribes are honoured across lists, or any mode that limits open and click tracking — identifying individual users through cookies is instead promoted as a headline capability. For a shop mailing its buyers, that silence on proof is a real cost. 6 9 10
The Integrator
Double opt-in and opt-out functions are stated as available, but we found no public information on whether opt-in is the default or on what the stored consent record contains. Tracking is marketed as cookie-based identification of individual users across page visits, carts and purchase details, and we found no public information on limiting or switching tracking off, preference-centre granularity, or handling of access and erasure requests. 6 9 10 8
The Skeptic
Double opt-in appears in deliverability copy as an available function said to help with GDPR, and we found no public information stating it as the default, describing the consent record, or on unsubscribe handling. Cookie-based open, click and website tracking of individual users is documented as a feature, and we found no public information on limiting or switching it off; the only access and objection rights we found sit in the affiliate terms, which govern affiliates rather than subscribers. 2 6 9 10
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
Inbound is evidenced — a MailChimp list importer and an API to create and manage campaigns and mailing lists programmatically — but we found no public information on subscriber export, whether custom attributes, engagement history or unsubscribe state can leave, or on deletion that executes across records. For a tool whose value sits in behavioural history, an exit path that is not documented is a risk I would price into any contract. 11
The Deliverability Engineer
Inbound is documented — a MailChimp list import, an API to create and manage campaigns and lists programmatically — and the terms pages say they cover data ownership and account termination. We found no public information on subscriber export, whether engagement history or unsubscribe state can leave the platform, or deletion that is evidenced rather than asserted. 11 3 2
The Data Protection Officer
An inbound import from MailChimp and a programmatic API to create and manage campaigns and mailing lists are documented, but nothing states what a subscriber export contains. I found no public information on export of custom fields, engagement history or unsubscribe state, on documented deletion across records, or on export throttling — exit is simply not addressed on the captured pages. 11
The Shop Owner
The API to create and manage campaigns and mailing lists programmatically plus a MailChimp import tool show a way in, but I found no public information on exporting subscribers with custom attributes, engagement history and unsubscribe state, or on deletion that executes across records. Exit is where I would learn whether my list and its history stay mine, and the captured pages do not address it. 11
The Integrator
List import from MailChimp and an API to create and manage mailing lists programmatically give real paths in, and the tracking pages show exactly the engagement data that would need to leave with the list. We found no public information on export completeness, engagement-history export or documented deletion — exit is not evidenced as a feature. 11 10 2
The Skeptic
Import paths are plentiful — a MailChimp importer, Segment, and 42 native integrations with two-way contact sync — and the API manages campaigns and mailing lists programmatically. But we found no public information on what a subscriber export contains, whether engagement history or unsubscribe state can leave, how deletion executes, or exit as a supported and priced feature. 2 11 12
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
Forty-two native integrations including WooCommerce, Magento, OpenCart and Zen Cart, two-way contact syncs with a long roster of CRMs, and a developer surface covering API references, SMTP service, a transactional API, DNS setup and website tracking put this well past a read-only API. We found no public information on event webhooks with retries, documented rate limits, a sandbox, or API versioning and deprecation policy, which is what separates a connected tool from a component. 11 12
The Deliverability Engineer
Forty-two native integrations counted on the page including WooCommerce and Magento, a thousand more via Zapier, and SMTP plus a transactional API alongside marketing sending — respectable breadth on one platform. We found no public information on event webhooks with retries, documented rate limits, or a sandbox, which is what separates a solid surface from a buildable one. 11 12 7
The Data Protection Officer
Forty-two native integrations including WooCommerce, Magento, Zen Cart and major CRMs, a transactional API and SMTP service alongside the campaign API, and two-way contact syncs give a real connection surface. We found no public information on event webhooks with retries, documented rate limits, or a sandbox, which is what separates a good score from the top of this range. 7 11 12
The Shop Owner
Forty-two native integrations including WooCommerce with cart-abandonment and product-recommendation mail, plus Magento, OpenCart, Zen Cart and CS-Cart, and a transactional API and SMTP service alongside the campaign API — that covers my checkout and my order receipts. I found no public information on event webhooks, documented rate limits or a sandbox, and the CRM side runs largely through Zapier connectors rather than maintained integrations. 11 12 5
The Integrator
There are 42 native integrations including WooCommerce, Magento, Salesforce, HubSpot and Segment, plus an API reference, a transactional API and a direct SMTP service — enough surface to build against without a partner agreement, though the via-Zapier catalogue is an outsourced one. We found no public information on webhooks, retry behaviour, rate limits, a sandbox, or any versioning and deprecation policy, which is precisely the operational contract I need before wiring this into an existing stack. 11 12 5
The Skeptic
Forty-two native integrations including WooCommerce, Magento and OpenCart on the shop side and Salesforce, HubSpot and Dynamics on the CRM side, plus Zapier to 1,000+ apps, and a developer surface combining API references, an SMTP service and a transactional API on one product. We found no public information on webhooks, documented rate limits, a sandbox, or an API versioning and deprecation policy. 5 11 12
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
Contact data is claimed as EU-hosted on AWS, but the claim sits in trust-centre marketing copy covering only customer's contact data, the contracting party is a London entity under a Constant Contact parent, and we found no public information on a subprocessor list beyond AWS — a US-headquartered provider, so the CLOUD Act reaches that hosted data regardless of region. I weigh this heavily: an EU hosting claim without a named, complete chain and with ownership whose jurisdiction the site does not state is not something I would sign against for subscriber behavioural data. 2 3 5
The Deliverability Engineer
The trust page states customer contact data is hosted in the EU through AWS, and the contracting entity is a London company under UK law — but the same pages state Moosend is now a Constant Contact company without stating that parent's jurisdiction, and we found no published subprocessor list. AWS being a US-headquartered provider puts the stored data within reach of the US CLOUD Act, and the EU-hosting claim covers only contact data in marketing copy. 3 2 5 10
The Data Protection Officer
EU hosting through Amazon Web Services is claimed in trust-center copy but only for "customer's contact data", while the contracting entity is Moosend Ltd. of London under a parent the pages name only as "a Constant Contact company" with no jurisdiction given, and I found no published subprocessor list. With AWS US-headquartered and the region of sending, tracking and analytics never stated, answering where behavioural data lives still requires exactly the transfer argument I refuse to make. 2 3 5
The Shop Owner
The trust page states customer contact data is hosted in the EU through Amazon Web Services, but the contracting entity is Moosend Ltd. of London under United Kingdom law and courts, the site announces Moosend is now a Constant Contact company, and AWS is a US-headquartered provider so the CLOUD Act reaches the data despite the EU region. I found no public information on a subprocessor list or on the region of sending, tracking and support tooling, and I weigh this heavily. 3 2 1
The Integrator
Hosting is stated as EU-based on AWS and the contracting entity is Moosend Ltd. of 5 New Street Square, London under United Kingdom law, while the site states Moosend is now a Constant Contact company — a parent whose jurisdiction the captured pages never give. The EU-hosting statement covers only the customer's contact data, and we found no published subprocessor list, so the region of sending, tracking and support tooling and every downstream processor is unevidenced. 3 2 5
The Skeptic
The trust centre's EU-hosting claim covers only "customer's contact data" and rests on AWS, a US-headquartered host that keeps the US CLOUD Act in the chain, with sending infrastructure, tracking and support tooling left uncovered by any statement we found. The contracting entity is a UK company under UK law and exclusive London jurisdiction, the captured pages name the parent as Constant Contact without a jurisdiction, and we found no published subprocessor list. 2 3 5
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
A headline price of $7 and $9 per month is public with monthly, biannual and annual billing periods and their 15% and 20% discounts stated, and email campaigns and sends are advertised as unlimited, so send volume is not the trap. But the captured pages give only the $7 and $9 figures without the contact counts each covers, and we found no public information on per-tier feature boundaries such as where automation sits, overage treatment, or VAT — so I cannot compute an invoice for a given list size. 1
The Deliverability Engineer
Prices of $7 and $9 per month are public with monthly, biannual and annual billing periods at exact stated discounts, and unlimited campaigns and sends are stated alongside a free trial. But the captured pages give no contact counts for those tiers, no VAT treatment and no overage rates, so a sender cannot compute the real invoice for their list size from these pages alone. 1 7
The Data Protection Officer
A headline "$7 $9 Per month" is public together with monthly, biannual and annual billing (save 15% and 20%) and an "Unlimited Email Campaigns / Sents" claim, which is more than a bare sticker price. But we found no public information on contact-tier boundaries, overage rates, the tier where automation begins, or VAT treatment, so a buyer still cannot compute the real invoice for a given list size. 1 7
The Shop Owner
The homepage shows a price of $7 $9 per month with monthly, biannual and annual billing, a 20% annual saving and unlimited email campaigns, so the headline and send limits are public. I found no public information on which contact counts those prices cover, overage rates, add-on pricing or VAT treatment, so I cannot compute the real invoice for my list size from the public pages alone. 1 7
The Integrator
A headline price of "$7 $9 Per month" is public with monthly, biannual and annual billing — "Save 20% automatically—pay once a year" — and unlimited email campaigns and sends are stated. We found no public information on what list size those prices cover, where automation or SMS begins, or VAT treatment, so the real invoice for a given list size cannot be computed from the captured pages. 1
The Skeptic
The pricing page shows "$7 $9 Per month" with monthly, biannual and annual periods (15% and 20% off) and unlimited email campaigns/sents, so there is no overage staircase to decode. But we found no public information on what separates the two figures, how price scales with list size, or contact-tier boundaries and VAT treatment; the most precisely documented numbers on the site are the affiliate commission terms, not the buyer's invoice. 1 2 7
European sovereignty — proven facts
Built 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 GB ⚠ unverified | 1/3 pts | 2 Report an error |
|---|---|---|---|
| Ownership | Foreign-controlled ⚠ unverified | 0/2 pts | 3 Report an error |
| Data residency | EU only ⚠ unverified | 3/3 pts | 3 Report an error |
| Subprocessors | US CLOUD Act reach ⚠ unverified | 0/2 pts | 3 Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 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 — Ownership. The page never states Constant Contact's own jurisdiction or the deal structure; classifying it as foreign-controlled rests on outside knowledge that Constant Contact is a US company.
- Weak sourcing — Legal entity. The imprint gives only a London address rather than a company register, and the site also states "Moosend is now a Constant Contact company", so the UK entity may no longer be the operative contracting party.
- Weak sourcing — Data residency. The claim sits in trust-center marketing copy and covers only "customer's contact data"; no contractual statement in the excerpts confirms the region of all product data or that no non-EU default exists.
- Weak sourcing — Subprocessors. AWS is a US-headquartered provider, so the US CLOUD Act reaches the customer data even though the same page states the hosting is EU-based.
- 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.
- 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 integrations 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 (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.moosend.com Checked 29 Sep 2026 Details →
- 2 Terms of service — found from the homepage moosend.com Checked 30 Sep 2026 Details →
- 3 Security / trust page — found from the homepage moosend.com Checked 30 Sep 2026 Details →
- 4 Campaigns & automation — found from sitemap moosend.com Checked 30 Sep 2026 Details →
- 5 Campaigns & automation — found from sitemap moosend.com Checked 30 Sep 2026 Details →
- 6 Deliverability infrastructure — found from sitemap moosend.com Checked 30 Sep 2026 Details →
- 7 Deliverability infrastructure — found from sitemap moosend.com Checked 30 Sep 2026 Details →
- 8 Consent, proof & tracking limits — found from sitemap moosend.com Checked 30 Sep 2026 Details →
- 9 Consent, proof & tracking limits — found from sitemap moosend.com Checked 30 Sep 2026 Details →
- 10 List ownership, import & exit — found from sitemap moosend.com Checked 30 Sep 2026 Details →
- 11 Integrations & API — found from sitemap moosend.com Checked 30 Sep 2026 Details →
- 12 Integrations & API — found from sitemap moosend.com Checked 30 Sep 2026 Details →