marketing.docsPage.nav.trustCenter — ActLoom Documentation

Trust Center

In ActLoom, the Trust Center is the public-facing layer of the compliance workspace. It lets a company expose a curated view of its AI governance posture without giving external readers access to the full internal dashboard.

The real product includes more than a public page: it includes Trust Center settings, a preview flow, an optional private Trust Center, and an embeddable badge that can be reused on external websites or partner pages.

What the Trust Center does in the application

Publish a shareable trust surface

Instead of answering the same diligence questions repeatedly, teams can point customers and auditors to a maintained Trust Center URL.

Separate public trust from internal evidence

The Trust Center exposes selected systems, scores, and policy references while keeping internal assessments and working notes private.

Support both public and controlled sharing

The application supports a public Trust Center and a private variant, which makes the feature useful for both broad credibility and restricted review.

Operational aspect	What to know in ActLoom
Prerequisites	A company profile and saved Trust Center settings should exist. The feature becomes more useful once AI systems, trust posture, and public-facing metadata are already curated.
Main inputs	Slug, public/private mode, selected visible systems, public positioning, and optional badge/embed distribution choices.
Main outputs	Public Trust Center URL, optional private Trust Center URL, and embeddable badge or distribution assets.
Who typically uses it	Founders, sales, legal, compliance, procurement-response teams, and customer trust owners.
Plan access	Public and private trust-sharing workflows are available across plans and become more useful when paired with richer system and reporting data.
Relevant routes	/api/trust-center/[slug], /api/trust-center/private, /api/trust-center/[slug]/badge, /trust-center/[slug], /trust-center/[slug]/private

1. Trust Center In The Dashboard

In the application, Trust Center management lives in `Settings`. Users do not publish content by editing the public page directly; they configure activation, slug, private access, and distribution from the workspace, then preview the result through the generated links.

Public Trust Center

Share an external AI trust page for customers and auditors

URL slug

actloom.com/trust-center/neurovista-ai

Preview last saved public page

Private Trust Center

Keep a richer internal or invite-only version alongside the public page

Public preview snapshot

NeuroVista AI Trust Center

Enabled

84%

Embeddable badge

data-slug="neurovista-ai"

Script

SVG

iframe

Fig 32a. Trust Center workspace — settings for public activation, slug management, private access, and embeddable badge distribution.

Main controls shown in Settings

Control in the app	What it lets the user do
Public Trust Center toggle	Enable or disable the public-facing Trust Center without deleting the configuration
Slug field	Define the public URL path used for the external page
Preview link	Open the currently saved Trust Center page in a new tab
Private Trust Center toggle	Enable a more restricted private view alongside the public page
Private link	Open the private Trust Center URL for more detailed controlled sharing
Save action	Persist the current Trust Center settings before previewing the latest changes

Preview reflects the last saved state

In the real settings flow, the preview link shows the last saved Trust Center. Unsaved changes in Settings do not automatically appear on the live public page.

2. What The Public Trust Center Looks Like

The public Trust Center is designed as a lightweight proof layer. It gives external readers a structured summary of the company’s AI posture without exposing all of the operational detail held in the dashboard.

actloom.com/trust-center/neurovista

NeuroVista AI

✓ AI Act CompliantISO 42001 Aligned

84%

Compliance Score

AI Systems

High-Risk

Candidate Screening AI

High-Risk

78%

Support Assistant

Limited

95%

Fraud Detector

High-Risk

72%

Fig 32. Public Trust Center — branded public page showing AI compliance posture for clients and regulators.

Public elements commonly shown

Company identity, logo, and high-level compliance positioning.
Overall score and selected trust badges to help readers orient quickly.
A curated list of AI systems that the company has chosen to expose publicly.
Policy or standards references that support external trust conversations.
Public contact or policy links that give external stakeholders a next step.

Why teams publish it

To answer procurement or partnership diligence faster.
To give auditors and regulators a compact external landing page.
To show progress and maturity without exposing the full compliance workspace.
To create a stable URL that sales, legal, and compliance teams can reuse consistently.

