PathFactory

The Head of Content

The captured pages sell content destinations — templates, playlists, hubs, AI recommendations — and I found no public information on an editorial calendar, briefs, owners, due dates or content statuses. Strategy-to-scheduled-work simply is not evidenced here; planning would stay in whatever tool the team already brings. 1 4

Report an error

The SME Marketer

The captured pages present a content-experience and personalization platform — playlists, hubs, AI buying agents, ABM motions — and we found no public information on an editorial calendar, briefs, campaigns or topics grouping scheduled work, owners, or a view of what is due or late. 1 4

Report an error

The Localisation Lead

We found no public information on an editorial calendar, briefs, campaign or topic grouping, or any notion of owners, due dates and statuses for planned work. The captured product pages describe experience templates and curated content playlists, which assemble content for delivery rather than turn a content strategy into scheduled editorial work. 1 4

Report an error

The Web Engineer

Every captured page is about consuming and personalizing content that already exists — experience templates, curated playlists, AI recommendations — and I found no public information on an editorial calendar, briefs, campaign or topic grouping, ownership of planned work, or statuses. As far as the evidence goes, strategy and planning happen somewhere else entirely. 1 4

Report an error

The Data Protection Officer

The captured pages present a delivery platform — playlists, personalized hubs and dynamic landing pages assembled from existing assets — and we found no public information on an editorial calendar, briefs, owners, due dates, statuses or campaigns grouping scheduled work. Content is described as curated into experiences for buyers, not planned as accountable editorial work. 1 4

Report an error

The Skeptic

Every captured product module — playlists, personalized hubs, AI buying agents, search optimization — is about delivering content to buyers, and we found no public information on an editorial calendar, briefs, campaign or topic grouping, owners, statuses or due dates. This is a platform for the last mile of content, with the work of planning it invisible in the captures. 1 4

Report an error

The Head of Content

The terms define Administrator and Employee user accounts and forbid sharing them, which is the only role structure I found; there is no public information on comments, suggested edits, version history or an approval trail recording who released which version. That is a far cry from a status legal can stand behind. 2

Report an error

The SME Marketer

The terms define only Administrator and Employee user accounts and prohibit account sharing, which is a hint of role separation, but we found no public information on comments, version history, restricted guest access for our agency, or an approval trail recording who released which version. 2

Report an error

The Localisation Lead

The terms define Administrator and Employee user accounts and forbid account sharing, which is a basic multi-user setup, but we found no public information on comments, version history, guest or freelancer access, review roles or any approval trail recording who released which version. 2

Report an error

The Web Engineer

The service terms define only Administrator and Employee user accounts, with account sharing prohibited, and I found no public information on inline comments, suggested edits, version history, guest access, approval steps or an audit log of who released which version. That is a two-tier login, not a review pipeline. 2

Report an error

The Data Protection Officer

The terms define Administrator and Employee User Accounts and forbid sharing an account, which is the only role structure visible, while we found no public information on comments, suggested edits, version history, approval steps, external contributor access or an audit log of who released what. For a system that would hold campaign data and author activity, an unrecorded release process is the part I would refuse to sign off first. 2

Report an error

The Skeptic

The terms describe Administrator and Employee user accounts and forbid sharing an account, which is seat administration rather than editorial review; we found no public information on comments, version history, multi-step approval, external contributor access or an audit trail. There is a 30-day cure period and support cadence in the terms, but no evidence of who may release which version. 2

Report an error

The Head of Content

Experience templates and content playlists give some structure to the destinations, and the documented REST API reaches content asset data, but I found no public information on a configurable content model, locale handling or a documented export of the repository. Assets appear to connect through external systems such as Aprimo and Adobe Experience Manager rather than a native library. 1 4 5

Report an error

The SME Marketer

Experience templates and curated playlists are described for buyer-facing destinations and the Aprimo connection brings in external digital asset management, but we found no public information on a configurable content model, on managing German and English locales side by side, or on a documented export of the repository beyond a REST API aimed at engagement and asset data. 1 4 5

Report an error

The Localisation Lead

This is the criterion that decides it for a multi-market buyer, and it is thin: Experience Templates and a publicly documented REST API covering content assets and experiences are the only structure-adjacent evidence, and the platform syncs assets from external systems like Adobe Experience Manager and Aprimo. We found no public information on a configurable content model, locales on the entry with fallback languages, translation status per language, or a documented export of content, model and locales — a repository with no evidenced exit path is a hostage. 1 4 5

Report an error

The Web Engineer

Experience templates and curated content playlists are reusable composition units, and the connectors lean on external systems like Aprimo and Adobe Experience Manager for asset management, which fits a picture of templates with assets living elsewhere. I found no public information on a configurable content model, localisation, or a documented export of entries and assets; the documented API is aimed at audience and engagement data rather than repository portability. 1 4 5

Report an error

The Data Protection Officer

