Who Actually Owns Your Website? It Is Not One Question

This is the part that surprises people. In most jurisdictions, copyright in a created work sits with whoever created it unless it has been assigned in writing. An employee building something for their employer is a different case. A freelancer or an agency is not — absent a written assignment, they typically keep the copyright and you get an implied licence to use what you paid for. That licence covers you fine right up until you want to move the site somewhere else, hand it to a different developer, or reuse the design. If your contract does not say the finished work transfers to you on final payment, it is worth asking why.

People talk about owning "the website" as though it is a single object. It is at least four. The domain is your address and is registered to somebody. The files and code are the site itself and are covered by copyright. The hosting account is where it lives and controls backups and restores. And the licences for stock photography, fonts, themes and plugins sit with whoever bought them. Those four can genuinely end up with three different parties, and businesses usually find out one at a time, in the middle of trying to do something else.

On the domain specifically, one distinction does most of the work. The registrant is the field in the domain record naming the legal holder. The account login is simply who can sign in and manage it. A developer can hold the login while your business is the registrant, which is fine, or the developer can be the registrant while giving you a login, which looks the same day to day and is not fine at all. Whoever registers a domain in their own name controls it — they can transfer it, let it lapse, or change where it points. If you check one thing after reading this, check that field.

A few patterns show up repeatedly. The bundled deal, where a low or free build comes attached to an ongoing monthly fee, and the site turns out to belong to the supplier for as long as that fee runs. The proprietary platform, where the site is genuinely not portable — there is nothing to hand over, because what you have only exists inside one company’s system. And the ownership condition clause, where the work becomes yours after a stated date or set of conditions, so leaving early triggers a fee. None of these are hidden, exactly. They are in the contract. They are just rarely read before signing and rarely explained.

Worth saying, because the internet on this subject runs hot. A supplier keeping reusable internal components, a shared agency plugin licence, or stock images licensed with limited rights is doing something completely normal — a builder does not hand over their tools with the house. The problem is not retention. The problem is when retention is the thing keeping you as a customer. Which is why the useful test is not "do you own every part of this" but "if I left tomorrow, what could I take with me, and what would stop working?" A supplier who is comfortable answering that plainly is telling you a lot.

Register the domain yourself, in your business name, using an email address you control, and add your developer as a user rather than the holder. Keep the hosting account in your own name for the same reason. Get the ownership position written down before work starts rather than discovered afterwards, and tie the final payment to receiving what you were promised — domain access, hosting credentials, the files, and a real administrator login rather than an editor-level one. For our part, every package transfers full ownership of the finished site, and the maintenance service is optional precisely because it should not be the thing keeping anyone here.