Journal · The AI Architect · 2026-08-14
Never paste passwords or account numbers into a prompt. If a task seems to need one, that's a signal to pause.
Never paste passwords or account numbers into a prompt. If a task seems to need one, that’s a signal to pause.
The tension isn’t really about passwords. It’s about convenience versus consequence, and how good AI tools are at making the risky option feel like the reasonable one. When a chatbot says “just paste your account details here and I’ll draft the dispute letter for you,” it sounds efficient, even smart. The pause the book asks for feels like friction for its own sake. But that friction is doing real work, and it’s worth understanding why before you decide when to honor it and when you might not.
The prompt box is not a locked room
People treat a chat window like a private notebook, but it behaves more like a postcard. What you type can be logged, reviewed by the company that runs the model, used to improve future versions, or exposed in a data breach you’ll never hear about. Even when a service promises not to retain your data, you’re trusting a policy, not a wall. Passwords and account numbers are different from ordinary sensitive facts because they’re keys, not just information. If someone gets your birthday, they know your birthday. If someone gets your bank login, they can act as you.
Try this: the next time you’re about to paste something into a prompt, ask “would I be comfortable if this text were printed on a postcard and mailed?” If the answer is no, that’s your signal, not the content of the task itself.
Separate the task from the credential
Most of the time, the actual work you need help with doesn’t require the secret at all. You want help writing an email to your bank, not help logging into your bank. You want a script that organizes files, not one that contains your Wi-Fi password baked into the code. The habit worth building is splitting the job in two: the part that’s just words, reasoning, or drafting, which AI can help with freely, and the part that requires an actual credential, which you handle yourself, outside the chat.
Try this: when a task feels like it needs a password, rewrite your request using a placeholder. Instead of “here’s my password, write a script to log into my account and download my statements,” try “write a script that logs into an account using a variable called PASSWORD that I will fill in myself, and never print or log that variable.” Good coding assistants can absolutely work this way, and it’s a better habit even outside of AI use, since it keeps secrets out of chat histories, screenshots, and shared documents.
Build a personal rule, not just a reflex
A one-time hesitation is useful, but it fades. What holds up over time is a rule you’ve said out loud to yourself, something specific enough to catch you in the moment. “Never paste passwords” is a fine start, but consider widening it slightly: never paste anything that would let someone impersonate you or drain an account, including security question answers, one-time codes, or full ID numbers. Say the rule in your own words, write it somewhere you’ll see it, maybe as a sticky note near your keyboard or a note in your phone, and treat any prompt that tests that line as a reason to stop and think, not a reason to comply faster.
Try this: write your own one-sentence rule right now, in language that feels natural to you, and read it back. If it’s vague, tighten it until you could explain to a twelve-year-old exactly what it means and why it matters.
The deeper habit here isn’t caution for its own sake. It’s noticing when a tool is asking for more trust than the task actually requires, and treating that gap as information rather than an inconvenience. This one line about passwords is really a small example of a much bigger practice: learning to read the shape of a request before you fill it. The book spends more time on that broader skill, including how to think about data you didn’t even realize was sensitive, and how to build habits that hold up when you’re tired, rushed, or just trying to get something done. But the instinct to pause, the one this essay started with, is where all of that begins.
Go deeper. The full method is in The AI Architect. New here? Start with the free companion pack, or explore the series.