Email Marketing & Newsletter
GetResponse
Provenance unknown Report an error0–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? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
GetResponse is an email marketing platform strongest on campaign and automation, where scores run 6 to 7: journeys for welcome, cart recovery and win-back with AI send-time optimisation, dynamically updated behaviour segments, and behavioural tags and scores are documented, though testing evidence covers only landing pages and signup forms. Integrations scored 4 to 6 on a 150+ integration directory and a deep Shopify connection. Deliverability is the genuine split, 4 to 7: some judges credited the documented dedicated IPs, warm-up programmes and a Deliverability Team working with mailbox providers, while others held scores down because we found no public information on SPF, DKIM or DMARC setup and the 99% figure appears only as a marketing number. Consent and proof is the weak spot at 2 to 3: list import is documented as single opt-in, and we found no public information on double opt-in, stored consent records, unsubscribe handling, or limiting open and click tracking. Pricing transparency scored a uniform 4; the captured pages give different figures for the entry price, $19 USD per month and $13.30 /mo.
Speaks for it
- Journeys for welcome, cart recovery and win-back with AI send-time optimisation and dynamically updated behaviour segments are documented.
- A Shopify connection imports customer data, product catalog, order information and abandoned checkouts, within a 150+ integration directory.
- Deliverability operations include dedicated IPs, standard and assisted IP warm-up, and a team engaging mailbox providers and blocklist operators.
- A free plan at $0 for up to 500 contacts and 1,000 landing-page visits per month, with a 14-day free trial requiring no credit card.
- The contracting entity is a Polish joint-stock company in Gdansk with a National Court Register number and VAT number, a named Data Protection Officer, and Bureau Veritas-accredited GDPR certification.
Held against it
- List import is documented as single opt-in, and we found no public information on double opt-in, on what a stored consent record contains, or on switching off open and click tracking.
- We found no public information on SPF, DKIM or DMARC setup, and the 99% deliverability figure appears only as a marketing number.
- Export is documented as personal data in.CSV format, and we found no public information on exporting engagement history, unsubscribe state, campaigns or templates.
- The captured pages give different figures for the lowest paid plan, $19 USD per month on one page and $13.30 /mo on another, and we found no public information on contact-tier prices beyond entry, overage rates or VAT treatment.
- We found no public information naming a data-centre provider or a complete subprocessor list, and the privacy notice states transfers outside the EEA are possible for chat, SMS, analytics, marketing, sales and CRM.
Best for
- You run an ecommerce store and want abandoned-checkout recovery and purchase-history segmentation on a documented Shopify connection.
- You need lifecycle journeys — welcome, cart recovery, win-back — with AI send-time optimisation and behaviour-based segmentation out of the box.
- You send at volume and want a dedicated IP with standard or assisted warm-up, accepting that the MAX2 tier is custom pricing.
- You require an EU-contracting vendor — a Polish joint-stock company in Gdansk with a named Data Protection Officer — and Google LLC in the USA, named as a recipient under SCCs and the Data Privacy Framework, is an acceptable transfer.
Avoid if
- Your compliance regime requires double opt-in or a demonstrable consent record; the documented list import is single opt-in.
- You must keep all processing inside the EEA; the privacy notice states transfers outside the EEA are possible for chat, SMS, analytics, marketing, sales and CRM.
- You need to compute your annual invoice before committing; the captured pages give different figures for the entry price and the MAX2 tier is custom pricing.
- Your deletion obligations require immediate erasure; the policy states deleted data stays in encrypted backups for up to 120 days.
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
Behaviour-based segmentation with dynamically updated segments, tags and scores on contact behaviour, and journeys for welcome, cart recovery and win-back with AI send-time recommendations — that is genuine lifecycle work, and purchase-history segmentation on Shopify data is documented. What holds it back is the measurement layer: A/B testing is documented for landing pages and signup forms, and I found no public information on email subject-line testing that reports significance, on branching journeys, or on holdout groups. 1 4 8 11
The Deliverability Engineer
Journeys for welcome, cart recovery and win-back with AI send-time optimisation, behaviour segmentation with dynamically updated segments, behavioural tags and scoring, and autoresponder scheduling in list or calendar view are all documented, on top of 200-plus templates with a drag-and-drop editor. I found no public information on holdout groups or significance-tested experiments, and the A/B testing I could see documented covers forms and landing pages rather than email content. 1 4 7 8
The Data Protection Officer
Journeys for welcome, cart recovery and win-back with AI send-time optimisation, dynamic segments by location, interests and behaviour, and 200-plus templates put this comfortably beyond a basic broadcaster. The evidence shows A/B testing only for landing pages and signup forms, and I found no public information on branching journeys or on tests that report significance rather than raw counts. 1 4 7 8
The Shop Owner
Journeys for welcome, cart recovery and win-back with AI send-time recommendations, behaviour-based dynamic segments, tags and scores are exactly what I run, and abandoned-checkout recovery is documented on the Shopify connection. I found no public information on branching on behaviour or data inside the journey builder, holdout groups, or email testing that reports significance — the A/B testing I can see is documented for signup forms and landing pages. 1 8 11 9 4
The Integrator
Templates with a drag-and-drop editor, behaviour tags and scores, dynamically-updated segments, and journeys for welcome, cart recovery and win-back with AI send-time optimisation clear the midpoint. The documented A/B testing covers landing pages and signup forms, and I found no public information on email subject-line testing, journey branching, holdout groups or significance reporting. 1 4 7 8
The Skeptic
Journeys for welcome, cart recovery and win-back with AI send-time optimisation, behaviour segmentation with dynamically-updated segments, tags and scores, and event-triggered autoresponders are all documented. But testing is evidenced only for landing pages and signup forms, and we found no public information on email split testing, branching logic, holdout groups or significance reporting. 1 4 8 11
Deliverability infrastructure
panel disagrees
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
Dedicated IP addresses on MAX, documented standard and assisted warm-up with an automatic send threshold, list-hygiene tooling that processes undeliverable addresses, and a Deliverability Team working with mailbox providers and blocklist operators — operational substance, not just the advertised 99% figure. But the foundation is undocumented: I found no public information on SPF, DKIM or DMARC setup, custom sending domains, or complaint-loop handling, and the strongest material sits on the MAX pages. 1 5 6
The Deliverability Engineer
The operational layer is documented unusually well: dedicated IPs with standard and assisted warm-up, reputation-adjusting automated sending controls, constant IP and domain reputation monitoring by a dedicated account manager, a deliverability team engaging mailbox providers and blocklist operators, and stated processing of undeliverable addresses under list-hygiene policies. But I found no public information on SPF, DKIM or DMARC setup, complaint-loop handling, inbox-placement testing or engagement-based sunsetting — and the advertised 99% deliverability figure is a marketing number I disregard on principle. 1 5 6
The Data Protection Officer
Dedicated IPs with both a standard and an assisted warm-up, a deliverability team engaging mailbox providers and blocklist operators, list-hygiene tooling and reputation monitored by a named customer experience manager read like deliverability operated as a service. But I found no public information on SPF, DKIM or DMARC setup, on complaint-loop handling or on inbox-placement testing, so the authentication basics rest on an advertised 99 percent figure. 1 5 6
The Shop Owner
A dedicated IP on MAX accounts, an assisted warm-up documented with a client case, reputation constantly watched by a dedicated manager, and a deliverability team working with mailbox providers and blocklist operators is deliverability run as a service on my behalf. What held it down: I found no public information on SPF, DKIM or DMARC setup, complaint-loop handling, seed or inbox-placement testing, so the documented foundation under the 99% marketing figure is thin. 5 6 1
The Integrator
Dedicated IPs, a documented warm-up programme (own schedule or assisted), published list-hygiene tooling and a named Deliverability Team that works with mailbox providers and blocklist operators are operations, not slogans. But I found no public information on SPF, DKIM or DMARC setup documentation, seed or inbox-placement testing or sunsetting, and the 99% figure appears only as a marketing rate. 5 6
The Skeptic
Standard and assisted IP warm-up with automated thresholds, reputation monitored by a dedicated vendor team, blocklist-operator engagement, and processing of undeliverable addresses are documented, with dedicated IPs on the top plans. But we found no public information on SPF, DKIM or DMARC setup or custom sending domains, and the 99% figure appears only as a marketing number. 1 5 6
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
List import is documented as single opt-in, with multiple consent fields available on signup forms and landing pages and reCAPTCHA against bots — that is consent capture, not proof. I found no public information on double opt-in, on what a stored consent record contains, on unsubscribe handling, or on any way to switch off or limit open and click tracking. 8 9 2
The Deliverability Engineer
Multiple consent fields on signup forms and landing pages are documented, with reCAPTCHA available to keep bots out. But the documented import path is single opt-in, and I found no public information on double opt-in handling, on what the consent record preserves — source, wording, IP — on one-click unsubscribe, or on any option to switch open and click tracking off. 8 9
The Data Protection Officer
The list-building pages document a single opt-in import, multiple consent fields and reCAPTCHA against bots, and the privacy policy lists subscriber rights including erasure. But I found no public information on double opt-in, on what a stored consent record captures, or on any way to switch off open and click tracking — and for a tool that records who opened what, that silence is what decides it. 2 8 9
The Shop Owner
Multiple consent fields on signup forms and landing pages, Bureau Veritas-accredited GDPR compliance and a privacy settings panel are real consent tooling, but list import is documented as single opt-in. I found no public information on double opt-in defaults, what the stored consent record contains, one-click unsubscribe handling, or any way to limit or switch off open and click tracking. 8 9 2
The Integrator
Multiple consent fields on signup forms and landing pages, reCAPTCHA and a Bureau Veritas-accredited GDPR certification are what the pages show; list import is documented as single opt-in, and I found no public information on double opt-in, on what a consent record stores, on unsubscribe handling, or on any way to switch open and click tracking off. 8 9 2
The Skeptic
Multiple consent fields on signup forms and landing pages is the whole consent story here, and the captured list-building page describes single opt-in import. We found no public information on double opt-in defaults, what the stored consent record contains, unsubscribe handling, or whether open and click tracking can be limited or switched off. 2 8 9
List ownership, import & exit
Show reasoningHide reasoning
How this is scored
Whether the list and its history remain the sender's: import with attributes intact, full export including engagement history, deletion that executes, and no metering that prices leaving out of reach.
0 — Export is addresses only; engagement history, segments and automations cannot leave.
3 — CSV import and export of subscriber fields, but engagement history and unsubscribe state are not exportable.
5 — Full subscriber export including custom attributes, subscription status and unsubscribe state, plus API access sufficient to sync elsewhere.
8 — Everything exportable in open formats — subscribers, engagement history, campaigns and templates — with documented deletion of a subscriber across all records, and no export throttling.
10 — Exit is a documented feature: full-fidelity export of the whole account, contractual data return, deletion that is evidenced rather than asserted, and migration tooling in both directions.
The CRM Manager
Import is well covered — file upload, manual copy-paste and nearly twenty sources, with names, emails and custom fields arriving intact, plus a documented API and CRM sync for keeping contacts current elsewhere. The exit side is thin: portability is documented only as personal data delivered in.CSV format, and I found no public information on exporting engagement history, unsubscribe state, campaigns or templates, or on documented deletion of a subscriber across all records. 8 11 2
The Deliverability Engineer
Import is documented from file upload, copy-paste, integrations and nearly twenty sources, with names, emails and custom fields arriving intact through the Shopify connection. For the way out, the privacy notice promises personal data as CSV and gives a 120-day encrypted backup window after deletion; I found no public information on exporting engagement history, campaign content or unsubscribe state, or on account-level export limits. 2 8 11
The Data Protection Officer
Import is well covered — file upload, manual entry and nearly twenty sources — personal data leaves in CSV form, and the privacy policy is candid that deleted data persists encrypted in backups for up to 120 days. I found no public information on exporting engagement history or unsubscribe state, no evidence of full-account export, and the only exit-adjacent item is account migration support listed in the custom-priced top tier. 2 8 9
The Shop Owner
Import is well covered — file upload, copy-paste, integrations, nearly 20 sources with custom fields — and the privacy policy promises personal data in CSV format, with an API to build against and migration support listed on the top plan. I found no public information on exporting engagement history, campaigns or templates, or on documented deletion of a subscriber across all records; the only retention figure is a 120-day encrypted backup window after deletion. 8 2 11 9
The Integrator
Import is well documented — file upload, manual entry and integrations from nearly 20 sources with custom fields — and the legal notice names CSV as the portability format and a 120-day encrypted backup window after deletion; but I found no public information on exporting engagement history, unsubscribe state, campaigns or templates, and account migration support appears only in the custom-priced top tier. 8 2 9
The Skeptic
Import from nearly 20 sources with custom fields, a CSV export, and API access are documented, with account migration support appearing only in a custom-priced tier. We found no public information on exporting engagement history or unsubscribe state, and deletion is evidenced only through the 120-day backup retention note. 2 8 9 11
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
A maintained directory of 150-plus integrations with CRM, ecommerce and analytics categories, a deep Shopify connection importing customers, product catalog, orders and abandoned checkouts, and an advanced API for building your own integration with a partner programme behind it. I found no public information on webhooks, retries, documented rate limits or a sandbox — the difference between a broad catalogue and one I can build a lifecycle programme on. 1 10 11
The Deliverability Engineer
A directory of 150-plus integrations with counted ecommerce and CRM categories, a Shopify integration documented to import customer, product and order data, CRM sync with automatic contact updates, and API docs plus a partner program for building your own. I found no public information on webhooks, documented rate limits or a sandbox, which is what separates a real connection surface from a listing. 1 8 10 11
The Data Protection Officer
A 150-plus directory across sixteen pages with Shopify, WooCommerce and the major CRMs, product catalog and abandoned-checkout data flowing in from Shopify, CRM sync that automatically updates contact data, and an advanced API for building your own connections. I found no public information on webhooks, retry behaviour, rate limits or a sandbox, so someone building against this API does so without documented limits. 1 8 10 11
The Shop Owner
The Shopify connection imports customer data, the product catalog, order information and abandoned checkouts, and drives recovery workflows and purchase-history segmentation — the plumbing my shop needs — on top of a directory of 150+ integrations across ecommerce and CRM and an advanced documented API. I found no public information on event webhooks with retries, documented rate limits, or a sandbox, and I can see data flowing in more clearly than events flowing back out. 11 10 1 8
The Integrator
The breadth is real — 150+ integrations across fourteen categories, a maintained Shopify connection importing customer, product, order and abandoned-checkout data, CRM sync, and an API you can build your own integration against — but this is the part I cannot wire in with confidence: I found no public information on webhooks, retry behaviour, documented rate limits, a sandbox or an API deprecation policy. 10 11 1
The Skeptic
A directory of 150+ integrations across sixteen pages, with a genuinely deep Shopify connection importing orders, abandoned checkouts and product catalogues, CRM reach through partners, and an API plus partner programme for custom builds. But we found no public information on webhooks, documented rate limits, or a sandbox. 1 9 10 11
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where subscriber data and behavioural tracking live, who the contracting entity is, and which subprocessors touch the send. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily.
0 — US vendor and contracting entity, US hosting, subprocessors unnamed; subscriber behaviour leaves the EU with no stated basis.
3 — EU hosting offered as an option or for storage only, while sending, tracking or support access remains non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — sending infrastructure, analytics, support tooling — are non-EU without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, complete subprocessor list published, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, sending and every subprocessor in the EU, certification published, and no transfer that needs a Schrems II argument to survive.
The CRM Manager
The contracting entity is GetResponse S.A., a Polish joint-stock company in Gdansk, with a designated Data Protection Officer, GDPR compliance certified by Bureau Veritas, and the one named non-EEA processor — Google LLC in the USA — carrying Data Privacy Framework membership and standard contractual clauses. Weighing this as heavily as I do: the policy itself says transfers outside the EEA are possible for chat, SMS, analytics, marketing, sales and CRM functionality, and I found no public information on where subscriber data is hosted, on a named data-centre provider, or on a complete published subprocessor list. 2 9
The Deliverability Engineer
The contracting entity is GetResponse S.A., a Polish joint-stock company in Gdansk with a named Data Protection Officer, processing is stated to be mainly in the EEA, and the named non-EEA recipient — Google LLC in the USA — carries SCCs and Data Privacy Framework membership, alongside Bureau Veritas-accredited GDPR certification. For a buyer who weighs this heavily, the holes are real: I found no public information naming the data-centre or hosting provider, one named subprocessor is not a published complete list, and chat, SMS, analytics, marketing, sales and CRM processing is acknowledged to leave the EEA for some functions. 2 9
The Data Protection Officer
The contracting entity is a Polish joint-stock company in Gdansk with a named Data Protection Officer, and recipients of the data are stated to be based mainly in the EEA. Chat, SMS, analytics, marketing, sales and CRM processing can, however, leave the EEA under standard contractual clauses, with Google LLC in the USA named as a recipient — a transfer my complaints file would have to defend with a Schrems II argument. I found no public information naming a data-centre provider or publishing a complete subprocessor list. 2
The Shop Owner
The contracting entity is a Polish joint-stock company in Gdansk with a designated data protection officer, recipients are stated to be mainly in the EEA, and the non-EU subprocessor I can see — Google LLC in the USA — is named with SCCs and Data Privacy Framework membership as the stated basis. I weigh this heavily and it stops short of full evidence: transfers outside the EEA are stated as possible for chat, SMS, analytics, marketing, sales and CRM, and I found no public information naming the data-centre provider or publishing a complete subprocessor list. 2 9
The Integrator
The independent sovereignty check returned unknowns on ownership and residency, so I am left with the vendor's own legal notice: a Polish contracting entity fully identified with company and VAT numbers (the captured pages give different versions of its legal form), recipients based mainly in the EEA, Google LLC in the USA named as a non-EEA recipient with SCCs and Data Privacy Framework status as the stated basis, and a Bureau Veritas-accredited GDPR certification. A complete published subprocessor list, a named data-centre provider and an EU-only chain are what would move it, and I found no public information on any of them. 2 9
The Skeptic
An EU contracting entity in Gdansk with registry numbers, a named Google LLC transfer carrying SCC and Data Privacy Framework as its stated basis, and the privacy notice conceding transfers outside the EEA for chat, SMS, analytics, marketing, sales and CRM. But hosting location and the data-centre provider are not shown, no complete subprocessor list appears, and recipients are promised only to be "mainly" in the EEA. 2 9
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 free tier with a 500-contact cap and named features is public, and marketing automation and segmentation are listed in the paid plans with the lowest plan starting at $13.30 /mo — though a captured page gives the Basic plan entry as 19 USD per month, so the pages give different figures for the entry price. I cannot compute a real invoice from what is published: no contact-tier ladder for larger lists, no overage rates, no VAT treatment, and the MAX2 plan is custom pricing. 9 4 7
The Deliverability Engineer
A free tier with its 500-contact and 1,000-monthly-visit limits, a 14-day no-credit-card trial and badge removal on paid plans are public; the captured pages give different figures for the lowest paid plan. I found no public information on send limits per tier, overage rates or VAT treatment, and the dedicated-IP and transactional tiers are custom-priced. 4 7 9
The Data Protection Officer
A free tier for 500 contacts and a stated lowest paid plan are public, with unlimited autoresponder sends and the free landing-page visit cap stated, and the paid tiers are listed by feature. The captured pages give different figures for the cheapest paid plan, and I found no public information on contact-tier prices beyond the free 500, overage rates or VAT treatment, so the real invoice for a grown list is not computable from public pages. 4 7 9
The Shop Owner
A free tier at $0 for up to 500 contacts, a stated paid entry point and some feature boundaries are public — marketing automation sits in paid plans, dedicated IP in MAX, MAX2 is custom pricing — though the captured pages give different figures for the entry price ($13.30 /mo on one, 19 USD per month on another). I found no public information on contact-tier prices beyond the entry point, overage rates or VAT treatment, so I cannot compute the annual invoice for my list size and send volume. 9 4 7
The Integrator
The captured pages give different figures for the entry price — 19 USD per month on one page, $13.30 /mo on another — while the free tier is defined (500 contacts, 1,000 monthly landing-page visits) and the top tier is custom-priced; I found no public information on send limits, overage rates or VAT treatment, so a buyer cannot compute the invoice for a given list size from these pages alone. 4 9 7
The Skeptic
The captured pages give different figures for the lowest plan — "$19 USD per month" on one page and "$13.30 /mo" on another — and beyond entry prices we found no public information on the contact tier ladder above them, overage rates, or VAT treatment. Dedicated IP addresses and transactional sending sit in a custom-priced tier, so the real invoice for a serious sender is a sales conversation. 4 7 9
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- 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.
- 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 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 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 (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.getresponse.com Checked 22 Sep 2026 Details →
- 2 Legal notice — found from the homepage www.getresponse.com Checked 30 Sep 2026 Details →
- 3 Campaigns & automation — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
- 4 Campaigns & automation — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
- 5 Deliverability infrastructure — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
- 6 Deliverability infrastructure — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
- 7 Consent, proof & tracking limits — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
- 8 List ownership, import & exit — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
- 9 List ownership, import & exit — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
- 10 Integrations & API — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →
- 11 Integrations & API — found from sitemap www.getresponse.com Checked 30 Sep 2026 Details →