Purplelink
← All guides

Pasted a password or API key into ChatGPT: what to do

If you pasted a password or an API (application programming interface) key into ChatGPT, treat it as exposed. Do these five things in order, and do the first one before anything else.

Disclosure up front: I make Outbound Veil, a Mac menu-bar app that checks what you type for sensitive text. It appears in step 5. I read the provider pages below on November 18, 2026. They change, so check them for your account.

1. Rotate the key or change the password first

Replace the secret before you do anything else, because deleting the chat does not make a pasted key safe and the old key keeps working until you turn it off.

2. Delete the chat

Delete the chat. OpenAI says it is removed from your view at once and scheduled for permanent deletion within 30 days. The exceptions are data already de-identified or held for security or legal reasons (Deleting and archiving chats). Treat the secret as exposed anyway, which is why step 1 comes before this one.

3. Unshare any link to that chat

Anyone with a shared link to a personal-account chat can read it. OpenAI says deleting a conversation removes its shared link. To check, go to Settings, then Data controls, then Shared links, then Manage. Select Delete shared link for one chat, or Delete all shared links under More actions. Deleting a link stops new access but does not remove a copy someone already saved (Sharing conversations).

4. Check the access logs for use of the key

If you see use you do not recognize, treat the account as compromised and follow the provider's own steps, which I have not covered here.

5. Check before you paste

Most pasted secrets sit inside a config file or a log that you copied for another reason. A checker that runs where you type can flag them before you press send. Outbound Veil runs on your Mac, and the checking is done locally. It will miss some things, as every tool does, so read the list below before you rely on it.

On November 18, 2026, I ran the detection code from release 1.6.0 on made-up values only (plus AWS's documented example key ID). I did not use a real key. This tested the detector on text. I did not launch the app or type into a text field, so it says nothing about how the app reads a particular field. The compatibility page covers the fields I tested earlier.

I left out other providers, other key formats, and private keys, because I did not test them.

The video AWS access key in a config you paste into ChatGPT on Mac shows how to find a key in a config file with grep and hide it with sed before you paste. Outbound Veil has its own product page, and the wider checklist, including what ChatGPT and Claude say they keep, is in the client-notes guide.

Related guides