Email Marketing & Newsletter
Rule
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Rule Communications AB · rule.io
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.
Rule at a glance
- Vendor
- Rule Communications AB
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 3 Nov 2026
- Panel verdict
- The AI panel rates Rule 2/5, the mean of 6 judges. Rule is a Swedish email marketing and marketing automation platform, scored strongest on campaign and automation, list data control and integrations, and weakest on deliverability and consent and proof. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 3 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Rule is a Swedish email marketing and marketing automation platform, scored strongest on campaign and automation, list data control and integrations, and weakest on deliverability and consent and proof. Each of the strong three reached 6, on documented triggered sends for cart abandonment, back-in-stock, win-back and onboarding, segmentation on purchase history, activity and site behaviour, import with duplicate removal and tagging, XLS export filtered to all, active or blocked members, and a public API with webhooks on five event types alongside integrations including Centra and Vendre. Sovereignty topped out at 5: the data processing agreement names a Stockholm entity under Swedish law and states processing within the EU/EES, but provides standard contractual clauses for third-country transfers, and we found no public information on hosting or subprocessor locations. Deliverability topped out at 2 and consent and proof at 3: three judges declined to score deliverability, citing no public information on authentication or bounce and complaint handling, and we found no public information on double opt-in, consent records or unsubscribe handling. The deliverability judge scored 0 on every criterion, weighing documentation gaps heavily.
Speaks for it
- Triggered automations for cart abandonment, back-in-stock, win-back and onboarding are documented, with segmentation on purchase history, activity, site behaviour and preferences
- Import is documented end to end — file or paste, automatic duplicate removal, tagging, updating of existing members, order-history import — with XLS export filtered to all, active or blocked members and a documented deletion flow
- A public API with keys and webhooks on Transactions, Campaigns, Subscribers, Imports and Preferences sits alongside named integrations including Centra and Vendre
- The published data processing agreement names Rule Communication – Nordic AB under Swedish law, states processing within the EU/EES, grants audit rights, requires encryption, and promises no personal data remaining 30 days after the agreement ends
- A free plan with published limits — 250 active members importable and 1,000 emails per month — is offered with self-service signup
Held against it
- We found no public information on sending-domain authentication, bounce or complaint handling, dedicated IPs or reputation monitoring, and deliverability scored at most 2
- We found no public information on double opt-in, per-subscriber consent records, unsubscribe handling, or switching open and click tracking off
- API sends are documented as working only in the previous version of Campaigns — "API sends are not supported in the campaign editor" — and correct technical implementation is stated to be the customer's responsibility
- The agreement provides standard contractual clauses under Decision 2010/87/EU for any third-country transfers, and we found no public information on hosting infrastructure or subprocessor locations
- We found no public information on exporting engagement history, campaigns or templates, so exit is proven for the subscriber list, not its history
Best for
- You run a Nordic e-commerce shop on Centra or Vendre and want documented cart-abandonment, back-in-stock and win-back automations
- You need documented control of your list — import with de-duplication and tagging, XLS export, per-subscriber deletion — throughout the relationship and at exit
- You want to wire transaction, campaign, subscriber and import events into your own systems through the documented API and webhooks
- You want a Swedish contracting entity with a published data processing agreement stating EU/EES processing and audit rights
Avoid if
- You plan to send campaigns via the API from the current campaign editor, where API sends are documented as not supported
- You expect the vendor to own correct API implementation, which it expressly states it does not take responsibility for
- You need export of engagement history, campaigns and templates at exit; the documented export covers the subscriber list in XLS only
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 2.5 of 5 |
| Deliverability infrastructure | 1 of 5 |
| Consent, proof & tracking limits | 1 of 5 |
| List ownership, import & exit | 2.5 of 5 |
| Integrations & API | 2.5 of 5 |
| European sovereignty | 2 of 5 |
Campaigns & automation
panel disagrees
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
A visual editor, auto-branded templates and automation flows adapted to customer-journey phases are documented, with segmentation on real behaviour (purchase history, site behaviour, activity) and behaviour-triggered sends like cart abandonment and back in stock. But we found no public information on A/B testing, send-time optimisation or branching logic, and a journey programme whose testing story is undocumented stops short of what I run a lifecycle on. 1 4 10
The Deliverability Engineer
A visual editor, automatically brand-styled templates, segmentation on activity, purchase history and on-site behaviour, and automated trigger sequences — cart abandonment, back in stock, win-back, onboarding — are all documented, and a Journey Builder is named. We found no public information on A/B testing or on how journeys branch, so I place this just under the level where testing is part of the documented bundle. 1 4 10
The Data Protection Officer
A visual editor with automatically brand-matched templates, segmentation on activity, purchase history, on-site behaviour and preferences, and triggered automation for cart abandonment, back-in-stock, onboarding and win-back are all documented. I found no public information on A/B testing or on journey branching, which keeps this just below the fully-rounded mark. 1 4
The Shop Owner
The evidence shows automation built for a shop: behaviour-triggered emails, automatic cart-abandonment reminders, back-in-stock mails, digital receipts and product recommendations drawn from order history and site behaviour, with a customer-journey module and segmentation on activity and purchases. We found no public information on A/B testing, journey branching or send-time optimisation, so I could run my abandoned-cart and win-back flows but not measure variants against each other. 1 4 8 10
The Integrator
A visual editor with automatically brand-styled templates, automation flows, and behavioural triggers — cart abandonment, back in stock, onboarding, win-back — plus segmentation on activity, purchase history, site behaviour and preferences are all documented, and a Journey Builder is referenced in the import guide. We found no public information on A/B testing or on branching and send-time control within the flows, so it sits just above the mid mark. 1 4 10
The Skeptic
A visual editor with auto-branded templates, segmentation on purchase history, activity and site behaviour, and a broad catalogue of triggered sends (cart abandonment, back-in-stock, win-back, onboarding, transactional) is documented on the marketing pages. We found no public information on A/B testing, and Journey Builder appears only as a passing note that preferences work there, so branching journeys are a name rather than a documented capability. 1 4 10
Deliverability infrastructure
n/r
n/r
n/r
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 not rated — no public information
We found no public information on authentication set-up, bounce and complaint handling, or sending reputation; the two captured help-centre pages on DNS settings and deliverability tips yielded no confirmed facts I could score. Whether the mail arrives is therefore an open question I cannot place on any level. 5 6
The Deliverability Engineer
The help centre carries an article on DNS settings for deliverability and one on tips for improving deliverability, and members can be blocked from campaign and SMS sends — but we found no public information confirming SPF, DKIM or DMARC specifics, hard-bounce suppression, complaint feedback loops, dedicated IPs, warm-up or reputation reporting. The advertised opening rate tells me nothing; the sending infrastructure itself is only documented at the level of DNS configuration guidance. 1 5 6 10
The Data Protection Officer
The help centre includes guidance pages on DNS settings and on tips for improving deliverability, and the product itself sends the mailings, but I found no public information confirming SPF or DKIM set-up for the sender's domain, bounce suppression, complaint handling or reputation measures. For a tool that holds the sending reputation I can verify none of the specifics an inbox team would ask for. 1 5 6
The Shop Owner not rated — no public information
We found no public information on how mail is authenticated, how bounces and complaints are handled, or what sending infrastructure delivers the campaigns. The captured help-centre pages on DNS settings and deliverability tips yielded no confirmed SPF, DKIM or DMARC detail, and an advertised opening rate is not documentation I can judge. 5 6
The Integrator
Mail plainly sends through the vendor's platform, and the help centre publishes a page on DNS settings for deliverability and one on tips for improving the deliverability of mailings. The captured pages do not confirm what authentication the DNS page sets up, and we found no public information on bounce handling, complaint suppression, or reputation measures. 1 5 6
Consent, proof & tracking limits
panel disagrees
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
Sign-up widgets and a GDPR checklist are documented, and the data processing agreement carries encryption, breach-notification and audit obligations — but that is contract language, not consent mechanics. We found no public information on double opt-in, per-subscriber consent records, unsubscribe handling, or whether open and click tracking can be limited or switched off. 2 7 8
The Deliverability Engineer
The data processing agreement shows customers can build their own sign-up widgets for the website, the vendor publishes a GDPR checklist and consent guidance, and blocked members can be excluded from sends. We found no public information on double opt-in, per-subscriber consent records, unsubscribe handling, or whether open and click tracking can be limited or switched off. 2 7 10
The Data Protection Officer
Forms built in the product and displayed on the website are documented, as are a GDPR consent page and checklist, but I found no public information confirming double opt-in, a stored consent record per subscriber with timestamp and source, or unsubscribe handling. Worse for my purposes, the platform advertises a detailed picture of customer behaviour and targeting on website visits, with no documented way to switch open and click tracking off. 2 4 7
The Shop Owner
Sign-up forms ('widgets') for the website are documented, the vendor publishes GDPR consent material and a checklist, and subscribers can be blocked from campaign and SMS sends. We found no public information on double opt-in, per-subscriber consent records, unsubscribe handling or tracking controls, so the proof I would need after a complaint is not shown. 2 7 10
The Integrator
Sign-up widgets created in the product and displayed on the customer's website are documented in the data processing agreement, and the vendor publishes GDPR consent guidance, a GDPR checklist and a full data processor agreement. We found no public information on double opt-in, a per-subscriber consent record, unsubscribe handling, or any way to switch open and click tracking off. 2 7 8
The Skeptic
Sign-up widgets are documented in the data processing agreement and a GDPR checklist is offered, but we found no public information on double opt-in, the consent record with timestamp and source, unsubscribe handling, or switching open and click tracking off — while the vendor's own page markets Rule as a GDPR compliant platform where all customer data is secured. A preference concept appears only in a note that it works in Journey Builder alone. 2 7 8 10
List ownership, import & exit
panel disagrees
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 is well covered — CSV or paste, duplicate removal, tags assignable on import, updating existing members, order-history import — alongside export to XLS with filters for active or blocked members, a documented delete-subscribers flow, API-based import, and deletion within 30 days after agreement expiry. We found no public information on export of engagement history, campaigns or templates, so exit looks workable but not full-fidelity. 2 9 10
The Deliverability Engineer
Import from CSV or XSL files with duplicate removal, tagging, updating of existing members and order-history import is documented, subscribers export to XLS with filters for all, active and blocked, deletion is a help-centre procedure, and the agreement commits to no personal data remaining 30 days after it ends. The list can also be written via the documented API; we found no public information on exporting engagement history, campaigns or templates. 2 9 10 11
The Data Protection Officer
Import handles files and paste-in, tags, updates of existing members, de-duplication and blocking, export to XLS covers all, active or blocked members, subscriber deletion is documented, and the agreement promises no personal data remains 30 days after it ends. Engagement history export and campaign or template export are not described, so full portability of the record is not shown. 2 9 10
The Shop Owner
Import is thorough — file upload or paste, automatic duplicate removal, tagging on import, updating existing members, even order-history import — export runs to XLS with all/active/blocked filters, deleting subscribers has its own help article, and the data processing agreement promises no personal data remains 30 days after the agreement ends. We found no public information on exporting engagement history, campaigns or templates. 9 10 2
The Integrator
Import by file upload or paste with duplicate removal, tag assignment, updating of existing members and import result counts; XLS export filtered to all, active or blocked members; a documented subscriber deletion flow; and a contractual promise that no personal data remains 30 days after the agreement ends. We found no public information on exporting engagement history, campaigns or templates, which is what I would need for a clean exit. 2 9 10 11
The Skeptic
Import is well documented — file or paste, duplicate removal, tag assignment, updating existing members, order history — and per-subscriber deletion plus an XLS export filtered to all, active or blocked members sit in the help centre, with API keys and webhooks on subscriber events alongside. We found no public information on exporting engagement history, campaigns or templates, or on export throttling; exit is proven for the list, not for its history. 2 9 10 11
Integrations & API
panel disagrees
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
There is documented API documentation with API keys, webhooks firing on transactions, campaigns, subscribers, imports and preferences, and named integrations including the commerce platforms Centra and Vendre. The edges show, though: API sends are stated to work only in the previous version of Campaigns, the vendor takes no responsibility for correct implementation, and we found no public information on rate limits, retries or a sandbox. 2 11 12
The Deliverability Engineer
There is a public API with key-based access and documentation, and webhooks fire on transactions, campaigns, subscribers, imports and preferences, set up under Settings then Developer. Named integrations with setup guides exist for Centra, Vendre, Yotpo, Confetti and Sesamy; we found no public information on webhook retries, rate limits or a sandbox, and the vendor itself notes API sends are not supported in the current campaign editor and that correct technical implementation of such dispatches is the customer's responsibility. 7 8 11 12
The Data Protection Officer
A documented API with keys, webhooks on transactions, campaigns, subscribers, imports and preferences, and named integrations including the shop platforms Centra and Vendre meet the working standard. The tempering facts: API sends apply only to the previous version of Campaigns, the vendor disclaims responsibility for API dispatches working, and I found no public information on rate limits, retries or a sandbox. 7 11 12
The Shop Owner
Named shop integrations include Centra and Vendre — the platforms a Nordic shop like mine actually runs on — alongside Yotpo, a documented API with keys, and webhooks firing on transactions, campaigns and subscriber events. We found no public information on webhook retries, rate limits or a sandbox, and the vendor's own note says API sends apply only to the previous version of Campaigns, stating that correct implementation is the customer's responsibility. 11 12 10
The Integrator
A public API documentation site with API keys, a transactional send endpoint, and webhooks on transactions, campaigns, subscribers, imports and preferences set up under Settings — Developer, not a partner form, alongside named integrations including the shop platforms Centra and Vendre. We found no public information on rate limits, webhook retry behaviour, a sandbox, or a deprecation policy, and the vendor states that API sends apply only to the previous version of Campaigns with correct technical implementation left to the customer. 2 7 11 12
The Skeptic
Five named integrations including Centra and Vendre, a documented API with keys, and webhooks on five event types including subscribers and imports make a solid middle-weight connection surface. The small print bites: API sends are documented as working only in the previous version of Campaigns — "API sends are not supported in the campaign editor" — and the vendor writes that correct implementation "is not something we take responsibility for"; we found no public information on rate limits, retries or a sandbox. 7 10 11 12
European sovereignty
panel opinion
panel disagrees
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 and processing entity is Rule Communication – Nordic AB, registered in Stockholm with a Swedish company number and Swedish governing law, under a published data processing agreement that names subprocessors in an appendix and relies on standard contractual clauses for third-country transfers. Hosting location and subprocessor locations are unproven in what we captured, and a third-country transfer clause is exactly what I would interrogate before calling this chain European. 2 8
The Deliverability Engineer
The published data processing agreement names Rule Communication – Nordic AB of Stockholm under Swedish law, states processing within the EU/EEA, and provides standard contractual clauses for any third-country transfer plus a 14-day objection window before new subprocessors. Hosting infrastructure and subprocessor locations are not stated on the captured pages, so I stop at the level where the European entity and the agreement are proven but the rest of the chain is not — and I weigh that gap heavily. 2 4 8
The Data Protection Officer
The contracting entity is Rule Communication – Nordic AB of Stockholm under Swedish law, with a data processing agreement granting audit rights, breach notification, encryption and deletion within 30 days, and stating personal data is processed within the EU/EEA. But hosting infrastructure is not named, the subprocessor list sits in an appendix without published locations, and the agreement expressly contemplates third-country transfers under standard contractual clauses of Decision 2010/87/EU — exactly the transfer argument I would rather not have to make. 2 4 8
The Shop Owner
The contracting entity is Rule Communication – Nordic AB of Stockholm under Swedish law, a data processing agreement is published, and it covers processing within the EU/EES with standard contractual clauses for any third-country transfers. We found no public information on where the platform is hosted, and the subprocessor list sits in a contract appendix rather than published with locations — solid paperwork, not yet a proven chain for my subscriber data. 2 7 8
The Integrator
The contracting entity is Rule Communication – Nordic AB, registration number 556740-1293 at Kammakargatan 48, Stockholm, under Swedish governing law, with a published data processor agreement stating that processing takes place within the EU/EES and naming standard contractual clauses under Decision 2010/87/EU for any third-country transfers plus a 14-day objection window for new subprocessors. We found no public information on hosting infrastructure, sending infrastructure locations, or the subprocessor list itself in the captured pages, so the chain is proven only at the mid level — and I weigh that heavily. 2 4 8
The Skeptic
The data processing agreement names a Swedish contracting entity with registration number and Stockholm address, Swedish governing law, audit rights, encryption, 30-day deletion after expiry, and a 14-day objection window for subprocessors. But we found no public information on hosting infrastructure or subprocessor locations, and the same agreement books third-country transfers under standard contractual clauses — a Schrems II instrument, not a proven European chain. 2 4 8
Pricing transparency
not rated — the vendor publishes no price
panel disagrees
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 is public with concrete limits — 250 active members importable and 1,000 emails per month — which is more than a bare "from" price. We found no public information on paid tiers, per-contact scaling or overage, so the real invoice for a growing list cannot be computed from the captured pages. 4 10
The Deliverability Engineer
A free plan is public with concrete limits: 250 active members imported and a total of 1,000 emails per month. We found no public information on paid tier prices, how cost scales with contacts or send volume, overage rates, or VAT treatment — so the real invoice for a real list cannot be computed from what is published. 4 10
The Data Protection Officer
A free plan with public hard limits — 250 importable active members and 1,000 emails a month — is stated alongside free sign-up. I found no public information on paid tiers, contact-tier pricing, overage rates or VAT treatment, so the real invoice for a growing list cannot be computed from public pages. 4 10
The Shop Owner
A free plan is public and precise — 250 active members imported and 1,000 emails per month — which tells a small sender exactly what they get before paying. We found no public information on paid-tier prices, billing period, contact-band scaling or VAT treatment, so I cannot compute what my own list would cost and my revenue channel would be priced on faith. 1 4 10
The Integrator
A free plan is public with its limits stated precisely — 250 active members importable and a total of 1,000 emails per month — and self-service signup is offered. No captured page prices the paid tiers, contact bands, or overage, and the route shown for anything beyond free is a demo and CSM meetings. 1 4 10
The Skeptic
A free plan with hard limits — 250 active members and 1,000 emails per month — and a "Sign up free" button are the only priced items on any captured page. We found no public information on any paid tier's price, billing period or limits, and the vendor offers free CSM meetings as sales support, pointing to a conversation-based sale. 4 10
European sovereignty — proven facts
0 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 | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Rule
Is Rule European?
Not determined: the vendor’s pages as captured do not say where Rule is based.
Where does Rule store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does Rule have a free plan?
Yes. Rule has a free plan, per the vendor’s page captured 3 Nov 2026.
What are the best alternatives to Rule?
As of 3 Nov 2026, the panel rates Brevo (3.5/5), CleverReach (3/5) and Dotdigital (3/5) highest among the other 31 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). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Rule alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement, Hosting location. Not confirmed on the vendor’s own pages as captured.
- 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.
- 8 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
- 4 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
- 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 compliance 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
- 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page rule.io Checked 3 Nov 2026 Details →
- 2 Data processing agreement (dpa) — found from the homepage www.rule.io Checked 3 Nov 2026 Details →
- 3 Campaigns & automation — found from sitemap www.rule.io Checked 3 Nov 2026 Details →
- 4 Campaigns & automation — found from sitemap www.rule.io Checked 3 Nov 2026 Details →
- 5 Deliverability infrastructure — found from sitemap help.rule.io Checked 3 Nov 2026 Details →
- 6 Deliverability infrastructure — found from sitemap help.rule.io Checked 3 Nov 2026 Details →
- 7 Consent, proof & tracking limits — found from sitemap www.rule.io Checked 3 Nov 2026 Details →
- 8 Consent, proof & tracking limits — found from sitemap www.rule.io Checked 3 Nov 2026 Details →
- 9 List ownership, import & exit — found from sitemap help.rule.io Checked 3 Nov 2026 Details →
- 10 List ownership, import & exit — found from sitemap help.rule.io Checked 3 Nov 2026 Details →
- 11 Integrations & API — found from sitemap help.rule.io Checked 3 Nov 2026 Details →
- 12 Integrations & API — found from sitemap help.rule.io Checked 3 Nov 2026 Details →