Keys and secrets
1. No secret in the code
Search your project for secret, sk_, service_role and token. A key typed directly into a file ends up on GitHub with the rest of the code. GitHub's secret scanning looks through a repository's history for credentials like these and raises an alert when it finds one. If a real key was ever committed, assume it's public: create a new one in the service's dashboard and delete the old one.
2. Secret keys only on the server
Most services give you two kinds of key. On Supabase, the publishable key is made for code that runs in the browser, because it can only reach what your access rules allow. The secret key, and the older service_role key, skip those rules entirely and must stay on a server or in an edge function. If one appears in a file that ships to the browser, fix that before anything else.
Your data
3. Access rules on every table
If your app uses Supabase, turn on Row Level Security for every table that holds user data. Once it's on, the publishable key can't read or write anything until you add policies that say who may do what. Supabase's dashboard shows which tables have it switched off.
4. Try to see someone else's data
Create two test accounts. Sign in as the first, note the address of a page that shows personal data (an order, a profile), then sign in as the second and open that address. You should see nothing. This five-minute test catches the mistake that leaks the most data in small apps.
5. Know how to restore a backup
Check what backups your database plan includes and how far back they go. Then find the restore button before you need it. A backup you've never looked at is a hope, not a plan.
Money and email
6. Payments tested end to end in test mode
Stripe's sandboxes let you run real checkouts with test card numbers, without moving money. Go through a full purchase, a declined card and a refund. Only then switch the keys to live mode, and only on the server.
7. Emails go to the right people
Send yourself every email the app can send: sign-up, password reset, receipts, notifications. Check the sender, the links and that nothing is sent to a test address left in the code.
Going live, and coming back
8. Production settings set in your host
Your hosting provider has its own list of environment variables for production. Make sure every key the app needs is there, with live values where needed, and that none of them is a test value you forgot.
9. A way back in one minute
Find out how your host rolls back to the previous version, and try it once on a quiet day. When something breaks after a release, going back first and investigating second is almost always the right order.
10. Errors you can see, and a privacy notice
Set up some form of error tracking or at least know where your host's logs are, so you hear about problems before your users tell you. And if you collect personal data from people in the EU, even just an email address, publish a short privacy notice that says what you collect, why, and how to have it deleted.
Run it again after big changes
This list isn't a one-off. Go through points 1 to 4 again whenever your agent touches sign-in, payments or the database. It's quicker the second time, and it's the kind of change where agents most often do more than you asked.