u/juliarmg

If you've sat in front of ChatGPT with a real client document open in another window and decided not to paste it in, this is for you.

The honest answer to "is it safe to paste confidential client documents into ChatGPT?" is no, not by default. But "no" leaves a lot on the table. The professionals who would benefit most from AI on real work, lawyers, therapists, accountants, financial advisors, consultants, end up using AI on toy examples instead of actual documents.

There are real workflows that solve this. Here's what they actually look like.

What's Actually Wrong with Pasting Into ChatGPT (or Claude, or Gemini)

Three things, in increasing order of how seriously they're treated:

1. Provider data retention. OpenAI retains API and ChatGPT inputs for up to 30 days for abuse monitoring even with training opted out (OpenAI's data usage policy). Anthropic and Google have similar retention windows. "Don't train on my data" is not the same as "don't store my data."
2. Engagement agreements. Most client engagement letters either prohibit sharing client data with third-party services or are silent, which still leaves the professional liable under their underlying confidentiality duty.
3. Profession-specific obligations. HIPAA for healthcare. Attorney-client privilege and ABA Model Rule 1.6, see ABA Formal Opinion 512 on AI use in legal practice. FINRA and SEC for financial advisors. Most have issued specific opinions and most land in the same place: don't disclose client information to a service that doesn't have a BAA / DPA / equivalent.

The combination is what makes this hard: three overlapping rules, and checking two doesn't save you on the third.

The Four Workflows That Actually Work

Option 1: Don't use AI on this document

Sometimes the right answer. A custody affidavit, a psych intake from a high-risk client, a privileged settlement memo, there are documents where the cost of any breach exceeds the productivity gain.

When this is right: high-stakes, high-sensitivity material where the work is mostly judgement, not synthesis.

Option 2: Manually redact, then paste

Open the document. Find-and-replace every name, account number, and identifying detail with placeholders. Paste the redacted version. Reverse the placeholders manually in the response.

When this is right: occasional one-offs on a single short document.

The real problem: slow and error-prone. Names appear in 40 places in a 30-page brief. One missed instance defeats the whole exercise.

Option 3: Run a local model on your own machine

Tools like Ollama, LM Studio, and GPT4All let you run open-weight models (Llama, Mistral, Qwen) entirely on your computer. No cloud call, no provider, no retention.

When this is right: M-series Mac with 16GB+ RAM, work where a smaller model is good enough, summarising a 5-page memo, drafting a routine email, light Q&A on a single document.

The real problem: open-weight models are improving fast but still trail GPT-4-class and Claude-class on dense legal/medical/financial reasoning. If you're using AI to genuinely improve your output on hard documents, the quality gap is real.

Option 4: Automated redaction + frontier model ("Smart Redaction")

Software on your machine identifies and replaces sensitive entities, names, emails, account numbers, case numbers, dates, addresses, with placeholders, sends the cleaned prompt to a frontier model (GPT, Claude, Gemini), and reverse-maps the placeholders in the response.

A real example. Original prompt:

Draft a response to opposing counsel re: Smith v. Patel (23-CV-1042). They're requesting production of the 2022 financial records for $4.2M from John Smith's company, Patel Industries. Reference the protective order signed 03/15/24.

After redaction, what the cloud model actually receives:

Draft a response to opposing counsel re: [CASE_1] ([CASE_NUMBER_1]). They're requesting production of the [YEAR_1] financial records for [AMOUNT_1] from [PERSON_1]'s company, [COMPANY_1]. Reference the protective order signed [DATE_1].

The cloud model has enough structure to draft a useful response. It never learns the parties' names, the case number, the dollar figure, or the date. The response is reverse-mapped on your device before you see it.

When this is right: dense work where you want frontier-model quality on documents that can't go in raw. Multi-page contract review, brief drafting, session note synthesis, financial memo drafting.

The real problem: redaction is only as good as the entity recognition. Unusual names, internal codenames, and novel identifiers can slip through. Tools that handle this well let you preview the redacted version before any prompt is sent, and let you add custom patterns.

Quick Comparison

Workflow	Output Quality	Privacy	Setup	Best For
Don’t use AI	n/a	Highest	None	High-stakes judgement work
Manual redact + cloud	Frontier	High (if you don’t miss anything)	Per-doc effort	Occasional one-offs
Local model	Mid	Highest	One-time install	Lighter work, M-series Mac
Smart Redaction + cloud	Frontier	High	One-time install	Dense work on real documents

For most professionals doing daily client work, the answer is a mix of Options 3 and 4 depending on the document.

What to Actually Look for in a Tool

If you're evaluating something that promises privacy-aware AI for professional work, ask:

Where does redaction run? On your device, or on the vendor's server? "We redact before sending" means nothing if "redact" happens after the document already left your machine.

Where do the documents themselves live? On your disk, or in the vendor's cloud index? Indexed-in-vendor-cloud is back to the original problem.

Can you run a fully local model when you want to? For the highest-sensitivity work, no cloud at all should be an option.

Custody on cancellation. If you stop paying, what happens to your indexed documents? Clean delete, or stuck on someone's server?

Elephas, a Mac-native AI workspace built around Smart Redaction (Option 4) for this category of work. It supports both cloud-via-redaction and fully local models, indexes documents on your disk. Mentioning it because it's directly relevant, Options 1, 2, and 3 are also real and sometimes the better fit.

Here is the website: https://elephas.app

Happy to answer questions about how the redaction pipeline handles edge cases, unusual names, custom entity types, multi-document context. That's the part that's hardest to get right and worth being skeptical about with any tool that claims to do it.

FAQ

Is it ever safe to paste a confidential document into ChatGPT?

Without a BAA or equivalent agreement with OpenAI, no. Inputs are retained for up to 30 days even with training opt-out. Some enterprise plans add zero-retention agreements; check the specific contract.

Does ChatGPT "memory off" or "temporary chat" solve this?

No. Those settings affect what's available in your later chats. They don't change input retention or processing on OpenAI's side.

What about Claude and Gemini?

Same baseline. Inputs are retained for abuse monitoring even with training opted out. Specific retention windows are published by each provider.

Are local models good enough?

For routine summarisation, drafting, and Q&A on a single document, current open-weight models (Llama 3.x+, Qwen 3.5+, Mistral) are surprisingly capable on a recent Mac. For dense reasoning on legal, medical, or financial documents, frontier models still pull ahead, which is why Smart Redaction exists.

How accurate is automated redaction?

Depends heavily on the tool. Common entities (names, emails, phones, US date formats, US addresses) are caught reliably. Edge cases, internal codenames, unusual transliterations, project-specific identifiers, depend on whether the tool lets you add custom patterns. Always preview before sending.

Does Smart Redaction make a workflow HIPAA- or privilege-compliant by itself?

No tool by itself does. The architecture is one part of a compliant workflow; firm policy, BAAs where applicable, and user practice are the other parts. Smart Redaction makes the technical foundation defensible; the rest is on the professional.

Hi,

I am new to camera systems. I am looking to set up an outdoor security camera system. India now has some restrictions on security cameras. Would this model https://www.pramaindia.in/product/pt-nc34tp3-4namd2/ work with Scrypted? It says ONVIF under protocol.

I would appreciate your help.