Skip to main content
RelixQ
Menu
Trust CenterAi
Trust Center
Public summaryAI policy under review

Trust Center

AI-assisted workflows with customer-visible boundaries.

Review where AI may assist RelixQ users, what data may be sent, how providers are governed, and which no-training or retention claims are not yet made.

Access
Public
Scope
AI-assisted explanations, recommendations, report drafting, customer-selected providers, prompts, responses, and administrative controls in RelixQ SaaS.
Last reviewed
Aug 17, 2026
Evidence owner
AI governance owner
Approval role
Security, privacy, and legal reviewer
Evidence posture
Gated evidence

Evidence posture

Gated evidence

Gated artifacts

The public boundary is documented; provider contracts, data fields, retention, and configuration evidence remain under review.

Evidence artifacts

  • AI feature inventory
  • Prompt and response data map
  • Provider review
  • Customer configuration model

Framework relationships

Alignment is not the same as certification.

NIST AI Risk Management Framework

Vendor control mapping

AI governance reference for transparency, human oversight, data boundaries, and provider review.

Official reference

NIST Cybersecurity Framework 2.0

Vendor control mapping

Control-language mapping for buyer review; not a certification.

Official reference

AICPA Trust Services Criteria / SOC 2

Assurance roadmap

Control mapping and examination roadmap only. RelixQ does not claim a completed SOC 2 examination.

Claim register

Public wording tied to evidence and review state.

Each statement carries its own scope, evidence posture, framework relationship, and review date. Roadmap language remains visibly separate from achieved controls.

Published claim

Optional assistance, not autonomous authority

AI-assisted explanations and drafting are intended to help users interpret evidence. They do not authorize scans, change scope, approve exceptions, close findings, or replace customer review.

Documented practice
Scope
AI-assisted explanation, recommendation, and report-drafting features.
Last reviewed
Evidence owner
AI governance owner
Approval role
Security, privacy, and legal reviewer

Evidence

Design evidence

Feature boundaries distinguish suggestions from governed product actions.

Review evidence artifacts
  • AI feature boundary
  • Human-review workflow
  • Authorization and approval model

Framework context

  • NIST AI Risk Management Framework

    Vendor control mappingAI governance reference for transparency, human oversight, data boundaries, and provider review.

  • NIST Cybersecurity Framework 2.0

    Vendor control mappingControl-language mapping for buyer review; not a certification.

Published claim

Data sent to an AI provider

The final policy must identify the feature, provider, fields sent, purpose, retention, region, customer controls, and deletion behavior. RelixQ does not represent full source files as a default AI input.

Under review
Scope
Finding metadata, matched evidence, prompts, responses, report context, and customer configuration sent to an AI service.
Last reviewed
Evidence owner
AI governance owner
Approval role
Security, privacy, and legal reviewer

Evidence

Gated evidence

The data map and provider configuration require final production confirmation.

Review evidence artifacts
  • AI data-flow inventory
  • Feature field list
  • Provider configuration and contract review

Framework context

  • NIST AI Risk Management Framework

    Vendor control mappingAI governance reference for transparency, human oversight, data boundaries, and provider review.

  • AICPA Trust Services Criteria / SOC 2

    Assurance roadmapControl mapping and examination roadmap only. RelixQ does not claim a completed SOC 2 examination.

  • ISO/IEC 27001

    Assurance roadmapInformation-security management roadmap only. RelixQ does not claim ISO/IEC 27001 certification.

Published claim

Provider retention and model training

No broad no-training or zero-retention claim is made until the selected provider, contract, API configuration, retention behavior, and customer option are verified and published.

Not claimed
Scope
Third-party AI provider handling of RelixQ customer inputs and generated responses.
Last reviewed
Evidence owner
AI governance owner
Approval role
Security, privacy, and legal reviewer

Evidence

Public summary

The claim boundary is explicit while provider review is incomplete.

Review evidence artifacts
  • Public AI claim boundary

Framework context

  • NIST AI Risk Management Framework

    Vendor control mappingAI governance reference for transparency, human oversight, data boundaries, and provider review.

Published claim

Customer-selected AI providers

When a customer enables or supplies an AI-provider connection, the resulting data flow is customer configured and must be included in that customer processing and subprocessor review.

Customer configured
Scope
Customer-enabled AI connections, provider credentials, routing, and feature use.
Last reviewed
Evidence owner
AI governance owner
Approval role
Security, privacy, and legal reviewer

Evidence

Operational evidence

Enabled connection state and routing are governed SaaS records.

Review evidence artifacts
  • AI connection configuration
  • Provider credential reference
  • Feature routing record

Framework context

  • NIST AI Risk Management Framework

    Vendor control mappingAI governance reference for transparency, human oversight, data boundaries, and provider review.

  • Customer security and resilience programs

    Customer evidence supportRelixQ artifacts can support an assessment; they do not certify the customer or provide a legal opinion.

Publication boundary

Status applies only to the scope and evidence shown above.

This page is a public summary. Detailed evidence may still require controlled access, an NDA, or an active procurement review. The catalog entry was last reviewed on .