Email Marketing & Newsletter
AWeber
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by AWeber Communications · www.aweber.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
AWeber, an email marketing and newsletter platform, scores best on integrations, 4 to 6, and campaign and automation, 5 to 6 — a documented API with OAuth 2, PKCE and free webhooks, plus automations on page-hit, engagement and RSS triggers with segment-targeted split tests of up to three groups. Import accepts five file formats with required source disclosure and a manual review answered within one business day, and domain authentication is documented with automatic DKIM and DMARC setup for 40+ providers and a re-check before every broadcast. Pricing transparency is weakest at 1 to 2: the only price on the captured pages is a limited-time done-for-you setup offer quoted at "$599 $79", with no public information on contact-tier prices, send limits or billing periods. Sovereignty scores run from 2 to 2: the contracting entity is AWeber Systems, Inc. at Pennsylvania addresses, Amazon AWS is named for cloud infrastructure hosting, and transfers rest on the Data Privacy Framework and standard contractual clauses. Criterion scores sit in narrow bands, persona-weighted totals span 3.4 to 4.4, and no flagged split was flagged.
Speaks for it
- DKIM and DMARC setup is documented with automatic record creation for 40+ domain providers, and authentication is re-checked before every broadcast
- List import accepts XLS, XLSX, TSV, CSV and TXT files, requires source disclosure, and passes through a review answered within one business day
- The API is documented with OAuth 2, scopes, PKCE and API keys, alongside free webhooks for subscriber events with HMAC-SHA256 verification
- Any list, or selected information within a list, can be exported at any time while the account is active
- Automations respond to page-hit, engagement and RSS triggers, with split tests of up to three groups targeted at a chosen segment
Held against it
- The only price on the captured pages is a limited-time done-for-you setup offer quoted at "$599 $79", and we found no public information on contact-tier prices, send limits or billing periods
- The contracting entity is AWeber Systems, Inc. at Pennsylvania addresses, Amazon AWS is named for cloud infrastructure hosting, and transfers rest on the Data Privacy Framework and standard contractual clauses
- Webhook delivery is explicitly not guaranteed, and we found no public information on retries or a sandbox
- The import flow allows the confirmation message to be skipped, and we found no public information on a stored consent record or on switching off open and click tracking
- We found no public information on SPF configuration, bounce suppression, complaint-loop handling or dedicated IP options
Best for
- You are wiring subscriber data into your own systems — integrations scored 4 to 6, the highest band on the table, on a documented API with OAuth 2 and free webhooks
- You are migrating an existing list and want reviewed imports — five file formats, required source disclosure, and a review answered within one business day
- You send from your own domain and want enforced authentication — automatic DKIM and DMARC setup for 40+ providers with a re-check before every broadcast
Avoid if
- You must keep EU subscriber data under EU processing — the contracting entity is AWeber Systems, Inc. at Pennsylvania addresses and the stated transfer basis is the Data Privacy Framework plus standard contractual clauses
- You need a computable invoice before committing — the captured pages show only a limited-time "$599 $79" setup offer and the existence of an AWeber Free plan
- Your automation depends on webhook delivery — delivery is explicitly not guaranteed
- You must enforce confirmed opt-in on every import — the import flow lets you choose whether the confirmation message is sent
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
Behavioural triggers are genuinely documented — page-hit automations, an engagement trigger, RSS-driven sends and tagging subscribers who visit a page — and split tests can target a segment with up to three groups on subject lines or content. What I found no public information on is journey branching, dynamic content per segment, or any test reporting significance rather than raw response, which is exactly the step a lifecycle programme needs, so this sits mid-table rather than top. 1 4 5 6
The Deliverability Engineer
Workflows with page-hit, RSS and engagement triggers plus website-visit tagging and segment-targeted split tests of subject lines and content are documented, which carries the multi-step automation and testing level. We found no public information on dynamic content per segment, send-time optimisation, holdout groups or significance reporting. 1 4 5
The Data Protection Officer
Automations and workflows are documented with engagement triggers and page-hit triggers, and split tests run subject-line and content variants with segment targeting and preset distributions. We found no public information on a visual journey builder, dynamic content per segment, or send-time optimisation, and split testing sits above the Free plan and caps at three groups. 1 4 5
The Shop Owner
The docs show genuine automation machinery — workflows with engagement and page-hit triggers, RSS automations, tagging subscribers off website visits — plus split tests of subject lines or content with up to three groups, preset distributions and segment targeting, and pre-built automations with ready-made landing pages. For my shop the hooks I actually buy for are missing from the evidence: we found no public information on cart or order events entering a journey, send-time optimisation, or test results reported with significance. 1 4 5
The Integrator
Split testing of subject lines and content is documented with segment targeting and preset distributions, and automations run on page-hit, engagement and RSS triggers with tagging from website visits — a solid mid-market feature set. I found no public information on a branching journey builder, dynamic content per segment, send-time optimisation, or tests that report significance, so I cannot credit the higher levels. 1 4 5
The Skeptic
Multi-step automations and workflows are documented with genuine triggers — page hits, engagement, RSS — and subscribers can be tagged by website visit, while split tests cover subject lines or message content against a chosen segment. What holds it below the top rungs: we found no public information on a journey builder with branching, dynamic content per segment, send-time optimisation, or testing that reports significance, and split testing is gated above the free plan. 1 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 — 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
Authentication is documented unusually well: automated DKIM and DMARC setup for forty-plus DNS providers, a status view in the account, a default DMARC reporting address, M3AAWG membership, and sender authentication re-checked on every broadcast. The captured pages are silent on bounce suppression, complaint-loop handling, dedicated IPs and sunsetting, so I cannot credit the full next level despite the strong setup story. 3 6 7
The Deliverability Engineer
DKIM and DMARC are documented for automatic setup across 40+ DNS providers and manual entry, record status is viewable in the account, a default DMARC reporting address is offered, and authentication is re-verified before every broadcast with unauthenticated sends returned to draft. We found no public information on SPF, bounce suppression, complaint-loop handling, dedicated IP options, warm-up or engagement-based sunsetting. 3 6 7 10
The Data Protection Officer
DKIM and DMARC are documented deeply — automatic record creation for over 40 DNS providers, a status view, a default DMARC reporting address, and a re-check of authentication before every broadcast that returns the mail to draft if the domain falls out of order, which is enforced authentication I genuinely value. We found no public information on bounce suppression, complaint-loop handling, dedicated IP options or seed testing, which holds this back. 3 6 7
The Shop Owner
Authentication is properly documented — DKIM and DMARC, automatic for forty-plus domain providers with status visible per domain, and every broadcast re-checks authentication so an unauthenticated domain drops the send back to Draft, which is more enforcement than most vendors show. But we found no public information on SPF, bounce suppression, complaint-loop handling, dedicated IPs or inbox-placement testing, so half the mail-arrives story is untold. 3 6 7
The Integrator
DKIM and DMARC setup is documented unusually well — automatic for 40+ domain providers, simultaneous setup, a status view per domain, a default DMARC reporting address, and sender authentication re-verified on every broadcast. I found no public information on SPF, bounce handling, complaint-loop handling, dedicated IP options or warm-up, so only the authentication half of the picture is evidenced. 3 6 7
The Skeptic
DKIM and DMARC setup is documented unusually thoroughly — automatic records for 40+ providers, a status view, a default reporting address, and authentication re-checked before every broadcast with the message pulled back to draft if the domain fails. But we found no public information on SPF configuration, bounce handling, complaint-loop processing, or dedicated-IP options, which is the rest of what a deliverability story needs. 3 6 7
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
Confirmed opt-in is clearly defined — non-clickers never become active — and imports must disclose how subscribers signed up, which is more diligence than most. But I found no public information on whether opt-in is the default, what the stored consent record contains beyond a click, one-click or cross-list unsubscribe honouring, or any way to switch open and click tracking off, so the burden of proof stays entirely with me as controller. 8 9 10
The Deliverability Engineer
Confirmed opt-in is clearly defined with non-clickers never becoming active, unsubscribe-at-any-time and erasure/restriction rights are documented. The import flow allows skipping the confirmation message, and we found no public information on a stored consent record with source and wording, one-click mechanics, or any option to limit or disable open and click tracking. 8 9 10
The Data Protection Officer
Confirmed opt-in is properly defined — nobody becomes active without clicking the confirmation link — and imports require you to state how subscribers signed up, with erasure and access handled on stated timescales. We found no public information on whether the consent record stores IP or the wording consented to, on cross-list unsubscribe, and — the part that decides this score — on whether open and click tracking can be limited or switched off at all. 2 8 9 10
The Shop Owner
Confirmed opt-in is clearly defined — nobody becomes active without clicking the confirmation link — and the import flow asks how subscribers signed up, lets me require a confirmation message on import, and the GDPR page documents erasure, restriction and portability with removal promised within 30 business days. Beyond that it thins out: we found no public information on what the stored consent record holds, on one-click unsubscribe mechanics, or on turning open and click tracking off. 8 9 10
The Integrator
Confirmed opt-in is documented and the import flow lets you switch the confirmation message on or off, which makes double opt-in optional rather than a default; imports do require stating how subscribers signed up, but I found no public information on a stored consent record per subscriber, one-click unsubscribe mechanics, or any way to limit or switch off open and click tracking. Erasure on request and a 30-day response window are documented, which keeps this above the floor. 2 8 9 10
The Skeptic
Confirmed opt-in is clearly defined — a click on a confirmation link before a subscriber becomes active — and imports must declare how subscribers signed up, but nothing shows confirmed opt-in as the default (imports can skip the confirmation message), and we found no public information on a stored consent record carrying source, IP or the wording consented to. Tracking limits are the bigger hole: no captured page mentions turning open or click tracking off, let alone pixel-free sending. 8 9 10
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 thoroughly documented — five file formats, custom fields, tags, update modes and a review queue with a one-day SLA — and portability is promised as export of any list or selected information at any time while the account is active. Whether engagement history and unsubscribe state can leave is not shown, the free migration team only moves accounts in, and erasure is promised within thirty business days rather than evidenced. 1 2 3 9 10
The Deliverability Engineer
Import is thorough — five file formats, custom fields, tags, update modes, mandatory source disclosure and a review process — and export of lists or selected information is available on an active account with an unsubscribe-status filter, alongside a full API and a 30-business-day removal response commitment. We found no public information on exporting engagement history, campaigns or templates, or on evidenced rather than asserted deletion. 2 3 9 10
The Data Protection Officer
Import is thoroughly documented — XLS, XLSX, TSV, CSV and TXT, custom fields, tags, update options and a manual review with a one-business-day SLA — and lists can be exported at any time with unsubscribe state filterable out, subscriber removal carries a 30-business-day response commitment, and migration in is free. We found no public information on exporting engagement history, campaigns or templates, or on any full-fidelity account export for leaving. 1 2 3 9 10 11
The Shop Owner
Import is the best-documented part of the product — five file formats, custom fields, tags, update rules, a review queue answered within one business day and an import history page — and export of any list or selected information is promised at any time while the account is active, with a full-featured API to sync elsewhere. But we found no public information on exporting engagement history or unsubscribe state, and the free migration offer runs one direction only, into AWeber. 1 10 3 13
The Integrator
Import takes CSV, spreadsheet and text files with custom fields, tags and update options behind a documented review process, and export of lists or selected fields is available at any time while the account is active, with filters that expose subscription status. I found no public information on exporting engagement history, campaigns or templates, or on full-account export; deletion is met with a 30-business-day response window rather than evidenced erasure. 3 9 10
The Skeptic
Import is documented to a rare level of detail — five file formats, three update modes, tagging, manual review with a one-business-day service level — and export of any list or selected information is a stated right at any time while the account is active, with a full API to sync elsewhere. We found no public information on exporting engagement history, campaigns or templates, and the only stated deletion commitment is a response within 30 business days. 2 3 9 10 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
A documented API with OAuth 2, PKCE, scopes and a rate-limiting topic, plus no-cost webhooks for the core subscriber events — added, subscribed, unsubscribed — with HMAC-SHA256 payload verification, is the full mid-tier package. Webhook deliveries carry no guarantee and retries and a sandbox are undocumented, and while a searchable directory claims hundreds of integrations, the captured pages name no major shop platform, so I stop short of the higher bar. 12 13
The Deliverability Engineer
A documented API with OAuth 2, scopes, PKCE and API keys, plus free webhooks for the three core subscriber events with HMAC-SHA256 verification, meets the documented-REST-with-webhooks level; delivery is explicitly not guaranteed and no retry mechanism is shown. A searchable directory advertises hundreds of integrations, but we found no named major shop or CRM platform in the captures and no sandbox. 2 12 13
The Data Protection Officer
The API is real — OAuth 2 with PKCE and documented scopes, a rate-limiting FAQ, and free webhooks for the core subscriber events with HMAC-SHA256 payload verification — plus a searchable directory of hundreds of integrations with a connect button, though the captured pages name only the WordPress plugin. Webhook delivery is explicitly best-effort, and we found no public information on retries or a sandbox. 4 12 13
The Shop Owner
The developer surface is real — OAuth 2 with scopes and PKCE, a rate-limiting FAQ topic, free webhooks with HMAC verification and a deduplication identifier — but the only outbound events are subscriber added, subscribed and unsubscribed, and delivery is explicitly not guaranteed. As a shop owner the top end fails me: we found no public information naming a shop or CRM platform among the claimed hundreds of integrations, no order or cart events, and no public information on a sandbox to build against. 12 13
The Integrator
The API is real and documented: OAuth 2 with scopes and PKCE, an API key, a rate-limiting FAQ, and free webhooks for the core subscriber events with HMAC-SHA256 verification and a deduplication header. But webhook delivery is explicitly not guaranteed and I found no public information on retries, a sandbox, a versioned API with a deprecation policy, or vendor-maintained bidirectional shop integrations — the directory is largely integrations developers have already created. 12 13
The Skeptic
The API is documented with OAuth 2, scopes, PKCE and API keys, webhooks cover the core subscriber events with HMAC-SHA256 payload verification and a deduplication identifier, and a searchable directory lists hundreds of integrations with a connect button. But webhook delivery is explicitly not guaranteed — so there is no retry story — rate limiting appears only as a FAQ question without documented figures, and we found no public information on a sandbox or vendor-maintained bidirectional shop integrations. 12 13
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
Everything contracts and processes on the US side: AWeber Systems, Inc. in Pennsylvania, Amazon AWS for hosting, OpenAI and Anthropic for content generation, Google for analytics — I found no EU hosting option at all, and data residency is not confirmed on the vendor's own captured pages. Transfers rest on the Data Privacy Framework and standard contractual clauses rather than EU processing, and the customer pre-authorises any other third parties as subprocessors, which is precisely the gap I will not accept for subscriber behaviour data. 2 3
The Deliverability Engineer
Vendor, contracting entity and both postal addresses are US, and every named subprocessor — AWS, Anthropic, OpenAI, Google, Cloudflare, Stripe, PayPal — is a US processor, with transfers resting on the Data Privacy Framework and standard contractual clauses. No EU hosting, EU entity or EU contracting path appears in the captured pages; the published subprocessor list is the only thing above the floor. 2 3
The Data Protection Officer
The contracting entity is AWeber Systems, Inc. in Pennsylvania, we found no public information on EU hosting, and the entire stated transfer basis is standard contractual clauses (modules 1 and 2) plus the EU-US Data Privacy Framework — exactly the argument I would rather not have to make — with named US subprocessors including AWS, OpenAI and Anthropic for customer content generation. A general authorisation to engage further third parties as sub-processors with a five-day objection window deepens the exposure. 2 3
The Shop Owner
The vendor, contracting entity and hosting all sit in the United States: AWeber Systems, Inc. at Pennsylvania addresses is the data importer, Amazon AWS is named for cloud infrastructure hosting, and Google, OpenAI and Anthropic appear in the subprocessor table for analytics and content generation. The published subprocessor list, Data Privacy Framework certification and standard contractual clauses with breach notice and audit assistance are more than many US vendors show. But we found no public information on EU hosting or an EU contracting entity, so every order and click my shop generates crosses the Atlantic on a Schrems II argument. 2 3
The Integrator
The contracting entity is AWeber Systems, Inc. in Pennsylvania, hosting sits with Amazon AWS, the named subprocessors include US names such as Anthropic, OpenAI, Google and Stripe, and I found no public information on EU hosting or an EU entity. The published subprocessor list and a stated transfer basis — the Data Privacy Framework and standard contractual clauses — lift this just above the floor, but the whole arrangement rests on the transfer argument I would rather not have to defend. 2 3 9
The Skeptic
The contracting entity is a US company at Pennsylvania postal addresses, the subprocessor table names Amazon AWS for cloud infrastructure hosting, OpenAI and Anthropic for customer content generation, and Google for business analytics, and we found no public information on any EU hosting option for storage or sending. Transfers are carried by Data Privacy Framework self-certification and standard contractual clauses, so the chain is documented — but every named link in it sits in the US. 2 3
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 only public price I can find is a promotional one-time setup offer of $79 marked down from $599, alongside documentation naming an AWeber Free plan that excludes split testing. No contact-tier prices, send limits, billing periods or overage rates appear in the captured pages, so a sender cannot compute even an approximate invoice for their list size. 1 5
The Deliverability Engineer
The only prices visible are a promotional done-for-you setup at "$599 $79" and the note that split testing is unavailable on the free plan. We found no public information on plan tiers, contact prices, send limits, overage rates or VAT treatment, so the real invoice is not computable from these pages. 1 5
The Data Protection Officer
The only price on the captured pages is a $79 limited-time done-for-you setup offer, marked down from $599, alongside the existence of a Free plan that split testing sits above. We found no public information on contact-tier prices, billing periods, send limits or overage rates, so a real invoice cannot be worked out from these pages. 1 5
The Shop Owner
The only price in the captured pages is a limited-time done-for-you launch offer quoted as '$599 $79', plus the bare existence of a free plan that excludes split testing. We found no public information on contact-tier prices, billing periods, send limits, overage or VAT treatment, so I cannot compute the invoice for my list size and send volume from what is public. 1 5
The Integrator
The only price visible anywhere is a limited-time done-for-you launch offer quoted as "$599 $79", plus the existence of a Free plan that gates split testing behind an upgrade you are told to discuss with the Customer Solutions team. I found no public information on subscription tier prices, contact or send limits, overage rates, or VAT treatment, so a real invoice cannot be computed from these pages. 1 5
The Skeptic
The only price on the captured pages is a limited-time setup offer — "$599" struck through to "$79" to launch your email marketing — and a free plan is visible only sideways, through a note that split testing is not accessible on it. We found no public information on contact-tier prices, billing period, send limits, overage rates, or the tier where automation begins. 1 5
European sovereignty — proven facts
2 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 | Incorporated in US ⚠ unverified | 0/3 pts | 3 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 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 — Legal entity. Jurisdiction rests on postal addresses naming "USA" and the US-style "Inc."; no state of incorporation or commercial register is stated.
- Weak sourcing — Data residency. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Subprocessors. The excerpted sub-processor table is truncated by "[…]" and no provider's headquarters are stated; the US attribution rests on the names Amazon AWS and Anthropic, and the customer-data nature of some rows (Calendly, Discourse) is not spelled out.
- 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.
- 7 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
- 6 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
- 4 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 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
- 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 legal 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
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. 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.aweber.com Checked 29 Sep 2026 Details →
- 2 Privacy policy — found from the homepage www.aweber.com Checked 30 Sep 2026 Details →
- 3 Data processing agreement (dpa) — found from the homepage www.aweber.com Checked 30 Sep 2026 Details →
- 4 Campaigns & automation — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
- 5 Campaigns & automation — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
- 6 Deliverability infrastructure — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
- 7 Deliverability infrastructure — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
- 8 Consent, proof & tracking limits — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
- 9 Consent, proof & tracking limits — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
- 10 List ownership, import & exit — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
- 11 List ownership, import & exit — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
- 12 Integrations & API — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →
- 13 Integrations & API — found from sitemap docs.aweber.com Checked 30 Sep 2026 Details →