Broker guide
Is Claude Safe for Client Data in 2026?
Claude’s privacy depends on your plan and your training setting. Check what Anthropic keeps, how to delete chats and what client data to hold back.
- Published
- Updated
It depends: Claude’s safety for client data depends on your account type, training setting and the information you submit. Keep identifying client records out of personal Claude accounts. Team and Enterprise provide commercial protections, but your brokerage must still approve the service and what staff can enter.
Is Claude Safe for Client Information?
Personal Claude accounts need different treatment from an approved Team or Enterprise organisation. Paying for Pro or Max doesn’t turn a personal account into a commercial workspace.
Before pasting a client’s details, separate these risks:
- Retention is how long Anthropic keeps the chat or related data.
- Training is whether Anthropic uses the content to improve models.
- Human review is whether authorised people can examine the content.
Turning training off doesn’t immediately delete stored chats or remove every safety-review exception. A chat can remain stored even when it isn’t eligible for general model training.
Anthropic’s consumer access guidance limits training review to a small number of personnel. It describes separating data from user identifiers before review. That processing doesn’t give you permission to upload confidential client records.
For commercial customers, Anthropic’s Commercial Terms treat customer content as confidential information. Those terms permit access by representatives who need it and have confidentiality obligations. Commercial confidentiality still involves third-party processing.
Does Claude Train on Your Data?
Yes, Claude can use personal-account chats for training when you allow model improvement, with separate rules for feedback and safety review. Team and Enterprise content is excluded from model training by default.
Anthropic’s Consumer Terms permit training “unless you opt out of training through your account settings”. They also state that feedback and content flagged for safety review can be used for training despite an opt-out. Treat the training setting as one control over data use.
To turn off ordinary consumer model improvement:
- Open your account menu and select Settings.
- Select Privacy.
- Turn off Help Improve our AI models.
- Reopen Privacy and confirm the switch stays off.
Anthropic’s model-improvement instructions say this stops previous and new chats being used in future training runs. It doesn’t undo training already underway or remove data from models already trained. Safety-flagged conversations remain subject to separate uses.
Retention With and Without Training
Saved Claude chats stay available until you delete them, subject to the applicable account rules. The ordinary deletion period starts when you delete a chat. It isn’t an automatic expiry 30 days after you send a message.
Anthropic’s consumer retention policy gives these periods:
| Situation | Published retention rule |
|---|---|
| Saved chat with model improvement off | Remains in your history until deleted; backend deletion follows within 30 days |
| Chat you delete | Removed from history immediately and deleted from backend storage “within 30 days” |
| Eligible chat with model improvement on | De-identified data can remain in training pipelines for “up to 5 years” |
| Chat flagged as violating the Usage Policy | Inputs and outputs can be retained for up to two years; classification scores for up to seven years |
The five-year training period applies to new or resumed chats after you enable the setting. Turning it off stops future training use of stored chats. Legal obligations, disputes and policy enforcement can require longer retention.
Incognito Still Has Retention
Claude incognito chats stay out of chat history and memory and aren’t used for model training. They are retained for 30 days by default. An Enterprise organisation’s retention setting can require longer storage.
To start one, open a new chat outside a project and select the ghost icon. Confirm that the interface shows the Incognito chat label before entering your prompt. Incognito doesn’t use existing memory or create future memory entries, but it can access profile preferences.
Team and Enterprise incognito chats can appear in organisation data exports. Enterprise compliance access can include them too. Incognito doesn’t make an identifiable client file suitable for an otherwise unapproved service.
Personal Plans vs Team and Enterprise Plans
Team and Enterprise change the agreement governing your data and give the organisation control over its use. They don’t remove storage or your brokerage’s responsibility to protect information.
| Control | Personal Claude accounts | Team | Enterprise |
|---|---|---|---|
| General model training | Depends on your model-improvement choice | Excluded by default | Excluded by default |
| Feedback exception | Related conversation can be used when you submit feedback | Explicit feedback or permission can allow training | Explicit feedback or permission can allow training |
| Saved chats | Kept until deletion under consumer rules | Kept for continued use until deletion | Kept until deletion or applicable custom retention |
| Retention administration | Personal deletion controls | Organisation and user deletion processes | Custom retention controls with a 30-day minimum |
| Organisation access | Personal account controls | Primary Owner manages access and can request data exports | Organisation access, exports and additional administrative controls |
| Data-processing terms | Consumer Terms and Privacy Policy | Organisation agreement and commercial processing terms | Organisation agreement and commercial processing terms |
Anthropic’s commercial training policy explains the default exclusion and feedback exception. Owners can disable member feedback through Rate chats in Organization settings under Data and Privacy. That can prevent staff from sending a confidential conversation with a rating.
Anthropic’s organisation retention rules keep saved commercial chats available for continued use. Deleting one removes it from history immediately, with backend deletion within 30 days, subject to exceptions. Don’t apply an API retention promise to saved Team chats.
Enterprise custom retention controls need an owner to configure them. Data is retained indefinitely by default unless a custom period is set. Project retention takes precedence over the standalone-chat period, so a chat-only setting doesn’t establish when project chats disappear.
Your organisation’s Primary Owner can request exports containing conversations and uploaded files. The commercial agreement incorporates a Data Processing Addendum, which sets processing responsibilities. An account labelled Enterprise doesn’t by itself establish that a particular client-data workflow meets your brokerage’s requirements.
What a Broker Must Never Enter
Keep identifying client records out of personal Claude prompts, and follow your brokerage’s approved data rules in commercial accounts. Anthropic’s consumer terms require you to have the permissions needed for it to process what you submit.
Don’t paste these into an ordinary assistant conversation:
- Client names combined with income, debts, assets or credit-history details.
- Tax file numbers, identity-document numbers or copies of identity documents.
- Bank statements, payslips and tax returns containing client identifiers.
- Account credentials, passwords and verification codes.
- Material a client supplied in confidence without authorisation for this use.
Remove the details that identify someone directly and the combinations that identify them indirectly. An unusual job, exact employer and small location can identify a client even after you remove their name. Initials alone don’t solve that problem.
This hypothetical example uses invented details:
Incorrect: “Explain what documents Sam Example at 24 Sample Road needs, with $118,450 income from Sample Aviation and account number 98765432.”
Safer: “Give a generic document checklist for an employed applicant with variable overtime. Leave all personal and account details blank.”
The safer version preserves the question without sending the client record. Add identifying details later in your brokerage’s approved system. If the question still requires confidential information, use an approved process for that information.
Delete Claude Chats or Your Account
Claude lets personal users delete one conversation, select all conversations or permanently delete their account. These actions have different effects, so choose the smallest one that removes the information you intend to remove.
Delete One Chat
Follow Anthropic’s conversation deletion instructions on the web:
- Find the conversation in the sidebar or open Chats and tasks.
- Hover over the conversation and open its three-dot menu.
- Select Delete, then confirm Delete.
- Confirm the conversation no longer appears in your chat history.
Delete All Chats
- Open Chats and tasks in the sidebar.
- Open a conversation’s three-dot menu and choose Select.
- Choose Select all at the top.
- Select Delete and confirm the deletion.
- Confirm your chat list is empty.
Deleting every chat doesn’t delete the whole account. Other saved data, including projects, needs its own removal or account deletion. If a client record was exposed, preserve the incident details securely before deleting the content.
Delete Your Account
Account deletion is permanent and removes access to conversations, projects and other saved account data. Anthropic’s account deletion procedure requires paid personal subscribers to cancel and wait for the subscription period to end first.
- Export any records you are authorised and required to retain before deletion.
- If you have a paid personal plan, cancel it through Billing and wait for it to lapse.
- Open your account menu, then Settings and Account.
- Select Delete account and complete the confirmation prompts.
- Confirm that you can no longer access the deleted account.
If your settings require support to complete deletion, follow that account-specific route. Organisation accounts have separate ownership controls, so involve the Primary Owner when removing work-account data.
What Deletion Leaves Behind
Deleting a chat starts backend removal, subject to the published retention exceptions. It doesn’t remove information from an already-trained model or reverse a training run already in progress. Legal and policy-enforcement retention can outlast normal deletion.
Copies you exported or sent to another service remain separate. Review projects and other saved data as well as chat history. After an accidental client-data upload, record what you removed and escalate through your brokerage’s incident process instead of treating an empty chat list as complete containment.