Is it safe to paste passwords or API keys into ChatGPT?
Do not paste a live password or API key into ChatGPT or another cloud chat. The text goes to the provider's servers and is handled under its retention rules and by its sub-processors. If you already pasted a credential, rotate it with the service that issued it.
Where a cloud chat sends the secret
A cloud model receives the text you send so it can answer. If that text includes a password, the provider receives the password too. Your message is subject to that provider's retention rules and can be handled by other companies it uses, called sub-processors. Check which services handle the chat and how long each keeps it before deciding what to share.
This page does not describe OpenAI's current retention policy. The useful habit is to keep a working credential out of the message in the first place. You can usually explain a login error or an API request with a placeholder.
The Fireworks AI breach and Notion AI chats show why the provider chain matters. On 11 November 2026, BleepingComputer reported that Notion AI transcripts had been exposed through Fireworks AI, an infrastructure provider used by Notion. BleepingComputer, 11 November 2026. Source read 2026-11-20 by our reviewer. This was a specific incident involving Notion's provider, not a finding about every cloud chat.
If you already pasted a password or key
- Go to the service that issued the credential. Change the password, or revoke the old API key and create a replacement. Follow that service's instructions.
- Update the apps or jobs that used the old key. Keep the replacement out of the chat while you test the change.
- Review the account's available activity records for use you do not recognise. Ask your workspace administrator for help with a work credential.
Notion advised affected users to rotate any passwords, API keys or other credentials entered into affected chats, according to the 11 November BleepingComputer report, read 2026-11-20 by our reviewer. Deleting the chat does not change the credential at its issuer. Do not rely on deletion as a substitute for rotation.
Ask the question without the live credential
Redact the text before you paste it. Replace a password with [PASSWORD] and a key with [API_KEY]. Keep enough structure to show the problem, such as the header name, the error message and the order of the steps. Read error logs and screenshots for secrets too.
Use a secrets manager to store and retrieve working credentials. For a question about code, show where the program reads the secret rather than its value. Never paste a live key just to make an example look complete. Review the final text yourself before sending it.
What changes with a local model
Outlier's local model inference runs on your Mac. With a local model and web tools off, the text stays on the Mac. That removes the server copy of the local chat. It does not remove the need to protect the computer, its files and its backups.
The full network-use list covers model downloads, update checks, Pro licence checks and the price lookup when an upgrade window opens. These built-in uses carry none of your chat words. Optional web search sends a search query, agent web tools use the network when enabled, and a cloud model sends the chat to the provider you choose with your own API key. Connections you set up yourself have their own requests.
You can download Outlier and follow the Mac offline check while a local model answers. A local workflow is a choice about where the text is processed. Keep using placeholders when a task does not need the real secret.