Panel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by SIA Sender · www.sender.net
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.
Sender at a glance
- Vendor
- SIA Sender
- Headquarters
- Not stated on the vendor’s pages as of 26 Oct 2026
- Data hosting
- In the EU by default source, captured 26 Oct 2026
- Free plan
- Yes, per the vendor’s own page source, captured 29 Sep 2026
- Panel verdict
- The AI panel rates Sender 3/5, the mean of 6 judges. Sender, an email and SMS marketing platform, is strongest on campaign and automation, where scores cluster at 7–8: a drag-and-drop builder with eleven trigger types plus custom events via API or Zapier, and split testing with a statistical significance calculator. how scores are made
- As of
- Vendor pages captured 29 Sep 2026 to 26 Oct 2026; evaluated by the panel 28 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Sender, an email and SMS marketing platform, is strongest on campaign and automation, where scores cluster at 7–8: a drag-and-drop builder with eleven trigger types plus custom events via API or Zapier, and split testing with a statistical significance calculator. Integrations follow at 6–7, on a documented API and eight HMAC-signed webhook topics. Deliverability and list data control hold at 6 — exact SPF, DKIM and DMARC values and automatic hard-bounce suppression are published, but no public information appears on dedicated IP options, warm-up or complaint feedback loops. The widest spread is consent and proof, 4 to 6: the consent record is documented — never pre-ticked checkbox, timestamped double opt-in, audit logging — judges split over absent public information on tracking controls and preference centres. Sovereignty sits at 4–5: the vendor's GDPR page states subscriber data is hosted in the EU by default on every plan including the free tier, with an Article 28 DPA, but we found no public information on sending-infrastructure or subprocessor locations. The only public price is the Free Forever plan at up to 15,000 emails a month.
Speaks for it
- Automation builder documented with eleven trigger types, custom events fired via API or Zapier, and workflow split testing with a statistical significance calculator.
- Webhooks cover eight topics with HMAC signing, rotatable secrets, retries on timeout and failure monitoring, alongside a documented API at api.sender.net.
- SPF, DKIM and DMARC records published to the exact values, with automatic hard-bounce suppression and soft-bounce retry.
- Consent documented as evidence: a never pre-ticked confirmation checkbox, timestamped double opt-in and automatic logging of every submission.
- Contact export to CSV or Excel carries subscription status, group assignments and activity dates, with per-subscriber export and a free migration service.
Held against it
- The judges found no public information on dedicated IP options, warm-up, complaint feedback loops or inbox-placement testing.
- We found no public information on where the sending infrastructure runs or on locations for named third parties such as Cloudflare Turnstile and Google reCAPTCHA.
- We found no public information on switching open and click tracking off, on a preference centre, or on consent IP capture.
- The judges found no public information on documented API rate limits or a sandbox environment.
Best for
- You run an ecommerce store and want premade cart-abandonment, post-purchase and win-back workflows with branching on purchases.
- You build your own stack and need a documented API plus HMAC-signed webhooks with retries and failure monitoring.
- You must show consent proof — a never pre-ticked checkbox, timestamped double opt-in and audit logging — when building GDPR-conscious lists.
- You want to start on the Free Forever plan, up to 15,000 emails a month with no credit card required, before committing.
Avoid if
- You need dedicated IP options, warm-up guidance or complaint feedback loops — the judges found no public information on any of these.
- Your procurement demands an evidenced data chain end to end — the judges found no public information on sending-infrastructure or subprocessor locations.
- You must be able to switch off open and click tracking or offer a preference centre — we found no public information on either.
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 4 of 5 |
| Deliverability infrastructure | 3 of 5 |
| Consent, proof & tracking limits | 2.5 of 5 |
| List ownership, import & exit | 3 of 5 |
| Integrations & API | 3.5 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 1.5 of 5 |
Campaigns & automation
Show reasoningHide reasoning
How this is scored
Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.
0 — Not a campaign tool; mail cannot be composed and sent to a list from the product.
3 — Broadcasts to a list built in an editor with templates, with simple list or tag segmentation; automation and testing are basic or not described.
5 — A drag-and-drop editor with reusable templates, segmentation on subscriber fields or behaviour, automated sequences on common triggers (sign-up, date, click), and A/B testing of campaigns.
8 — A visual journey builder with branching on behaviour and data, dynamic content per segment, send-time optimisation, event triggers from shop or app data, and testing that reports significance rather than raw counts.
10 — Journeys treat the whole lifecycle: event-driven entry from other systems, branching on any attribute or event, holdout groups for measurement, and automations a marketer can read months later without a diagram.
The CRM Manager
The visual drag-and-drop builder has If/Else conditions branching on clicks, opens and purchases, eleven trigger types plus custom events fired via API or Zapier, and split testing of subject lines, delays, messages and whole workflows — with a statistical significance calculator that says when a winner is reliable, which is exactly what I demand of a testing tool. Segmentation on engagement, location and any profile field, with one-click segment exclusion, is documented. I found no public information on holdout groups for lifecycle measurement, which is what would set it apart at the very top. 3 4 5
The Deliverability Engineer
The journey builder is documented in depth: a visual drag-and-drop builder with triggers, actions and if/else branching on clicks, opens and purchases, eleven trigger types plus custom events fired via API or Zapier, and a library of ecommerce workflows. Testing is unusually grown-up for the category — a statistical significance calculator, live results before the test closes, and split testing of whole workflows including SMS-versus-email paths. What keeps it off the top band is that I found no public information on holdout groups for measuring a journey's net effect. 4 5
The Data Protection Officer
The documented automation builder is a visual drag-and-drop journey tool with triggers, actions, conditions and If/Else branching on opens, clicks and purchases, plus custom events fired via API or Zapier, and the A/B testing page describes a statistical significance calculator, send-time tests and live results. This reads as a strong journey builder; we found no public information on holdout-group measurement or automatic send-time optimisation. 4 5 3
The Shop Owner
The visual drag-and-drop automation builder carries eleven trigger types including purchases plus custom events fired in via API or Zapier, If/Else branching on clicks, opens and buys, and a ready library that already covers cart abandonment, post-purchase upsells and win-back — the exact flows my shop runs on. Testing is grown-up too: subject lines, delays, messages, send times and whole workflows can be split-tested, with a statistical-significance calculator instead of raw counts and live results while the campaign sends. We found no public information on holdout groups for measuring a journey against a control group. 4 5 1
The Integrator
The automation builder is a visual drag-and-drop system with triggers, actions and If/Else conditions branching on clicks, opens and purchases, eleven starting trigger types plus custom events fired via API or Zapier, email and SMS in one workflow, and A/B testing of subject lines, delays, whole workflows and send times with a statistical significance calculator rather than raw counts. Dynamic content arrives through personalisation tags, segmentation and conditional steps. We found no public information on holdout groups for measuring journeys against a control, which is what would separate this from the top level. 4 5 1
The Skeptic
The visual drag-and-drop automation builder documents triggers, actions and If/Else conditions — eleven trigger types plus custom events fired via API or Zapier — alongside personalization tags, segment-based dynamic steps, premade workflow templates and per-workflow analytics. Testing is the real differentiator: subject lines, content and send times, workflow split tests with SMS-versus-email paths, and a statistical significance calculator declaring when a winner is reliable. We found no public information on holdout groups for lifecycle measurement. 4 5
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
SPF, DKIM and DMARC set-up is documented down to record values, with domain ownership verification and a re-check button, and bounce handling is genuinely managed: hard bounces auto-suppressed, soft bounces retried then reclassified, bounce rates split hard and soft on the dashboard, and per-domain bounce logs for transactional mail. Purchased and scraped lists are screened before sending and accounts are reviewed after major uploads. I found no public information on dedicated IP options, warm-up, seed testing, complaint feedback loops or engagement-based sunsetting, so this sits above solid but below the full diagnostics tier. 3 6 7
The Deliverability Engineer
Authentication is properly documented — exact SPF, DKIM and DMARC records with domain ownership verification, a recheck button, the single-SPF merge rule and a path to harden DMARC to quarantine or reject — and bounce discipline is real: hard bounces suppressed automatically and excluded from all future sends, soft bounces retried then suppressed, hard and soft rates reported separately, and per-domain bounce views for transactional mail. I set the advertised 99% delivery figure aside on principle; the infrastructure is what counts. I found no public information on dedicated IPs, warm-up, complaint feedback loops, engagement-based sunsetting or inbox-placement testing. 6 7 1
The Data Protection Officer
The help centre documents exact SPF, DKIM and DMARC records for an authenticated custom sending domain with a recheck button, automatic hard-bounce suppression, soft-bounce retry with suppression after persistent failures, bounce rates split into hard and soft on the dashboard, and list screening at signup and after uploads. We found no public information on dedicated-IP options, warm-up, complaint feedback loops or seed and inbox-placement testing, which keeps it below the higher level. 6 7 3
The Shop Owner
Set-up guidance is complete with exact SPF, DKIM and DMARC records, domain ownership verification and a one-click re-check, and bounce handling is more granular than most: hard bounces suppressed automatically, soft bounces retried then reclassified, hard and soft tracked separately even for transactional mail, and bounces filterable per recipient domain. Purchased and scraped lists are screened before sending, and accounts are reviewed at signup and after major uploads. We found no public information on dedicated IPs, warm-up, complaint feedback loops or inbox-placement testing, so I credit the documented layer only, not the advertised 99% deliverability claim. 3 6 7
The Integrator
SPF, DKIM and DMARC are documented down to the record level with domain ownership verification, a re-check button and warnings about free sender addresses, and bounce handling is properly engineered: hard bounces suppressed automatically, soft bounces retried then suppressed after repeated failures, hard and soft rates split on the dashboard, and per-domain bounce logs for transactional sends. Account review at signup and after list uploads, plus screening of purchased and scraped lists, covers hygiene. We found no public information on dedicated IP options, warm-up, complaint feedback loops or per-domain reputation reporting. 6 7 3
The Skeptic
Domain authentication is documented record by record — exact SPF, DKIM and DMARC values, single-SPF merge rules, verification checkmarks and a free-mail sender warning — and bounce handling runs deep: hard and soft rates tracked separately, automatic hard-bounce suppression, soft-bounce retry with suppression after persistent failures, and per-domain bounce logs for transactional mail. We found no public information on dedicated IP options, warm-up, complaint feedback loops or inbox-placement testing; the advertised "up to 99% email deliverability" is a marketing claim, not documentation. 6 7 3
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 proof is the strong half: a required, never pre-ticked confirmation checkbox with customisable wording, the consent action recorded alongside the subscriber record, timestamped double opt-in with confirmed and not-confirmed groups, automatic logging of every submission for an audit trail, and a designated DPO. Unsubscribes are removed from lists automatically. I found no public information on whether open or click tracking can be limited or switched off, on a preference centre, or on retention rules for inactive subscribers, which is why I hold this just under the level where tracking controls are documented. 3 8 9
The Deliverability Engineer
Double opt-in is documented both as a product claim with timestamped confirmation and as a working build — confirmation email, a link-clicked condition, and Confirmed and Not confirmed groups — and consent is logged: every submission recorded for the audit trail, the consent action stored alongside the subscriber record, signup source visible in the single profile, and a checkbox that is never pre-ticked and blocks submission unchecked, with customisable wording. I found no public information on whether open or click tracking can be switched off, on IP capture in the consent record, or on a preference centre. 3 8 9
The Data Protection Officer
Double opt-in with timestamped confirmation is documented, every form submission is automatically logged for an audit trail, the consent action is recorded alongside the subscriber record with signup source in one view, and the granular consent checkboxes are never pre-ticked with the form blocked until checked. But we found no public information on switching open or click tracking off, on a preference centre, or on storing the confirmation wording and IP per subscriber, so the proof is real while the tracking limits are undocumented. 3 8 9 2
The Shop Owner
Consent collection is documented thoroughly: a required confirmation checkbox whose wording and validation message I can edit, granular checkboxes that are never pre-ticked, double opt-in built on a timestamped confirmation the recipient must click, and the consent action recorded against the subscriber record together with signup source, plus automatic logging of every submission. Unsubscribe runs from a footer link and cleans the lists automatically. We found no public information on one-click unsubscribe without a landing page, a preference centre, storing the consent IP, or switching off open and click tracking. 2 3 8 9
The Integrator
Consent is built as a record: the confirmation checkbox blocks form submission, its wording and validation message are customisable, and the consent action is stored against the subscriber with a timestamped double opt-in, signup source and automatic logging of every submission for the audit trail, while unsubscribes remove the subscriber automatically. The confirmation email itself is assembled as an automation step, so the proof depends on that workflow being built correctly. We found no public information on a preference centre or on switching open and click tracking off. 8 9 3 2
The Skeptic
Consent is built as evidence: a required, never pre-ticked confirmation checkbox with customizable wording recorded alongside the subscriber record, double opt-in with timestamped confirmation and signup source in one view, and automatic logging of every submission for an audit trail; unsubscribes are removed from lists automatically. We found no public information on whether open and click tracking can be limited or switched off, on a preference centre, on IP capture in the consent record, or on retention rules for inactive subscribers. 8 9 3 2
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 accepts CSV, Excel and TXT with custom fields, and export to CSV or Excel carries contact details, email and SMS subscription status, group assignments, custom fields and registration and activity dates, filterable by status, group or segment — with export explicitly framed for backup, analysis and migration. Per-subscriber export from the profile, profile deletion with a clean audit record of when and why, an API, and a free migration service in the other direction are all documented. I found no public information on exporting campaign or template history, and full engagement history goes only as far as activity dates. 3 10 11 12
The Deliverability Engineer
Import handles CSV, Excel and TXT with downloadable templates and custom-field columns, and export is documented down to contents — contact data, subscription status for email and SMS, group assignments, custom fields, registration and activity dates — in CSV or Excel, filterable by status, group or segment, with migration to another platform named as a purpose. A single subscriber's data exports from their profile, deletion leaves an audit record of when and why, and the API reads and writes the list. I found no public information on exporting campaigns or templates, or on export throttling. 3 10 11 12
The Data Protection Officer
Import handles CSV, Excel and text files with custom fields and templates, and export in CSV or Excel covers contact details, email and SMS subscription status, group assignments, custom fields and registration and activity dates, with documented deletion of a profile together with a clean audit record of when and why. We found no public information on exporting campaign content, templates or event-level engagement history, or on export throttling. 10 11 3 12
The Shop Owner
Import takes CSV, Excel and TXT with required headers and custom fields, and export to CSV or Excel includes subscription status for email and SMS, group assignments, custom fields and registration and activity dates, filterable by segment — with migration to another platform named as an intended use. Profile deletion is documented with a clean audit record of when and why, single subscribers can be exported from their profile, an API with tokens reads and writes the list, and a free migration service exists. We found no public information on exporting campaigns and templates or on engagement history beyond activity dates. 3 10 11
The Integrator
Import accepts CSV, Excel and TXT up to 64MB with required headers, downloadable templates and custom-field columns; export delivers contact data, email and SMS subscription status, group assignments, custom fields and registration and activity dates in CSV or Excel, filterable by status, group, segment or advanced criteria, and a single subscriber can be exported from their profile. Deletion is documented with an audit record of when and why, and a migration service is offered. We found no public information on exporting campaigns or templates, or on export throttling. 10 11 3 12
The Skeptic
Export is documented as a migration path — CSV and Excel with custom fields, email and SMS subscription status, group assignments and registration and activity dates, filterable by status, group and segment — and import handles CSV, Excel and TXT with custom-field columns up to 64MB. Deletion of profiles carries a clean audit record of when and why, single-subscriber export works from the profile, and a free migration service is listed. We found no public information on exporting campaigns, templates or full engagement history, or on export throttling. 10 11 3
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 documented REST API with bearer tokens and code examples, plus webhooks on eight topics that are HMAC-signed with rotatable secrets, retried on timeout, pausable and monitored with failure counts and response times — that is real event plumbing, not a connector screenshot. Named integrations include Shopify, WooCommerce, PrestaShop and WordPress, with behavioural data pulled from CRM or ecommerce and custom events fired in via API. I found no public information on rate limits or a sandbox, which keeps it one step below the top connection surface. 4 5 12 13
The Deliverability Engineer
Named shop integrations include Shopify, WooCommerce and PrestaShop alongside WordPress and Zapier, the API is documented with Bearer tokens and code examples, and the webhooks are real engineering: eight topics including bounces, HMAC signing with a rotatable secret, retries on timeout, pause, and failure and response-time monitoring. I found no public information on documented rate limits or a sandbox, which is what separates a documented API from one you can build a business on. 4 12 13
The Data Protection Officer
Named integrations cover Shopify, WooCommerce, PrestaShop, WordPress and Zapier, the API is documented at api.sender.net with bearer tokens, code examples and authentication badges, and the webhook guide shows eight topics, HMAC signing with a rotatable secret, retries on timeout, failure counters, response times and pause. We found no public information on documented rate limits, a sandbox, or bidirectional sync with the named systems. 12 13 5
The Shop Owner
The shop connections I need are named — WooCommerce, Shopify and PrestaShop — alongside WordPress, Zapier, Jumpseller and an MCP server for AI assistants, with behavioural data pulled from the shop or CRM for segmentation and personalisation. The API lives at its own domain with Bearer tokens, code examples and authentication badges on protected endpoints, and webhooks cover eight subscriber, group, campaign and bounce topics with HMAC signature verification, rotatable secrets, retries on timeout, pause, failure counters and response-time monitoring. We found no public information on documented rate limits or a sandbox environment. 4 5 12 13
The Integrator
This is the surface I can actually build against: a documented API at api.sender.net with bearer tokens, code examples and requires-authentication badges, plus webhooks that behave like production infrastructure — eight topics across subscribers, groups, campaigns and bounces, HMAC signatures with a rotatable secret, retry on timeout, HTTPS-only endpoints, pause, failure counters and response-time monitoring. Integrations cover WooCommerce, Shopify and PrestaShop with custom events from the API or Zapier, and transactional sending sits in the same product. We found no public information on documented rate limits, a sandbox, or an API versioning and deprecation policy — the three things I check before wiring a stack in. 12 13 5 4
The Skeptic
The API is documented at api.sender.net with Bearer tokens, code examples and authentication badges, and webhooks are a serious surface: eight topics across subscribers, groups, campaigns and bounces, HMAC signing with rotatable secrets, retry on timeout, pause, and failure and response-time monitoring. Shopify, WooCommerce, PrestaShop, WordPress and Zapier are named, with custom events flowing in via API or Zapier. We found no public information on documented rate limits or a sandbox, and the integrations are named rather than described as vendor-maintained. 13 12 5 4
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
Subscriber data is stated as hosted in the European Union by default on every plan including the free tier, a processing agreement under GDPR Article 28 is offered, and a designated DPO is reachable, operated by UAB Sender.lt. I found no public information on the contracting entity's jurisdiction, the named hosting infrastructure, or the location and safeguards of the wider subprocessor chain — only website protection tools such as Google reCAPTCHA and Cloudflare Turnstile are named. As a buyer who weighs this heavily, the hosting default and the processing agreement are welcome, but the chain beyond that statement is not proven European. 2 3
The Deliverability Engineer
The vendor's own GDPR page states subscriber data is hosted in the European Union by default on every plan including the free tier, offers a data processing agreement under Article 28, names Sender as processor with the customer as controller, and lists a designated DPO. The contracting entity's jurisdiction is not independently confirmed in what was captured, and the subprocessor chain is not located — only two website-protection tools, Cloudflare Turnstile and Google reCAPTCHA, are named, without locations stated for anything in the send path. 2 3
The Data Protection Officer
The vendor's own GDPR page states subscribers' data is hosted in the European Union by default on every plan including the free tier — no transfer mechanism to evaluate — alongside a data processing agreement under Article 28, stated processor and controller roles, and a designated DPO at dpo@sender.net. The privacy policy names UAB Sender.lt as operator and discloses Cloudflare Turnstile and Google reCAPTCHA on its website, but we found no public information on the locations of the sending and analytics infrastructure or a published subprocessor list with locations, and the independently computed sovereignty attributes remain unknown. 3 2
The Shop Owner
The vendor's own GDPR page states that subscriber data is hosted in the European Union by default on every plan including the free tier — no transfer mechanism to evaluate — and a data processing agreement under Article 28 is offered, with the operator named as UAB Sender.lt and a designated DPO at a published address. The captured pages name Cloudflare Turnstile, Google reCAPTCHA and a card processor as third parties without locations or a stated safeguard, and we found no public information on where the sending infrastructure or support tooling sits. I weigh this heavily, and I can only credit what is stated: hosting is, the rest of the chain is not. 2 3
The Integrator
The vendor's own GDPR page states EU-based infrastructure on every plan including the free tier and EU hosting by default, with a data processing agreement under Article 28, a designated DPO and a named operator, UAB Sender.lt. Beyond that claim the chain thins out: the captured pages do not name the hosting provider or its location, the privacy policy's subprocessors — Cloudflare Turnstile, Google reCAPTCHA and an unnamed card processor — are listed without locations or stated safeguards, and we found no public information placing the sending infrastructure on a published subprocessor list. 3 2
The Skeptic
The vendor's own compliance page states subscribers' data is hosted in the European Union by default on every plan including the free tier, an Article 28 data processing agreement is offered, and a designated DPO is reachable — more than a bare European option. But that statement covers stored data, and we found no public information on where the sending infrastructure runs, on the contracting entity's jurisdiction beyond the name UAB Sender.lt, or on locations for the named third parties such as Google reCAPTCHA, Cloudflare Turnstile and the credit card processor. A chain asserted in part, not evidenced end to end. 3 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 up to 15,000 emails/month is public, no credit card is required, and the positioning is "Premium features included No hidden costs or usage limits". I found no public information on paid tier prices, contact tiers, billing periods, overage rates or VAT treatment, so a real invoice for a growing list and send volume cannot be computed from the captured pages. 1 4 1
The Deliverability Engineer
The public pages document a Free Forever plan at up to 15,000 emails a month with no credit card required and a 14-day window after which you stay free or upgrade — but "No hidden costs or usage limits" is positioning language, not a price. I found no public prices for the paid tiers, no contact-band pricing, no overage rates and no VAT treatment, so a sender with a growing list cannot compute the real invoice from these pages. 4 5 1
The Data Protection Officer
A Free Forever plan with up to 15,000 emails per month, no credit card required and cancel anytime is public, alongside the claim of no hidden costs or usage limits. The captured pages show no paid-tier prices, billing periods or overage rates, and we found no public information on how cost scales with contacts or send volume. 4 5 1
The Shop Owner
The captured pages show a Free Forever plan with up to 15,000 emails a month and no credit card required, with a choice after fourteen days to stay free or upgrade. Beyond that, we found no public information on prices for paid tiers, contact-based scaling, overage rates or VAT treatment; 'no hidden costs or usage limits' is a slogan, and I cannot build a real invoice for my list size from it. 1 4 1
The Integrator
The captures publish exactly one number: the Free Forever plan at up to 15,000 emails a month, with no credit card required and a 14-day window before choosing free or paid. "No hidden costs or usage limits" is a slogan, not a price, and we found no public information on paid tier prices, contact bands, overage rates or VAT treatment — so the real invoice for a given list size cannot be computed from the pages read. 4 1 1
The Skeptic
A free plan is public and quantified — "Free Forever plan — automate up to 15,000 emails/month" — with no credit card required and a 14-day window after which one stays free or upgrades. We found no public information on any paid tier price, on how cost scales with contacts or send volume, on overage rates, or on VAT treatment; the "No hidden costs or usage limits" positioning arrives with no numbers behind it. 4 1 1
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 | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?The statement sits in marketing copy on the GDPR landing page, and 'by default' leaves open that some data or customers could be hosted elsewhere; no subprocessor table or privacy-policy line confirms server locations. |
2/4 pts | 3 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 needed, no transfer outside the EU/EEA
unverified
Why unverified?This is marketing copy on the GDPR landing page, qualified 'by default', and no formal transfer impact assessment document is published anywhere in the excerpts. |
1/1 pts | 3 Report an error |
Questions about Sender
Is Sender European?
Not determined: the vendor’s pages as captured do not say where Sender is based.
Where does Sender store data?
Sender stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 26 Oct 2026.
Does Sender have a free plan?
Yes. Sender has a free plan, per the vendor’s page captured 29 Sep 2026.
What are the best alternatives to Sender?
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: Sender alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 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 — Transfer impact assessment. This is marketing copy on the GDPR landing page, qualified 'by default', and no formal transfer impact assessment document is published anywhere in the excerpts.
- Weak sourcing — Hosting location. The statement sits in marketing copy on the GDPR landing page, and 'by default' leaves open that some data or customers could be hosted elsewhere; no subprocessor table or privacy-policy line confirms server locations.
- 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.
- 16 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 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 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
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.sender.net Checked 26 Oct 2026 +1 earlier capture: 29 Sep 2026 Details →
- 2 Privacy policy — found from the homepage www.sender.net Checked 26 Oct 2026 Details →
- 3 Data processing agreement (dpa) — found from the homepage www.sender.net Checked 26 Oct 2026 Details →
- 4 Campaigns & automation — found from sitemap www.sender.net Checked 26 Oct 2026 Details →
- 5 Campaigns & automation — found from sitemap www.sender.net Checked 26 Oct 2026 Details →
- 6 Deliverability infrastructure — found from sitemap www.sender.net Checked 26 Oct 2026 Details →
- 7 Deliverability infrastructure — found from sitemap www.sender.net Checked 26 Oct 2026 Details →
- 8 Consent, proof & tracking limits — found from sitemap www.sender.net Checked 26 Oct 2026 Details →
- 9 Consent, proof & tracking limits — found from sitemap www.sender.net Checked 26 Oct 2026 Details →
- 10 List ownership, import & exit — found from sitemap www.sender.net Checked 26 Oct 2026 Details →
- 11 List ownership, import & exit — found from sitemap www.sender.net Checked 26 Oct 2026 Details →
- 12 Integrations & API — found from sitemap www.sender.net Checked 26 Oct 2026 Details →
- 13 Integrations & API — found from sitemap www.sender.net Checked 26 Oct 2026 Details →