EmailOctopus
Provenance unknown 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 EmailOctopus Ltd · emailoctopus.com
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.
EmailOctopus at a glance
- Vendor
- EmailOctopus Ltd
- Headquarters
- Incorporated in the United Kingdom source, captured 10 Nov 2026
- Data hosting
- In the EU by default; pages mention Ireland source, captured 10 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 10 Nov 2026
- Panel verdict
- The AI panel rates EmailOctopus 2/5, the mean of 6 judges. EmailOctopus is a UK email-marketing product from Three Hearts Digital Ltd, strongest on integrations, with consent and proof, campaign and automation and list data control all at 4-5, and weakest on deliverability at 2. how scores are made
- As of
- Vendor pages captured 10 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
EmailOctopus is a UK email-marketing product from Three Hearts Digital Ltd, strongest on integrations, with consent and proof, campaign and automation and list data control all at 4-5, and weakest on deliverability at 2. The pages document a drag-and-drop and code-your-own editor, hundreds of brand-adapting templates, automated welcome and birthday sequences, double opt-in creating a clear sign-up record, open and click tracking the sender may enable or disable, a direct Shopify sync, an official WordPress plugin and a public API. Deliverability bottoms out because judges found no public information on SPF, DKIM or DMARC set-up, bounce or complaint handling, or reputation reporting — only EU sending servers and AI abuse screening. Judges split on sovereignty: the data protection officer's 6 credits the self-serve Article 28 schedule, the Article 27 representative in Ireland and the published sub-processor page, while judges scoring 4 weigh the London contracting entity and the terms' statement that some services use servers outside the UK and the EEA, with no transfer safeguard stated. Pricing transparency sits at 3; no per-tier prices appear.
Speaks for it
- Double opt-in is documented as creating a clear record that someone signed up, with consent checkboxes recording specific permission and open and click tracking the sender may enable or disable.
- A direct Shopify sync pulls customers, orders and abandoned checkouts automatically and consent-first, alongside an official WordPress plugin and a public API.
- Contact export and deletion are documented on demand, and the terms state customers retain ownership of user data.
- Contact data is stored with Amazon Web Services in Ireland and mail is sent from EU servers, with a self-serve Article 28 processing schedule, an Article 27 representative in Ireland, a published sub-processor page and a 48-hour breach-notification commitment.
- A free tier (with required branding) and a free trial are offered with no credit card required.
Held against it
- Deliverability scores sit at 2, with judges finding no public information on SPF, DKIM or DMARC set-up, bounce or complaint handling, or reputation reporting.
- Judges found no public information on A/B testing, dynamic content per segment or send-time optimisation.
- The captured pages give different figures for the integration count — over 1,000 on the homepage against 90 on the directory — and Zapier connections are managed and supported by Zapier rather than the vendor.
- The contracting entity is a London company and the terms state some services use servers outside the UK and the EEA, including US-based AI content moderation, with the transfer safeguard not stated on the captured pages.
- Backups may persist for up to 90 days after deletion, and free accounts not used for 24 months may be closed with their data deleted.
Best for
- You run a Shopify store and want customers, orders and abandoned checkouts synced into your list automatically and consent-first.
- You need a self-serve GDPR package — an Article 28 processing schedule built into the terms, an Article 27 EU representative and a published sub-processor page — without negotiating a contract.
- You send newsletters and welcome, sign-up or date-triggered sequences built in a tree view and do not depend on documented A/B testing or send-time optimisation.
- You want EU-located storage and sending by default, with contact data on Amazon Web Services in Ireland and mail sent from EU servers.
Avoid if
- You require end-to-end EEA processing with no US exposure — the terms state some services use servers outside the UK and the EEA, including US-based AI content moderation, and the contracting entity is a UK company.
- You must know your costs before committing — the pages publish no per-tier prices, usage above limits triggers an automatic tier upgrade, and yearly subscription fees are not refundable mid-term.
- You plan to keep a dormant free account as an archive — free accounts not used for 24 months may be closed and their data deleted.
- You depend on integration breadth for critical workflows — the directory shows 90 integrations against over 1,000 on the homepage, and Zapier connections are managed and priced by Zapier.
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 2.5 of 5 |
| Deliverability infrastructure | 1 of 5 |
| Consent, proof & tracking limits | 2.5 of 5 |
| List ownership, import & exit | 2 of 5 |
| Integrations & API | 2.5 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 drag-and-drop and code-your-own editors, hundreds of brand-adapting templates, and segmentation on subscriber data and behaviour give the campaign core, and automations with ready-made templates, a tree view for complex journeys, and repeatable entry cover the welcome and date-triggered sequences I need. We found no public information on A/B testing, branching conditions, dynamic content or send-time optimisation on the captured pages, so I cannot credit this as a full lifecycle programme. 1 5 6 7
The Deliverability Engineer
A drag-and-drop editor plus a code-your-own editor, hundreds of templates that adapt to brand colours, segmentation on subscriber data and behaviour, and automated welcome and birthday sequences with a tree view are all documented. We found no public information on A/B testing, dynamic content per segment or send-time optimisation, so the evidence sits at solid mid-level without the testing story. 1 5 6 7
The Data Protection Officer
The documented picture is a drag-and-drop editor with hundreds of brand-adapting templates, tags and behaviour-based segmentation, scheduling, and automated welcome and birthday sequences presented in a tree view. We found no public information on A/B testing, branching journeys, dynamic content per segment or send-time optimisation, so the evidence reaches just under the middle level rather than through it. 1 5 6 7
The Shop Owner
Drag-and-drop and code-your-own editors, hundreds of templates that adapt to my brand colours, tags plus data- and behaviour-based segmentation, and automations with templates and a tree view for more complex journeys — that covers welcome and birthday sequences well. We found no public information on A/B testing, dynamic content per segment or send-time optimisation, which is what separates this from a full journey builder for my revenue reporting. 1 5 6 7
The Integrator
The drag-and-drop editor, a code-your-own option and hundreds of brand-adapting templates are documented, alongside tags, behaviour-based segmentation, scheduling, and automated sequences on sign-up and date triggers with a tree view for more complex journeys. I found no public information on A/B testing, dynamic content per segment or send-time optimisation, which is what the higher levels describe. 1 5 6 7
The Skeptic
A real editor story: drag-and-drop plus a code-your-own option, hundreds of templates that adapt to brand colours, behavioural segmentation with scheduling, and automations from welcome to birthday with automation templates, a tree view and repeatable journeys. What I cannot find is testing — no public information on A/B testing of campaigns, and nothing on branching on data, dynamic content per segment or send-time optimisation. 1 5 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 — 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
The vendor states mail is sent from its own servers in the EU, and an alternative mode delegates sending to the customer's own email provider account. We found no public information on SPF, DKIM or DMARC set-up, bounce and complaint suppression, warm-up or reputation handling on the captured pages, so I cannot score beyond the existence of sending infrastructure. 4 2
The Deliverability Engineer
The trust page states mail is stored and sent from servers in the EU, the terms require delegated access to your own email provider account under EmailOctopus Connect, purchased lists are banned and content is screened for phishing and fraud — but we found no public information on SPF, DKIM or DMARC set-up, bounce handling, suppression, dedicated IPs, warm-up or reputation reporting. Authentication and bounce discipline are the two things I read for, and neither is documented. 2 3 4
The Data Protection Officer
The terms describe a Connect mode granting the vendor delegated access to your own email service provider account, while the GDPR page states emails are sent from servers in the EU and content is screened by automated tools for phishing and abuse. We found no public information on SPF, DKIM or DMARC set-up, bounce suppression, complaint feedback loops or reputation handling, so the arrival story rests almost entirely on the sending location. 2 3 4
The Shop Owner
Their GDPR page states emails are sent from servers in the EU, so the sending infrastructure is theirs, and the Terms also describe an EmailOctopus Connect option where I grant delegated access to my own email service provider account. We found no public information on SPF or DKIM set-up, bounce and complaint handling, warm-up or reputation tooling, so I cannot judge whether my campaigns actually land. 2 4
The Integrator
Vendor sending infrastructure is documented — contact data on Amazon Web Services in Ireland with mail sent from EU servers — and content is screened by automated tools including AI models for phishing and abuse. Beyond that the captured pages are silent: no SPF, DKIM or DMARC set-up guidance, no bounce or complaint handling, and no reputation reporting, so a sender cannot verify authentication from public pages. 2 3 4
The Skeptic
Emails are stated to be sent from servers in the EU, so this is a sending service and not purely a relay through the customer's own infrastructure — though an EmailOctopus Connect mode grants the vendor delegated access to the customer's own email provider account. Beyond that, we found no public information on SPF, DKIM or DMARC set-up, bounce or complaint suppression, dedicated IPs, warm-up or reputation reporting; the AI screening described targets phishing, fraud and abuse, not delivery. 2 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
Double opt-in is documented as creating a clear record that a subscriber signed up, consent checkboxes keep a record of specific permission, unsubscribe links are built in, and open and click tracking can be enabled or disabled — with export and deletion framed as the way to answer a contact's request and breach notice within 48 hours. We found no public information on stored confirmation wording with IP, a preference centre, or tracking off by default. 4 7 2
The Deliverability Engineer
Double opt-in with a clear record that the subscriber signed up, consent checkboxes that keep a record of specific permission, unsubscribe links, and open-and-click tracking the sender may enable or disable are all documented. What the pages don't show is the depth a regulator would ask for — timestamp, source or IP per subscriber — nor a preference centre or tracking off by default, so this stops short of the evidentiary level. 4 2 7
The Data Protection Officer
Double opt-in is documented as producing "a clear record that they signed up", consent checkboxes on forms keep a record of specific permission, unsubscribe links are standard, and the terms state open and click tracking is something "you may enable or disable" — a real switch, which is what I look for before signing anything off. We found no public information on stored confirmation wording or IP per subscriber, a preference centre, or tracking off by default, so the consent proof rests on the vendor's word rather than a reproducible history. 2 3 4
The Shop Owner
Double opt-in is documented as giving a clear record that someone signed up, consent checkboxes on forms keep a record of specific permission, unsubscribe links are standard, and open and click tracking can be enabled or disabled — that last one matters to me. The captured pages stop short of timestamp, source and IP detail in the consent record and describe no preference centre, so proof reaches a clear record rather than evidence I could hand an authority. 2 4 7
The Integrator
Double opt-in is described as creating a clear record that someone signed up, consent checkboxes keep a record of specific permission, unsubscribe links are documented, and open and click tracking can be enabled or disabled by the sender. The detail that makes consent provable — timestamp, source or IP per subscriber — plus one-click unsubscribe and a preference centre do not appear on the captured pages. 2 4 7
The Skeptic
Double opt-in, consent checkboxes that "keep a record of it", and unsubscribe links are documented, open and click tracking can be enabled or disabled, purchased lists are contractually prohibited and inactive free accounts are closed after 24 months. The consent record is asserted but its timestamp, source and IP are not detailed; we found no public information on a preference centre, unsubscribe honoured across lists, or tracking off by default. 2 3 4 7
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
Export and deletion of contacts are documented, ownership of user data is stated in the terms, and a documented API plus the Shopify and Zapier syncs give me programmatic paths in and out of the list. We found no public information on field mapping on import, export of engagement history, or export of campaigns and templates, so exit remains asserted rather than described in full. 4 2 7 8
The Deliverability Engineer
Export and deletion of contacts whenever you need them, a clause that you retain ownership of your data, published API documentation, and inbound syncs from Shopify and via Zapier are all stated. CSV import with field mapping, export of engagement history, and whether the export carries custom fields and unsubscribe state are not described, and backup copies may persist for up to 90 days after deletion. 4 2 8 9
The Data Protection Officer
Contacts can be exported and deleted "whenever you need to" including to answer a contact's request, the terms confirm customers retain ownership of user data, and a public API reads and writes the list; the privacy policy is candid that backups persist up to 90 days after deletion. We found no public information on whether the export carries engagement history, or on export throttling. 2 3 4 7
The Shop Owner
I retain ownership of my data, can export and delete contacts whenever I need to, and the API is documented. Import with field mapping and export of engagement history are not described in what was captured, and backups may remain in storage for up to 90 days after deletion, which tempers the deletion promise. 2 3 4 7
The Integrator
Export and deletion of contacts on demand is documented for answering contact requests, the terms state customers retain ownership of user data, and an API is offered alongside the product. What an export actually contains — custom fields, engagement history, unsubscribe state — and import field mapping are not described, and the privacy policy notes backups can persist for up to 90 days after deletion. 2 3 4 8
The Skeptic
Contact export and deletion are documented ("whenever you need to"), ownership of user data is retained in the terms, backups are overwritten within 90 days of deletion, an API is documented and contacts can flow in from Shopify and Zapier. We found no public information on CSV import with field mapping, export of custom fields, engagement history, campaigns or templates, or any export throttling — and a free account unused for 24 months is closed and deleted, which is an exit risk rather than an exit feature. 2 3 4 8
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
Ninety listed integrations include a direct Shopify customer, order and abandoned-checkout sync billed as consent-first, an official WordPress plugin, and Zapier as the connector for everything else, with public API documentation alongside. Webhook retries, rate limits, a sandbox and bidirectional sync are not described on the captured pages, and the Zapier integration is supported by Zapier rather than the vendor. 8 9 7 1
The Deliverability Engineer
A direct Shopify customer sync for customers, orders and abandoned checkouts, an official WordPress plugin, some 90 listed integrations plus a Zapier connector, and API documentation give a real connection surface. Event webhooks with retries, documented rate limits, a sandbox and bidirectional sync aren't described, and the Zapier integration is managed and priced by Zapier rather than the vendor. 8 9 7 1
The Data Protection Officer
A direct Shopify customer, order and abandoned-checkout sync and an official WordPress plugin are documented alongside public API documentation, with Zapier covering Salesforce and ClickFunnels. The homepage claims "over 1,000 and counting" while the integrations page shows all 90 — the captured pages give different figures for the count — and we found no public information on webhooks, rate limits or a sandbox; the Zapier connector is managed and supported by Zapier rather than the vendor. 1 7 8 9
The Shop Owner
The direct Shopify sync pulls customers, orders and abandoned checkouts into my list automatically and consent-first, there is an official WordPress plugin for sign-up forms, a documented API, and Zapier for the rest — though that piece is managed and priced by Zapier itself. The captured pages give different figures for the integration count — 90 shown on the integrations page against over 1,000 on the homepage — and webhooks, rate limits and a sandbox are not described. 7 8 9
The Integrator
A documented API, a direct Shopify sync for customers, orders and abandoned checkouts, and an official WordPress plugin are genuine vendor-side connections — but the breadth runs through Zapier, which manages and supports that path itself, and the captured pages give different figures for the total, over 1,000 on the homepage against 90 on the integrations page. I found no public information on rate limits, webhooks with retries, a sandbox environment or an API deprecation policy, so I could not build against this sight unseen. 1 7 8 9
The Skeptic
A direct Shopify sync of customers, orders and abandoned checkouts, an official WordPress plugin and a documented API put this past the connector-only tier; the captured pages give different figures for the total, "over 1,000 and counting" on the homepage against "showing all 90" on the directory. Breadth rides on Zapier, whose support team handles the integration and whose own pricing the vendor defers to; we found no public information on event webhooks with retries, documented rate limits, a sandbox or bidirectional maintained syncs. 1 8 9
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
Contact data and content sit with Amazon Web Services in Ireland, mail is sent from EU servers, the data processing agreement is built into the terms automatically, an Article 27 EU representative is appointed, and a sub-processor page listing providers and locations is published. The contracting entity is a London company, however, and the terms state some services run on servers outside the UK and EEA, including US-based AI content moderation — which I weigh heavily. 4 2 3
The Deliverability Engineer
Hosting and email sending are stated on named EU infrastructure — Amazon Web Services, primarily Ireland — with a data processing agreement built into the terms for every account, an Article 27 representative in Ireland, and a published sub-processor page claiming every provider with location. The contracting entity is a London company, though, and the terms themselves state some services use servers outside the UK and EEA, with the transfer safeguard for that processing not stated on the captured pages. 4 2 3
The Data Protection Officer
Lists, content and sending are stated to sit with Amazon Web Services in Ireland, a sub-processor page is published with each provider's role and location, an Article 28 processing schedule applies automatically to every account, and an Article 27 representative sits in Cork. But the contracting entity is a London company, and the terms themselves say some services use servers "outside the United Kingdom and the EEA" — the US-based AI content moderation — governed by contractual retention limits rather than a documented transfer basis, and we found no public information on a transfer impact assessment. 2 3 4
The Shop Owner
Lists and content sit with Amazon Web Services in Ireland, mail is sent from EU servers, the data processing agreement is built into the Terms as a self-serve schedule, an Article 27 representative is appointed in Ireland, and a subprocessors page is published listing providers and their locations. The contracting entity is a London company, however, and the Terms state some services use servers outside the UK and EEA — the privacy policy describes US-based AI content moderation — so the chain is not European end to end. 2 3 4
The Integrator
Contact data sits with Amazon Web Services in Ireland, mail is sent from EU servers, a published sub-processor page lists every provider with its location, and a self-serve Article 28 processing schedule plus an Article 27 representative in Ireland are in place. The contracting entity is a London company and the terms state some services use servers outside the UK and the EEA, so the chain is proven European at its core but not end to end. 2 3 4
The Skeptic
Storage and sending are stated as EU — Amazon Web Services, primarily Ireland — with a published sub-processor page, a self-serve data processing agreement built into the terms as Schedule 2, a 48-hour breach commitment and an Article 27 EU representative in Ireland. But the contracting entity is a London company following the UK GDPR, and the terms themselves state some services use servers outside the UK and EEA, with US-based AI content moderation named and no stated transfer safeguard anywhere I read; hosting options and any transfer impact assessment are unknown. 2 3 4
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
A free tier is documented, billing is monthly or yearly with a 10% yearly saving, prices are stated exclusive of VAT, and exceeding limits moves you automatically to the tier matching your usage. The captured pages give no per-contact or per-send price figures, so I cannot compute an invoice for my list size from public information. 1 2
The Deliverability Engineer
A free plan with EmailOctopus branding, a free trial with no credit card, monthly or yearly billing with a 10% yearly saving, automatic tier upgrades when usage exceeds limits, VAT-exclusive fees and a no-refund yearly policy are all documented. We found no public price figures per contact or send tier on the captured pages, so a real invoice for a given list size can't be computed from what's shown. 1 2 6
The Data Protection Officer
A free tier with required branding, a no-credit-card trial, monthly or yearly billing advertised as "Save 10%", automatic upgrades to the tier matching your usage when limits are exceeded, VAT-exclusive fees and non-refundable yearly subscriptions are all public. The captured pages give no per-contact or per-send prices for any tier, so a sender cannot compute the invoice for their list size from what was captured. 1 2
The Shop Owner
The billing mechanics are public: a free tier and a free trial without a credit card, monthly or yearly billing with a 10% yearly saving, fees stated exclusive of VAT, automatic moves to the tier matching my usage if I exceed limits, and yearly fees not refundable mid-term. The captured pages show no prices per contact tier at all, so I cannot compute the invoice for my list size and send volume. 1 2
The Integrator
A free tier with required branding, monthly and yearly billing with a 10% yearly saving, automatic upgrade to the tier matching your usage, VAT-exclusive pricing and 30 days' notice of fee changes are all documented. No per-tier prices or contact and volume limits appear on the captured pages, so a buyer cannot compute a real invoice for a given list size from what is captured. 1 2
The Skeptic
The machinery is documented: a free tier (branding required), a no-credit-card trial, monthly and yearly billing with a 10% yearly discount, fees stated exclusive of VAT, automatic renewal, automatic upgrade to whichever tier matches your usage when limits are exceeded, and yearly fees that are not refundable mid-term. Yet we found no public information on what any paid tier actually costs, so a buyer cannot compute an invoice — and discovering the auto-upgrade price by experiment is expensive given the no-refund clause. 1 2
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 GB | 1/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?The GDPR page markets EU-only storage, but the Terms themselves state some services use servers outside the UK and EEA (e.g. US-based AI content moderation in the privacy policy). |
2/4 pts | 2 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Published, self-serve | 1/1 pts | 4 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about EmailOctopus
Is EmailOctopus European?
Not determined: the vendor’s pages as captured do not say where EmailOctopus is based. Its vendor, EmailOctopus Ltd, is incorporated in the United Kingdom, per the vendor’s page captured 10 Nov 2026.
Where does EmailOctopus store data?
EmailOctopus stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 10 Nov 2026. The vendor’s pages mention Ireland as hosting location, per the vendor’s page captured 10 Nov 2026.
Does EmailOctopus have a free plan?
Yes. EmailOctopus has a free plan, per the vendor’s page captured 10 Nov 2026.
What are the best alternatives to EmailOctopus?
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: EmailOctopus alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. The GDPR page markets EU-only storage, but the Terms themselves state some services use servers outside the UK and EEA (e.g. US-based AI content moderation in the privacy policy).
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 10 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 7 legal 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
- 6 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
- 6 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
- 2 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 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
- 1 hosting 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 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 support 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 (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page emailoctopus.com Checked 10 Nov 2026 Details →
- 2 Terms of service — found from the homepage emailoctopus.com Checked 10 Nov 2026 Details →
- 3 Privacy policy — found from the homepage emailoctopus.com Checked 10 Nov 2026 Details →
- 4 Security / trust page — found from the homepage emailoctopus.com Checked 10 Nov 2026 Details →
- 5 Campaigns & automation — found from sitemap emailoctopus.com Checked 10 Nov 2026 Details →
- 6 Campaigns & automation — found from sitemap emailoctopus.com Checked 10 Nov 2026 Details →
- 7 Consent, proof & tracking limits — found from sitemap emailoctopus.com Checked 10 Nov 2026 Details →
- 8 Integrations & API — found from sitemap emailoctopus.com Checked 10 Nov 2026 Details →
- 9 Integrations & API — found from sitemap emailoctopus.com Checked 10 Nov 2026 Details →