Paying for a website does not automatically make it yours. If the domain, hosting and accounts are registered to the developer, any dispute, or simply losing touch, can leave you without your site, email and ads. Here is what a website consists of from an ownership point of view, how to check who owns what, and what to collect at handover.
What a website is made of, ownership-wise
To a visitor, a website is one thing at one address. To the owner, it is a set of separate pieces, and each one has its own owner:
- domain: the site’s address, registered to a specific person or company;
- hosting or server: where the site actually runs, with its own account and billing;
- code and database: the site itself and everything stored in it, including leads and customer data;
- admin panel: where you change texts, prices and products;
- design source files: the layouts used to build new pages and ad creatives;
- services around the site: analytics, ad accounts, business email, paid subscriptions, payment providers.
If even one of these is in someone else’s name, you depend on that person more than you should. Sometimes that is an inconvenience. Sometimes it is a serious problem.
Who should register your domain name
Register the domain to yourself or your company, never to the developer. Of all the pieces, it matters most. The domain is your address online. It is on your business cards and in your ads, and your email and search rankings are tied to it. Losing it is much worse than losing the site itself: a site can be rebuilt, but an address customers have used for years can be very hard to get back.
The owner of a domain is whoever it is registered to, not whoever paid for it. A common pattern: the developer registers the domain in their own name “for convenience,” renews it, and adds it to the invoice. While the relationship is good, nothing goes wrong. If they disappear or a dispute starts, changing the owner without their cooperation is hard.
What to do:
- register the domain to yourself or your company, with your email and phone number;
- keep the registrar account login yourself, and give the developer separate access if they need it;
- turn on auto-renewal and watch the expiry date: an expired domain can be taken by someone else.
Hosting, code, data and ownership rights
The hosting account should also be opened in your name. The developer can set up everything inside it, but the account itself should use your email and your payment method. Then, if you change contractors, you just give access to the new person.
Code has two sides. Physically, you should have a full copy of the site, not just the ability to open it in a browser. Legally, the contract should state that rights to the code and design pass to you after payment. Our article on the website development contract covers this in detail.
Then there is data. Leads, orders and your customer base live on the server. If the server belongs to the developer, your customer data effectively sits with them. Make sure you can export it at any time and that regular backups are made.
Analytics, ads, email and subscriptions
These accounts often get created along the way and then forgotten.
Analytics and search tools. Your analytics and search console accounts with Google should be under your own account. You can give the developer access, but you stay the owner. Otherwise your whole traffic history leaves with the contractor.
Ad accounts. Same rule: the account is yours, the specialist works with granted access. Campaign history and settings have real value and are worth keeping.
Business email. Addresses like info@yourdomain depend on the domain. If the domain is not yours, the email is not really yours either.
Paid subscriptions and services. Ready-made components, fonts, stock photos, newsletter tools, live chat widgets. Find out which are in use, whose name they are in and what they cost. Otherwise something will switch off one day because the developer’s card stopped working.
Payments and messengers. The agreement with your bank or payment provider, your Telegram bot and your WhatsApp Business account should be registered to your company. Customer payments should land in your account.
If you have a mobile app
Apps add one more important piece: developer accounts in the App Store and Google Play. An app is published under the account owner’s name. Moving it to another account is possible, but it is a separate procedure that needs both sides to take part.
So it is best to open developer accounts for your own company from the start. That costs $99 per year with Apple and a one-time $25 with Google. You add the developer as a team member instead of handing them ownership. More on app costs in our article on how much a mobile app costs.
How to check who owns what
If your site is already live, you can check this in one evening:
- Find out which registrar holds the domain and log in. If you cannot, or the owner details show someone else’s name, fix that first.
- Log in to the hosting account. Check whose name it is in and which card pays for it.
- Log in to the admin panel with your own administrator account.
- Open analytics and ad accounts. Make sure you are the owner, not a guest.
- Ask the developer for a current copy of the code and the database.
- List every paid subscription with its renewal date.
If something is registered to the developer, that is not necessarily bad intent: often it was just faster. Calmly ask them to transfer it. An honest developer will do it without fuss. If you hear “no” or “we’ll hand over access after one more payment,” treat it as a serious red flag.
What website access to collect at handover
Before the final payment, put together a list of access with the developer. A table works best:
| What | Whose name | What to receive |
|---|---|---|
| Domain | Yours or your company’s | Registrar login |
| Hosting | Your account, your card | Account login |
| Code and database | Your rights per contract | Full copy |
| Admin panel | Your login | Admin rights |
| Design | Your rights per contract | Source files |
| Analytics and ads | Your account | Owner rights |
| Your domain | Mailbox management | |
| Subscriptions | Your account, your card | List and renewal dates |
| App Store and Google Play | Company account | Owner rights |
Keep passwords in a password manager, not in your phone’s notes. Once the developer has finished, change passwords or remove their access wherever they no longer need it.
Everything tied to your business should be in your name from day one. You can give the developer access, but you never need to give them ownership.
It is handy to add this list to your website acceptance checklist so it does not get lost among the other checks. At NOVO we hand over a list like this with every project: the client should be able to run the site without us.
In short
- A website is several pieces with separate owners: domain, hosting, code, admin panel, design and the services around it.
- Register the domain to yourself: losing the address is worse than losing the site.
- Keep analytics, ads, email and App Store and Google Play accounts under your company, and give the developer access.
- You can check who owns what in one evening: just log in to each account yourself.
- At handover, get the access list, a copy of the code and the design source files, then change the passwords.