Provenance
    DirectoryUse casesTrust pagesAI ActPricingDocs
    Sign inStart free
    Provenance

    AI Act Article 50 trust pages for AI SaaS — public evidence profiles, disclosure templates, and hosted buyer-ready trust pages on the Naburis platform.

    Product

    • Directory
    • Use cases
    • Trust pages
    • Pricing
    • Docs

    Company

    • About
    • Contact
    • Changelog
    • EU AI Act

    Developers

    • API
    • ProvenanceBot
    • Webhooks
    • LLMs.txt

    Legal

    • Terms
    • Privacy
    • DPA

    Powered by Provenance — Article 50 trust pages and public-source vendor evidence.

    © 2026 Naburis. All rights reserved.

    Procurement checklist

    Security review checklist for AI SaaS

    Use this checklist to answer buyer reviews with official sources instead of scattered PDFs and email threads.

    Turn the checklist into a trust pageView evidence example
    Procurement-readyGap-awareExportable

    Review readiness checklist

    Security, privacy, AI, and evidence freshness

    First interaction

    User notice placement captured

    Generated content

    Label and metadata path drafted

    Checklist areas

    • SOC 2 / ISO evidence
    • Security controls
    • Privacy and DPA
    • AI transparency disclosures

    Inventory evidence

    List audit reports, privacy terms, AI policies, status pages, and subprocessors.

    Mark gaps

    Separate public facts, access-controlled documents, missing owners, and stale dates.

    Create the public page

    Publish the facts buyers can self-serve and route sensitive requests to the right process.

    Security-review summary

    What the visitor gets before signup

    A procurement-ready checklist that distinguishes public claims, restricted evidence, freshness, and open gaps.

    • Audit availability
    • Control summary
    • AI disclosure status

    Prepare this evidence

    • Current reports
    • Public source links
    • Named owner
    • Freshness dates

    Questions buyers ask

    These pages are written for a specific search intent, then route serious users into the same save and publish flow.

    Why include AI transparency in a security checklist?

    AI SaaS reviews increasingly combine security posture, privacy posture, and AI disclosure obligations in one buyer workflow.

    Should incomplete sections be hidden?

    No. The product should show honest gaps internally, then publish only sections that have enough evidence for buyers.

    Build the public page from this intent

    Save the draft, add official evidence, then publish on Provenance or a custom domain when the trust page is ready.

    Turn the checklist into a trust page
    Trust page generatorSOC 2 trust page example1Password evidence profilePricing