---
title: "Trust, security, and deployment | Clearly AI"
description: "How Clearly AI protects customer data: SOC 2 Type II, zero data retention, no model training, and SaaS, single-tenant, or private cloud deployment."
canonical: https://clearly-ai.com/platform/trust-security-and-deployment
---

# Trust, security, and deployment

How Clearly AI protects customer data, where it runs, and how its AI handles your information. Compliance reports and security documents are available under NDA. For access, email [security@clearly-ai.com](mailto:security@clearly-ai.com).

- [Read the security and privacy docs](https://docs.clearly-ai.com/docs/security-and-privacy)

- SOC 2 Type II, AICPA
- GDPR
- Amazon Bedrock
- RSAC 2026 Innovation Sandbox Top 10 Finalist

## Overview

- **SOC 2 Type II audited against the AICPA Security Trust Services Criteria**
- **Annual third-party penetration test:** An independent firm tests the platform every year.
- **Zero data retention by default:** Clearly AI’s default model providers don’t retain or train on your data.
- **No model training by default:** Reviews draw on your sources at the inference layer, without training or fine-tuning a model on them.
- **Deploy your way:** Multi-tenant SaaS, single-tenant, or private cloud on AWS, Azure, or Google Cloud.
- **Your models, your keys:** Bring your own model provider keys and encryption keys.
- **GDPR and CCPA aligned:** US hosting by default, with multiple regions supported.

## Deployment options

Clearly AI is available in three deployment models. All three run the same platform, review templates, and integrations.

### Multi-tenant SaaS

- **Best for:** Fastest rollout
- **Where it runs:** Clearly AI's AWS environment
- **Data isolation:** Logical separation: organization-level authentication, separated database records and storage, and session controls
- **Encryption keys:** A unique AWS KMS key per customer
- **Identity:** SSO, 2FA, allowed email domains, role-based access
- **Models:** Clearly AI defaults: OpenAI and Anthropic under zero data retention
- **Network:** Shared static egress IPs for allowlisting
- **Data residency:** United States (AWS us-west-2, multiple availability zones)

### Single-tenant

- **Best for:** Dedicated isolation, hosted by Clearly AI
- **Where it runs:** A dedicated Clearly AI-hosted AWS environment with its own endpoint
- **Data isolation:** Dedicated network, compute, storage, queues, secrets, logs, and monitoring
- **Encryption keys:** Customer-managed keys (BYOK) available
- **Identity:** Adds SCIM provisioning
- **Models:** Bring your own key: OpenAI, Anthropic, Google, Azure OpenAI, Amazon Bedrock, or OpenRouter
- **Network:** Dedicated, configurable static IPs
- **Data residency:** US by default; EU and other regions available

### Private cloud

- **Best for:** Data that can't leave your cloud
- **Where it runs:** Your AWS, Azure, or Google Cloud account (BYOC), or your existing AWS VPC (BYOVPC)
- **Data isolation:** Inside your own cloud boundary, under your network controls
- **Encryption keys:** Your keys, in your cloud
- **Identity:** Adds SCIM provisioning
- **Models:** Bring your own key: OpenAI, Anthropic, Google, Azure OpenAI, Amazon Bedrock, or OpenRouter
- **Network:** Private routes to self-hosted tools: peering, VPN, or private links you control
- **Data residency:** Any region your cloud supports

**Bring your own S3 bucket (AWS).** Clearly AI can store files and review data in an S3 bucket in your AWS account.

**Private cloud:** With BYOC, Clearly AI provisions a dedicated virtual network and the application infrastructure in your cloud account. With BYOVPC on AWS, Clearly AI deploys into private subnets you provide. Either way, you can layer on your own monitoring, backup, disaster recovery, and network controls, and connect to self-hosted Jira, GitHub Enterprise, Confluence, or ServiceNow without exposing them to the internet.

- [Read the deployment guide](https://docs.clearly-ai.com/docs/deployment-patterns)

_Clearly AI architecture on AWS, showing ingress through a web application firewall to containerized services in private subnets, with encrypted storage and per-customer keys._

## AI and model data handling

**No training on your data.:** Clearly AI uses techniques like retrieval-augmented generation (RAG) to optimize at the inference layer. Reviews draw on your documents, tickets, and code without training or fine-tuning a model on them. Clearly AI only builds a customer-specific model if you ask for one, and it stays within your data tenancy.

**Zero data retention by default.:** Clearly AI has zero data retention agreements with OpenAI and Anthropic. Neither provider retains or trains on data sent through Clearly AI.

**Bring your own model provider:** Single-tenant and private cloud deployments let you use your own keys for OpenAI, Anthropic, Google, Azure OpenAI, Amazon Bedrock, or OpenRouter. Your provider account settings and terms apply. Saved keys are encrypted and never displayed again.

**Keep model calls in AWS:** With Amazon Bedrock, prompts and completions stay in AWS and aren’t used to train AWS models.

- [See supported model providers](https://docs.clearly-ai.com/docs/model-providers)

## Agent controls

Clearly AI’s agents read from connected sources to build each review. These controls limit what an agent can access and change.

_A Clearly AI agent reads only the sources a review needs, runs in an isolated sandbox, writes only to its assigned review, and needs a person’s approval for destructive changes._

1. **Read:** Only the sources the review needs
2. **Run:** Isolated sandbox
3. **Write:** This review only
4. **Approve:** A person approves destructive changes

- **Isolated execution:** Each agent runs in its own isolated sandbox, separated from the host and from every other workload.
- **Restricted network access:** Agents can only reach the sources and services a review needs.
- **Scoped writes:** An agent can only write to the review it’s assigned. It can’t change other reviews, projects, or settings.
- **Human approval for destructive changes:** In chat, Clearly AI suggests edits, and a person approves any destructive change before it runs.
- **Schema-validated output:** Every model response must match a defined schema. Responses that don’t are rejected.
- **Source citations:** Every finding links to the document, ticket, or code that supports it. Missing information is flagged rather than inferred.

- [See how Clearly AI tunes review accuracy](https://clearly-ai.com/platform/quality)

## Encryption and key management

- **In transit:** TLS 1.2 or higher on every connection.
- **At rest:** All files and application data are encrypted with managed cloud encryption. S3 public access is blocked.
- **Per-customer keys:** Each customer’s data is encrypted with its own AWS KMS key.
- **Customer-managed keys:** Single-tenant and private cloud customers can bring their own keys (BYOK) for their organization’s project and knowledge data.
- **Secrets:** API keys and integration credentials are stored in AWS Secrets Manager.

## Access control

- **Single sign-on and provisioning:** SAML or OIDC single sign-on, with SCIM provisioning.
- **Login policy:** Require two-factor authentication, SSO, or sign-up from approved email domains only.
- **Roles and project access:** Owners and admins add and remove users, assign roles, and control which projects reviewers and submitters can see.
- **Least-privilege employee access:** Clearly AI employees only access customer data when a specific service requires it, and only the minimum needed. Every access is logged, and access logs are kept indefinitely.

- [See SSO, SAML, and SCIM setup](https://docs.clearly-ai.com/docs/sso-saml-scim)

## Compliance and governance

- **SOC 2 Type II:** Clearly AI has completed a SOC 2 Type II audit. The report is available under NDA.
- **Penetration testing:** An independent firm tests the platform every year. A summary is available under NDA.
- **Information security program:** A documented information security program covers access control, incident response, data classification, vulnerability management, audit logging, secure development, business continuity, disaster recovery, and AI governance. Policies are available for review on request.
- **Breach notification:** If a security incident affects your data, Clearly AI will notify you within 72 hours of confirming it.
- **Personnel:** Every employee and contractor signs confidentiality and data access agreements and completes security awareness training at hire and every year after.
- **Vendor management:** Security, privacy, and IT review every vendor before it’s used, and critical vendors are reassessed every year. [See the current subprocessor list](https://clearly-ai.com/trust/subprocessors).

## Privacy

- **Personal data:** Clearly AI only processes the employee names and email addresses your team adds to projects, plus the content you choose to review.
- **Export and deletion:** Request an export or deletion of your organization’s data at any time.
- **GDPR and CCPA:** Clearly AI’s privacy program aligns with GDPR and CCPA. [Read the Clearly AI privacy policy](https://clearly-ai.com/trust/privacy-policy).

## Security documents

Additional documentation is available under NDA:

- SOC 2 Type II report
- Penetration test summary
- Security and Privacy Whitepaper
- Completed security questionnaires
- Security policies

For access, email [security@clearly-ai.com](mailto:security@clearly-ai.com).

_FAQ_

## Answers to your top questions

### Is Clearly AI SOC 2 compliant?

Yes. Clearly AI has completed a SOC 2 Type II audit against the AICPA Security Trust Services Criteria. Customers and prospects can request the report under NDA. For access, email security@clearly-ai.com.

### Does Clearly AI train AI models on customer data?

No. Clearly AI uses techniques like retrieval-augmented generation (RAG) at the inference layer, so reviews draw on your sources without training or fine-tuning a model on them. Clearly AI only builds a customer-specific model if you ask for one. Its default model providers, OpenAI and Anthropic, operate under zero data retention agreements, so neither retains or trains on your data.

### Can Clearly AI run in our own cloud?

Yes. Clearly AI’s private cloud deployment runs in your AWS, Azure, or Google Cloud account, or in an existing AWS VPC you provide. You keep control of the network, keys, and monitoring.

[See the deployment guide.](https://docs.clearly-ai.com/docs/deployment-patterns)

### What’s the difference between multi-tenant and single-tenant?

Multi-tenant SaaS runs on shared infrastructure, with each organization logically separated by authentication, storage boundaries, and session controls. Single-tenant gives you a dedicated environment with its own network, compute, storage, secrets, logs, and monitoring, plus customer-managed encryption keys, your own model provider keys, and the option to use your own S3 bucket.

### Can we use our own LLM provider or API keys?

Yes. Single-tenant and private cloud deployments can bring their own keys for OpenAI, Anthropic, Google, Azure OpenAI, Amazon Bedrock, or OpenRouter. Your provider account’s settings and terms then apply.

### Where is our data stored?

In the United States by default. Clearly AI supports multiple hosting regions, including the EU. Enterprise customers can also run Clearly AI in their own cloud or store data in their own S3 bucket on AWS.

### Can we manage our own encryption keys?

Yes. Every customer’s data is encrypted with its own AWS KMS key, and single-tenant and private cloud customers can bring their own keys to control encryption for their organization’s data.

### What can Clearly AI’s agents access?

Only what a review needs. Each agent runs in an isolated sandbox with restricted network access, can only write to the review it’s assigned, and needs a person’s approval for destructive changes.

[See agent controls.](https://clearly-ai.com/platform/trust-security-and-deployment#agents)

### Does Clearly AI support SSO and SCIM?

Yes. Clearly AI supports SAML and OIDC single sign-on, SCIM provisioning, two-factor authentication, and sign-up restricted to your email domains.

[See SSO, SAML, and SCIM setup.](https://docs.clearly-ai.com/docs/sso-saml-scim)

### What security documentation is available for vendor reviews?

The SOC 2 Type II report, penetration test summary, Security and Privacy Whitepaper, completed security questionnaires, and security policies are available under NDA. For access, email security@clearly-ai.com.

### Who are Clearly AI’s subprocessors?

Clearly AI keeps its full, current subprocessor list on the [subprocessors page](https://clearly-ai.com/trust/subprocessors).

## Learn more

- [Secure everything that ships](https://clearly-ai.com)
- [We built the tool we wished we had](https://clearly-ai.com/about-us)
- [One platform. From intake to remediation.](https://clearly-ai.com/platform)
- [Know everything that needs a review. Skip the 300-question form.](https://clearly-ai.com/platform/security-intake)
- [Ask only what matters. Get it right the first time.](https://clearly-ai.com/platform/conversational-intake)
- [Every finding, tracked to a decision](https://clearly-ai.com/platform/resolve/risk-registry)
- [Show leadership and auditors exactly what security reviewed](https://clearly-ai.com/platform/resolve/reporting)
- [Security reviews you can stand behind, every time](https://clearly-ai.com/platform/quality)
- [Threat models built from the tools you already use](https://clearly-ai.com/integrations)
- [Threat models that know about today's attacks](https://clearly-ai.com/platform/threat-intelligence)
- [Automate every step around the review](https://clearly-ai.com/platform/workflows)
- [Threat models your teams can work on together](https://clearly-ai.com/platform/collaboration)
- [Understand the system before the review starts](https://clearly-ai.com/platform/enterprise-context-graph)
- [Trust, security, and deployment](https://clearly-ai.com/platform/trust-security-and-deployment)
- [Every plan reviewed. Every risky change threat modeled.](https://clearly-ai.com/platform/ide-and-mcp)
- [Verify what actually shipped](https://clearly-ai.com/platform/control-and-remediation-verification)
- [A current threat model for everything that ships](https://clearly-ai.com/solutions/continuous-threat-modeling)
- [Prove every product that ships meets your security bar](https://clearly-ai.com/solutions/product-security-assurance)
- [Privacy reviews your team can stake decisions on](https://clearly-ai.com/solutions/privacy)
- [Every vendor reviewed against your standards](https://clearly-ai.com/solutions/third-party-risk)
- [Review every design before it's built](https://clearly-ai.com/solutions/design-and-architecture-reviews)
- [Secure the AI you build, buy, and code with](https://clearly-ai.com/solutions/ai-agentic-security)
- [Every regulation you answer to. One review process.](https://clearly-ai.com/solutions/compliance)
- [Every product ready for the Cyber Resilience Act without growing your team](https://clearly-ai.com/solutions/compliance/cyber-resilience-act)
- [Build vs. buy for security review automation](https://clearly-ai.com/compare/claude-chatgpt)
- [The ThreatModeler alternative built from your own docs, code, and policies](https://clearly-ai.com/compare/threatmodeler)
- [The Clover Security alternative with findings your team can trust](https://clearly-ai.com/compare/clover)
- [The Prime Security alternative for every review your team runs](https://clearly-ai.com/compare/prime)
- [Security and Privacy](https://clearly-ai.com/trust/security-privacy)
- [Clearly AI Privacy Policy](https://clearly-ai.com/trust/privacy-policy)
- [Clearly AI Subprocessors](https://clearly-ai.com/trust/subprocessors)
- [AI Risk Reviews](https://clearly-ai.com/use-cases/ai-risk-reviews)
- [Automate Triage](https://clearly-ai.com/use-cases/automate-triage)
- [Privacy Impact Assessments](https://clearly-ai.com/use-cases/privacy-impact)
- [Vendor Risk Assessments](https://clearly-ai.com/use-cases/vendor-risk)
- [Threat Modeling](https://clearly-ai.com/use-cases/threat-modeling)
- [Contact](https://clearly-ai.com/contact)
- [Contact Enterprise Sales](https://clearly-ai.com/demo)
- [Latest from the Clearly AI blog](https://clearly-ai.com/blog)
- [In the news](https://clearly-ai.com/press)
- [How Ericsson Enterprise Wireless Solutions cut review times by up to 80%](https://clearly-ai.com/customer-stories/ericsson)
- [How HID Global reviews 300+ products for the Radio Equipment Directive with the team it already has](https://clearly-ai.com/customer-stories/hid-global)
- [How Rivian scaled privacy and AI governance reviews 4x without adding headcount](https://clearly-ai.com/customer-stories/rivian)
- [Part 2! Okay, privacy is different from security. Now what?](https://clearly-ai.com/blog/part-2-okay-privacy-is-different-from-security-now-what)
- [How AI is rewiring our product engineering workflow](https://clearly-ai.com/blog/how-ai-is-rewiring-our-product-engineering-workflow)
- [Good Data Scientists and Bad Outcomes, Part 1: What's the difference between security and privacy work?](https://clearly-ai.com/blog/good-data-scientists-and-bad-outcomes-what-s-the-difference-between-security-and-privacy-work)
- [Why I Joined Clearly AI](https://clearly-ai.com/blog/why-vp-marketing-joined-clearly-ai)
- [Skip the Marketing: Clearly AI for Technical People](https://clearly-ai.com/blog/clearly-ai-technical-explanation)
- [Clearly AI Raises $8.4M Seed Round to Scale Product Security](https://clearly-ai.com/blog/seed-round)
- [Why We Started Clearly AI](https://clearly-ai.com/blog/why-we-started-clearly-ai)
- [Applying AI to Threat Modeling - Where AI Thrives, Survives, and Dies](https://clearly-ai.com/blog/applying-ai-to-threat-modeling)
- [Why We Build in Public](https://clearly-ai.com/blog/why-we-build-in-public)
- [Solving the Threat Modeling Bottleneck with AI Workflows](https://clearly-ai.com/blog/solving-the-threat-modeling-bottleneck-with-ai-workflows)
- [Clearly AI Named Finalist in the 2025 Okta Startup Challenge](https://clearly-ai.com/blog/clearly-ai-named-finalist-in-the-2025-okta-startup-challenge)
- [Security, SOC 2, & Startups](https://clearly-ai.com/blog/security-soc-2-startups)
- [Building Reliable AI Systems for Security and Privacy Reviews](https://clearly-ai.com/blog/building-reliable-ai-systems-for-security-and-privacy-reviews)
- [How to Automate Security and Privacy Reviews with Clearly AI](https://clearly-ai.com/blog/how-to-automate-security-and-privacy-reviews-with-clearly-ai)
- [One Year of Clearly AI](https://clearly-ai.com/blog/one-year-of-clearly-ai)
- [Navigating EU RED Compliance: Meeting the August 2025 Deadline](https://clearly-ai.com/blog/navigating-eu-red-compliance-meeting-the-august-2025-deadline)
- [The AI Engineer Cheat Sheet](https://clearly-ai.com/blog/the-ai-engineer-cheat-sheet)
- [Intelligent Vendor Risk Assessments](https://clearly-ai.com/blog/intelligent-vendor-risk-assessments)
- [Clearly AI wins the AWS Bedrock Builder's Challenge](https://clearly-ai.com/blog/clearly-ai-wins-the-aws-bedrock-builder-s-challenge)
- [Reviews, reviews, reviews!](https://clearly-ai.com/blog/reviews-reviews-reviews)
- [Halfway through YC](https://clearly-ai.com/blog/halfway-through-yc)
- [llms.txt — site overview for LLMs](https://clearly-ai.com/llms.txt)
- [llms-full.txt — full site content for LLMs](https://clearly-ai.com/llms-full.txt)
- [sitemap.xml — all public routes](https://clearly-ai.com/sitemap.xml)
- [Documentation](https://docs.clearly-ai.com/docs)

[Canonical page](https://clearly-ai.com/platform/trust-security-and-deployment)