Visible systems are explicitly selected

Public exposure is curated. The idea is not to publish every internal system automatically, but to choose which systems are suitable to represent your AI posture externally.

3. Public Trust Center Vs Private Trust Center

One of the product-specific strengths of ActLoom is that it does not force the company into a single publication mode. The application supports a public Trust Center and a private Trust Center because the audience and level of detail are not always the same.

Mode	Typical audience	Why a team would use it
Public Trust Center	Prospects, customers, partners, auditors, regulators, or anyone with the public URL	Best when the goal is broad trust signalling and reusable external positioning
Private Trust Center	Restricted reviewers who need more context without giving them internal dashboard access	Best when the company wants to share richer trust material in a controlled way

When the private Trust Center is especially useful

When a customer or auditor needs more detail than the public page should expose.
When the company wants a controlled review surface without granting dashboard access.
When the public Trust Center is enabled for broad trust signalling but deeper sharing still needs a separate route.

4. Configuration Flow In Practice

In real usage, teams usually move through the Trust Center in a simple sequence: activate, define the slug, save, preview, optionally enable the private page, then distribute the URL or badge externally.

Typical Trust Center setup flow

Enable

Turn on the public Trust Center from Settings when the company is ready to expose an external trust page.

Name the URL

Define the slug that will become the public Trust Center path and keep it stable for reuse.

Save & Preview

Persist the configuration, then open the generated preview link to validate the last saved state.

Distribute

Share the public URL, private URL, or embeddable badge depending on the audience and use case.

Setting	What it controls	Notes from actual product behavior
Trust Center enabled	Whether the public Trust Center exists at all	The page can be turned on or off without deleting the slug
Trust Center slug	The public path under `/trust-center/{slug}`	The slug is normalized and becomes the external identifier of the page
Private Trust Center enabled	Whether the private companion page is available	Useful for controlled sharing scenarios
Preview links	Direct access to saved public or private pages	Preview is based on saved settings, not temporary edits
Save button	Persistence of the Trust Center configuration	Important because external links depend on the last saved state

5. Embeddable Badge And External Distribution

The application also includes an embeddable badge workflow, which extends the Trust Center beyond the hosted page itself. Once a Trust Center is saved and enabled, the user can generate badge snippets for reuse on other web properties.

What the embed feature adds

Script embed

Useful when the company wants a dynamic trust badge that can reflect the Trust Center from a script include.

SVG badge

Useful when the company wants a lightweight image-style trust artifact for websites or partner pages.

iframe option

Useful when the company wants to embed a fuller trust surface rather than only a badge.

Trust Center is more than a hosted page

In ActLoom, the Trust Center feature also serves distribution: public URL, private URL, and embeddable badge all help the company reuse the same trust posture in different contexts.

Before you enable a public Trust Center

Make sure the systems you expose are actually the ones you want external parties to associate with your AI posture.
Check that the public trust narrative matches the current dashboard reality rather than an outdated milestone.
Decide whether a prospect should receive the public page, the private page, or a direct report instead.
Review the saved preview before reusing the URL in procurement, sales, or badge embeds.

Related Sections

Documents

Use this when the next step is generating or refreshing the material that the trust surface will expose.

Security

Read this before enabling broader external sharing if reviewers are likely to ask how access and logs are controlled.

Artifacts

Go here for the output-centric map of public pages, diligence rooms, badges, and controlled evidence surfaces.

Use Cases

Use this when the trust center is part of a larger audit-prep or customer-diligence workflow.

Ready to get started?

Join hundreds of companies using ActLoom to simplify AI Act compliance. Start your free assessment today — no credit card required.

Start Free Assessment View Pricing

Questions? Contact us at support@actloom.com

Operational aspect

What to know in ActLoom

Prerequisites

A company profile and saved Trust Center settings should exist. The feature becomes more useful once AI systems, trust posture, and public-facing metadata are already curated.

Main inputs

Slug, public/private mode, selected visible systems, public positioning, and optional badge/embed distribution choices.

