# Is It Safe to Put Security Documents into ChatGPT or Claude?

> ChatGPT and Claude for compliance work: what to check before you paste security documents, what to redact and where the vendors say it. Audit from $4,400.

- Canonical: https://auditsuisse.com/is-it-safe-to-use-ai-for-soc-2
- Language: en
- Author: Sébastien Ruosch, CPA — Director of Audits
- Published: 2026-11-15
- Updated: 2026-11-15
- Alternates: fr → https://auditsuisse.com/fr/utiliser-l-ia-pour-soc-2-est-ce-sur, es → https://auditsuisse.com/es/es-seguro-usar-ia-para-soc-2

SOC 2 with AI

 The short answer

It can be, if you check four things first and redact before you paste. Using ChatGPT or Claude for compliance work means sending documents outside your environment, so find out exactly what leaves it, who can see it, whether it is retained or used for training, and which contract covers your plan. Remove secrets, personal data, customer data and exploitable detail from anything you upload. Then treat the AI vendor as one of your vendors.

## Key takeaways

- The answer depends on your plan, your settings and your contract. Read the vendor’s own documentation for the plan you use.
- Redact a copy before the assistant sees it. Keep the original unchanged.
- Never paste secrets, keys or tokens. Rotate any that were pasted by mistake.
- An AI vendor that receives company information belongs in your vendor inventory, with a review on file.

## What should we check before pasting security documents into ChatGPT or Claude?

Four questions decide whether a document may go into an assistant. Answer them once for each plan your company uses, and write the answers down.

Data-handling questions to answer before using an AI assistant for compliance work, and where to find each answer.

| Question | What to find out | Where the answer is |
| --- | --- | --- |
| What leaves your environment? | The text you paste, the files you upload, and everything a connector or agent can read on your behalf | Your own configuration: which folders, repositories and accounts the assistant can reach |
| Who can see it? | Which colleagues share the workspace or the conversation, and whether the vendor’s staff or subprocessors can access content | Your workspace settings and the vendor’s terms |
| Is it retained or used for training? | How long conversations and files are kept, whether you can delete them, and whether content is used to train models | The vendor’s privacy documentation and your plan’s settings |
| Which contract covers it? | Whether your company accepted commercial terms or an individual accepted consumer terms, and whether a data processing agreement applies | The agreement itself, and whoever signed up |

Check your customer contracts too. Some restrict where customer data may be processed or which subprocessors you may use.

## Is a business plan different from a consumer plan?

Generally, yes. Business and API plans are typically covered by commercial terms and consumer plans by consumer terms, and the two can differ on training and retention. We do not summarize any vendor’s terms here: they change, and the vendor’s own page is the source. Read the page for the plan you use.

