Anyone can read your secret key
24 August 2026

One of the biggest risks when vibe coding your website is unknowingly handing strangers access to your services and your data. It doesn't take a hacker, just a secret key you accidentally published on your own site.
The day you add a proper feature, an AI chat, a booking calendar, email automations, you start collecting secret keys. Every one of those features runs on an outside service, and each service hands you a key that proves you are you.
If your AI coding tool isn't told to handle keys correctly, it can leave them sitting in the website code itself. Anyone can right-click your site, view the source, and lift them. And people run bots that scan websites for exposed keys around the clock, so an exposed key gets found.
Whoever finds it can use that service as you, running up your bill, sending emails from your business, and reading whatever data the service holds.
Two rules keep you safe.
One, tell your AI directly: never put a secret key in the website code, keys stay on the server. It knows how to do this properly. It just needs to know you care.
Two, if a key has ever been public, replace it. A fresh key takes about a minute to generate from any service you use.
I finish build sessions with one question: are any secret keys visible in this site's code? The AI checks every file and reports what it finds.
Ask your AI the same question today.