Knowledge Base

Corporate AI security: controlling data shared with AI tools

Before approving an AI tool, check three things: whether the provider uses requests for model training, how long it stores chats and files, and who can access them. Record those answers for the exact product and plan your team uses.

Training, chat history and data retention

OpenAI does not train on ChatGPT Business, Enterprise or API data by default. Chat history and file retention follow separate rules. For the OpenAI API, Zero Data Retention (ZDR) requires approval and applies subject to feature and endpoint limits. Standard API abuse-monitoring logs may retain content for up to 30 days, with exceptions.

Anthropic publishes separate retention rules for its commercial chat products and API. For Microsoft 365 Copilot, Microsoft says it does not train foundation models on prompts or responses. Interaction data can still be stored under the organization’s Microsoft 365 policies. Verify the terms and settings for your account.

Data Exposure Vectors in Everyday LLM Usage

Three vectors dominate risk: pasting confidential records into prompts, uploading files with embedded metadata, and indirect prompt injection. Developers occasionally upload stack traces containing active database credentials, while sales reps upload lead spreadsheets with phone numbers and identity records.

Indirect prompt injection occurs when an agent evaluates external emails or web pages. Embedded adversarial instructions cause the model to read internal documentation and transmit extracts to an external attacker system.

Where to apply data sharing rules

Give employees approved work accounts and document the data they may use. Check what controls your plan actually supports, including access management and connected apps.

Data loss prevention (DLP) can flag recognizable patterns such as API keys and payment card numbers where the product or gateway supports inspection. Test file uploads and connected apps separately. Pattern matching can miss sensitive information.

What to verify before sharing company data

Training and retention by product
ProductModel trainingHistory and retention
ChatGPT Business / EnterpriseBusiness data excluded by defaultCheck workspace history and available retention settings
OpenAI APIAPI data excluded by defaultCheck monitoring logs, endpoint storage and ZDR eligibility
Claude commercial productsCheck commercial terms and settingsCheck the chat product and API separately
Microsoft 365 CopilotPrompts and responses excluded from foundation-model trainingCheck interaction history and Microsoft 365 retention policies

Implementation Procedure for Secure AI Adoption

Practical setup sequence for corporate environments and employee devices.

  1. List the AI tools and accounts each team uses.
  2. Verify training, retention, file handling and connector terms for each approved product and plan.
  3. Define which classes of data staff can share. Keep credentials and access tokens out of prompts and attachments.
  4. Test the available sharing controls with synthetic data.
  5. Assign an owner to review settings, contracts and connected apps when they change.
Further reading: NIST AI Risk Management Framework (AI RMF 1.0)Further reading: OWASP Top 10 for Large Language Model ApplicationsFurther reading: OpenAI Business Privacy and Enterprise Data ControlsFurther reading: OpenAI API: data retention controlsFurther reading: Anthropic: commercial data retentionFurther reading: Microsoft 365 Copilot: data, privacy and security

Practical answers

Questions about this topic

Does turning off model training delete my ChatGPT history?

Training controls and chat deletion are separate settings. Check the history and retention rules for your account, including exceptions and what happens to uploaded files.

Do pre-commit hooks stop secrets from reaching a coding assistant?

A pre-commit hook runs when you commit. The assistant may already have read the file. Keep secrets outside the assistant’s accessible context and test the tool’s exclusion and sharing settings.

What if someone already uploaded a customer list?

Record what was shared and where, restrict access to the conversation and follow the provider’s deletion process. Revoke any exposed credentials. Have the person responsible for privacy assess notification duties.

LET US DISCUSS YOUR TASK

Review how your team shares data with AI tools

We can review account settings, connected apps and where requests and logs are stored.

Request a technical review