Encharge
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 4 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Ench Corp. (Encharge) · encharge.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.
Encharge at a glance
- Vendor
- Ench Corp. (Encharge)
- Headquarters
- Incorporated in the United States source, captured 30 Sep 2026
- Data hosting
- In the EU; pages mention the United States and Ireland source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Encharge 2.5/5, the mean of 6 judges. Encharge is a marketing automation platform positioned for B2B SaaS businesses. how scores are made
- As of
- Vendor pages captured 29 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Encharge is a marketing automation platform positioned for B2B SaaS businesses. Its strongest showing is channel coverage, the only criterion whose scores never drop below 6: email, SMS through a native Twilio integration and custom Facebook audiences all run off one user profile. Journey orchestration and CRM and data follow: a drag-and-drop flow builder with event, webhook and Segment entry and if/else branching, plus two-way sync with Salesforce and HubSpot and a documented API set. The bench's weak marks land on consent and profiling and sovereignty: the vendor's own GDPR checklist marks objection and stop-processing 'not started', the captured pages give different figures for hosting — trust pages state all app data sits with AWS in Ireland while the terms state the site is hosted in the United States — and the only transfer safeguard named is the EU-US Privacy Shield Framework, and the contracting entity is PXCH Holding I, LLC of Miami. Judges' marks stayed within a single point on every criterion, so no genuine split emerged; pricing transparency reflects that no public prices appear on the pages.
Speaks for it
- Email, SMS through a native Twilio integration and custom Facebook audiences all act on a single user profile
- A drag-and-drop flow builder supports event, segment, score and webhook entry, if/else branching on field values and an End Flow step
- Two-way sync with Salesforce and HubSpot covers default and custom fields, filtering by any Salesforce field and near-instant email-activity sync
- REST, ingestion and JavaScript APIs are published with a downloadable OpenAPI 3 definition, and anonymous-to-known identity resolution is documented
- Scoring on engagement and attributes triggers segments, sales tasks and automatic HubSpot deals with assigned deal owners
Held against it
- The captured pages give different figures for hosting, with all app data stated to sit with AWS in Ireland while the terms state the site is hosted in the United States
- The only transfer safeguard named is the EU-US Privacy Shield Framework, and the contracting entity is PXCH Holding I, LLC of Miami
- The vendor's own GDPR checklist marks objection and stop-processing items 'not started', and backups are retained for 90 days beyond deletion
- We found no public information on duplicate handling, per-field conflict resolution or documented API rate limits for the CRM syncs and APIs
- No public prices appear on the captured pages — no tier costs, contact or send limits — only a 'Get Started — It's Free' claim and a free trial
Best for
- You run behaviour-driven email and SMS journeys off one profile, with entry from product events via Segment, an ingestion API or webhooks
- Your team runs Salesforce or HubSpot and wants scores, deals and email activity synced both ways, including custom fields
- You are a B2B SaaS team that scores leads on in-app engagement and hands off to reps as sales tasks and HubSpot deals with assigned owners
Avoid if
- You need one consistent data-residency story for named EU residents: the captured pages state Ireland for all app data and the United States for the site itself, and the only transfer safeguard named is the EU-US Privacy Shield Framework
- You must evidence consent per channel with timestamps, or handle objection and stop-processing requests — the vendor's own GDPR checklist marks those items 'not started'
- You need published prices before a shortlist — the public pages show only a 'Get Started — It's Free' claim, with no tier price, contact limit or send volume
The scores
| Criterion | Panel median |
|---|---|
| Journeys & orchestration | 3 of 5 |
| Lead scoring, routing & lifecycle | 2.5 of 5 |
| Channels & personalisation | 3 of 5 |
| Consent, tracking & profiling | 2 of 5 |
| CRM integration & data model | 3 of 5 |
| European sovereignty | 2 of 5 |
Journeys & orchestration
Show reasoningHide reasoning
How this is scored
Multi-step automation: triggers, branching, waits, goals — and what happens when a contact qualifies for several journeys at once.
0 — No automation; the product sends one-off campaigns only.
3 — Autoresponders or linear sequences started by a trigger such as a sign-up or a tag, with waits between steps.
5 — A visual workflow builder with triggers on behaviour and attributes, if/else branching and waits, and goals or exit conditions that take a contact out of the flow.
8 — Event-driven entry from external systems through an API, frequency capping and suppression across journeys, priority when a contact qualifies for several, per-contact journey state and reporting per step, versioning or safe editing of a live journey, and testing against real records.
10 — Orchestration is coherent across the whole programme: one decision layer deciding what a person receives next regardless of which journey wants to send it, holdout groups for measurement, and journeys documented and readable months later.
The Demand Gen Lead
Real orchestration, not autoresponders: drag-and-drop flows, event entry from Segment, an ingestion API and webhooks, if/else branching on field values, and exit steps. We found no public information on frequency capping, priority when a contact qualifies for several journeys, per-step reporting or safe editing of a live journey — the governance layer I need before trusting it with a quarter. 1 4 9
The Sales Ops Manager
A visual flow builder is documented with event and attribute triggers, property filters on event triggers, If/Else branching through the Check Condition step, webhook entry and an End Flow action, plus emails triggered by action or inaction. We found no public information on frequency capping or suppression across journeys, priority when a contact qualifies for several, or safe editing and versioning of a live flow. 1 4 9 6
The Data Protection Officer
A visual flow builder is documented with event, webhook, form and CRM triggers, if/else conditions and an End Flow step, and entry can come from external systems through a webhook and the ingestion APIs. We found no public information on waits between steps, frequency capping or suppression across flows, what happens when a contact qualifies for several flows, or safe editing and versioning of a live flow. 1 4 9 12
The Lifecycle Marketer
Drag-and-drop flows with behavioural event triggers, webhook entry, field-based if/else branching, an End Flow exit and A/B testing of emails and flows are all documented. We found no public information on frequency capping or suppression across journeys, priority when one person qualifies for several, or holdout groups, so this is a capable workflow builder rather than evidenced whole-programme orchestration. 1 4 9 12
The Solution Architect
The drag-and-drop flow builder has event, segment and score triggers, if/else conditions on field values, an explicit end-flow step, and entry from external systems via webhooks, Segment events and an Ingestion API — a real workflow engine, not autoresponders. I stop short of more because we found no public information on waits between steps, frequency capping or suppression across flows, priority when a person qualifies for several journeys, or safe editing of a live journey. 1 4 6 9
The Skeptic
The flow builder is real and documented: Event and Segment Event triggers on a visual canvas, if/else Check Condition steps on field values, End Flow exits, and a Receive Webhook trigger that lets outside systems start a flow. Waits are implied by trial-expiration and inaction-triggered follow-ups rather than named as a step. What we found no public information on is the discipline between journeys — frequency capping, priority when a contact qualifies for several at once, and safe editing of a live flow. 1 4 9
Lead scoring, routing & lifecycle
Show reasoningHide reasoning
How this is scored
Scoring, qualification and handover to sales — including whether the customer can explain to a lead why the system decided what it decided.
0 — No scoring, lifecycle or lead handling at all; the product is a sending tool for lists.
3 — A rule-based lead score from attributes or engagement, or lifecycle stages set by tags or fields.
5 — Configurable lead scoring on attributes and behaviour, lifecycle or pipeline stages, and qualified leads assigned or notified to sales.
8 — Multiple scoring models per product or region, negative scoring and score decay, account-level scoring alongside contact-level, routing rules to owners or teams with follow-up SLAs, and score history visible per contact.
10 — Scoring is explainable and accountable: the contribution of each signal visible per record, model changes versioned with their effect on the funnel, routing rules auditable, and predictive scoring — where offered — documented well enough for a DPO to assess it as automated decision-making.
The Demand Gen Lead
Scoring runs on engagement and attributes, automated actions fire when a user reaches a specific score, sales tasks are assigned to reps, and the score lands in HubSpot via two-way sync where flows create deals and assign deal owners — a handover sales will actually use. We found no public information on negative scoring, score decay, account-level scoring, score history per contact or follow-up service levels. 6 7
The Sales Ops Manager
Scoring on engagement and attributes is configurable, messages and actions fire when a user reaches a score, sales tasks go to reps based on score, and automation flows create HubSpot deals with deal owners assigned while the score syncs back to HubSpot. We found no public information on negative scoring, score decay, multiple scoring models, or score history visible per contact. 6 7
The Data Protection Officer
Scoring on engagement and attributes is configurable, triggers automated actions at score thresholds, and hands over to sales through assigned tasks and automatically created HubSpot deals with owners. We found no public information on multiple scoring models, negative scoring or decay, score history per contact, or any documentation of how a score was computed for an individual — the piece I would need to assess automated decisions about a person. 6 7 12
The Lifecycle Marketer
Scoring on engagement and attributes, score-triggered segments and messages, sales-task assignment and automatic HubSpot deal creation with named deal owners are all evidenced. We found no public information on negative scoring, score decay, multiple scoring models, account-level scores or score history per contact, which is where a scoring programme becomes accountable. 6 7
The Solution Architect
Scoring on engagement and attributes is configurable, scores drive segments and automated actions, sales tasks are assigned to reps, and automation flows create HubSpot deals with named deal owners — a genuine handover to sales. We found no public information on multiple scoring models, negative scoring or decay, account-level scoring, follow-up SLAs, or per-contact score history, so nobody could explain to a lead what built their number. 6 7
The Skeptic
Scoring on engagement and attributes is stated, scores push people into segments and trigger automated actions, and qualification hands off cleanly — flows create HubSpot deals with assigned deal owners, and sales tasks go to reps based on score. The lifecycle itself lives in the CRM, not in this product. We found no public information on negative scoring, score decay, multiple scoring models, or score history per contact — so a lead asking why the system scored them as it did has no documented answer. 6 7
Channels & personalisation
Show reasoningHide reasoning
How this is scored
What the platform can send and personalise — email, SMS, push, on-site content, ad audiences — judged on what shares one profile and one suppression list.
0 — Not a sending platform; the product cannot deliver messages on any channel.
3 — Email with merge-field personalisation, plus sign-up forms or landing pages.
5 — Email plus at least one further channel (SMS, push, or ad-audience sync) driven from the same contact profile, and dynamic content blocks based on contact data.
8 — Email, SMS and push from one profile with shared unsubscribe handling, on-site personalisation, ad-audience sync to the major networks, cross-channel frequency capping, and content personalised on behaviour rather than only on stored fields.
10 — Channel is a delivery detail: one profile and one consent state across every channel, next-best-channel selection, and personalisation that draws on the full behavioural record without the marketer assembling it by hand.
The Demand Gen Lead
Email and SMS ride the same profile through a native Twilio integration — including an SMS follow-up when a lead ignores email, which is genuine behaviour-driven cross-channel work — alongside Facebook custom-audience actions, dynamic merge-tag blocks and in-app Intercom messages. We found no public information on push delivery, cross-channel frequency capping or shared unsubscribe handling across channels. 1 4 8
The Sales Ops Manager
Email plus SMS through the native Twilio integration and custom Facebook audiences are driven from the same contact profile, with dynamic merge blocks and personalisation drawing on event properties. We found no public information on push, on-site personalisation, cross-channel frequency capping, or shared unsubscribe handling across channels. 1 4 8
The Data Protection Officer
Email, SMS through a native Twilio integration, and Facebook custom-audience actions all run from the same user profile, with dynamic blocks and messages personalised on behaviour rather than only stored fields. We found no public information on push, on-site personalisation, cross-channel frequency capping, or shared unsubscribe handling across channels. 1 4 8
The Lifecycle Marketer
Email plus native Twilio SMS and Facebook custom audiences, with dynamic blocks and segmentation on email opens, clicks and event properties, gives behavioural personalisation from one profile. We found no public information on push, on-site personalisation, shared unsubscribe handling or cross-channel frequency capping. 4 8
The Solution Architect
Email, SMS through the native Twilio integration, Facebook custom-audience actions and in-app Intercom messages all run off the one user profile, with merge-tag dynamic blocks and segments built from opens, clicks and product events. We found no public information on push, on-site personalisation, shared cross-channel unsubscribe handling, or cross-channel frequency capping, so this is email-plus rather than one consent state across every channel. 1 4 8 10
The Skeptic
Email with dynamic merge blocks, SMS through the native Twilio integration, and custom Facebook audiences all act on one profile, and personalisation runs on behaviour — event properties, interaction segments, SMS drawing on the whole marketing stack — not just stored fields. On push sending, shared unsubscribe handling across channels, and cross-channel frequency capping we found no public information. 4 8
Consent, tracking & profiling
Show reasoningHide reasoning
How this is scored
The platform builds behavioural profiles of named people. Consent capture and proof, tracking that can be limited, retention, and whether automated decisions about individuals are documented and contestable.
0 — The vendor states a practice that defeats consent, such as importing purchased lists or tracking named contacts with no opt-in mechanism at all.
3 — Double opt-in available and unsubscribe handled per contact.
5 — Double opt-in with the consent timestamp and source stored per contact, consent or subscription status per channel, and a documented way to answer access and erasure requests.
8 — Consent reproducible as evidence with the wording versioned, tracking switchable per contact or a cookieless or first-party tracking mode, profiling suppressible per person, retention for inactive records stated and executed per data category, and erasure covering derived scores.
10 — Built for the accountability principle: a per-contact history of what was tracked, scored and decided, automated decision-making documented well enough to support an Art. 22 DSGVO assessment, profiling off by default for anyone who has not consented to it, and deletion that removes derived scores as well as raw events.
The Demand Gen Lead
Double opt-in is enforced two ways, through forms and through flows, with a confirmation-link merge tag and a segment built on confirmation-link clicks, and there is a documented data-request route with permanent deletion and customer-controlled retention. We found no public information on consent timestamps and sources stored per contact, consent status per channel, or per-person suppression of profiling; the vendor's own GDPR checklist marks object-to-processing and stop-processing items as not started. 3 11 3
The Sales Ops Manager
Double opt-in is enforceable two ways with a confirmation link that can be segmented on, a data request route exists, deletion is stated as permanent, retention is customer-controlled, and backups expire after 90 days — set against anonymous behavioural tracking stitched to named profiles on identification. We found no public information on consent timestamps and source stored per contact, a cookieless or first-party tracking mode, suppression of profiling per person, or erasure covering derived scores. 11 3 10 3
The Data Protection Officer
Double opt-in can be enforced through forms or flows with a confirmation link, a data request can be submitted, and deletion is stated as permanent, with backups disclosed as retained for 90 days and not deletable by the customer. Anonymous activity is tracked across devices and merged into named profiles once identified, and we found no public information on consent proof with timestamp and source stored per contact, per-contact tracking or profiling suppression, retention for inactive records, or erasure covering derived scores; the vendor's own compliance checklist shows objection and stop-processing handling not started. 3 10 11 3
The Lifecycle Marketer
Double opt-in is enforced through forms and flows with confirmation links, data requests and permanent deletion are offered, and backup retention is stated at 90 days. The profiling of named people is real — anonymous activity across devices linked to profiles on identification — but we found no public information on consent timestamps and sources stored per contact or consent status per channel, and the vendor's own GDPR checklist marks objection, stop-processing and impact-assessment items as not started. 3 10 11 3
The Solution Architect
Double opt-in is documented two ways — forms with a built-in setting and flows using the confirmation-link merge tag — a data-request route is published, deletion is stated as permanent, and backup retention is disclosed at 90 days with no selective deletion from backups. We found no public information on consent timestamps or source stored per contact, per-channel consent status, a per-contact way to limit tracking, or whether erasure covers derived scores like the engagement score. 3 10 11 3
The Skeptic
Double opt-in is genuinely built in — a forms toggle plus a flows method with a confirmation-link merge tag and an Email Activity condition to segment the confirmed — and access and erasure requests run through a request form with permanent deletion. The profiling underneath is deep: anonymous activity is collected across devices and stitched into the profile on identification, deletion does not reach the 90-day backup set, and the vendor's own GDPR checklist shows objection and stop-processing marked 'not started'. We found no public information on consent timestamps or source stored per contact, consent per channel, or switching tracking or profiling off per person. 3 10 11 3
CRM integration & data model
Show reasoningHide reasoning
How this is scored
The join that decides the implementation: how the platform and the CRM stay in agreement about who a person is, and what happens when they disagree.
0 — No way to get contact data in or out beyond typing it in.
3 — CSV import and export, and a sync or connector to a named CRM.
5 — Two-way sync with at least one major CRM (or a built-in CRM) with field mapping, duplicate handling, and a documented API.
8 — Configurable conflict resolution per field, account and contact objects both modelled, custom objects supported, near-real-time sync with retry and an error log, and API rate limits documented.
10 — One record, two systems, no ambiguity: identity resolution across anonymous and known states, field-level ownership defined per system, replay of failed syncs, and a data model the customer can extend without vendor services.
The Demand Gen Lead
Two-way sync with both Salesforce and HubSpot — default and custom fields, filtering by any Salesforce field, email activity synced almost instantly — plus a REST and ingestion API with a downloadable OpenAPI definition, and anonymous browsing linked to identified profiles. We found no public information on duplicate handling, conflict resolution per field, custom objects, API rate limits or replay of failed syncs. 7 10 12 13
The Sales Ops Manager
Two-way sync with Salesforce and HubSpot is documented, with sync filtering by any Salesforce field, default and custom field support, near-instant email activity sync, and a documented REST API with a downloadable OpenAPI definition. We found no public information on duplicate handling, configurable per-field conflict resolution, a sync error log with retry, or documented API rate limits — exactly the disagreement rules that decide whether my pipeline report is right. 12 7 13
The Data Protection Officer
Two-way sync is documented for Salesforce, covering default and custom fields, record filtering and near-instant email activity sync, and for HubSpot with score and deal sharing, alongside a documented REST and Ingest API with an OpenAPI definition and anonymous-to-known identity resolution in the profile. We found no public information on duplicate handling, per-field conflict resolution, account or custom objects, or documented API rate limits — so what happens when the two systems disagree is not established. 7 10 12 13
The Lifecycle Marketer
Two-way sync with both Salesforce and HubSpot, default and custom field support, filtering on any Salesforce field, near-instant email-activity sync, and a REST API with an OpenAPI definition are evidenced, alongside identity resolution across anonymous and known states. We found no public information on duplicate handling, conflict resolution, custom objects or documented API rate limits. 7 10 12 13
The Solution Architect
Two-way sync with Salesforce ships as an AppExchange managed package supporting default and custom fields with per-field filtering and near-instant email-activity sync, HubSpot syncs scores and deals both ways, and the REST, Ingest and JavaScript APIs come with a downloadable OpenAPI definition. Anonymous-to-known identity resolution is explicitly documented, which is the join that decides implementations. We found no public information on duplicate handling, per-field conflict resolution, an account object alongside people, custom objects, sync retries and error logs, or API rate limits — the last one always surfaces in month three. 7 9 10 12 13
The Skeptic
Two-way sync to both Salesforce and HubSpot, filtering by any Salesforce field, all default and custom fields supported, email activity synced 'almost instantly', and a REST and ingestion API published as an OpenAPI 3 definition — the joins exist and are documented. We found no public information on duplicate handling, per-field conflict resolution, account-level objects, or API rate limits, which are exactly the questions that decide who a person is when the two systems disagree. 7 12 13
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where behavioural profiles of named EU residents are processed, who the contracting entity is, and which subprocessors see them. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which given the profiling is heavily. Dimensions the sources do not establish are unknown, not non-EU.
0 — Proven non-EU: a non-EU vendor and contracting entity with hosting and tracking stated outside the EU.
3 — One European element proven — an EU contracting entity or EU data residency stated — with the rest of the chain undocumented.
5 — An EU contracting entity and EU hosting both stated, and a data processing agreement offered.
8 — EU hosting on named infrastructure, EU contracting entity, a subprocessor list published with locations, and any non-EU processing (tracking, AI scoring, support access) named with its legal basis.
10 — Sovereign end to end and evidenced: every profile, event and derived score processed in the EU by European subprocessors, certification published, and no transfer requiring a Schrems II argument to survive.
The Demand Gen Lead
All app data is stated to sit on AWS in Ireland, the subprocessor list names Twilio's US infrastructure for email delivery, and a data processing agreement can be signed self-serve — but the contracting entity is a US LLC in Miami, and the terms state the site is hosted in the United States with continued use transferring data there. The captured pages give different figures for hosting location, and the only transfer safeguard named is the EU-US Privacy Shield Framework — for behavioural profiles of named EU people, that is a conversation with legal before I sign. 2 3 3
The Sales Ops Manager
All app data is stated to be hosted on AWS in Ireland, a subprocessor list is published naming US-located Twilio for email sending on certain accounts, and a self-serve data processing agreement is offered. The contracting entity is a US LLC, and the captured pages give different statements on hosting location — the terms state the site is hosted in the United States with express consent to US transfer, while the trust pages place app data in Ireland — and transfer safeguards cite the EU-US Privacy Shield Framework. 3 2 3
The Data Protection Officer
App data is stated to be hosted with Amazon Web Services in Ireland, a self-serve data processing agreement is published, and a subprocessor list names Twilio in the US for email sending on certain accounts. The contracting entity is a US LLC in Miami and the terms state the site is hosted in the United States with consent to US transfer, so the captured pages give different figures for where data sits, and no EU contracting entity or legal basis for the named non-EU processing is stated — a heavy weight for profiles of named EU residents. 2 3 3
The Lifecycle Marketer
The captured pages give different statements on hosting: the trust pages put all app data on AWS in Ireland with a self-serve data processing agreement and name Twilio in the US as an email sub-processor, while the Terms of Use state the site is hosted in the United States with consent to US transfer through continued use, under a Miami LLC as contracting entity. The transfer safeguard cited is the EU-US Privacy Shield Framework. For behavioural profiles of named EU residents I need a European contracting entity and one consistent residency story, so this sits between the lower levels. 2 3 3
The Solution Architect
All application data is stated to sit in AWS Ireland, a subprocessor list is published with Twilio's US infrastructure named for email sending on certain accounts, and a DPA is offered — but the contracting entity is PXCH Holding I LLC of Miami, and the terms state the site is hosted in the United States with continued use counted as consent to US transfer, so the captured pages give different figures for where data sits. The only transfer safeguard named is the EU-US Privacy Shield Framework, with Bulgarian governing law under a US LLC — a combination I would want clarified before putting named EU residents' profiles here. We found no public information on hosting options beyond AWS Ireland or any transfer impact analysis. 1 2 3 3
The Skeptic
All app data is stated to live with AWS in Ireland, a subprocessor list is published with locations, and a data processing agreement is offered for signing. But the contracting entity is PXCH Holding I, LLC of Miami, email delivery for certain accounts goes through Twilio Sendgrid whose infrastructure is 'located in the US', and the terms state the site is hosted in the United States — so the captured pages give different figures for where processing happens. The one transfer safeguard named is 'the EU-US Privacy Shield Framework', which has not been a valid basis since Schrems II; for profiles of named EU residents that is the argument this buyer should not have to make. 2 3 3
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their contact base and send volume — including the tier where automation actually begins, overage, and mandatory onboarding — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or a single tier with its contact limit.
5 — Prices per tier public with the billing period and contact limits stated, and which tier includes automation visible.
8 — Every tier priced publicly with contact and volume limits, feature boundaries, overage rates, onboarding costs, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given contact count, send volume and feature set, including overage, additional users and any implementation fee stated outright.
The Demand Gen Lead
We found no public pricing figures on the pages captured — only a free-to-start claim and terms mechanics: USD billing, sales tax added as the vendor deems required, prices changeable at any time, and fair-usage limits with termination for excess. I cannot compute an annual invoice for a contact base and send volume from public pages. 1 2 8
The Sales Ops Manager
The only public pricing signals are "Get Started — It's Free" and a free trial, alongside USD billing, pro-rated refunds up to 30 days after initial purchase, and sales tax added as deemed required. We found no public price for any tier, no contact or volume limits, and no cost stated for the named Done-for-you Onboarding and Migration premium plans, so a real annual invoice cannot be computed from public pages. 1 2 8
The Data Protection Officer
The only public price signal is a free-to-start claim; the premium onboarding and migration plans are named without amounts, and the terms cover currency, refunds, tax treatment and the right to change prices, but no tier price, contact limit or feature boundary appears on the captured pages. A buyer cannot compute a real annual invoice from public information. 1 2 8
The Lifecycle Marketer
The public pricing signals are a "Get Started — It's Free" claim, a free trial, and the terms' statements that payments are in US dollars with sales tax added and a 30-day pro-rated refund window. We found no public information on tier prices, contact or volume limits, which tier includes automation, overage rates, or the cost of the named onboarding and migration premium plans, so a buyer cannot compute an annual invoice from the captured pages. 1 2 8
The Solution Architect
Public pages show a free-start and free-trial claim, and the terms state USD billing, recurring charges, sales tax added 'as deemed required by us', and partial pro-rated refunds up to 30 days after initial purchase with none on renewals. We found no public information on paid tier prices, contact or volume limits, which tier includes automation, or the cost of the onboarding and migration 'Premium Plans', so a buyer cannot compute an annual invoice from public pages alone. 1 2 8
The Skeptic
Beyond a 'Get Started — It's Free' button that the email marketing page frames as a free trial, we found no public prices on the captured pages — no tiers with contact limits, no send volumes, no overage rates, and no price stated for the Done-for-you Onboarding or Migration 'Premium Plans' whose cost I looked for first. The terms say prices 'may change at any time', sales tax is added 'as deemed required by us', and refunds are pro-rated only up to 30 days after the initial purchase with none on renewals. No buyer can compute a real annual invoice from these pages. 1 2 8
European sovereignty — proven facts
4 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in US
unverified
Why unverified?The seat is stated only as a Terms-of-Service address with no commercial register cited; nothing in the excerpts marks the entity as a subsidiary. |
0/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?Optional sub-processors such as Twilio Inc may receive data, and the FAQ answer on transfers outside the EU only points to Irish data centers without an explicit 'no' statement. |
4/4 pts | 3 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source |
Proprietary
unverified
Why unverified?The proprietary claim covers the Site and its software generally; no excerpt names a specific licence (e.g., from a code repository) for the Encharge application itself. |
0/1 pts | 2 Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?Only the Trust Center link and the completed checklist entry are shown; the DPA text and the actual signing flow are not reproduced in the excerpt. |
1/1 pts | 3 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Encharge
Is Encharge European?
Not determined: the vendor’s pages as captured do not say where Encharge is based. Its vendor, Ench Corp. (Encharge), is incorporated in the United States, per the vendor’s page captured 30 Sep 2026.
Where does Encharge store data?
Encharge stores customer data in the EU, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention the United States and Ireland as hosting locations, per the vendor’s page captured 30 Sep 2026.
Does Encharge have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Encharge?
As of 18 Nov 2026, the panel rates Braze (3/5), HubSpot Marketing Hub (3/5) and ActiveCampaign (Automation) (3/5) highest among the other 20 Marketing Automation 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 (Automation) (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: Encharge 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 — Data processing agreement. Only the Trust Center link and the completed checklist entry are shown; the DPA text and the actual signing flow are not reproduced in the excerpt.
- Weak sourcing — Open source. The proprietary claim covers the Site and its software generally; no excerpt names a specific licence (e.g., from a code repository) for the Encharge application itself.
- Weak sourcing — Legal entity. The seat is stated only as a Terms-of-Service address with no commercial register cited; nothing in the excerpts marks the entity as a subsidiary.
- Weak sourcing — Hosting location. Optional sub-processors such as Twilio Inc may receive data, and the FAQ answer on transfers outside the EU only points to Irish data centers without an explicit 'no' statement.
- 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.
- 6 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
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 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
- 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
- 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 subprocessors 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page encharge.io Checked 29 Sep 2026 Details →
- 2 Terms of service — found from the homepage encharge.io Checked 30 Sep 2026 Details →
- 3 Security / trust page — found from the homepage gdpr.encharge.io Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
- 4 Journeys & orchestration — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 5 Journeys & orchestration — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 6 Lead scoring, routing & lifecycle — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 7 Lead scoring, routing & lifecycle — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 8 Channels & personalisation — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 9 Channels & personalisation — found from sitemap help.encharge.io Checked 16 Nov 2026 Details →
- 10 Consent, tracking & profiling — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 11 Consent, tracking & profiling — found from sitemap help.encharge.io Checked 16 Nov 2026 Details →
- 12 CRM integration & data model — found from sitemap help.encharge.io Checked 16 Nov 2026 Details →
- 13 CRM integration & data model — found from sitemap docs.encharge.io Checked 16 Nov 2026 Details →