Home/ AI Compliance and Governance
Compliance knowledge center

Understand the control evidence behind regulated AI.

Use these guides to connect regulatory expectations with runtime policy enforcement, human review, audit records, and deployment choices.

Applies to: Engineering, security, risk, compliance, and procurement teams Status: Framework-specific; confirm current obligations with counsel Reviewed: 31 July 2026

Choose the regulatory context

Each guide addresses a distinct jurisdiction, regulated audience, and review question. The pages explain what the framework asks teams to demonstrate, where AxonFlow can provide supporting evidence, and where organizational controls remain outside the product.

European Union

EU AI Act

High-risk classification, record keeping, transparency, human oversight, robustness evidence, and conformity-assessment workflows.

Review the EU AI Act guide
India

Indian financial services

Orient shared platform teams across RBI FREE-AI, SEBI AI/ML responsibilities, and the broader Indian data-protection context.

Open the India overview
Reserve Bank of India

RBI FREE-AI

System inventory, validation records, incident governance, emergency controls, and board-level evidence for banking and payments.

Review RBI FREE-AI
Securities and Exchange Board of India

SEBI AI/ML governance

Responsibility for client data and outputs, AI/ML reporting, retention, readiness, and audit evidence for securities-market firms.

Review SEBI guidance
Singapore

MAS FEAT

Fairness, ethics, accountability, transparency, materiality assessments, inventories, and human intervention in financial services.

Review the Singapore guide
Indonesia

UU PDP, OJK, and Bank Indonesia

Personal-data governance, banking AI oversight, payment-system controls, incident evidence, and cross-border transfer records.

Review the Indonesia guide

Three sources, three different jobs

The landing site, technical documentation, and Trust Center are intentionally related without repeating the same page three times.

Compliance guides

Scope and control intent

Start here to understand applicability, regulatory status, practical obligations, AxonFlow's role, and the limits of that role.

Technical documentation

Implementation details

Use the docs for endpoint families, identity headers, payloads, deployment modes, tier boundaries, and evidence-export workflows.

Open compliance documentation
Trust Center

Shipped security posture

Use the Trust Center for concrete security features, deployment boundaries, telemetry behavior, certification status, and disclosure channels.

Open the Trust Center

What AxonFlow contributes to a control environment

AxonFlow governs AI requests and tool actions at runtime. It can produce evidence that supports a broader compliance program, but the complete program also depends on people, process, system design, model governance, and legal interpretation.

Control needRuntime contributionEvidence availableOrganizational responsibility
Policy enforcementEvaluate requests and tool calls against system and tenant policies.Policy decisions, matched rules, outcomes, and request context.Define approved use cases, thresholds, and accountable owners.
Human oversightPause configured high-risk actions for review before execution.Approval status, reviewer identity, timestamps, and decision history.Set reviewer authority, escalation paths, and separation of duties.
Data protectionDetect and act on configured PII patterns before model or tool access.Detection category, policy action, and governed request record.Classify data, choose lawful processing grounds, and configure deployment boundaries.
TraceabilityRecord governed LLM and connector activity with correlation context.Decision and execution records for investigation and export.Set retention, downstream logging, access review, and incident procedures.
Emergency interventionApply scoped or broader circuit-breaker controls where licensed and configured.Trip, reset, actor, reason, and affected scope.Authorize activation, rehearse recovery, and own business continuity.

Be precise about the boundary

AxonFlow can support

  • Runtime enforcement around prompts, responses, and connector actions
  • Configurable human-review gates and emergency intervention
  • Audit records, evidence exports, and framework-oriented workflows
  • Self-hosted and customer-controlled deployment patterns

AxonFlow does not provide by itself

  • Legal advice or a determination that a use case is compliant
  • Regulatory approval, certification, or conformity marking
  • Statistical fairness testing or automated bias detection
  • A replacement for model validation, risk ownership, or human accountability

These guides describe technical support for a control environment. Legal and compliance teams must validate the complete system against the current law, regulator guidance, contractual obligations, and deployment facts.

Test the control path against a real workflow.

Use the Evaluation license to assess policy enforcement, human review, evidence records, and deployment boundaries before a regulated rollout.