---
title: Compliance
description: Export signed evidence bundles, manage legal holds, and queue DSAR requests.
---

The **Compliance** screen (Governance pillar) is the in-product compliance workspace. It is a thin UI over existing `compliance.*` RPC handlers — no separate backend.

## Evidence export wizard

Generate signed, regime-specific evidence bundles from the audit ledger between a `from` / `to` date range.

Supported regimes: **SOC 2**, **HIPAA**, **GDPR**, **CCPA**, and **ISO 27001**.

The result card shows bundle summary, manifest download, and verification hints. Exports are suitable for auditor handoff when your retention and legal-hold posture is current.

## Legal holds

- **List** active holds (`compliance.legalHold.list`).
- **Place** a hold on a scope (`compliance.legalHold.put`).
- **Release** when preservation is no longer required (`compliance.legalHold.release`).

Holds affect retention pruning — check **Prune status** before assuming old data was removed.

## DSAR queue

List and create data-subject access or erasure requests (`compliance.dsar.list`, `compliance.dsar.create`). Erasure cascades are coordinated with tenant admin tooling on cloud deployments.

## Retention and GC status

**Prune status** and **GC status** show whether retention executors and cloud garbage collection are wired and when they last ran. These are read-only indicators for operators.

## Related screens

| Need | Go to |
|---|---|
| Raw audit entries | [Governance](/docs/using-the-app/governance) › Audit |
| Security posture | [Security](/docs/using-the-app/security) |
| Quality / benchmark evidence | [Quality checks (Evals)](/docs/using-the-app/evals) |
| OEM admin compliance ops | Admin app `/compliance` (operator console) |