Security & trust - Your app, in your own cloud account
If a customer has sent you a security review to fill in, or you work in a field with rules about handling client records, here is what I build into every deployment. Everything goes into your own cloud account. I take only the access the work needs, and you can withdraw all of it the day we finish.
If you work in a regulated field — financial services, tax and accounting, legal, insurance — the controls below are not optional extras. Every deployment gets them by default, so you are not going back to add them after a customer has already asked.
Being ready to meet the rules is not only a technical question. The controls below are the part that needs an engineer: here is what stays your responsibility.
- You own everything. Your cloud account, your code, and your infrastructure all live in your account, in your name. Nothing ties you to me, so you can hand the whole thing to anyone, anytime.
- Only the access the work needs. I ask for the least access that lets me do the work, never the level that would let me change your billing or lock you out. The exact roles are listed up front in the setup guide, so there are no surprises.
- Revocable anytime. Remove my access in a couple of clicks whenever you want, and all of it the day the project ends. Your app carries on running either way.
- Passwords and keys stay out of the code. Every password and key lives in a locked store that only your app can open, never written into your code. There is no file with your passwords in it for anyone to copy.
- Secure by default. Your data is encrypted — scrambled so it cannot be read even if someone takes a copy — both where it sits and while it travels. Your staff sign in with a second step. The database is reachable only by your app, never from the public internet. All of it is set up at the start, not added after someone asks.
- Nothing lives only in my head. When your app goes live you receive a written handover covering every account, password, and security setting, in plain English, so you can hand it straight to a compliance officer, a customer, or the next engineer. Everything about how your app runs is written down and given to you.
See it for yourself
Two documents show what this looks like in practice: the access I ask for before we start, and the written record you receive when your app goes live.
Twenty minutes, and no pitch.
I'll tell you what I'd fix first in what you've built, and why. No pitch.