Credentials Without Chaos: How to Use Claude Safely With Sensitive Data
Claude needs access to your tools, not to your passwords. Here's how I set it up: Cloudflare Workers in the cloud, with a password vault as the on-computer fallback.
The more work I hand to Claude, the more access it needs: email, CMS, invoicing, ad platforms. And that's where most setups quietly go wrong. API keys end up in a Google Drive doc "for Claude to reference", in a note, in a text file on the desktop, or pasted straight into a chat.
The problem: credentials flying around everywhere
Anything Claude can read, it can also repeat. A key sitting in a document a connector can access becomes part of every conversation that touches that document. Add shared folders, sync across devices and saved chat histories, and one key lives in five places, none of them designed to protect secrets.
The principle: use, never see
The rule I now work by: Claude should be able to use a credential without ever seeing it. Secrets are fetched at the moment they're needed and never stored in prompts, docs or memory.
The cloud setup: Cloudflare Workers
My main setup runs entirely in the cloud:
- Credentials are stored as encrypted secrets in a Cloudflare Worker.
- Claude calls the Worker, not the underlying API.
- The Worker injects the key and makes the call. Claude only sees the result.
The big win: it works from Claude Chat, Cowork and scheduled routines, including on an iPad or phone. I can get things done on the go without a single credential sitting on a device.
The fallback: a vault on your computer
Not every tool fits behind a Worker. For those, a local password vault is the next best thing:
- 1Password with its CLI and a service account, so Claude Code or Cowork can fetch one secret at runtime without access to the whole vault.
- Apple Keychain on a Mac, keeping credentials in your iCloud account and pulling them only when needed.
One caveat: never let Claude print the value. The moment a key is echoed into the chat, it's back in the history.
Do's and don'ts
- Rotate any key that has ever appeared in a chat.
- One key per tool, scoped to the minimum permissions.
- Search your connected drives for files containing "password" or "API key" and clean them up.
- No credentials in notes, text files or spreadsheets. Ever.
Wrapping up
Getting real productivity out of AI and keeping your credentials safe aren't in conflict. It just takes one deliberate setup. Start with a quick audit of where your keys live today; you'll probably be surprised.