User.com
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by User.com Sp. z o.o. · user.com
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.
User.com at a glance
- Vendor
- User.com Sp. z o.o.
- Headquarters
- Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting
- In the EU source, captured 10 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 10 Nov 2026
- Panel verdict
- The AI panel rates User.com 2.5/5, the mean of 6 judges. User.com, a marketing automation platform, comes out of this bench strongest on channels and consent and weakest on pricing and lead qualification. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
User.com, a marketing automation platform, comes out of this bench strongest on channels and consent and weakest on pricing and lead qualification. Channel coverage scores cluster at 6-7: email, SMS, WhatsApp, web and mobile push, mobile wallet, on-site experience and live chat are documented off one contact profile. Journey orchestration holds at 6 with no spread — a visual builder with per-automation entry throttling, but no public information on cross-journey suppression or per-step reporting. Consent and profiling runs 6-7, split between judges calling it the deepest-documented area and those noting consent kept as yes/no attributes without timestamps or versioned wording. CRM and data sits at 5 on Zapier-based HubSpot sync. The weak ends are sharp: pricing transparency at 0-1, with a free trial and demo scheduling the only visible commercial elements; lead management at 2-4, the widest spread — the sales-ops view credits documented capture and Facebook Lead Ads rep assignment while others weigh no public information on lead scoring or lifecycle stages; sovereignty at 4, on a French entity and an EEA-server statement scoped to EEA contacts.
Speaks for it
- Email, SMS, WhatsApp, web and mobile push, mobile wallet, on-site experience and live chat are documented off one unified contact database, with unsubscribe state stored per channel.
- Per-channel consent attributes, double opt-in, a preference centre and email tracking that can be disabled workspace-wide or gated to explicit consent are documented.
- Automation settings document entry-frequency controls including a required restart break, hour and date-range limits, and draft-before-activation.
- Two-way HubSpot sync for contacts and companies, plus CSV and Excel import with deduplication, is documented.
- Manual contact deletion is documented as permanent, removing engagement history, tracking and chat conversations, and anonymous contacts auto-delete after a configurable number of days.
Held against it
- We found no public information on lead scoring, lifecycle stages or routing rules with follow-up service levels.
- A free trial and demo scheduling are the only commercial elements visible, with no public tier prices, contact limits or billing periods.
- Frequency controls are documented per automation only, with no public information on a cap shared across channels or ad-audience sync.
- HubSpot sync runs through Zapier with loop prevention left to a manual attribute convention and dates rounded down to UTC midnight.
- We found no public information on the parent's seat, a data processing agreement or a subprocessor list, and the vendor line names User.com Sp. z o.o. while the captured pages carry Positive Groupe France.
Best for
- You run B2C lifecycle messaging across email, SMS and WhatsApp from one contact database and want per-channel unsubscribe state stored on the profile.
- Your compliance team requires double opt-in, per-channel consent records, a preference centre and email tracking gated to contacts who explicitly consent.
- You already run HubSpot and can staff a Zapier-based two-way sync built on your own loop-prevention convention.
- You sell to EEA contacts and value a French contracting entity with a stated line that EEA contacts' data stays on servers within Europe.
Avoid if
- You need explainable lead qualification now — the documented lead handling is capture, Facebook Lead Ads deal creation with rep assignment, and per-member visibility over assigned leads.
- You must compute an annual invoice before a sales conversation — the captured pages offer a free trial and demo scheduling and no public prices.
- Your programme depends on one frequency cap shared across channels or ad-audience synchronisation — the documented frequency rules govern a single automation's entries and restarts.
- Your procurement requires a data processing agreement and subprocessor list on file — the captured pages document a French entity and EEA servers for EEA contacts' data, and we found no public information on the rest of the chain.
The scores
| Criterion | Panel median |
|---|---|
| Journeys & orchestration | 3 of 5 |
| Lead scoring, routing & lifecycle | 1 of 5 |
| Channels & personalisation | 3.5 of 5 |
| Consent, tracking & profiling | 3 of 5 |
| CRM integration & data model | 2.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 0.5 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
The journey builder is real: a drag-and-drop editor with triggers, conditions and actions, an automations builder with event triggers, filters, send-campaign and finish-path modules, and settings that cap re-entry six ways ("no more often than", max once per day) with hour and date windows plus draft-before-activate control. External events can start journeys — the HubSpot path creates an event that triggers automation, and API docs are public — but we found no public information on cross-journey suppression, priority when a contact qualifies for several journeys, or per-step reporting, so I cannot yet tell my reps which journey sent yesterday's email. 3 4 9 11
The Sales Ops Manager
The visual journey builder with triggers, filters, actions and finish paths is documented, and the automation settings add real entry-frequency controls, time windows, and draft-before-activation; external events from HubSpot and form submissions can start an automation through Zapier. What I cannot find is anything on priority or suppression when a contact qualifies for several journeys at once, per-step state reporting, or safe editing of a live journey. 3 4 9 11
The Data Protection Officer
A drag-and-drop journey builder is documented with event triggers, filters, send and finish-path modules, per-automation entry caps (once, once per day, no-more-often-than per person), time windows, and draft-before-live saving, and journeys can be entered from external systems through the HubSpot connection via Zapier. We found no public information on arbitration when one contact qualifies for several journeys, suppression across journeys, per-step reporting, or holdout groups, so the documented level sits between a plain visual builder and a fully arbitrated programme. 3 4 9 11
The Lifecycle Marketer
A visual journey builder with event triggers, filters, conditions and a finish path, plus draft-before-live activation and per-automation entry throttling ("no more often than" a set break per person), is real orchestration past linear sequences. But every throttle I found is scoped to a single automation: we found no public information on capping or suppression across journeys, priority when a contact qualifies for several, per-step reporting, or holdout groups, so nothing yet lets me prove a journey's effect. 3 4 9 11
The Solution Architect
A visual journey builder with triggers, conditions and actions is documented, and the automation settings show real entry-frequency control — a restart break in days, hours or minutes, day-of-week and time-window limits — plus draft-before-activation. External entry from HubSpot form submissions can start an automation, but it rides on Zapier rather than a documented platform trigger, and I found no public information on cross-journey suppression, priority when a contact qualifies for several journeys at once, per-step reporting, or versioning of a live journey. 3 4 6 11
The Skeptic
A visual journey builder with triggers, conditions and actions is documented, and the automation settings go further than most: entry-frequency rules including a required break before an automation can restart for the same person, hour and date-range limits, and draft saving before anything goes live. That is frequency control per automation, not suppression across journeys — we found no public information on what happens when a contact qualifies for several journeys at once, per-step reporting, or safe editing of a journey already live. Six, held down by what the settings screen stays silent on. 3 4 9 1
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
Lead capture and handover exist — forms and pop-ups, Facebook Lead Ads synced into deals with the rep assigned, and team permissions scoped to assigned leads — but we found no public information on numeric lead scoring, lifecycle stages, negative scoring or follow-up SLAs. Behaviour-based segments like cart abandoners and email engagers are documented, which is targeting, not a score sales will trust. As evidenced, this is a capture engine, not a qualification engine. 1 5 8 10
The Sales Ops Manager
Lead capture forms, deal creation from Facebook Lead Ads with rep assignment, and per-member visibility over assigned leads are documented, and the lead-magnet widget targets visitors by attribute rules. We found no public information on lead scoring, score history, or lifecycle stage management — without a score my reps cannot explain why the system decided what it decided about a lead. 1 5 8
The Data Protection Officer
We found no public information on lead scoring, score history, or routing rules with follow-up service levels. Documented lead handling is capture through forms and pop-ups, a widget that targets visitors who have an email but no phone number, behavioural audience segments, and deal creation with rep assignment through the Facebook Lead Ads and HubSpot connections — with lifecycle stages effectively living in the synced CRM's deals rather than in the platform's own scoring layer. 1 5 10 11
The Lifecycle Marketer
Behaviour-based segments, a rule-qualified lead-magnet widget, and Facebook lead ads that create deals and assign the right rep cover basic qualification and handover. We found no public information on a scoring model, score history or decay, lifecycle stage definitions, or routing rules with follow-up SLAs — and without a score on the record, there is nothing yet to explain to a lead or a DPO. 1 2 5 10
The Solution Architect
Lead capture is covered — sign-up forms, pop-ups, a lead-magnet widget targeting visitors who have an email but no phone — and Facebook Lead Ads sync assigns "the right rep", with team visibility restricted to each member's assigned contacts. But we found no public information on lead scoring, lifecycle or pipeline stages, qualification rules, or follow-up SLAs; the buyer cannot see any of the scoring machinery I would need to audit. 1 5 8
The Skeptic
The captured pages show lead capture through sign-up forms and pop-ups, a lead-magnet widget aimed at visitors who already have an email but no phone number, rep assignment for Facebook Lead Ads, and per-team-member visibility restricted to assigned leads — capture and routing-lite. We found no public information on lead scoring, lifecycle stages or any qualification logic the customer could explain to a lead. The staircase stops at the front door. 1 5 8 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
Eight channels are documented off one contact profile — email, SMS, WhatsApp, mobile wallet, mobile app marketing, web push, on-site experience, live chat and chatbot — with per-channel unsubscribe attributes stored on the contact record and journeys combining email, SMS and push. Personalisation leans on real-time behavioural profiles and segments built on actions rather than merge fields alone. We found no public information on ad-audience sync to the major networks or cross-channel frequency capping, which is what stops a programme this broad from burning a contact out. 1 6 7 8 10
The Sales Ops Manager
Email, SMS, WhatsApp, web and mobile push, wallet, on-site content and chat are all listed on one contact profile, with unsubscribe flags stored per channel and personalisation claimed from real-time behavioural profiles. The gaps are ad-audience sync and cross-channel frequency capping: the frequency controls I can see govern a single automation's entries, not contact volume across channels. 1 6 7 8 10
The Data Protection Officer
Email, SMS, web and mobile push, WhatsApp, mobile wallet, on-site and chat channels all hang off one contact profile, with per-channel unsubscribe attributes for email, SMS and WhatsApp, journeys that combine email, SMS and push, and messages and content personalised from the behavioural record in real time. We found no public information on ad-audience sync to the major networks, a frequency cap shared across channels, or next-best-channel selection, which keeps this just short of the top of the scale. 1 6 7 8 10
The Lifecycle Marketer
Email, SMS, WhatsApp, web and mobile push, on-site experience and live chat all hang off one 360° profile combining behavioural, purchase and engagement data, with per-channel unsubscribe attributes for email, SMS and WhatsApp and messages triggered on behaviour or lifecycle events. That is close to what I run; we found no public information on ad-audience sync or one frequency cap shared across channels, which is where it stops short. 1 5 6 8 10
The Solution Architect
Email, SMS, WhatsApp, web push, mobile app marketing, mobile wallet and on-site widgets all drive from one contact database, and unsubscribe state is stored per channel on the profile — email, SMS, WhatsApp — which is the shared suppression handling I look for. Behavioural segmentation and attribute-based on-site targeting are documented; we found no public information on ad-audience sync to the major networks or cross-channel frequency capping. 1 6 7 8 10
The Skeptic
Eight channels — email, SMS, WhatsApp, mobile wallet, mobile app marketing, web push, website experience, live chat — are listed as driven from one unified contact database, with per-channel unsubscribe attributes for email, SMS and WhatsApp, behavioural audiences built on abandoned carts, email engagement and page visits, and an on-site widget targeted by stored data. We found no public information on ad-audience synchronisation to the major networks or cross-channel frequency capping; the frequency rules we saw govern one automation's restarts. Six. 1 6 7 8 10 5
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
This is the strongest set of pages: double opt-in with an automated confirmation email, per-channel boolean consent attributes on the profile, a preference centre where contacts review tracking choices, and email tracking that can be disabled workspace-wide or gated per contact with an opt-out link beside the unsubscribe. Anonymous contacts are auto-deleted after a configurable number of days, and manual deletion is permanent, removing engagement history, tracking and chat conversations. We found no public information on consent wording being versioned, retention executed per data category, or erasure reaching derived scores — the accountability end of the scale. 8 9
The Sales Ops Manager
Per-channel consent booleans on the profile, double opt-in, a preference centre, an automated withdrawal link, email tracking that can be disabled workspace-wide or gated per contact, anonymous-contact auto-deletion after a configurable period, and permanent erasure are all documented. For accountability I still miss a consent timestamp and source stored per contact, versioning of the consent wording, and retention stated for named-contact data categories, not only anonymous ones. 5 8 9
The Data Protection Officer
This is the platform's strongest ground: email tracking can be disabled workspace-wide or limited to contacts who explicitly consented, per-channel consent booleans live on the profile, double opt-in, a preference centre, a withdrawal link beside the unsubscribe button, WhatsApp sending gated on live consent, full-profile CSV export and documented deletion that removes interactions, statistics and chat history are all in the help pages. As a DPO I still cannot call it accountable: consent is stored as a yes/no attribute with no evidence of a timestamp, source or versioned wording per contact, single opt-in without verification is offered alongside the recommended double opt-in, retention automation is documented only for anonymous contacts, profiling suppression per person is not documented, and erasure says nothing about derived scores. 5 8 9
The Lifecycle Marketer
Email tracking can be disabled for the whole workspace or enabled per contact only where consent was explicitly given, alongside double opt-in, a preference centre, withdrawal links beside the unsubscribe button, per-channel consent attributes, and deletion that removes history, interactions and chat. We found no public information on versioned consent wording as reproducible evidence, per-person suppression of profiling, or retention rules for inactive named contacts beyond the automated removal of anonymous ones. 8 9
The Solution Architect
The deepest-documented area: per-channel boolean consent attributes, a standard email opt-in attribute, double opt-in, a preference centre for contacts to adjust their choices, an opt-out link placed beside unsubscribe, and email tracking switchable per contact or disabled workspace-wide. Anonymous contacts are auto-deleted after a configurable number of days — stated and executed — and manual deletion is permanent, removing engagement history and tracking including chat; we found no public information on consent wording versioning, retention per data category for known contacts, or erasure of derived scores. 8 9
The Skeptic
Consent is modelled as per-channel boolean attributes on the contact profile, double opt-in is available and recommended, and email tracking can be disabled for all, enabled for all, or enabled per contact only for those who explicitly consented — with a preference centre and a withdrawal link meant to sit beside the unsubscribe button. Deletion is permanent and removes engagement history, email interactions and chat conversations, anonymous contacts are removed after a configurable number of days, and a full-profile CSV export is documented. We found no public information on versioned consent wording, suppression of profiling as such, or retention stated per data category, and single opt-in without verification is offered alongside. Six. 8 9
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
HubSpot sync is two-way for contacts and companies, plus deals and form submissions, configured through Zapier with no code — but it is a middleware marriage: loop prevention is a build-it-yourself "synced from" attribute pattern, dates round down to UTC midnight, and HubSpot allows one Zapier connection per account. A documented API, mobile SDK docs, CSV import and export, and deduplication on import round out the basics on a 360-degree unified profile. We found no public information on field-level conflict resolution, sync retry with an error log, or API rate limits — the answers I would need before trusting this join with my pipeline. 1 6 7 11
The Sales Ops Manager
A documented API, CSV, Excel and CRM import with deduplication, and two-way contact and company sync with HubSpot through Zapier cover the basics — but loop prevention is a manual synced-from attribute pattern rather than configurable conflict rules, and we found no public information on field-level ownership, sync retry, an error log, or rate limits. As the one who inherits the duplicates, that is the difference between a connector and a liability. 1 6 7 11
The Data Protection Officer
Two-way sync of contacts and companies with HubSpot is documented, alongside duplicate handling on import, CSV import and export, a public API and mobile SDK. The sync runs through Zapier rather than a native connector, and keeping the two systems from fighting over one person is left to a user-built "synced from" convention instead of configurable conflict resolution; we found no public information on sync retries, an error log, documented API rate limits, or custom objects on the platform side. 1 6 8 11
The Lifecycle Marketer
Contacts and companies sync both directions with HubSpot, though through Zapier middleware with a documented loop-prevention workaround and format quirks like Unix timestamps and dates rounded to UTC midnight; import from CSV, Excel and integrated CRMs with duplicate elimination, full-profile export, and API and mobile SDK documentation round out the join. We found no public information on field-level conflict resolution, retry or error logs for failed syncs, or documented API rate limits. 1 6 8 11
The Solution Architect
Two-way HubSpot sync of contacts and companies exists, but it rides on Zapier with loop prevention left to a manual "synced from" convention and dates rounded down to UTC midnight — I have maintained that kind of glue and it drifts, and the rounding loses time-of-day in every synced date. Import deduplication and public API and mobile SDK documentation are stated; we found no public information on field-level conflict resolution, custom objects on the platform side, retry and error logs, or API rate limits, and no documented anonymous-to-known identity resolution. 1 6 10 11
The Skeptic
HubSpot two-way sync for contacts, companies, deals and form submissions is documented, configured through Zapier's visual interface, with a customer-managed pattern using a synced-from attribute to keep the two systems from triggering each other, duplicate elimination on import, public API and mobile SDK documentation, and full-profile CSV export. We found no public information on conflict resolution per field, retry and error logs for failed syncs, or documented API rate limits — and the join that decides the implementation runs through middleware requiring Super Admin permissions and a single connection per HubSpot account. Five. 11 1 6 8
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
The captured pages show a French entity and address under Positive Groupe France, and a help-centre statement that EEA contacts' data stays on servers within Europe — a line scoped to EEA contacts, not a hosting commitment for the whole platform. We found no public information on a data processing agreement, a subprocessor list with locations, the parent's seat, or named infrastructure, and for a platform profiling named EU residents that gap sits exactly where my DPO will push. Local European teams are advertised, but presence is not processing. 2 8
The Sales Ops Manager
A French contracting entity and a statement that EEA contacts' data stays on European servers are proven, but the parent company's seat, the named hosting infrastructure, a data processing agreement, and subprocessor locations are not documented. Given that this platform builds behavioural profiles of named people, that chain is thinner than I would sign off on. 2 8 10
The Data Protection Officer
A help-centre line states that EEA contacts' data stays on servers within Europe, and the captured pages carry a French entity name and a French address, so one or two European elements are proven. The contracting entity is not established — the vendor line names a Polish company while the pages name a French group — and we found no public information on a data processing agreement, named hosting infrastructure, a subprocessor list with locations, or any non-EU processing such as AI scoring or support access, so the chain beyond residency is undocumented. 2 8 10
The Lifecycle Marketer
The help centre states European servers keep EEA contacts' data inside the region, and the pages carry a French entity and address with local European teams — one solid European element, though the residency line is scoped only to EEA contacts. The rest of the chain is undocumented: we found no public information on the contracting parent's seat, a data processing agreement, named hosting infrastructure, or a subprocessor list with locations, which for a platform profiling named people is the part I weigh heaviest. 2 8 10
The Solution Architect
Two European elements are proven: a French contracting entity with a published address (Positive Groupe France) and a help-centre line that servers are located within Europe and EEA contacts' data stays in that region. The rest of the chain is undocumented — we found no public information on a data processing agreement, a subprocessor list with locations, the parent company's seat, or hosting outside the EEA statement's scope. 2 8 10
The Skeptic
A French address and the Positive Groupe France copyright appear on the pages, and a help-centre line states servers located within Europe keeping EEA contacts' data in the EEA — a statement scoped to EEA contacts rather than to where a workspace is hosted. We found no public information on the parent company's seat, a data processing agreement, named hosting infrastructure, or any subprocessor list; for a platform building behavioural profiles of named people, that silence is itself the finding. Four. 8 2 10 11
Pricing transparency
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
A free trial is public, and that is the whole of it: we found no public information on tier prices, contact limits, send volume, overage, or the tier where automation begins. I cannot compute an annual invoice for my contact base from these pages, so every budget conversation starts with a sales call — which is exactly what I refuse to defend in a quarterly review. 2 10
The Sales Ops Manager
The captured pages advertise a free trial and a demo, and beyond that we found no public information on tier prices, contact or volume limits, or the tier where automation begins. I cannot compute a real annual invoice from what is public, and that means the renewal lands as a surprise. 2 3 10
The Data Protection Officer
The captured pages offer a free trial and invitations to schedule a demo, and nothing else: we found no public information on tier prices, billing periods, contact or send limits, overage rates, onboarding costs, or which tier includes automation. A buyer cannot compute any invoice from these pages alone. 2 3 10
The Lifecycle Marketer
The captured pages offer a free trial and demo scheduling and not a single price figure, tier, contact limit or billing period. Nothing here lets a buyer compute an annual invoice; every number would come from a sales conversation. 2 3 10
The Solution Architect
The captured pages offer a free trial and demo scheduling and nothing else commercially: we found no public price for any tier, no contact or volume limits, no billing period, and no indication of which tier automation begins at. A buyer cannot begin to compute an annual invoice from these pages. 2 3 10
The Skeptic
A free trial is the only pricing element visible on the captured pages; we found no public information on tier prices, contact limits, the tier where automation actually begins, overage rates, onboarding fees, minimum terms or VAT treatment. Every question a buyer needs in order to compute an annual invoice ends at the demo form. One. 2 3 10
European sovereignty — proven facts
1 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
unverified
Why unverified?The vendor's pages name a local subsidiary and do not state the parent's seat. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?The statement is a help-centre line scoped to EEA contacts' data staying in the EEA and does not explicitly state where non-EEA customers' data is hosted. |
4/4 pts | 8 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about User.com
Is User.com European?
Not determined: the vendor’s pages as captured do not say where User.com is based.
Where does User.com store data?
User.com stores customer data in the EU, per the vendor’s page captured 10 Nov 2026.
Does User.com have a free plan?
Not stated on the vendor’s pages as of 10 Nov 2026.
What are the best alternatives to User.com?
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: User.com alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 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 — Legal entity. The vendor's pages name a local subsidiary and do not state the parent's seat.
- Weak sourcing — Hosting location. The statement is a help-centre line scoped to EEA contacts' data staying in the EEA and does not explicitly state where non-EEA customers' data is hosted.
- 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.
- 42 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
- 7 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 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
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page user.com Checked 10 Nov 2026 Details →
- 2 Security / trust page — found from the homepage www.user.com Checked 10 Nov 2026 Details →
- 3 Journeys & orchestration — found from sitemap www.user.com Checked 10 Nov 2026 Details →
- 4 Journeys & orchestration — found from sitemap help.user.com Checked 10 Nov 2026 Details →
- 5 Lead scoring, routing & lifecycle — found from sitemap www.user.com Checked 10 Nov 2026 Details →
- 6 Channels & personalisation — found from sitemap www.user.com Checked 10 Nov 2026 Details →
- 7 Channels & personalisation — found from sitemap www.user.com Checked 10 Nov 2026 Details →
- 8 Consent, tracking & profiling — found from sitemap help.user.com Checked 10 Nov 2026 Details →
- 9 Consent, tracking & profiling — found from sitemap help.user.com Checked 10 Nov 2026 Details →
- 10 CRM integration & data model — found from sitemap www.user.com Checked 10 Nov 2026 Details →
- 11 CRM integration & data model — found from sitemap www.user.com Checked 10 Nov 2026 Details →