Who Owns Your Website When the Developer Disappears

Your developer stops replying. It happens more often than anyone in the industry likes to admit. What happens next depends entirely on whose accounts your website actually lives in — and most business owners have never checked.

The four things that make up a website, and who usually holds them

A website is not one thing. It is four, and each can belong to a different person.

The domain — the address people type in — lives in a registrar account. GoDaddy, Namecheap, Cloudflare, Google Domains. If your developer registered it for you, there is a reasonable chance it is in their personal account, not yours. You do not own what you cannot access.

Hosting — the server the files sit on — is a second account. Some studios bundle this into their monthly fee, which is fine as long as you understand what you are paying for and what you lose if you stop. Others use a hosting provider and set you up with your own login. That is cleaner.

The code — the actual files — should live somewhere you can reach: a Git repository, a ZIP file, a handover folder. If it exists only on a developer's machine or a private server, you have a dependency that costs nothing to fix now and a great deal to fix in a crisis.

The content and data — your text, photos, customer records, order history — should export to a standard format. If it can only be read by one proprietary system and that system goes away, the content goes with it.

What the common failure looks like

A bakery owner in any mid-sized city asks us to take over their existing website. We ask for the domain login. They ring the person who built it two years ago. That person has changed jobs. The domain is in an old email account nobody can access. The hosting is a shared plan that lapsed six months back, which is why the site has been throwing errors. The code was never handed over.

This is not an invented scenario. It is a rough composite of conversations that happen regularly.

The cost to fix it varies. Recovering a domain from an inaccessible registrar account takes days and sometimes a lawyer. Rebuilding a site from scratch because there is no code to inherit means starting from zero on budget and timeline. None of this is inevitable.

How to check your own situation in ten minutes

Open your phone and work through these four questions now, not later.

1. Can you log into the domain registrar yourself? Search your email for the registrar name — Namecheap, GoDaddy, Cloudflare are common. If you cannot find an account in your name, you need to find out whose name it is in before you need it urgently.

2. Do you have the hosting login? Not the login to edit the site — the login to the server or hosting provider itself. These are different things.

3. Do you have a copy of the code? Ask your developer for it if you do not. A reputable studio hands this over without hesitation. Hesitation is information.

4. Can you export your content? If the site is built on a CMS, try exporting. If nothing exports, ask how you would take your content somewhere else if you needed to. The answer tells you a great deal.

If you cannot answer yes to all four, you have a risk worth addressing before it becomes a cost.

What to ask before signing anything new

If you are about to commission a new site or app, put these questions to the studio before you sign a brief.

• Will the domain be registered in my name, on my card?
• Who holds the hosting account — me or you?
• Will I receive the complete codebase at handover?
• If I stop using your care plan, can I move the site elsewhere without your involvement?

A studio that builds things honestly will answer all four without flinching. Vagueness on any of them is worth probing.

At PrimeVibers, every project includes a written agreement that specifies what gets handed over and when. The code is yours. The domain is registered in your name. The hosting account is yours to hold or transfer. We run care plans because clients want them, not because we have built a dependency that makes leaving painful.

One more thing about data

If your site collects customer data — bookings, orders, enquiries — that data is subject to GDPR regardless of where the developer lives. You are the data controller. That means you are responsible for it, even if it is sitting in a database you have never logged into.

This is another reason to hold your own accounts: it is not just practical, it is a legal requirement you cannot outsource.

If you want to check what you currently own and what you do not, contact us and we will walk through it in the intro call — no obligation, just a clear picture of where you stand. Or if you are ready to start a new build with proper handover terms built in from day one, take a look at how we price projects.