Embedded vs hosted Trust Centres: the architectural choice
A hosted Trust Centre is a standalone page, usually on a third-party platform under your vendor.com/trust subdomain. An embedded Trust Centre is a widget inside your existing site, in your own branding. The choice determines whether the surface reads as part of your brand or as a detour.
Hosted Trust Centres
A hosted Trust Centre is a standalone page rendered by a third-party platform. The vendor’s logo and certifications appear on a page that is, in everything but a subdomain, owned by the Trust Centre provider. The architecture is: visitor clicks a link in the vendor’s site, lands on a third-party page, and finds the security information there.
Most large hosted Trust Centre platforms (SafeBase, Whistic, Conveyor) work this way. They are mature, feature-rich, and trusted by enterprise buyers. They also produce a visible "you have left the vendor’s site" moment in the buyer flow.
Embedded Trust Centres
An embedded Trust Centre is a widget or component rendered inside the vendor’s own site, in the vendor’s own design system. The architecture is: visitor clicks a link in the vendor’s site, the same site renders the Trust Centre content in place, with the vendor’s branding and layout intact.
The same data can drive both architectures. The difference is the rendering surface.
Visitor flow comparison
In a hosted setup, the visitor follows a link, leaves your site, and arrives at the third-party Trust Centre. They scan the certifications, perhaps download a policy document under NDA, and either bounce back to your site or close the tab.
In an embedded setup, the visitor follows a link, stays on your site, and finds the Trust Centre content as a section or subsection of your existing navigation. There is no context switch, no third-party branding, no "you are now on someone else’s page" moment.
SEO and indexation
A hosted Trust Centre sits on a subdomain (typically trust.vendor.com) or under a partner’s domain. Either way, the Trust Centre pages live on a separate site for search-engine purposes. Inbound links and content authority do not accrue to your main site.
An embedded Trust Centre sits at vendor.com/trust-centre or similar. Pages are indexed under your domain. Inbound links from buyers, partners, and trade publications flow to your main domain.
Brand consistency
The hosted model has a defined design system inherited from the platform provider. Some platforms offer customisation; most leave a visible platform watermark or layout fingerprint.
The embedded model uses your design system directly. Type, colour, spacing, copy voice are all yours. For brand-conscious enterprises (financial services, design-led SaaS, B2B premium positioning), this is material.
Maintenance burden
Hosted platforms ship feature updates centrally. New certification types, new questionnaire integrations, new buyer-side workflows arrive automatically. The trade-off is that customisation is bounded by what the platform supports.
Embedded approaches give the vendor full control over what is rendered, at the cost of taking responsibility for the rendering layer. The data layer (certifications, sub-processors, policy versions, monitoring status) is still platform-driven; only the front-end of the rendering is owned by the vendor.