Email Marketing & Newsletter
MailerLite
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by UAB MailerLite · www.mailerlite.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.
No written verdict for this product
The panel scored MailerLite, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.
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
Segmentation is the strong suit: prebuilt engagement, geography and purchase-history segments, combinable with custom fields and auto-updating, which is real behaviour targeting rather than list picks. Automations exist with multiple triggers and even a webhook action, but on everything I judge journeys by — branching on behaviour, A/B testing that reports significance, holdouts, dynamic content — we found no public information on any of it. 2 2 6 9 14
The Deliverability Engineer
The captured pages document a drag-and-drop editor with segmentation by engagement, geography, interests, purchase history and signup source, plus multi-step automations with per-tier limits and a webhook action usable inside workflows. I found no public information on subject-line A/B testing for campaigns or a journey builder that branches on behaviour, so this sits solidly mid-table rather than higher. 2 6 14
The Data Protection Officer
Drag-and-drop plus HTML editors, reusable templates and genuinely deep segmentation — by engagement, geography, purchase history and signup source, with seven pre-built segments that self-update — go beyond the mid description, and automations run on form and group triggers with a webhook action available. We found no public information on a visual journey builder with branching, send-time optimisation, or campaign A/B testing that reports significance. 2 2 6 9 14
The Shop Owner
Multi-step automations are real and tiered — three on the free plan, fifty on Comfort, unlimited with multiple triggers on Power — and segmentation reaches purchase history through the e-commerce integrations plus engagement, geography and signup source, which is the targeting my shop sells against. We found no public information on campaign A/B testing, journey branching or dynamic content per segment, so I stop short of the top half. 2 1 2 6
The Integrator
The segmentation is genuinely grown-up — engagement, geography, time zone, purchase history and signup source, combinable with custom fields and auto-updating — and automations scale from three on the free tier to unlimited with multiple triggers, with a webhook action available inside the workflow. What keeps this off the upper rungs is testing and journey sophistication: I found no public information on subject-line A/B testing, dynamic per-segment content or send-time optimisation, and the only A/B testing the pages describe is PostHog analysing MailerLite's own product usage. 2 6 14
The Skeptic
The three editors, template library and genuinely deep segmentation — engagement, geography, purchase history, signup source, combinable custom fields with auto-updating segments — are publicly documented, and automations go well beyond a single welcome mail with per-form and group triggers plus tiered automation counts. But I found no public information on subject-line A/B testing for senders, journey branching, dynamic content, or significance reporting; the only A/B testing in evidence is the vendor testing its own product through an analytics subprocessor. 2 1 2 6 9
Deliverability infrastructure
Show reasoningHide reasoning
How this is scored
Whether the mail arrives — authentication, sending reputation, bounce and complaint handling — judged on what the vendor documents rather than the inbox rate it advertises.
0 — No documentation of authentication or bounce handling; deliverability appears only as a marketing number.
3 — SPF and DKIM setup documented, but no DMARC guidance, no stated bounce policy and shared sending only.
5 — SPF, DKIM and DMARC documented with a custom sending domain, automatic hard-bounce suppression, and complaint-loop handling stated.
8 — The above plus dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, and published guidance on list hygiene.
10 — Deliverability is operated as a service: reputation monitoring surfaced to the customer, per-domain and per-ISP diagnostics, enforced authentication before first send, and postmaster or blocklist handling the vendor documents doing on the customer's behalf.
The CRM Manager
SPF, DKIM and domain verification are documented with automatic DNS configuration and alignment guides, and bounce handling is unusually well specified: hard bounces auto-removed, three consecutive soft bounces treated as a hard bounce, hard and soft broken out per campaign report. We found no public information on DMARC guidance, complaint-loop handling, warm-up for the Enterprise dedicated IP, or seed and inbox-placement testing. 2 7 8
The Deliverability Engineer
Authentication is documented end to end — DKIM, SPF and domain verification records with an automated DNS setup path — and bounce discipline is real: hard bounces auto-suppressed, three consecutive soft bounces treated as hard, and a list-verification tool recommended. I found no public information on DMARC guidance, on warm-up for the dedicated IP that appears in the enterprise tier, or on inbox-placement testing, so the documented stack stops short of the top. 2 7 8
The Data Protection Officer
SPF, DKIM and domain verification records are documented for both automatic and manual setup, hard bounces are automatically suppressed and three consecutive soft bounces are treated as hard, which is a real, documented bounce policy. We found no public information on DMARC guidance or complaint-loop handling, and nothing on warm-up or inbox-placement testing; a dedicated IP appears only as an Enterprise feature. 2 7 8
The Shop Owner
Domain authentication is properly documented — automatic DNS setup, DKIM as a CNAME record, SPF as TXT, plus domain verification — and bounce handling is an actual policy: hard bounces auto-removed, three soft bounces in a row treated as hard. We found no public information on DMARC guidance, complaint-loop handling or IP warm-up, and the dedicated IP appears only in the Enterprise tier. 7 8 2
The Integrator
SPF, DKIM and custom-domain authentication are documented down to the CNAME and TXT records with an automatic setup path, and bounce handling is precise: hard bounces auto-removed, three consecutive soft bounces promoted to hard. I found no public information on DMARC guidance, complaint-loop handling, dedicated-IP warm-up or inbox-placement testing; list verification is referred out to a separate tool, and the dedicated IP appears only in the custom-priced tier. 2 7 8
The Skeptic
Domain authentication is documented down to the record types — DKIM as CNAME, SPF as TXT, domain verification TXT — with an automatic DNS flow and a pending status while records propagate, and the bounce policy is stated precisely: hard bounces auto-removed, three consecutive soft bounces treated as hard. I found no public information on DMARC guidance, complaint-loop handling, warm-up for the Enterprise dedicated IP, or any inbox-placement testing; deliverability support sits inside an unpriced top tier. 2 7 8
Consent, proof & tracking limits
Show reasoningHide reasoning
How this is scored
How subscribers arrive and what the sender can prove afterwards: double opt-in, logged consent, unsubscribe handling, and whether open and click tracking can be limited or switched off.
0 — Single opt-in with no consent record; tracking is always on and cannot be disabled.
3 — Double opt-in available but not the default, and the consent record is a timestamp without the source, IP or the wording consented to.
5 — Double opt-in as the documented default with a stored consent record including source and timestamp, one-click unsubscribe, and tracking that can be turned off per campaign.
8 — Consent is reproducible as evidence: the confirmation mail and form wording versioned and retrievable per subscriber, unsubscribe honoured across lists, tracking off-by-default available, and retention rules for inactive subscribers.
10 — Built for the burden of proof: a per-subscriber consent history an authority would accept, documented handling of Art. 15 access and Art. 17 erasure requests, pixel-free and link-tracking-free sending as a supported mode, and preference-centre granularity rather than all-or-nothing.
The CRM Manager
Double opt-in is the documented default, editable per form with its own confirmation mail, and an API toggle means imports cannot quietly bypass it — the right default posture. The proof side is unverifiable: we found no public information on what the consent record stores (source, IP, wording), on one-click unsubscribe mechanics, or on any way to switch open and click tracking off. 3 3 9
The Deliverability Engineer
Double opt-in is the documented default on forms with a customizable confirmation email per form, every mail carries an opt-out link, and a subscriber preference centre appears in the paid tiers. I found no public information on a stored consent record showing source or the wording consented to, and nothing on turning open and click tracking off; the captured pages also state Do Not Track signals are not honoured. 3 2 3 9
The Data Protection Officer
Double opt-in is on by default on forms, customizable per form down to separate confirmation email and thank-you page, and extends to API and integration signups — the right default. But I found no public information on a stored consent record that would survive a complaint: nothing on source, IP or versioned wording per subscriber, and nothing on whether open and click tracking can be limited or switched off. Deletion within 30 days of an eligible request and a subscriber preference centre on paid plans are documented. 2 3 9
The Shop Owner
Double opt-in is enabled by default on every new form and can be enforced for API and integration signups too, with customisable per-form confirmation emails — a sound baseline. We found no public information on a retrievable per-subscriber consent record or on switching open and click tracking off, though every mail carries an opt-out link and the export segments keep unsubscribe state. 9 3 3
The Integrator
Double opt-in is on by default on forms and separately togglable for API and integrations, with per-form confirmation mails, redirects and a documented parameter flow for existing subscribers. Unsubscribe is documented as an opt-out link in every mail, but I found no public information on one-click specifics, on a stored consent record showing source and the wording consented to, or on switching open and click tracking off; the preference centre arrives one paid tier up. 3 2 9
The Skeptic
Double opt-in is on by default, customisable per form, and enforceable for API and integration signups — a documented default, which is more than most show. I found no public information on stored consent proof per subscriber (source, IP, versioned wording), on whether the opt-out link is one-click, on any way to limit or switch off open and click tracking, or on documented handling of access and erasure requests for the customer's subscribers; a preference centre exists but only from the Comfort tier up, and editing the confirmation email is itself paid-only. 3 2 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 properly built — direct Mailchimp migration, field mapping, duplicate cleanup, API — and export goes past bare addresses: unsubscribe and bounce status, campaign-level opens and clicks, and automation activity, in CSV. The exit side is thin: we found no public information on exporting campaigns and templates, on documented deletion of one subscriber across all records, or on outbound migration tooling, and export is administrators only. 1 3 11 12
The Deliverability Engineer
Import arrives with field mapping, duplicate cleanup, banned-address screening and a direct Mailchimp path, and export covers custom fields, group membership, unsubscribed and bounced status, campaign opens and clicks, and automation activity, with deletion promised within 30 days of an eligible request. Campaigns and templates are not shown as exportable and the export function is administrator-only, so exit is workable but not a documented feature. 3 11 12
The Data Protection Officer
Import arrives with field mapping, duplicate cleanup and a documented Mailchimp path, and export covers custom fields, subscription states including unsubscribed and bounced, per-campaign engagement and automation activity, in open CSV formats for administrators. Documented deletion within 30 days of an eligible request exists, though we found no public information on full-account export, contractual data return, or deletion that is evidenced rather than asserted. 3 11 12
The Shop Owner
Import arrives with field mapping, duplicate cleanup and a direct path from Mailchimp; export gives me subscriber fields with groups plus per-campaign engagement — opens, clicks, bounces, complaints — and automation activity in CSV. We found no public information on exporting campaigns and templates or on a whole-account export, so leaving would be piecework, though deletion on request is documented at within 30 days. 11 12 3
The Integrator
Import comes from CSV, Excel paste, single adds, the API and a direct Mailchimp path with field mapping and duplicate cleanup, and export covers chosen columns including groups, status segments down to unsubscribed, bounced and spam complaints, per-campaign engagement reports and automation activity, in CSV. I found no public information on exporting campaigns and templates, on documented deletion of a single subscriber across all records, or on export throttling — export is administrators-only, and the migration help on the pages I have points to moving in. 1 11 12
The Skeptic
Import is real work — CSV/TXT, Excel paste, single adds, API, direct from Mailchimp, field mapping and duplicate cleanup — and export covers custom fields via column selection, status segments including unsubscribed, bounced and spam complaints, per-campaign activity export and automation-flow export, with a documented API to sync elsewhere. I found no public information on exporting whole campaigns or templates, on full-account export, or on throttling; deletion is documented at account level within 30 days, but not per subscriber across all records, and the export function is administrators-only. 3 11 12 13
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
The developer surface is real: documented webhooks with HMAC signatures, retries at 10, 100 and 1000 seconds, fifteen event types including automation and spam events, batching, rate-limit awareness, plus named Shopify and WooCommerce integrations and an MCP server. Two things hold it back: we found no public information on a sandbox, and transactional sending runs through a separate MailerSend account rather than the same API, with API sending gated to paid plans. 1 2 3 13
The Deliverability Engineer
Shopify, WooCommerce, WordPress, Zapier and Canva are named among a claimed hundred-plus integrations, webhooks cover fifteen subscriber and campaign events with three retries, HMAC signatures and full create-read-update-delete management, and there is a batch endpoint plus an MCP server. I found no public information on a sandbox or on concrete rate-limit numbers beyond the batch cap, and transactional sending requires a separate MailerSend account rather than one API. 1 3 13
The Data Protection Officer
Webhooks are a mature surface — fifteen subscriber and campaign events, three retries at stated delays, HMAC-SHA256 signatures and batching — with named Shopify and WooCommerce integrations plus Zapier and a documented REST API with an MCP server. Gaps remain: no sandbox, rate limits only referenced in passing, transactional sending routed through a separate MailerSend account, and API sending excluded from the free plan. 1 2 3 13 14
The Shop Owner
Shopify and WooCommerce are named integrations and purchase-history segmentation rides on them — the pipe my shop needs — while webhooks push fifteen subscriber and campaign events with retries, HMAC signatures and a stated batch limit of fifty calls. We found no public information on a sandbox, transactional sending means a separate MailerSend account, and API sending is limited to paid plans. 1 2 6 13 14
The Integrator
This is what I came for: fourteen subscriber and campaign webhook events managed through create, read, update and delete endpoints, signed with HMAC-SHA256, retried three times at 10, 100 and 1000 seconds inside a documented 3-second response window, plus batch requests that reference the platform's rate limits — though the captured pages do not state the limit figures themselves. Native Shopify, WooCommerce and WordPress integrations and an MCP server sit next to a real developer API, but I found no public information on a sandbox or an API versioning and deprecation policy, and transactional sending requires a separate MailerSend account rather than one API. 1 1 3 13
The Skeptic
Shopify, WooCommerce, WordPress, Zapier and Canva are named with 100+ claimed, and the webhook subsystem is the strongest thing here: fifteen events, full create-update-delete management, HMAC-SHA256 signatures, three retries with stated delays, delivery inspection and batching to respect the rate limits. I found no public information on a sandbox or on the vendor maintaining the shop integrations bidirectionally rather than listing them; API sending is also withheld on the free tier. 1 2 13 14
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
Hosting is Germany and the Netherlands with an Irish contracting entity for EEA-billed customers, and the subprocessor list is published — most of the way to where I need it. But the chain runs on Google Cloud Platform, a US-headquartered provider, and names US processors such as OpenAI, Google Vertex AI, Intercom and Stripe without stated hosting regions, while a Delaware entity contracts for anyone billed outside the EEA — EU-resident with US exposure rather than sovereign, and I weight that heavily. 3 3 4
The Deliverability Engineer
Hosting is documented in Germany and the Netherlands with a named infrastructure provider, an Irish contracting entity covers EEA, UK and Swiss billing addresses, and a long subprocessor list is published. A second Delaware entity with Data Privacy Framework certification and FTC authority serves everyone else, US-headquartered processors — Intercom for support, OpenAI and Google Vertex AI for AI features, Stripe for payments — appear with hosting regions unstated, and the EU-only hosting claim sits in FAQ and trust-page copy rather than contract text. 3 3 4
The Data Protection Officer
For EEA customers the contracting entity is MailerLite Limited in Dublin with hosting in Germany and the Netherlands and a published subprocessor list, but the EU-residency claim sits in FAQ and trust-page copy while the same page names Google Cloud Platform, a US-headquartered provider, as the infrastructure. The chain then runs through US processors — Intercom for support without a stated hosting region, OpenAI and Google Vertex AI for product features, Stripe and Oracle NetSuite — with the US entity leaning on the Data Privacy Framework, so answering where behavioural data lives still requires a transfer analysis. 3 3 4
The Shop Owner
With an EU billing address I contract with MailerLite Limited in Ireland and my data sits in German and Dutch data centres on a named provider, with a published subprocessor list — more than most. The chain still runs through US-headquartered processors — Intercom for support, OpenAI and Google Vertex AI on product features, Stripe for payments — without stated hosting regions, and customers outside the EEA contract with a Delaware corporation. 3 3 4
The Integrator
For an EEA billing address the contract sits with MailerLite Limited in Dublin and storage is documented in Germany and the Netherlands, with a long published subprocessor list and ISO 27001 certification. Against that, the second contracting entity is a Delaware corporation serving the rest of the world, the EU-hosting statement sits in FAQ and trust-page copy while the infrastructure is named as US-headquartered Google Cloud Platform, and US processors such as Intercom, OpenAI, Google Vertex AI and Stripe appear without a stated hosting region or legal basis for the transfer. 3 3 4
The Skeptic
For an EEA buyer the contract lands with an Irish entity and data sits in Germany and the Netherlands — but the infrastructure is Google Cloud Platform, a US-headquartered provider, with the EU-residency claim living in FAQ and trust-page copy rather than contract text. The published subprocessor list names US processors for support (Intercom), AI (OpenAI, Google Vertex AI) and payments (Stripe) without stated hosting regions, and a Delaware entity with a Data Privacy Framework certification serves every billing address outside the EEA, UK and Switzerland. 3 3 4
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
The entry tiers are unusually clear: every plan's monthly mail limit, seats and automation count are published, with a stated overage mechanism of auto-upgrade to the next tier and 10% saved on annual billing. It frays beyond that: dedicated IP and deliverability support sit in an unpriced Enterprise tier, tax treatment is only stated as prices possibly being subject to applicable taxes, and the captured pages price up to the 500-subscriber step — we found no public information on figures for larger lists. 2 2 2
The Deliverability Engineer
Entry prices are public with billing period and currency — $0 for up to 250 subscribers, $12 listed and $10.80 per month billed yearly for the entry paid tier, $25 and $22.50 for the next — send limits are stated per tier, and overage behaviour is spelled out as an automatic upgrade and charge. The enterprise tier carrying the dedicated IP shows no captured price, taxes are covered only as "may be subject to applicable taxes", and I found no public information on tier prices beyond the 500-subscriber entry point. 2 2 2
The Data Protection Officer
Prices are public with billing periods stated — the free plan at 250 subscribers and 2,500 monthly emails, paid tiers up to 500 subscribers — and overage is documented as an automatic tier upgrade charged to the card, with billing based on active subscribers only. But the captured prices stop at the 500-subscriber tier, the dedicated IP sits in an unpriced Enterprise plan, and VAT is addressed only as prices that "may be subject to applicable taxes". 2 2 2
The Shop Owner
The entry tiers are computable to the cent — Comfort at "$12 $10.80 /month $129.60/year up to 500 subscribers" with 5,000 monthly emails, Power at "$25 $22.50/month $270.00/year" with unlimited sends — and overage is a stated rule: the tier auto-upgrades and the card is charged, with billing on active subscribers only. We found no public information on prices above the 500-subscriber tier or for the dedicated IP, and VAT appears only as "may be subject to applicable taxes." 2 2 2
The Integrator
The published tiers name subscriber ceilings, monthly email limits, seats and automation counts, the overage rule is an automatic upgrade to the next tier with the card charged, the free plan's lock at 250 active subscribers is spelled out, and billing counts only active subscribers. But the captured figures stop at "up to 500 subscribers", VAT treatment is only "All prices may be subject to applicable taxes", and the dedicated IP sits inside the unpriced custom tier, so a larger list has no visible number to compute an invoice from. 2 2 2
The Skeptic
Tier prices, billing periods, seats and send ceilings are public — "$0" with 250 subscribers and locked sending rather than billed, "$12" list price for Comfort at 5,000 sends with the stated "10× the ceiling of your subscriber tier", "$25" for Power with unlimited sends — and the overage behaviour is stated plainly: the tier auto-upgrades and the card is charged. But Enterprise and its dedicated IP carry no number, VAT treatment is only "All prices may be subject to applicable taxes", and the captured pricing pages show nothing above the 500-subscriber rung of the contact staircase. 2 2 2
European sovereignty — proven facts
1 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 ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | US CLOUD Act reach ⚠ unverified | 0/2 pts | 3 Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 30 Aug 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, Data residency. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Subprocessors. Intercom is US-headquartered and the policy does not state its hosting region; the policy also names other US-based processors of product data (OpenAI, Google Vertex AI, Stripe for payments), while no subscriber Personal Data goes to Intercom unless the customer uploads it to the live chat.
- 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.
- 46 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
- 27 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
- 23 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
- 13 integrations 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
- 8 support 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 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 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 data 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
- The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.mailerlite.com Checked 5 Oct 2026 +3 earlier captures: 28 Sep 2026, 16 Sep 2026, 30 Aug 2026 Details →
- 2 Pricing www.mailerlite.com Checked 5 Oct 2026 +3 earlier captures: 16 Sep 2026, 15 Sep 2026, 30 Aug 2026 Details →
- 3 Privacy policy www.mailerlite.com Checked 5 Oct 2026 +1 earlier capture: 16 Sep 2026 Details →
- 4 Security / trust page www.mailerlite.com Checked 5 Oct 2026 Details →
- 5 Campaigns & automation — found from sitemap www.mailerlite.com Checked 5 Oct 2026 +1 earlier capture: 30 Sep 2026 Details →
- 6 Campaigns & automation — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
- 7 Deliverability infrastructure — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
- 8 Deliverability infrastructure — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
- 9 Consent, proof & tracking limits — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
- 10 Consent, proof & tracking limits — found from sitemap www.mailerlite.com Checked 5 Oct 2026 +1 earlier capture: 30 Sep 2026 Details →
- 11 List ownership, import & exit — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
- 12 List ownership, import & exit — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →
- 13 Integrations & API — found from sitemap developers.mailerlite.com Checked 5 Oct 2026 Details →
- 14 Integrations & API — found from sitemap www.mailerlite.com Checked 5 Oct 2026 Details →