A publicly documented REST API in versions one and three gives programmatic access to audience and engagement data, and named connections to Adobe Experience Manager and Aprimo show assets can be sourced from other systems. We found no public information on a configurable content model, reusable components, locale handling with fallback languages, or a documented export of the content repository itself. 4 5

Report an error

The Skeptic

There is a library of experience templates and curated playlists, and asset management appears to arrive through an external digital asset manager (Aprimo) rather than anything evidenced on the platform itself; we found no public information on locales, side-by-side language management, or a documented export of content and model together. The publicly documented REST API covers audience, engagement and content-asset data — useful, but for a buyer running German alongside English the captures give nothing to plan localisation on. 1 4 5

Report an error

The Head of Content

Seventeen named integrations across CRM, marketing automation, analytics, ABM and sales engagement, webhooks, and a publicly documented REST API offered in versions one and three — the strongest area of the captured pages. I found no public information on rate limits, SDKs, preview environments or a status page, which is what separates a good connection layer from a dependable one. 4 5 1

Report an error

The SME Marketer

This is the strong side: seventeen named integrations in a public directory across CRM, marketing automation, ABM, analytics and sales engagement, webhooks, and a publicly documented REST API in versions v1 and v3 with public API keys; we found no public information on rate limits, SDKs, preview environments or a status page. 1 4 5

Report an error

The Localisation Lead

This is the strong side: seventeen named integrations across CRM, marketing automation, analytics, ABM and content platforms, plus a publicly documented REST API with v1 and v3, API keys and webhooks, cover a normal marketing stack in one place. We found no public information on published rate limits, SDKs, a status page or an API deprecation policy, which keeps it short of the dependable-source tier. 1 4 5

Report an error

The Web Engineer

This is where the platform earns its keep: a publicly documented REST API in versions 1 and 3 with API-key setup on the help site, webhooks, and seventeen named connectors across CRM, marketing automation, analytics, ABM, sales engagement and content platforms, with engagement data flowing out to Google Analytics, Adobe Experience Platform and Snowflake. I found no public information on published rate limits, SDKs, preview environments or a status page, and webhooks are asserted without the publish and change events spelled out. 4 5 1

Report an error

The Data Protection Officer

Seventeen named integrations are published with categories covering CRM, marketing automation, ABM, analytics and sales engagement, alongside webhooks and a REST API documented in two versions, and engagement data flows into Salesforce, Google Analytics and Snowflake. We found no public information on published rate limits, SDKs, preview environments or a public status page, which is what keeps this below the top of the scale. 1 4 5

Report an error

The Skeptic

Seventeen named integrations spanning CRM (Salesforce), marketing automation (Eloqua, HubSpot, Marketo, Pardot, Resulticks), analytics (Google Analytics, Snowflake, Adobe Experience Platform), intent and content platforms, plus a publicly documented REST API in versions 1 and 3 and webhooks on the integrations page. We found no public information on rate limits, SDKs, a public status page or an API deprecation policy, which is exactly the delivery-credibility layer the best-documented platforms publish. 1 4 5

Report an error

The Head of Content

AI is the loudest part of the pitch — buying agents, personalization by industry and account, search optimization — yet I found no public information on which models run, where prompts are processed, whether customer content trains them, or how an admin switches the features off. The terms do state customers retain all rights in their data, but the AI-specific questions a content owner must answer are unanswered publicly. 1 2

Report an error

The SME Marketer

As someone who ships half our content through an AI assistant, the answers I need I did not find: no model or provider is named for the AI buying agents, recommendations and AI search optimization, and we found no public information on whether our content trains their models, where prompts are processed, or whether AI features can be switched off. The terms do state the customer retains all rights in customer data, which covers my drafts, but say nothing about rights in AI-generated output. 1 2

Report an error

The Localisation Lead

AI is central to the pitch — buying agents, conversation agents and personalization by industry, account and individual behavior — yet we found no public information naming the models or providers, where prompts are processed, whether customer content trains them, or any admin switch, labelling for EU AI Act transparency or retention period for prompts. The terms do at least state that the customer keeps all right, title and interest in Customer Data, including intellectual property rights. 1 2

Report an error

The Web Engineer

AI is front and centre — buying agents, personalization by industry, account and behaviour, AI search optimization — but I found no public information on which models run, where prompts and content are processed, whether customer content trains them, admin switching, or labelling of generated output. The only rights statement found assigns Customer Data to the customer, which governs storage, not the AI features. 1 2 4

Report an error

The Data Protection Officer

AI is prominent — buying agents, AI search optimization, AI-driven personalization — yet we found no public information naming the models or providers, the processing location, prompt retention in days, or whether customer content is used for training; the terms do place all right, title and interest in Customer Data with the customer, but nothing covers ownership of AI output or an opt-out. Training exclusion and AI providers belong on a subprocessor list and in the contract, and neither is in the captured pages. 1 2

Report an error

The Skeptic

