What a business agreement actually buys

The tier difference is mostly contractual

Moving from a consumer plan to a business, team or enterprise plan rarely buys you a better model. It buys you a different contract, and for anyone handling other people’s information that contract is the product.

Five things typically appear.

A commitment not to train on your content, as a term of the agreement rather than a setting you can toggle. The practical difference is that breaking a contract has consequences that changing a default does not.

A data processing agreement. Under European and several other regimes, when you handle other people’s personal data you are the controller and the service is your processor, and the law requires a written agreement between you setting out what the processor may do. Consumer terms are not that agreement. If you handle client data professionally, this document is the reason to upgrade.

A sub-processor list. Who else touches the data: cloud hosts, moderation vendors, analytics. Usually with a commitment to notify you before adding one.

Retention controls. Options ranging from a shorter default to zero retention for qualifying customers, meaning inputs are not stored after the response is returned.

Regional processing. A choice of where computation happens, which is what makes a residency requirement satisfiable.

Certifications, and what they mean

You will see SOC 2 Type II, ISO 27001, sometimes ISO 42001 for AI management systems, and sector schemes such as HIPAA arrangements in the United States.

Read them accurately. A certification says an auditor checked that the company follows the security processes it says it follows. It does not say the product is safe, that the model will not make things up, or that your data cannot leak. It is meaningful evidence about organisational discipline and nothing at all about model behaviour.

For most small organisations the certification matters mainly because a customer or an insurer asks for it. That is a legitimate reason to want it, and it is worth being clear that is what it is.

Reading a sub-processor list

The list is usually a linked page and it is more informative than the policy. It names every other company involved: the cloud provider running the hardware, any model provider if this one resells, moderation and support vendors, analytics, and payment processing.

Two things to look for. First, whether a model provider appears, because a product built on somebody else’s model means your data reaches two companies and you should read both sets of terms. Second, where each sub-processor operates, since that is what determines whether data leaves your region. A provider whose page is current and specific is telling you something about how it is run, quite apart from what the list contains.

What no agreement gives you

It does not make the output correct. No contract addresses hallucination.

It does not remove your responsibility. If you feed a client’s confidential material into a service, you are the one who decided to, and the agreement is your evidence of due diligence, not a transfer of liability.

It does not survive the model. A commitment about training is about the future. Anything already used in a completed training run cannot be extracted from the resulting weights.

It does not bind a reseller. If you reach the model through a wrapper, a router or an agency, your contract is with them and theirs may be different.

The realistic version for a small operation

Most readers are not negotiating enterprise agreements. The practical equivalent is short:

1. Use the API or a business tier where the default terms are better, rather than a consumer free tier.
2. Turn off training in settings wherever it exists, and screenshot it.
3. Redact by role so that the sensitive material largely does not arrive in the first place.
4. Keep confidential material on a local model.
5. Write one paragraph for your own records saying which tools you use, for what, and on what terms.

That last paragraph takes ten minutes and is what you will be asked for if a client, an employer or a regulator ever enquires. Almost nobody has one, and having one changes a difficult conversation into an easy one.