- **Claude (Anthropic):** [commercial terms](https://www.anthropic.com/legal/commercial-terms) and [Privacy Center](https://privacy.claude.com/).
- **ChatGPT (OpenAI):** [enterprise privacy](https://openai.com/enterprise-privacy/) and [data controls FAQ](https://help.openai.com/en/articles/7730893-data-controls-faq).
- **Gemini (Google):** [Gemini Apps Privacy Hub](https://support.google.com/gemini/answer/13594961) and [Generative AI in Google Workspace Privacy Hub](https://knowledge.workspace.google.com/admin/generative-ai/generative-ai-in-google-workspace-privacy-hub).

Find out which account each person actually uses. A company agreement covers the company’s accounts. It does not cover a personal account that an employee uses for work.

## What should we redact before uploading a security document?

Redact a working copy and leave the original where it is. The copy is for analysis. It is not evidence: what you send to the auditor is the original record from the system, as [what auditors accept from AI](https://auditsuisse.com/what-auditors-accept-from-ai) and [audit evidence management best practices](https://auditsuisse.com/audit-evidence-management-best-practices) explain.

- **Secrets, keys and tokens:** passwords, API keys, private keys, connection strings, session cookies.
- **Personal data:** names, email addresses, HR and background-check records. Replace them with roles or placeholders.
- **Customer data:** customer names, contract terms, records from production databases or support tickets.
- **Unpatched vulnerability details:** open findings from scans or penetration tests, with affected hosts and reproduction steps.
- **Exact network layouts:** IP addresses, hostnames, account IDs, firewall rules, diagrams with real identifiers.
- **Documents you hold under a confidentiality agreement,** such as another company’s SOC 2 report.

Policies and procedures usually need the least redaction; scan reports, access lists and architecture documents need the most. The same care applies to [security questionnaires answered with AI](https://auditsuisse.com/security-questionnaires-with-ai).

### Prompt: plan the redaction of a document before analysis

```
I want to analyze a security document with you, and I need to redact it first. Do not ask me to paste the document yet.

Ask me what kind of document it is (policy, architecture description, scan report, access list, questionnaire), which systems it describes and what I want to learn from it, so that we keep what the analysis needs and remove the rest.

Then help me plan the redaction:
1. List the categories to look for in this kind of document: secrets, keys and tokens; personal data; customer data; unpatched vulnerability details; exact network layouts such as IP addresses, hostnames and account IDs.
2. For each category, give me search patterns I can run on my own machine and a consistent placeholder for each match, for example [HOST-1] or [EMPLOYEE-A], so that the document still reads correctly.
3. Tell me which details the analysis needs and which it does not. Flag every assumption you make about the document.

I will apply the redaction myself to a copy and keep the original unchanged. When I paste the redacted copy, check it once more and tell me if anything on the list still appears, without repeating the sensitive value in your answer.

List anything you assumed that I need to verify.
```

## Does using an AI assistant make its vendor one of our vendors?

Yes. Once company information goes into an assistant, its provider is a vendor that handles your data. Add it to your vendor inventory, tier it by the data it receives, review its terms and security documentation, and record who approved its use. The steps are in [vendor management for SOC 2 compliance](https://auditsuisse.com/vendor-management-for-soc-2-compliance). If the assistant is part of the service you deliver to customers, check whether its provider is a [subservice organization](https://auditsuisse.com/subservice-organizations-carve-out-vs-inclusive).

Write a short rule on acceptable use: which plans are approved, what may be shared and what may not. Then follow it. AI-written policies and descriptions are acceptable only if they describe what your company actually does. The audit tests how controls operate, not how documents read.

An agent with access to your cloud account can read far more than the file you meant to show it. Give it read-only access limited to the task: see [collecting SOC 2 evidence with an AI agent](https://auditsuisse.com/soc-2-evidence-collection-with-ai-agents).

These decisions are management’s. We do not choose your AI vendor, approve your settings or write your rule. In a [Zero-Platform SOC 2 audit](https://auditsuisse.com/zero-platform-soc-2-audit) we examine the evidence that your controls operated. That is AI-guided preparation, CPA-performed audit; the full workflow is in [SOC 2 with AI](https://auditsuisse.com/soc-2-with-ai).

## Who does what

Who does what when you decide what may go into an AI assistant.

| Task | Your team (with or without AI) | Your AI assistant | The auditor |
| --- | --- | --- | --- |
| Plan and settings | Decides which assistant and plan are approved, and who may use them | Explains a clause or setting you paste in; you read the source | No role |
| Redaction | Redacts a copy on its own machines and keeps the original | Suggests categories, patterns and placeholders; checks the redacted copy | Not involved. Examines original records, not working copies |
| Vendor review of the AI provider | Adds the provider to the inventory, reviews its terms, records the approval | Drafts review questions from your vendor policy | Inspects the vendor inventory and the reviews on file |
| Acceptable-use rule | Writes it, approves it and follows it | Drafts wording from what you tell it | Reads the rule and tests whether practice matches it |

## Zero-Platform SOC 2 Audit: the fee

A Zero-Platform SOC 2 audit from Auditsuisse costs $4,400 for Type I and $5,500 for Type II for companies of up to 50 people, fixed fee, Security criteria.

No compliance platform is required, so you save the platform fees, which start at about $10,000 to $15,000 a year for a GRC platform (an illustrative figure, not any vendor’s price).

Zero-Platform SOC 2 Audit fees for companies with 1–50 employees (USD, fixed fee, Security Trust Services Category). Fees as of November 15, 2026.

| Company headcount | SOC 2 Type I | SOC 2 Type II | Type I + Type II (combined) |
| --- | --- | --- | --- |
| 1–50 employees | $4,400 | $5,500 | $7,700 |

[See all headcount tiers](https://auditsuisse.com/zero-platform-soc-2-audit#fees)

Fees as of November 15, 2026.

## Free kit: prepare for SOC 2 without a platform

The prompt library from these guides, a policy index, the gap-assessment scoring sheet, the risk register template and the cost worksheet, as CSV and Markdown, with a short guide to the workflow. Free to use with attribution; not a substitute for an examination. Our evidence request list is not part of the kit: you receive it once the engagement letter is signed.

## Frequently asked questions

### Can we upload our SOC 2 policies to ChatGPT or Claude?

Policies rarely contain secrets, so they are among the lower-risk documents to work on. Still remove names, internal hostnames and anything a customer contract treats as confidential, and use a plan your company has approved.

### What if someone already pasted a key or a password?

Rotate it now. Then delete the conversation if the plan allows it, and record what happened as your incident process requires.

### Is a business plan always safer than a consumer plan?

Not automatically. The terms are typically different, and they can differ on training and retention. The answer for your plan is in the vendor’s own documentation and in the agreement your company accepted. Read both.

### Does the auditor care which AI assistant we use?

We do not choose or approve your tools. We look at whether the provider is in your vendor inventory, whether it was reviewed as your policy says, and whether your people follow your own rule on what may be shared.

## Sources & further reading

AICPA, [2017 Trust Services Criteria (with revised points of focus, 2022)](https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022); SSAE No. 18, AT-C sections 105 and 205. Vendor documentation is linked above.

**Related:** [Vendor management for SOC 2](https://auditsuisse.com/vendor-management-for-soc-2-compliance), [How to scope systems for SOC 2](https://auditsuisse.com/how-to-scope-systems-for-soc-2), [SOC 2 with Claude or ChatGPT](https://auditsuisse.com/soc-2-with-claude-or-chatgpt).

Product names are trademarks of their owners. Auditsuisse is not affiliated with these vendors.

---
Source: https://auditsuisse.com/is-it-safe-to-use-ai-for-soc-2 · This Markdown edition is generated from the same content as the HTML page.
