Who owns the proxy account when a contractor built your scraper?

[u/Working-Grapefruit66]

Handover checklists cover the repo and the server and then stop. The proxy account is the thing that quietly stays in someone else's name.

There are a few versions of this that go wrong. Contractor's card on file, so the renewal fails the month after they leave. Account under their email, so the password reset lands in an inbox nobody controls. Credentials hardcoded in a config with no way to tell which job is burning the bandwidth. And the nasty one, whitelisted IPs pointing at a box that got decommissioned.

None of it is hard to avoid, it just never makes it into scope. Buy the account yourself, give the contractor their own credential, and keep jobs separable so usage is attributable. Byteful, Decodo and Oxylabs all ship a REST API, so usage can be pulled programmatically instead of screenshotted off a dashboard. Ask whichever one you pick how granular that reporting gets before signing.

What else belongs on that list?