Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by GetResponse Sp. z o.o. · www.getresponse.com

Report an error on this page Is this your product? →

Link to this page

GetResponse: AI-assisted analysis on whats-best.ai GetResponse: AI-assisted analysis on whats-best.ai (dark)

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.

GetResponse at a glance

Vendor
GetResponse Sp. z o.o.
Headquarters
Incorporated in Poland source, captured 16 Nov 2026
Data hosting
In the EU by default source, captured 16 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 2 Nov 2026
Panel verdict
The AI panel rates GetResponse 2.5/5, the mean of 6 judges. GetResponse is an email marketing platform from GetResponse S.A., a Polish joint-stock company in Gdańsk. how scores are made
As of
Vendor pages captured 30 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

GetResponse alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Data Protection Officer

Weighted verdict

Signs off the tool that holds named people and records what each of them opened. Wants double opt-in with a proof that survives a complaint, tracking that can be switched off, and an answer to where the behavioural data lives that does not require a Schrems II argument.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Data Protection Officer

Panel median The Data Protection Officer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Data Protection Officer
Campaigns & automation 3.5 of 5 3.5 of 5
Deliverability infrastructure 3 of 5 3 of 5
Consent, proof & tracking limits 2 of 5 1.5 of 5
List ownership, import & exit 2.5 of 5 2 of 5
Integrations & API 3 of 5 3 of 5
European sovereignty 2 of 5 2 of 5
Pricing transparency 2 of 5 1.5 of 5

Campaigns & automation

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.

Report an error

The Data Protection Officer

A drag-and-drop editor with hundreds of templates, segmentation on location, interests and behaviour, automation workflows with conditions, filters and behaviour-based triggers, abandoned-cart recovery fed by shop data, and AI send-time recommendation cover the journey machinery well. I stop short of the top band because the captured pages do not describe testing that reports significance or holdout groups for measurement. 3 11 3 1 4

Report an error

Deliverability infrastructure

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.

Report an error

The Data Protection Officer

Dedicated IP on the MAX tier, a documented warm-up with an automated reputation threshold, assisted warm-up with shared-IP overflow, list hygiene with processing of undeliverable addresses, and a Deliverability Team working with mailbox providers and blocklist operators show delivery operated as a service. Authentication set-up, complaint feedback loops and inbox-placement testing are undocumented on the captured pages, much of this is tied to the MAX tier, and the advertised 99% deliverability figure is a claim rather than evidence. 5 6

Report an error

List ownership, import & exit

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.

Report an error

The Data Protection Officer

Import is well documented — file upload, manual entry, copy-paste and nearly 20 sources — and an advanced API with published docs exists, while the stated deletion tail (encrypted backups for 120 days after deletion) I credit. But the CSV export I can point to is the privacy-policy portability promise rather than a documented product export of the list with its fields and engagement history, and the migration service advertised runs in the inbound direction; exit tooling is not described. 2 8 10 4

Report an error

Integrations & API

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.

Report an error

The Data Protection Officer

A directory of 150+ integrations across shop, CRM and connector platforms, a maintained Shopify integration importing customers, orders and abandoned checkouts with its own support material, an advanced API with docs, and a partner programme give a broad connection surface. Webhooks with retries, documented rate limits and a sandbox are not described on the captured pages, which keeps this below the top band. 10 11 1 11

Report an error

European sovereignty

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.

Report an error

The Data Protection Officer

The contracting entity is a Polish joint-stock company in Gdańsk with a registry and VAT number, a Data Protection Officer is designated, and processing terms apply when the customer is established in the EEA — that much is solid. But no data-centre country is stated, no published subprocessor list with locations is evidenced, and the policy itself concedes transfers outside the EEA for chat, SMS, analytics, marketing, sales and CRM, naming Google LLC in the USA under SCCs and the Data Privacy Framework — behavioural data leaving the EEA is exactly the argument I want not to have to make. 2 1

Report an error

Pricing transparency

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.

Report an error

The Data Protection Officer

A free plan with stated limits (500 contacts, 1,000 unique visits per month) and a 14-day trial without credit card are public, but the captured pages give different figures for the entry price — "The lowest plan starts at $13.30 /mo" and "19 USD per month" — without billing-period context, and contact-tier scaling, overage rates, dedicated-IP pricing and VAT treatment are not documented. A buyer cannot compute the real invoice for a given list size from these pages. 4 7 9 9

Report an error

European sovereignty — proven facts

2 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location EU by default unverified
Why unverified?

The passage concerns recipients and transfers of personal data, not the stated location of the hosting infrastructure, and no data-centre country is named.

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 Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about GetResponse

Is GetResponse European?

Not determined: the vendor’s pages as captured do not say where GetResponse is based. Its vendor, GetResponse Sp. z o.o., is incorporated in Poland, per the vendor’s page captured 16 Nov 2026.

Where does GetResponse store data?

GetResponse stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026.

Does GetResponse have a free plan?

Yes. GetResponse has a free plan, per the vendor’s page captured 2 Nov 2026.

What are the best alternatives to GetResponse?

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: GetResponse alternatives.

Where this could be wrong

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.

Sources (11)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page www.getresponse.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  2. 2 Legal notice — found from the homepage www.getresponse.com Checked 16 Nov 2026 Details →
  3. 3 Campaigns & automation — found from sitemap www.getresponse.com Checked 16 Nov 2026 +1 earlier capture: 30 Sep 2026 Details →
  4. 4 Campaigns & automation — found from sitemap www.getresponse.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  5. 5 Deliverability infrastructure — found from sitemap www.getresponse.com Checked 16 Nov 2026 Details →
  6. 6 Deliverability infrastructure — found from sitemap www.getresponse.com Checked 16 Nov 2026 Details →
  7. 7 Consent, proof & tracking limits — found from sitemap www.getresponse.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
  8. 8 List ownership, import & exit — found from sitemap www.getresponse.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  9. 9 List ownership, import & exit — found from sitemap www.getresponse.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  10. 10 Integrations & API — found from sitemap www.getresponse.com Checked 16 Nov 2026 Details →
  11. 11 Integrations & API — found from sitemap www.getresponse.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →