If you've built a custom GPT or chatbot, assume a determined user can read its instructions. Build accordingly.
A lot of people paste their secret sauce, pricing logic, internal rules, even API keys, straight into a custom AI's instructions and assume it's hidden. It often isn't. With the right nudging, chatbots can be coaxed into revealing their own setup. Here's what leaks, and how to build so it doesn't matter.
Two things you should never treat as private inside an AI's instructions: the instructions themselves (users can often extract them), and any secret embedded in them, keys, passwords, internal-only pricing. If losing it would hurt, it does not belong in the prompt.
Tone, role, what topics to help with, how to escalate, public-facing info.
API keys, passwords, internal margins, anything you'd be upset to see screenshotted.
Real secrets belong in the layer users can't see: environment variables, a backend, a proper connector, not the text you typed into the AI. If your tool needs a key to work, it should read it from a secure place at run time, never carry it in its own instructions.
If the public can chat with your AI, add a layer that refuses off-topic, sensitive or manipulative requests before they reach the model, and always hands medical, legal, financial or order-specific questions to a human. Design for the user who's trying to break it, not just the one behaving.
This is the layer I put into every client build.
Strip private data before it ever reaches an AI. Real, working, free to install.
The setup most people never switch on. Carousel plus a 22-minute walkthrough.
Watch me build 4 working AI systems on Claude, start to finish. Yours to keep.
Want a second pair of eyes on where AI actually fits your business? Let's map it out together.