How I handle your access

Last updated 18 November 2026

Letting an outside engineer into your systems is a real decision. This is exactly how I work, so you know what you're agreeing to.

I never need your own password

For each job I ask for the narrowest access that works, and it's always something you can switch off yourself:

  • Linux servers: you add my public SSH key with an expiry date written into it. After that date the server refuses it on its own.
  • GitHub: you invite my account to one repository with a limited role. You can remove me in one click.
  • AWS: you create a role my account can use, locked to a unique external ID and an end date. No access keys change hands.
  • Google Cloud: one role on one project, with an expiry condition.
  • Kubernetes: a separate service account with a token that expires by itself. Your kubeconfig stays with you.
  • Machines behind a firewall: Tailscale sharing of a single machine. Nothing else on your network is visible to me.
  • Desktops: AnyDesk or RustDesk while you watch. Closing it ends the session.

Each of these comes with step-by-step instructions inside your request, and the matching steps to take it back.

When a secret is unavoidable

Some things are just a password, like a router login or a database connection string. Those go in the Secure Vault on your request, never in chat or email:

  • encrypted with AES-256-GCM before it is stored;
  • only I can open it, and you see every time it was opened;
  • deleted for good when the request is resolved, or earlier on the date you pick, or whenever you delete it.

If you paste something that looks like a password or key into a normal message, the portal stops you and points you to the vault.

When the job is done

  • You get written hand-over notes: what was wrong, what I changed, and how to undo it.
  • You get a checklist of every access you gave me, with the exact steps to remove it.
  • Your Access page shows what is still active and when it ends.

My side

  • My accounts use two-factor authentication, and my keys are on encrypted disks.
  • I don't copy your data off your systems unless the job needs it and you agree. If I do, I delete it at the end.
  • I don't subcontract. The person you talk to is the person doing the work.
  • Happy to sign your NDA before we start. Send it with your request.

Questions about any of this? Ask me before you share anything.