AI is the headline — AI-driven recommendations, AI buying agents, personalization by industry, account and behavior — and we found no public information on which models are used, where prompts are processed, whether customer content trains them, per-workspace switch-off, or labelling of generated content. The terms do state the customer retains all right, title and interest in Customer Data, and the privacy policy discloses transfers to the United States, Canada, India, Ireland, Israel, Japan and the United Kingdom without an AI-specific processing location. 1 2 3

Report an error

The Head of Content

The contracting entities are PathFactory Corp. in Washington, DC for the US and PathFactory Inc. in Toronto for Canada and elsewhere — both outside the EU — and I found no public information on where content and assets are hosted or which subprocessors touch them. Self-certification under the EU-US Data Privacy Framework is the only transfer safeguard the captured pages show. 2 3

Report an error

The SME Marketer

Contracting is with PathFactory Corp. in Washington, DC or PathFactory Inc. in Toronto, the privacy policy describes transfers of personal information to the United States, Canada, India, Ireland, Israel, Japan and the United Kingdom, and we found no public information on where content is hosted or which subprocessors touch it. A published data processing addendum and self-certification under the EU-US Data Privacy Framework are the only safeguards evidenced. 2 3

Report an error

The Localisation Lead

The contracting entities named in the terms sit in Washington, DC for US customers and Toronto for every other country, and we found no public information on where content, assets and AI prompts are stored or on any subprocessor list with locations and purposes. The privacy policy discloses transfers to the United States, Canada, India, Israel, Japan and the United Kingdom, with self-certification under the EU-US Data Privacy Framework as the only stated safeguard — nothing here lets me tell a DACH customer their content stays under European control. 2 3 4

Report an error

The Web Engineer

The contracting entities are a US corporation for US customers and a Canadian company for everyone else, transfers run through the United States, Canada, India, Ireland, Israel, Japan and the United Kingdom, and I found no public information on where content and assets are hosted or which subprocessors touch them. The Data Privacy Framework self-certification and a DPA link are transfer safeguards, not European hosting or a published subprocessor chain. 2 3

Report an error

The Data Protection Officer

The terms name PathFactory Corp. of Washington DC for US customers and PathFactory Inc. of Toronto for Canada and every other country — no EU contracting entity — and we found no public information on where content is hosted or on any subprocessor list. The privacy policy discloses transfers to the United States, Canada, India, Ireland, Israel, Japan and the United Kingdom and relies on the EU-US Data Privacy Framework, which is a transfer mechanism, not European hosting. 2 3

Report an error

The Skeptic

The contracting entities are PathFactory Corp. in Washington, DC for US customers and PathFactory Inc. in Toronto for Canada and elsewhere, with no European entity in the captures, and the privacy policy discloses transfers to the United States, Canada, India, Israel, Japan and the United Kingdom. A DPA exists and the company self-certifies under the EU-US Data Privacy Framework, but we found no public information on EU hosting, a subprocessor list with locations and purposes, or where AI prompts are processed; the acquisition by Kaltura leaves the ownership picture unstated on the captured pages. 1 2 3

Report an error

The Head of Content

Every fee is set in an Order Form; the public terms say only that amounts are in US dollars, payable within thirty days with taxes on the customer, plus interest at one and a half percent on late payment. I found no public plan prices, seat counts, usage limits or information on which plan unlocks anything — the annual cost is not computable from these pages. 2

Report an error

The SME Marketer

Every fee is set in an Order Form and we found no public information on plan prices, seat or contributor pricing, or locale and content limits, so I cannot begin to compute what a second language plus agency guests would cost us for a year; the terms at least state that fees are identified in US dollars, payment is due within 30 calendar days, late payment incurs 1.5% interest, and taxes are the customer's responsibility. 2

Report an error

The Localisation Lead

We found no public information on plan prices, seat counts, locales, content records or API limits; the terms place all fees in Order Forms, identified in US dollars, payable within 30 calendar days, with taxes on the customer and late-payment interest at one and a half percent. For a buyer, the annual cost is a sales conversation rather than something computable from public pages. 2

Report an error

The Web Engineer

No captured page states any plan price; the terms place all fees in Order Forms identified in US dollars with net 30 payment terms and 1.5 percent late interest, so annual cost is a sales conversation. I found no public information on seat prices, locales, records, API limits, AI usage or where any gated capability begins. 2

Report an error

The Data Protection Officer

The only pricing facts published are contract mechanics — fees in US dollars, payment within 30 calendar days, interest of one and a half percent on late payment, taxes excluded — with commercial terms evidently handled per Order Form. We found no public information on plan prices, seat costs, content or usage limits, AI credits, or which plan unlocks approval or SSO, so a buyer cannot compute an annual cost from these pages. 2

Report an error

The Skeptic

The captured terms point every fee to an Order Form, denominated in US dollars with net-30 payment terms and 1.5% late interest, and we found no public information on plan prices, seat or contributor costs, or any limit on locales, records, API calls or AI usage. A buyer cannot compute any annual cost from these pages — the number arrives by sales conversation. 2

Report an error