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.

    Security template

    Security page template for B2B SaaS

    Publish the security basics buyers expect: access control, encryption, incident response, audits, and evidence paths.

    Generate your security pageView evidence example
    Buyer-readyFreshness-awareEvidence-linked

    Security page outline

    Controls, audits, incident response, evidence

    Template excerpt

    Security controls are summarized for buyers with linked evidence, owner, freshness date, and access path for restricted documents.

    Required field
    Access controls
    Required field
    Encryption
    Required field
    Incident response

    List core controls

    Cover access control, encryption, logging, vulnerability management, and incident response.

    Attach evidence paths

    Link public pages and describe gated evidence request workflows.

    Add review cadence

    Show owner and last-reviewed date so the page does not feel stale.

    Security page excerpt

    Template preview before signup

    Security controls are summarized for buyers with linked evidence, owner, freshness date, and access path for restricted documents.

    • Access controls
    • Encryption
    • Incident response

    Prepare this evidence

    • Security owner
    • Control evidence
    • Audit status
    • Last reviewed date

    Questions buyers ask

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

    Should startups publish security details publicly?

    Publish high-level facts and request workflows. Keep sensitive reports and implementation details gated.

    How often should this page be reviewed?

    At minimum quarterly, and any time major controls, subprocessors, audits, or AI features change.

    Publish from this template

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

    Generate your security page
    Trust page generatorSOC 2 trust page example1Password evidence profilePricing