ChatGPT can be safe for company data, but only on a plan your organisation controls and only after you have checked its retention and training settings. A personal consumer account is not a safe place for business data: the employee, not the company, controls its settings, and there is no admin view, contract or audit. Business plans and the OpenAI API move that control to the organisation. Of these, the API, called through a gateway you govern, gives you the most control, because you also decide what content leaves.
This post compares the tiers on the questions a security or privacy lead has to answer, and explains why the plan alone does not settle the risk.
The question behind the question
"Is ChatGPT safe?" usually hides four separate questions:
- Training. Can the provider use our prompts and outputs to improve its models?
- Retention. How long are prompts and outputs stored, and where?
- Control. Who in our organisation can see and change those settings, and who can see usage?
- Content. What stops a person sending something that should never leave the company?
The tiers differ on the first three. None of them answers the fourth. Product names and defaults change, so treat the comparison below as the questions to check against the current terms for the plan you hold.
Tier by tier
Consumer accounts (free and individual paid plans)
Consumer accounts are set up and controlled by the individual. Data controls, such as whether conversations may be used to improve models, sit in that person's settings. The company has no administrative view of what was shared, no way to enforce a setting, and no data processing agreement covering the account. From a governance view this is the shadow AI case: use you cannot see or control. See how to build an AI agent inventory for how to find it.
Business and enterprise plans
Business and enterprise workspaces are owned by the organisation. Admins manage members, single sign-on and workspace settings, and the contract terms cover business data. These plans are the right choice when staff need the chat interface itself. Before rollout, confirm in the current contract and admin console: the training position, the retention period for conversations, available data residency options, and what usage and audit data admins can export.
The API
The API is what internal tools, scripts and agents use. OpenAI's API data controls documentation states that data sent to the API has not been used to train or improve OpenAI models since 1 March 2023, unless you opt in. By default, abuse monitoring logs are retained for up to 30 days. Approved customers can choose Zero Data Retention or Modified Abuse Monitoring at the organisation or project level, and data residency is a project configuration option for eligible customers. Some endpoints still store application state even with Zero Data Retention enabled, so check the endpoint table for the features you use.
Comparison table
| Question | Consumer account | Business / enterprise plan | API |
|---|---|---|---|
| Who controls data settings | The individual user | Organisation admins | Organisation, per org or project |
| Contract covering business data | No | Yes | Yes |
| Training on your data | Depends on the user's own setting | Check current plan terms | Not by default, unless you opt in |
| Default retention | Per the user's history and settings | Admin-managed, check terms | Abuse monitoring logs up to 30 days |
| Zero Data Retention | No | Check terms | For approved customers, configurable |
| Data residency | No | Check terms | Project option for eligible customers |
| Content controls before data leaves | None | Limited to admin settings | Whatever you put in front of it |
| Fit for company data | No | Yes, for chat use | Yes, for apps and agents |
The last two rows explain why many organisations end up with both a business plan for chat and a governed API path for everything built in-house.
Why the plan alone is not enough
A plan setting governs what the provider does with data after it arrives. It does nothing about what arrives. An enterprise workspace with zero retention will still receive the database password an engineer pasted. The control for that sits on your side of the connection.
On the API path, that control is a gateway between your callers and the provider:
- Keys held centrally. Applications and agents use a gateway key; the provider key stays in central configuration. Securing LLM provider API keys covers why keys on laptops become a private, ungoverned channel.
- Your own provider account. With bring-your-own-key, retention, residency and contract settings are the ones on your provider account. BYOK: managing LLM configurations explains the model.
- Content guardrails. Prompts are inspected before they leave, and matched content is blocked or redacted. The steps are in how to stop employees pasting sensitive data into ChatGPT.
- Region choice. Where a prompt is processed is set by the provider and account you configure. Data residency for AI agents covers how to plan for that.
Decision checklist
Where Praesidia fits
Praesidia covers the API side of this picture in three steps. Discover: register the agents and applications that call models, so you know which ones exist. Secure: Praesidia's model gateway puts one address in front of OpenAI and the other providers you use, holds your provider keys server-side, and applies guardrails that can block or redact matched content. Because the keys are yours, the retention and residency settings that apply are the ones on your provider account. Prove: calls the gateway blocks, or that require a step-up, are written to an append-only, hash-chained audit trail.
Praesidia does not govern the ChatGPT web or desktop app, and it does not record allowed gateway calls in the audit trail. For chat use, the plan's own admin controls and your acceptable use policy remain the controls.
Common questions
Is ChatGPT Enterprise GDPR compliant? A plan cannot be compliant on its own; your processing is. A business plan with a data processing agreement gives you the contractual basis. You still need a lawful basis, a record of processing, and limits on what staff enter.
Does OpenAI train on API data? According to OpenAI's API data documentation, not unless you explicitly opt in.
Is Zero Data Retention on by default? No. It is available to approved customers and is set per organisation or project.