What’s new

DeliverTrust now runs an MCP server. Connect Claude, Claude Code or any client that speaks the Model Context Protocol, sign in with your DeliverTrust account, pick one tenant and choose what the connection may do. Read access is always included; writing is opt-in by area.

Your assistant can read your trust page, edit branding, libraries, pages, documents and the request workflow with you, and bring a trust page over from SafeBase, Drata, Conveyor, UpGuard or Vanta as a plan you review first. It cannot publish: a person does that in the app.

Every connection shows under Settings, Connected apps, and every write lands in your Audit Logs like a hand edit.

Read about the MCP server

The homepage hero and the pricing card now carry a Book a call door. It opens the founder's calendar inside the site, so you can pick a slot without leaving the page.

The offer behind it is customer discovery: fifteen minutes on what you need from a trust center, and three months added to your trial afterwards.

Book a call

A buyer's guide to how the trust center platforms handle documents behind an NDA or an access request: who gates what, who verifies the requester, who logs the download, and what each one costs to get there.

It sits beside the existing guides on evaluating a trust center and on why a shared drive folder is not one.

Read the guideAll guides

The site has a blog. The first post is about how DeliverTrust is built and shipped by a one-person team working with AI agents, with the numbers.

Also fixed: an unknown URL used to paint the homepage under a 404 status. It now shows a proper not-found page, so a dead link looks like a dead link.

Read the blog

The consent banner now asks about analytics and advertising separately, and the choice is recorded per category rather than as one yes or no. A visitor who wants analytics but not ad tracking can say exactly that.

You can change your answer at any time from the footer, with no account and no sign-in.

Your trust page is untouched by any of this: DeliverTrust loads no consent banner and no trackers on the pages your prospects read.

Saving the Controls, Sub-Processors or Certifications library used to log "library updated". The row now names which items and which categories changed, in plain words, so a reviewer reading the log a month later does not have to guess.

The same detail is stored in a structured form alongside the sentence, ready for richer views later.

The bundled NDA ships with a header that says it is an example for review. If you paste your own counsel-approved text over the body but keep that header, visitors are asked to accept a document that still announces itself as a draft.

The setup checklist and the NDA panel now spot that line specifically and tell you, even after the rest of the text has been customized.

Your Sub-Processors register is now a page on your trust page with its own URL, the same way custom pages work: a path (legal/subprocessors by default), an optional nav label, and a switch for whether it appears in the navigation.

Procurement teams that only want the sub-processor list can be sent straight to it.

The Request Access button has its own color setting in Branding, separate from your primary brand color, so it can stand out against a dark rail or match a specific brand guide.

Branding changes now preview live in the editor before you save.

The public trust page moved from a stacked header (identity band, hero, tab strip) to a persistent left rail: logo, contact email, the Request Access button and the navigation in one column, with the page content beside it. On phones the rail collapses into a slim top bar.

Request Access and the contact line now appear on every page of the trust page, not only the Overview, so a visitor reading your FAQ or a custom page can ask for a document from where they are.

The Controls summary and Sub-Processors tiles open their full lists in a modal instead of navigating away.

A subscription that is about to lapse no longer ends silently. The team is emailed as the expiry approaches, and once it lapses the tenant is confined to Settings until it is renewed while the trust page returns a not-found rather than a stale copy of your last publish.

Self-service checkout and billing management are built and are being switched on tenant by tenant while the product is finished. Until yours is on, billing stays a conversation with us.

FAQ groups and the questions inside them can be dragged into the order you want. The order you see in the editor is the order a visitor reads on the trust page.

FAQ CSV import and export moved to the page header, and the Add group action is easier to find.

When a request workflow step posts to a JSON webhook, the editor now shows the exact envelope it sends: every top-level field, every payload key, and the handful of fields that are deliberately never sent, each with its reason.

The example is pinned to the code that builds the real payload, so the documentation cannot drift from what your endpoint receives.

Every team notification for a given event, whether it arrives by email or Slack, now uses one sentence, one title and one call to action, and every notice links straight to the request it is about in the admin app.

Webhook payloads carry the request URL too.

The Request Workflow tab was a very long form. It is now a horizontal rail of the six moments in a visitor's request, from submitting the form to receiving a decision, with one moment open at a time and the visitor-facing and team-facing settings side by side.

Steps that could never fire were removed from the picker.

The rich-text editor has an image button. Pictures are uploaded to your tenant's own storage, sized in place, and served behind the same access rules as the page they sit in, so an image on a gated page is gated too.

An FAQ is created in the Pages editor like any other page, with a type picker on create, grouped questions, per-page CSV import and export, and the same access chooser custom pages have. It renders as an accordion on the trust page.

The misconfiguration warnings that already covered documents now cover pages and the FAQ: gate a page behind the unreviewed example NDA, or route its approvals to nobody, and the checklist tells you.

The site publishes an accessibility statement, linked from the footer and the legal pages. Procurement reviewers look for one.

The status page is linked from the footer, and a Brand Resources page offers the DeliverTrust logo set for light, dark and solid backgrounds as transparent PNGs.

Accessibility statementBrand resources

Custom pages support tables: insert, add and remove rows and columns, and merge cells from one toolbar menu. Tables render on the public page with the same styling as the rest of the content.

The Audit Logs search box used to match one column. It now matches the person who acted, the address they acted from, and the detail line that names which documents or visitors were involved, so a revoke can be found by the visitor it named.

The default range is the last 30 days.

The third column on Users is now Last active rather than the date someone's role was last edited. A member who has never signed in reads as Never, which is the information the column was meant to carry.