Skip to content
AI & Privacy

Is It Safe to Upload Bank Statements, IDs, and Photos to ChatGPT? What Actually Happens to Your Files

Practical Web Tools
7 min read
Share:
XLinkedIn
Is It Safe to Upload Bank Statements, IDs, and Photos to ChatGPT? What Actually Happens to Your Files

Every week, millions of people drag a bank statement, a tax form, or a photo of their driver's license into ChatGPT and ask it to "check this" or "summarize the numbers." Most never read what happens next. This guide covers the actual mechanics (where the file goes, how long it stays, whether it trains future models), then goes document by document through the risk, and ends with a redaction workflow that takes about two minutes.

The short answer

Uploading a document to ChatGPT sends the file to OpenAI's servers. Files shared in personal (free and Plus) chats may be retained for ~30 days by default and can be used for model training unless you turn that off in Settings → Data Controls. So the honest rule is: fine for documents you'd be comfortable emailing a stranger's help desk; not fine for anything with account numbers, full ID images, or medical records unless you redact first.

Try Metadata Washer: free, no sign-up.

Where your file actually goes

When you attach a file to a chat, three things happen.

1. The upload. The file transmits to OpenAI's servers and is stored there, a fundamental difference from browser-based tools, where processing happens on your own machine.

2. The retention window. OpenAI's published policy has held that files in consumer chats are retained for around 30 days before deletion (enterprise plans differ, with stricter defaults).

3. The training question. Consumer-plan conversations have historically been eligible for model training by default, with an opt-out toggle in Settings → Data Controls ("Improve the model for everyone"). Team, Business, and Enterprise plans do not train on your data by default. Policies change, so check your plan's current terms before relying on any of this.

The nuance most people miss: deleting the chat from your history does not necessarily pull the file out of the retention pipeline immediately, and "retention" and "training eligibility" are separate systems. Turning off training does not delete anything; deleting a chat does not promise exclusion from a training set already created.

Risk by document type

Document Risk level What's actually exposed Safer approach
Bank statements High Account numbers, balance, transaction history, address Black out account numbers, or summarize the numbers yourself
Tax documents (W-2, 1099, returns) High SSN, income, employer, dependent details Remove SSN and employer EIN before uploading
Driver's license / passport High Full ID number, DOB, address: the identity-theft starter kit Don't upload full IDs; crop to just the part you need explained
Photos of yourself Medium Face biometrics tied to your chat content Prefer describing the question; avoid bulk photo dumps
Resume / CV Medium-low Phone, email, address, employment history Trim the contact header first if you're asking for writing feedback
Medical records High Diagnoses, IDs, insurance numbers Redact identifiers; consider whether you need AI at all here
Contracts / NDAs Medium Confidential or legally binding clauses Check confidentiality clauses first; many prohibit third-party processing
Homework / essays Low Originality only Fine for feedback
Code (non-proprietary) Low Logic, not personal data Fine; enterprise repos deserve enterprise plans

The redaction workflow that takes two minutes

Before uploading anything from the high-risk rows:

  1. Make a copy. Never redact your only original.
  2. Remove, don't cover. PDF viewers that "cover" text with a black box often leave the real text underneath: use select-and-delete, or a proper redaction flow that strips the text layer. (The full white-out guide covers the flatten step that makes removal real, including the copy-paste test that proves it.)
  3. Scrub the metadata too. Photos and PDFs carry hidden metadata (author names, creation timestamps, sometimes GPS coordinates from the phone that photographed the document). This is the step almost everyone forgets.
  4. Upload the cleaned copy only.

For step 3, the free Metadata Washer shows every metadata entry a JPG, PNG, or PDF carries (GPS, author, software) and strips it all, entirely in your browser with no upload, so the act of checking doesn't itself leak the file.

What about "temporary chat" mode?

ChatGPT's temporary-chat option doesn't save the conversation to your history and doesn't train on it, but the file still transits and is processed on OpenAI's servers during the session, and short-term retention for abuse monitoring still applies. It reduces the training and history footprint; it does not make the upload local. If a document is sensitive enough that you're relying on temporary mode, it's sensitive enough to redact first.

The local alternative

If what you're doing with a document (summarizing, extracting, asking questions) doesn't strictly need a frontier cloud model, a local model changes the risk math entirely: the file never leaves your machine, so there's nothing to retain and nothing to train on. Modern local models handle document Q&A surprisingly well, and you don't need exotic hardware: here's what runs well on 4, 8, 16, and 32 GB of RAM.

A simple decision rule

Ask yourself one question before any upload: "Would I mind if this file were stored on a stranger's server for a month?"

  • If no, obviously fine: upload away.
  • If yes: redact the sensitive fields, strip the metadata, then upload the cleaned copy.
  • If the whole document is sensitive (medical, legal, full ID): describe the problem in words instead of attaching the file. You'll often get 90% of the value from a good description.

AI chat is phenomenally useful; it's just most useful to you, on your terms, when you control exactly what it sees.

Frequently Asked Questions

Does ChatGPT keep files I upload?

Yes: uploads land on OpenAI's servers, and consumer-chat files have historically been retained for roughly 30 days before deletion. Deleting the chat from your history doesn't necessarily remove the file from that pipeline immediately.

Does ChatGPT train on my uploaded documents?

On consumer (free and Plus) plans, conversations including files have been eligible for training by default; the opt-out lives in Settings → Data Controls. Team, Business, and Enterprise plans don't train on your data by default. Check your plan's current terms, since this policy has shifted over time.

Is it safe to upload my resume to ChatGPT?

Mostly, with one cleanup step: trim the contact header (phone, email, address) before uploading if you're only asking for writing feedback. The employment history itself is low-risk.

Can I upload my bank statement if I black out the account number?

That's the right workflow: redact account numbers and any transaction lines you'd rather not share, strip the file's metadata, then upload the cleaned copy. Remember that a drawn black box isn't removal; use a redaction method that deletes the underlying text.

Does temporary chat mode prevent my file from being stored?

Partially. It skips history and training, but the file still uploads to OpenAI's servers for processing, and short-term abuse-monitoring retention still applies. For sensitive documents, redact first regardless of mode.

What's the alternative to uploading sensitive documents at all?

Two good ones: describe the problem in words instead of attaching the file, or run a local model that processes everything on your machine. Browser-based tools that never transmit (the Metadata Washer for scrubbing files, local models for asking questions) cover most of the workflow without the upload.

Try Metadata Washer: free

Open tool →

Inspect and strip EXIF, GPS & document metadata from JPG/PNG/PDF: in your browser

More from AI & Privacy

Browse all

79 more articles in this category