Provenance
    Sign inStart free
    ← Docs

    Trust pages

    A Provenance trust page is your public, always-on surface for security, compliance, and AI-disclosure statements. Visitors land on a hosted page with your branding, custom domain, evidence library, and a live change feed. See ours as a working example — that page is built from the same primitives your customers use.

    Publish flow

    1. Draft. In Trust pages → New, give your page a slug (used for the public URL fallback) and a display title. Drafts are private — visible only to your team inside the app.
    2. Add statements. Publish trust statements grouped by category (Security, Privacy, AI Act Article 50, etc.). Each statement carries a body, a status (published / pending / draft), and optional source URL + last-synced timestamp.
    3. Attach evidence. Upload PDFs, certifications, audit reports — each lands in your private evidence library and can be referenced from any statement. Evidence carries a content hash, a freshness indicator, and an optional retention policy.
    4. Pick subprocessors. The trust page links to the public directory entries for vendors you depend on. Visitors can drill into each subprocessor to see their own posture.
    5. Custom domain. Add a CNAME to cname.provenance.naburis.cloudand TLS provisions automatically.
    6. Publish. Toggle Published in Settings → Trust pages. The page goes live and shows up in the public directory.

    What visitors see

    A hosted page at https://your-slug.provenance.naburis.cloud (or your custom domain), themed to your brand, with: hero + readiness score, statements grouped by category, evidence library, subprocessors, AI disclosure (when applicable), recent changes feed, and a verify-by-Provenance footer that links back to the public directory profile. Search engines index the page; the change feed exposes Atom + JSON for machine consumers.

    Page schema

    The persisted shape (visible in the OpenAPI spec):

    • id, customer_id, slug, display_name
    • custom_domain (optional), footer_branding (boolean), published (boolean)

    Statements, evidence, and subprocessors are separate resources joined by customer_page_id; see the OpenAPI explorer for full schemas + endpoints.