> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truagents.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Security and compliance

> High-level overview of the trust, compliance, and operational-control posture described by TruAgents.

## Summary

Security and compliance are part of the core product story for TruAgents, especially because the platform is positioned for high-stakes customer communications.

The public-facing TruAgents positioning emphasizes:

* compliance-aware communications
* guardrails around message quality and behavior
* enterprise-grade reliability expectations
* trust signals such as the [TruAgents Trust Center](https://trust.truagents.com/)

## Who this is for

Prospective customers, new customers, and teammates who need the big-picture story.

## What this page should communicate clearly

* TruAgents is not trying to be "AI with no controls."
* Review, monitoring, and guardrails are part of the value proposition.
* Compliance-sensitive teams need both generation capability and operational controls.

## What we can say safely today

Without overclaiming certifications or legal posture, the current product and public positioning already support a few clear trust themes:

* human review is part of important workflows
* communication and draft activity can be inspected later
* settings and permissions help define who can do sensitive things
* the broader trust story should be anchored by the [TruAgents Trust Center](https://trust.truagents.com/)

Simple version: the product story is controlled automation, not blind automation.

## Product-level trust themes

### Operational control

The app already suggests multiple places where teams can review, approve, or inspect behavior instead of blindly trusting automation.

### Reporting and traceability

Features like history, campaign runs, communications detail, and public reports all reinforce the idea that actions should be observable and reviewable.

### Infrastructure confidence

The public product positioning also highlights enterprise expectations like uptime and support posture, which should eventually connect to more detailed trust documentation when available.

## What this page should not try to do

This page should not become a substitute for:

* the Trust Center
* legal review
* security questionnaires
* contractual or certification language

It should stay a product-facing overview that helps readers understand why TruAgents emphasizes controls, review, and traceability.

## Questions this page should help answer

* Is TruAgents designed for high-stakes communication workflows?
* Does the product include human review and operational controls?
* Where should a buyer go for deeper trust or security detail?

## Related pages

* [What is TruAgents](/overview/what-is-truagents)
* [Email settings and domain authentication](/admin/email-settings-and-domain-authentication)
* [History and audit trail](/admin/history-and-audit-trail)
* [Organization settings](/admin/organization-settings)