Main outputs

Public Trust Center URL, optional private Trust Center URL, and embeddable badge or distribution assets.

Who typically uses it

Founders, sales, legal, compliance, procurement-response teams, and customer trust owners.

Plan access

Public and private trust-sharing workflows are available across plans and become more useful when paired with richer system and reporting data.

Relevant routes

/api/trust-center/[slug], /api/trust-center/private, /api/trust-center/[slug]/badge, /trust-center/[slug], /trust-center/[slug]/private

Control in the app

What it lets the user do

Public Trust Center toggle

Enable or disable the public-facing Trust Center without deleting the configuration

Slug field

Define the public URL path used for the external page

Preview link

Open the currently saved Trust Center page in a new tab

Private Trust Center toggle

Enable a more restricted private view alongside the public page

Private link

Open the private Trust Center URL for more detailed controlled sharing

Save action

Persist the current Trust Center settings before previewing the latest changes

2. What The Public Trust Center Looks Like

actloom.com/trust-center/neurovista

NeuroVista AI

✓ AI Act CompliantISO 42001 Aligned

84%

Compliance Score

AI Systems

High-Risk

Candidate Screening AI

High-Risk

78%

Support Assistant

Limited

95%

Fraud Detector

High-Risk

72%

Fig 32. Public Trust Center — branded public page showing AI compliance posture for clients and regulators.

Public elements commonly shown

Company identity, logo, and high-level compliance positioning.
Overall score and selected trust badges to help readers orient quickly.
A curated list of AI systems that the company has chosen to expose publicly.
Policy or standards references that support external trust conversations.
Public contact or policy links that give external stakeholders a next step.

Why teams publish it

To answer procurement or partnership diligence faster.
To give auditors and regulators a compact external landing page.
To show progress and maturity without exposing the full compliance workspace.
To create a stable URL that sales, legal, and compliance teams can reuse consistently.

Visible systems are explicitly selected

Public exposure is curated. The idea is not to publish every internal system automatically, but to choose which systems are suitable to represent your AI posture externally.

Mode

Typical audience

Why a team would use it

Public Trust Center

Prospects, customers, partners, auditors, regulators, or anyone with the public URL

Best when the goal is broad trust signalling and reusable external positioning

Private Trust Center

Restricted reviewers who need more context without giving them internal dashboard access

Best when the company wants to share richer trust material in a controlled way

Setting

What it controls

Notes from actual product behavior

Trust Center enabled

Whether the public Trust Center exists at all

The page can be turned on or off without deleting the slug

Trust Center slug

The public path under `/trust-center/{slug}`

The slug is normalized and becomes the external identifier of the page

Private Trust Center enabled

Whether the private companion page is available

Useful for controlled sharing scenarios

Preview links

Direct access to saved public or private pages

Preview is based on saved settings, not temporary edits

Save button

Persistence of the Trust Center configuration

Important because external links depend on the last saved state

Trust Center

What the Trust Center does in the application

1. Trust Center In The Dashboard

Main controls shown in Settings

2. What The Public Trust Center Looks Like

Public elements commonly shown

Why teams publish it

3. Public Trust Center Vs Private Trust Center

When the private Trust Center is especially useful

4. Configuration Flow In Practice

Typical Trust Center setup flow

5. Embeddable Badge And External Distribution

What the embed feature adds

Before you enable a public Trust Center

6. Before You Share The Trust Center

Pre-share review

Related Sections

Ready to get started?

Trust Center

What the Trust Center does in the application

1. Trust Center In The Dashboard

Main controls shown in Settings

2. What The Public Trust Center Looks Like

Public elements commonly shown

Why teams publish it

3. Public Trust Center Vs Private Trust Center

When the private Trust Center is especially useful

4. Configuration Flow In Practice

Typical Trust Center setup flow

5. Embeddable Badge And External Distribution

What the embed feature adds

Before you enable a public Trust Center

6. Before You Share The Trust Center

Pre-share review

Related Sections

Ready to get started?