GetResponse
Provenance unknown Report an errorPanel 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
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
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 from GetResponse S.A., a Polish joint-stock company in Gdańsk. It scores strongest on campaign and automation and integrations: the captured pages document a drag-and-drop editor with 100+ templates, behaviour-triggered workflows fed by Shopify abandoned-checkout data, and 150+ integrations. Deliverability scores cluster at 6 — dedicated IPs on MAX accounts and standard plus assisted warm-up are documented, while no public information covers SPF, DKIM or DMARC set-up or complaint feedback loops. Consent and proof is the weakest criterion and widest spread: import is documented as single opt-in, no public information covers double opt-in, unsubscribe handling or switching tracking off, and the judge at 2 held that import path against the consent-field apparatus others credited. Sovereignty scores sit at 4 — recipients are based mainly in the EEA, but transfers outside the EEA are possible for chat, SMS, analytics, marketing, sales and CRM, Google LLC in the USA is named, and no data-centre country is named. Pricing transparency is capped by differing entry-price figures of 19 USD per month and $13.30 /mo.
Speaks for it
- Behaviour-triggered automation workflows with conditions and filters, including abandoned-cart journeys fed by Shopify order and checkout data
- 150+ integrations including a documented Shopify import of customers, product catalog, orders and abandoned checkouts, with public API documentation
- Dedicated IPs on MAX accounts with standard and assisted warm-up and a deliverability team working with mailbox providers and blocklist operators
- A free tier at $0 with a list up to 500 contacts and a 14-day trial requiring no credit card
- A Polish joint-stock contracting entity with a National Court Register number and EU VAT ID, a designated Data Protection Officer, SCCs for third-country transfers and Bureau Veritas-accredited GDPR compliance
Held against it
- Consent and proof scores span 2-4, with list import documented as single opt-in and no public information on double opt-in, per-subscriber consent records or switching open and click tracking off
- The captured pages give different figures for the entry price (19 USD per month and $13.30 /mo), the MAX2 tier is custom-priced, and no public information covers contact-tier scaling, overage rates or VAT treatment
- No data-centre country is named, transfers outside the EEA are possible for chat, SMS, analytics, marketing, sales and CRM, and Google LLC in the USA is a named recipient
- No public information covers SPF, DKIM or DMARC set-up guidance, complaint feedback loops or inbox-placement testing, and the 99% deliverability figure is an advertised rate
- The documented CSV export is the privacy policy's portability promise rather than a self-service product export, and the migration service captured runs inbound only
Best for
- You run a Shopify store and want abandoned-cart recovery and purchase-history segmentation wired directly from order data
- You want to start on a free tier at $0 with a list up to 500 contacts and a 14-day trial requiring no credit card
- You send at volume on the MAX tier and want dedicated IPs with assisted warm-up and reputation monitoring
- You need a Polish contracting entity with SCCs and a designated Data Protection Officer for your procurement paperwork
Avoid if
- You must run double opt-in or produce a per-subscriber consent record with timestamp and source — the documented import path is single opt-in
- You need to know your real invoice for a given list size before committing — the captured pages give different entry prices (19 USD per month and $13.30 /mo) and no public information covers contact-tier scaling
- Your compliance review cannot name a US subprocessor — Google LLC in the USA is a named recipient of transfers outside the EEA under SCCs and the Data Privacy Framework
- You expect documented self-service exit tooling — the migration service captured runs into the product ("Move to GetResponse")
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 3.5 of 5 |
| Deliverability infrastructure | 3 of 5 |
| Consent, proof & tracking limits | 2 of 5 |
| List ownership, import & exit | 2.5 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 2 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
Behaviour triggers, abandoned-cart automation fed by shop data, engagement scoring and dynamically updated segments put this well past a broadcast tool, with AI send-time recommendation documented. The A/B evidence covers landing pages and signup forms rather than campaign testing that reports significance, and branching appears only as conditions and filters rather than a documented visual journey builder. 3 11 3 1 8 7
The Deliverability Engineer
Workflows branch on behaviour with conditions and filters, Shopify purchase and abandoned-checkout events trigger journeys, dynamic segments update themselves, and AI chooses the send time — that is close to the top of what a journey product should document. The testing story is thinner: A/B testing is documented for landing pages and signup forms, and we found no public information on campaign testing that reports significance or on holdout groups. 3 11 1 4
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
The Shop Owner
The shop-relevant journeys are documented — abandoned cart emails, purchase-history segmentation, product recommendations, and behaviour-triggered workflows with conditions and filters — plus a drag-and-drop editor and AI-recommended send times. A/B testing is only shown for landing pages and forms on paid plans, and we found no public information on holdout groups or testing that reports significance. 3 3 7 1 8 11 4
The Integrator
A drag-and-drop email creator with 100+ templates, autoresponders triggered by subscription time, delay or exact hour, behaviour-based automation with conditions and filters, dynamic segments on location, interests and behaviour, and prebuilt workflows for welcome series and abandoned carts make this a full campaign tool, not a broadcaster. Send-time recommendation by AI, contact scoring and shop-data-driven workflows push toward the journey-builder end; we found no public information on documented branching, holdout groups or significance testing in what we captured. 3 4 8 3 1
The Skeptic
Drag-and-drop editor with 100+ templates, dynamic and behavioural segmentation, automation workflows with conditions and filters, AI send-time recommendation, and Shopify abandoned-checkout events feeding automation. The A/B testing the pages document covers landing pages (paid plans only) and signup forms, and we found no public information on email campaign testing with significance reporting or holdout groups. 3 4 11 3 7 1
Deliverability infrastructure
Show reasoningHide reasoning
How this is scored
Whether the mail arrives — authentication, sending reputation, bounce and complaint handling — judged on what the vendor documents rather than the inbox rate it advertises.
0 — The product does not send mail itself; delivery runs through the customer's own mail server with no sending infrastructure provided.
3 — Sending through the vendor's infrastructure with SPF and DKIM set-up for the sender's domain documented; bounce handling and reputation measures are basic or not described.
5 — SPF, DKIM and DMARC guidance with an authenticated custom sending domain, automatic suppression of hard bounces and complaints, and help-centre guidance on deliverability and list hygiene.
8 — Dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, complaint feedback loops stated, and reputation reporting per sending domain.
10 — Deliverability is operated as a service: reputation monitoring surfaced to the customer, per-domain and per-ISP diagnostics, enforced authentication before first send, and postmaster or blocklist handling the vendor documents doing on the customer's behalf.
The CRM Manager
Dedicated IPs with an assisted warm-up that sets automated sending thresholds, constant IP and domain reputation monitoring by a dedicated Customer Experience Manager, and a Deliverability Team working with mailbox providers and blocklist operators are documented. I found no public information on SPF, DKIM or DMARC set-up for the sender's domain, seed or inbox-placement testing, or complaint feedback loops. 5 6
The Deliverability Engineer
The captured pages document dedicated IP addresses on the MAX plan, a standard and an assisted warm-up with automated sending thresholds that adjust as reputation builds, a shared IP pool for overflow, processing of undeliverable addresses, and a deliverability team that deals with mailbox providers and blocklist operators — genuine infrastructure documentation, on the right side of my ledger. What I could not find: any page on SPF, DKIM or DMARC set-up for the sender's domain, complaint feedback loops, engagement-based sunsetting, or reputation reporting surfaced to the customer; and the advertised 99% deliverability rate I disregard as a matter of course. 5 6
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
The Shop Owner
Dedicated IP on MAX accounts, standard and assisted warm-up, reputation monitored by a dedicated Customer Experience Manager, a Deliverability Team working with mailbox providers and blocklist operators, and list-hygiene tooling with undeliverable-address processing are all documented. We found no public information on SPF, DKIM or DMARC set-up guidance, seed or inbox-placement testing, or complaint feedback loops. 5 6
The Integrator
Dedicated IPs on MAX accounts, documented standard and assisted IP warm-up, IP and domain reputation monitored by a named deliverability team that also works with blocklist operators, and list hygiene including processing of undeliverable addresses take this past basic sending. We found no public information on SPF, DKIM or DMARC set-up guidance, seed or inbox-placement testing, complaint feedback loops or engagement-based sunsetting, and the dedicated-IP and warm-up material sits with the MAX tier. 5 6
The Skeptic
Dedicated IPs on MAX accounts with documented standard and assisted warm-up, an automated send threshold, vendor-managed ISP and blocklist relationships, constant reputation monitoring by a named human role, and list-hygiene tooling. We found no public information on SPF/DKIM/DMARC set-up guidance, complaint feedback loops or inbox-placement testing, and the 99% deliverability figure is an advertised rate rather than documented infrastructure. 5 6 1
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
Consent fields on signup forms, consent verification, and targeting by consent status across multiple consent fields are documented, which is more than a checkbox. I found no public information on double opt-in, a stored consent record with timestamp and source, or any ability to switch open and click tracking off; the import flow the captured pages describe is single opt-in. 9 8 9 8
The Deliverability Engineer
Signup forms with GDPR consent fields, multiple consent statuses to target on, and reCAPTCHA are documented, and single opt-in list import is offered openly. We found no public information on double opt-in confirmation, the consent record kept per subscriber, unsubscribe handling, or any way to switch open and click tracking off. 8 9 8
The Data Protection Officer
Consent fields, multiple consent fields with targeting by consent status, and consent verification are documented, but the import path is described as single opt-in, and I found no public information on double opt-in, a per-subscriber consent record with timestamp, source and IP, unsubscribe handling, or any way to switch off open and click tracking — the highlighted Google Analytics, Tag Manager and Facebook Pixel integrations point the other way. For a sender who must survive a complaint, the burden-of-proof side is unevidenced. 8 9 8 2
The Shop Owner
Consent fields are built into sign-up forms, with multiple consent fields, consent-status targeting, consent verification, reCAPTCHA against bots, a right to withdraw consent and a privacy settings panel. We found no public information on double opt-in, unsubscribe handling, a stored per-subscriber consent record, or open and click tracking that can be switched off — and list import is documented as single opt-in. 2 8 9 8
The Integrator
Signup forms with consent fields built in, multiple consent fields for targeting by consent status, subscriber consent verification, reCAPTCHA, a privacy settings panel and Bureau Veritas-accredited GDPR certification describe a real consent workflow. We found no public information on double opt-in, per-subscriber consent records with timestamp and source, unsubscribe handling, or any way to switch open or click tracking off, and the documented list import is single opt-in. 2 8 9 8
The Skeptic
Consent fields — multiple ones, with sending based on consent status — plus reCAPTCHA and a consent-verification pitch are real sign-up apparatus, but the documented import path is single opt-in. We found no public information on double opt-in, unsubscribe handling, a per-subscriber consent record, or tracking that can be switched off, while analytics pixels are promoted in a few clicks. 8 9 7 8
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
Import by file, manual entry or integration from nearly twenty sources with custom data fields, a CSV export, documented erasure with a stated 120-day backup window, and an API for building your own integrations. I found no public information on exporting engagement history or campaigns, and the migration support I can see runs inbound only. 2 8 8 10 11
The Deliverability Engineer
Import is well covered — file upload, copy-paste and nearly 20 sources with custom fields carried over — and an API with public documentation exists; the privacy policy also promises personal data delivered out in CSV format. We found no public information on full subscriber-list export including engagement history, per-subscriber deletion, or export throttling, and the migration service documented runs into the product, not out of it. 2 8 8
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
The Shop Owner
Import is well covered — file upload, manual entry, copy-paste and nearly 20 sources with data fields — and there is CSV export, a documented erasure right with a stated 120-day encrypted backup window, and an API for custom integrations. We found no public information on exporting engagement history or campaigns and templates, and migration support is documented for moving in, not out. 2 8 10 4 8
The Integrator
Import by file upload, manual entry or copy-paste and from nearly 20 sources with data fields, a stated.CSV export, erasure rights documented with a 120-day encrypted backup window after deletion, and an API for custom integrations cover the middle ground. We found no public information on export of engagement history, campaigns or templates; the migration offer captured is "Move to GetResponse", and we found no public information on outbound migration tooling or export throttling. 2 8 10 4
The Skeptic
Import from nearly twenty sources with custom fields, an API for custom integrations, inbound migration support, the right to erasure with a stated 120-day encrypted backup window, and CSV delivery of personal data. The export evidence is the privacy policy's portability promise rather than a documented self-service export, and we found no public information on field mapping, engagement-history or template export, or export throttling. 2 8 10 11 4
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
A directory of 150+ integrations across commerce, CRM and connector platforms, a documented Shopify integration importing orders and abandoned checkouts, CRM connectors for Pipedrive, HubSpot and Salesforce, and API documentation for custom builds. I found no public information on event webhooks with retries, documented rate limits or a sandbox. 10 11 11 3 1
The Deliverability Engineer
A directory of 150+ integrations across ecommerce, CRM and connector platforms, a Shopify integration that imports orders, product data and abandoned checkouts, and an advanced API with public docs and a partner programme. We found no public information on webhooks with retries, documented rate limits or a sandbox, and bidirectionality is shown only in one direction — verification results written back as custom fields. 10 11 1
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
The Shop Owner
The strongest area for a shop: the Shopify integration imports customer data, product catalog, order information and abandoned checkouts, with FAQs, a guide and a setup video, backed by 150+ integrations across ecommerce, CRM and payment categories plus public API documentation. We found no public information on event webhooks with retries, documented rate limits or a sandbox, which I would need before wiring my orders deeper. 10 11 3 1 11
The Integrator
150+ integrations in a fourteen-category directory, a vendor-maintained Shopify page documenting customer, product, order and abandoned-checkout imports with requirements and setup support, CRM listings, connector platforms and an advanced API with API docs give me a surface to wire against. But we found no public information on rate limits, event webhooks with retries, a sandbox, or API versioning with a deprecation policy, the Shopify flow is documented as import into GetResponse, and the directory openly recruits third-party integration partners. 10 11 3 1
The Skeptic
A directory of 150+ integrations across e-commerce, CRM and connector-platform categories, a deep Shopify integration importing product, order and abandoned-checkout data, and public API documentation with a partner programme. We found no public information on event webhooks with retries, documented rate limits, a sandbox, or maintained bidirectional sync. 10 11 3 1 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. Dimensions not proven either way are unknown, not non-European.
0 — Vendor, contracting entity and hosting shown to be outside the EU, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist and one European element is proven (an EU contracting entity or representative, or EU hosting as an option); the rest of the chain is not stated.
5 — An EU contracting entity and EU hosting stated, with a data processing agreement; sending, tracking or support providers are not all shown to be European or are named without a stated safeguard.
8 — EU or DACH hosting on named infrastructure, EU contracting entity, the subprocessor list published with locations including the sending infrastructure, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, sending and every subprocessor in the EU, certification published, and no transfer that needs a Schrems II argument to survive.
The CRM Manager
The contracting entity is a Polish joint-stock company in Gdańsk with registry and VAT numbers, processing terms run through the Terms of Service for EEA customers, and the policy states recipients are based mainly in the EEA while naming a US transfer to Google under SCCs and the Data Privacy Framework. No data-centre country is stated anywhere I read, so hosting is unproven — a gap the customer must close on a dimension I weight heavily. 2
The Deliverability Engineer
A Polish joint-stock company in Gdansk with a court register number and EU VAT ID is the contracting entity, processing terms in the Terms of Service apply when the customer is established in the EEA, standard contractual clauses are invoked for transfers, and a Bureau Veritas GDPR accreditation is claimed. No data-centre country is named — the residency statement covers recipients of data, not hosting — and the only named subprocessor is Google LLC in the USA. 2 9
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
The Shop Owner
A Polish contracting entity with full registry and VAT details, a designated Data Protection Officer, standard contractual clauses and Bureau Veritas-accredited GDPR compliance are documented, and non-EEA transfer to Google LLC under the Data Privacy Framework is named. No data-centre country is stated anywhere we read, and transfers outside the EEA are flagged as possible for chat, SMS, analytics, marketing, sales and CRM, so the chain cannot be confirmed European end to end. 2 9 1
The Integrator
The contracting entity is Polish — GetResponse S.A., Gdańsk, with KRS and VAT numbers published — processing terms act as a DPA for EEA customers, SCCs govern third-country transfers, and Google LLC in the USA is named as a recipient under the Data Privacy Framework; add the GDPR certification and the European core is proven. We found no public information on hosting or data-centre location, a published subprocessor list or the sending infrastructure's location, and the privacy policy itself limits its EEA claim to recipients being "based mainly in the European Economic Area", with transfers outside the EEA possible for chat, SMS, analytics, marketing, sales and CRM. 2 9
The Skeptic
A Polish joint-stock company with registry number, VAT ID and a named Data Protection Officer, and data-processing terms in the Terms of Service for EEA customers — real European anchors. But the EEA statement concerns recipients of transfers rather than a hosting location, transfers outside the EEA are acknowledged for Chat, SMS, analytics, marketing, sales and CRM with SCCs and Google LLC in the USA named, and hosting country, sending infrastructure and a published subprocessor list with locations are not stated. 2
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 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 plan with its limits is spelled out (500 contacts, 1,000 landing-page visits a month) alongside monthly price points for the lowest and Basic plans, and MAX2 is marked as custom pricing. How the invoice scales with contact count past the free tier is not shown and I found no public information on overage rates or VAT treatment; the captured pages give different figures for the entry price ("$13.30 /mo" and "19 USD per month"), so a buyer must reconcile them with the vendor. 9 9 4 7
The Deliverability Engineer
A free tier up to 500 contacts and published starting points exist, but the captured pages give different figures for the entry price — 19 USD per month for Basic and 13.30 per month for the lowest plan — and the MAX2 tier is custom pricing. We found no public information on how cost scales with contacts or send volume, on overage rates or on VAT treatment, so a real invoice cannot be computed from these pages. 9 9
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
The Shop Owner
A priced free plan with a 500-contact limit, clear free-plan limits like 1,000 landing-page visits a month, and a 14-day trial are public, but the captured pages give different figures for the entry price — "The lowest plan starts at $13.30 /mo" on one and "GetResonse basic plan start at 19 USD per month." on another. How cost scales with contact count, the billing period, VAT treatment and add-on prices are not shown, so the real invoice for a given list cannot be computed from public pages. 4 7 9 1 9
The Integrator
The free tier is fully specified — $0, a list up to 500 contacts, landing pages capped at 1,000 unique visits a month — and a 14-day trial needs no credit card. The captured pages give different figures for the entry price — "GetResonse basic plan start at 19 USD per month" on the autoresponder page and "The lowest plan starts at $13.30 /mo" on the plan page — and we found no public information on contact-tier pricing, overage rates or VAT treatment. 4 7 9
The Skeptic
The free tier is fully specified at $0 with a 500-contact limit and named features, and the 14-day trial terms are clear. The captured pages give different figures for the entry paid price — "19 USD per month" on some pages and "$13.30 /mo" on others — with the enterprise tier custom-priced, and we found no public information on contact-tier scaling, overage rates or VAT treatment. 1 4 9 9 4
European sovereignty — proven facts
2 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 PL
unverified
Why unverified?Jurisdiction is taken from the privacy policy's contact details rather than a dedicated imprint, and no excerpt names a parent company, but GetResponse S.A. is treated as the parent since nothing marks it as a subsidiary, branch or regional entity. |
2/2 pts | 2 Report an error |
|---|---|---|---|
| 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
- Evidence ages. The oldest capture behind this page is from 30 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 — Legal entity. Jurisdiction is taken from the privacy policy's contact details rather than a dedicated imprint, and no excerpt names a parent company, but GetResponse S.A. is treated as the parent since nothing marks it as a subsidiary, branch or regional entity.
- Weak sourcing — Hosting location. The passage concerns recipients and transfers of personal data, not the stated location of the hosting infrastructure, and no data-centre country is named.
- 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.
- 4 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
- 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
- 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 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
- 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. 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 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 2 Legal notice — found from the homepage www.getresponse.com Checked 16 Nov 2026 Details →
- 3 Campaigns & automation — found from sitemap www.getresponse.com Checked 16 Nov 2026 +1 earlier capture: 30 Sep 2026 Details →
- 4 Campaigns & automation — found from sitemap www.getresponse.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 5 Deliverability infrastructure — found from sitemap www.getresponse.com Checked 16 Nov 2026 Details →
- 6 Deliverability infrastructure — found from sitemap www.getresponse.com Checked 16 Nov 2026 Details →
- 7 Consent, proof & tracking limits — found from sitemap www.getresponse.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 8 List ownership, import & exit — found from sitemap www.getresponse.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 9 List ownership, import & exit — found from sitemap www.getresponse.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 10 Integrations & API — found from sitemap www.getresponse.com Checked 16 Nov 2026 Details →
- 11 Integrations & API — found from sitemap www.getresponse.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →