Can ChatGPT Give Legal Advice? The Real Risk Isn't Bad Answers — It's Where Your Documents Go

A quick disambiguation first, because the search results pull in two different worries. "Can ChatGPT give legal advice?" is usually asked in one of two spirits: is the answer any good and am I allowed to rely on it, or is it safe to put my actual documents in here to get that answer. Almost every guide you'll find answers the first question — and warns, correctly, that ChatGPT sometimes fabricates case citations. This page is about the second, because for a small-office owner it's the one with teeth.

The short answer: yes, ChatGPT can produce text that reads like legal advice — but that's not the risk that should stop you. The moment you paste a real contract, settlement draft, or client agreement into a consumer ChatGPT account to get that advice, you have handed a copy of a confidential document to a third party. On the default consumer plans, OpenAI's own documentation says your content may be used to help train future models unless you opt out. The wrong-answer problem you can catch by having a lawyer check the work. The disclosure problem happens the instant you press enter, and it's the one regulators actually write rules about. Everything below is the detail behind that, with the primary documents linked at each claim.

Isn't the real problem that ChatGPT makes up cases?

That's the framing you'll see almost everywhere, and it's a real problem — ChatGPT will sometimes cite cases and statutes that don't exist, stated with total confidence. But it's a problem you can manage: you treat the output as a rough draft, and a licensed professional checks anything that matters. Notably, even the regulator that governs this — see the confidentiality guidance below — lists both risks: hallucinated citations and the reuse of what you input. Most ranking pages stop at the first.

There's a second, newer distraction. You may have read that ChatGPT "won't give legal advice" anymore. That's a description of a service limit — a company deciding what its product will and won't do for liability reasons. It tells you nothing about what happens to the document you upload. Those are two completely different questions, and searchers are being told the service-limit one is the whole story. It isn't. The custody question is where the exposure lives.

(One honesty note on our own claim: in a scan of the top search results on DuckDuckGo, none of the leading pages for these queries foreground where the pasted document goes — they orbit answer-quality or OpenAI's own service restrictions. We could not re-confirm Google's exact ranking set this round, so treat "nobody frames it this way" as a DuckDuckGo observation, not a Google-wide guarantee.)

Where does your contract actually go when you paste it in?

Trace it, step by step. You paste the text into the chat box. It's encrypted in transit and sent to OpenAI's servers, where it's processed in readable form — that's how the model can answer you. Then it's stored there under OpenAI's policies.

On the consumer plans a small office typically signs up for, that stored content may also be used to improve the product. OpenAI's help center states that for consumer services like ChatGPT it "may use your content to train our models" unless you opt out (OpenAI — How your data is used). You can turn that off — the "Improve the model for everyone" toggle under Settings → Data Controls stops future training, though the chat still sits in your history (OpenAI — Data Controls FAQ). The paid business tiers change the default: OpenAI states that "by default, we do not train on any inputs or outputs from our products for business users" — a category that covers ChatGPT Business, ChatGPT Enterprise, and the API. Better terms — but the document still lives, for some period, on machines you don't own and can't inspect.

The plan you're on decides the default, and most people paste into the free one without checking.

Why is "where it goes" a bigger problem than a wrong answer?

Because for anyone with a confidentiality obligation, the duty attaches to the disclosure itself — to the act of handing the document over — not to what the vendor does afterward.

The clearest named anchor here is the State Bar of California's Practical Guidance for the Use of Generative AI in the Practice of Law (verified against the live document as of July 2026). It states plainly: "As a general matter, a lawyer must not input any confidential information of the client into a generative AI solution that may present material risks to confidentiality or security, absent informed client consent" (California State Bar guidance, PDF). And it's explicit about why the input is the exposure: generative AI products "often utilize the information that is input by the user, including prompts and uploaded documents or resources, to further train or refine the AI, and might also share such information with third parties." In other words, the pasted contract itself is the risk — not just a bad reply.

The same guidance closes the "but the vendor promises it's private" escape hatch: satisfying the duty, it says, requires "reasonable efforts" that amount to "more than reliance on generalized marketing assurances," and may include actually reading the terms of use and privacy policy before you input anything. You have to read the contract behind the checkbox, not the ad copy.

This isn't one state's quirk. The American Bar Association's Formal Opinion 512 grounds the same duty in Model Rule 1.6 and reaches the structural point directly: because many self-learning AI tools are designed so their output "could lead directly or indirectly to the disclosure of information relating to the representation of a client, a client's informed consent is required prior to inputting information relating to the representation into such a GAI tool." A line buried in an engagement letter, the opinion adds, is "not sufficient" for that consent. And this isn't a peculiarly American duty: bar regulators and privacy authorities in other countries reach the same structural conclusion — the obligation to protect confidential information is a use of data your existing rules already govern, wherever your building is.

And you don't have to be a lawyer for this logic to bite. If you're an accountant, a clinic, a consultancy — anyone holding documents that someone trusted you to keep — the shape is identical: the obligation is triggered by sending the material out, and it doesn't dissolve because the answer came back useful. Practitioners feel it acutely; as one commenter, u/imangryignoreme, put it, "Reminder that giving client information to chatGPT is a violation of attorney-client privilege! DON'T DO THIS unless you're excited to meet your bar ethics committee." That's an anecdote, not a ruling — but it captures the duty the guidance above makes formal.

What actually happens to a legal document across the plans?

	Consumer ChatGPT (Free / Go / Plus / Pro)	ChatGPT Business / Enterprise	Local AI on your own hardware
Where the document goes	OpenAI's servers	OpenAI's servers	Your own machine, in your building
Used to train models?	Yes by default; opt-out available (data-usage page)	No by default (same page)	Nothing is sent anywhere when run offline
A third-party processor to vet?	Yes — and the duty says read the terms, not the marketing	Yes — plus a contract to sign and monitor	No third party exists to vet
Who governs the confidentiality risk	You, but the exposure is already out of your hands	You, via the vendor agreement	Your existing internal policies
Priced	Per user per month (pricing)	Per user per month (pricing)	Free software; you buy hardware once

Two things the table won't claim: that the business tier is "safe" — it's a legitimate route if you've signed the agreement and actually read it — and that local is always the cheaper answer. For a solo user it usually isn't; that's what the cost guide and worksheet are for.

Doesn't anonymizing the names make it safe?

This is the workaround practitioners reach for most — swap in "Party A" and "Party B," find-and-replace afterward. It genuinely reduces exposure, and for lightly sensitive work it may be enough. But it doesn't settle the duty, and lawyers argue about it among themselves. As one, u/learned_foot, put it: "Go post on your local bar forum your complex contract negotiations, just with 'party A' and 'B', and see who calls first, the discipline committee or the client who got alerted." The point: a distinctive deal — specific numbers, dates, and terms — can still identify the parties even with the names stripped, and the document has still left your control. Anonymization is harm reduction, not a custody fix.

When is ChatGPT genuinely fine for legal work?

Often, honestly. If the material contains nothing confidential — a blank template, publicly filed language, your own website's terms, a general "what does indemnification mean" question with no real matter attached — cloud AI is capable, cheap to start, and there's no custody problem because nothing sensitive is in custody. Using ChatGPT to understand the law before you call a professional is a reasonable, low-risk use.

The failure mode isn't "using ChatGPT." It's unsorted use — the real client contract and the harmless template flowing through the same consumer chat window with nobody deciding which is which. The sorting exercise is the whole game, and our ChatGPT confidentiality guide walks through it; the HIPAA-specific version does the same for clinics.

What if you kept the sensitive work on hardware you own?

The other option is to remove the third party from the confidential pile entirely. "Local AI" means an AI model that runs on a computer in your own office instead of a vendor's data center — the idea explained in What Is Local AI? and compared head-to-head in local AI vs cloud AI. When the model runs on your machine and can work offline, the pasted contract never leaves the building — so there's no vendor terms to read, no training default to toggle, and no outside company for the confidentiality duty to reach. It's the setup one trial lawyer, u/JohnnyLovesData on r/LawFirm, was pointing at: "sharing that information with ChatGPT (OpenAI), is not a good idea. Using your own self-hosted language model would be better."

The honest trade-offs: it costs real money up front, it gives you a machine to maintain, and the open models you'd run are a step behind the frontier (the largest, most capable models) — so many offices keep a cloud plan for the public pile and route only confidential work to the local one. Whether that trade is worth it depends on how much of your daily work actually touches confidential documents, which is exactly what the readiness quiz estimates in about two minutes.