Who owns your website when an agency builds it?

By Nikki Prokop, Co-founder and Creative Director, Noknok Studios

Many business owners pay for a website, use it happily for years, and then discover that they cannot easily move it, edit it or even log in to the accounts that run it. The invoice is paid, the website works as agreed — and yet, when the relationship with the provider changes, control can turn out to sit somewhere else entirely.

This is not usually the result of bad faith. It is the result of “you own the website” being treated as a single yes-or-no statement when, in practice, it covers several separate things: a domain, content, design, code, hosting, business accounts and various third-party licences.

A provider can say, quite truthfully, that you own your website while one or two of those pieces remain outside your control.

This article explains what website ownership actually involves, what is reasonable to expect and what to ask before you sign an agreement or pay a deposit.

Start with the domain

Before discussing design or code, start with the simplest and most consequential item: your domain name.

For an Australian .au domain, the business does not own the domain as conventional property. It holds a licence to use it and is recorded as the registrant.

Your business should be listed as the registrant, with contact details and recovery access controlled by the business. You should know which registrar or provider manages the domain, who can access the account and how to obtain the authorisation code needed to transfer it.

The domain may sit within an agency or reseller management system. That is not necessarily a problem, provided:

• Your business is correctly recorded as the registrant.
• Your business controls the registrant contact details.
• You can obtain the transfer authorisation code.
• The domain can be transferred without an unreasonable restriction or buyout.
• Renewal notices and important account messages reach your business.

Why does this matter so much? Because the domain is the address customers, search engines and email systems recognise as you. If you lose access to it, your website, email and other connected services may be affected regardless of who owns the design or code behind it.

The domain is also separate from the website build itself, even when both are included in one invoice or onboarding process. Confirm at the outset who the registrant is, where the domain is managed and how your business can regain or transfer control.

For .au domains, auDA explains how to update registrant information and transfer a domain to another provider.

“The website” is several different things

Once the domain is settled, the next step is recognising that “the website” is not one asset. It is a bundle of related but distinct components, each with its own ownership or control arrangement.

A practical ownership map includes:

• Copy — the words written for your pages, articles and product or service descriptions.
• Design — the original layout, interface, styling and visual direction created for the project.
• Code and configuration — the custom work, templates, components and technical setup used to turn the design into a functioning website.
• Database and content — the information stored within the website, including pages, images, form entries and customer records.
• Hosting — the server environment the website runs on and the access needed to manage or move it.
• Accounts — the domain registrar, analytics platform and any booking, payment, email or form systems connected to the site.
• Third-party licences — fonts, stock photography, plugins, software and other assets licensed from someone else.
• Transfer materials — the files, export, repository access or documentation another provider may need to take over.

[FIGURE — What “owning your website” actually includes]

A diagram showing a central “Website” block connected to nine components: Domain, Copy, Design, Code, Data, Accounts, Hosting, Third-party licences and Transfer files. Each component is labelled as Owned by the business, Transferred after payment, Licensed from a third party or Controlled through an account.

Some parts may transfer to you outright. Some remain licensed. Others are controlled through accounts rather than owned as assets.

Treating the entire website as one indivisible thing is where ownership questions usually go wrong.

Paying for a website does not answer every ownership question

It is a reasonable assumption: you paid for the website, so you own it.

In practice, payment alone does not necessarily answer who owns copyright in the original copy, design or code. The outcome depends on who created the work, the circumstances in which it was created and what the agreement says.

Copyright protection is automatic in Australia. The Australian Government’s Attorney-General’s Department explains that copyright can be assigned, licensed or sold. Under the Copyright Act 1968, an assignment of copyright generally needs to be documented in writing and signed by or on behalf of the copyright owner.

This is why the agreement matters more than the invoice.

A clear website agreement should state:

• What original project work transfers to the client.
• When the transfer takes effect, commonly after full payment.
• What pre-existing systems, tools or reusable components remain with the provider.
• Which third-party assets and software remain licensed.
• What the client is permitted to do with the finished work.
• What happens if the project ends before completion.
• What files or access will be provided if the client changes providers.

It should also account for work created by employees, contractors and specialist suppliers. A provider needs the appropriate rights before it can promise to transfer original work to a client.

If an agreement is silent or unclear, raise the issue directly before signing or making final payment. For commercially significant projects, have the relevant clauses reviewed by an Australian lawyer familiar with copyright and commercial contracts.

What may remain licensed rather than owned

Not everything used to build a website is intended to become yours outright — and that is normal, not a warning sign.

Stock photography, commercial fonts, premium plugins, third-party themes and open-source software are commonly licensed rather than sold. Your provider may hold the licence, purchase it for your business or use software under publicly available licence terms.

The same applies to external systems such as booking calendars, payment gateways, review widgets, mapping tools and form-handling services. These are separate products connected to the website, each with its own account, pricing and conditions.

None of this is inherently a problem. Most professionally built websites include licensed components, and open-source software is a normal part of modern web development.

The issue arises when a business does not know what the website depends on. A licence expires, a subscription ends or the relationship with the provider changes — and an important feature stops working or cannot be moved.

It is reasonable to ask your provider for a plain-language explanation of:

• Which important components are licensed.
• Who holds each licence.
• Whether the licence continues if you cancel hosting or care.
• Whether it can be transferred or replaced.
• What it would cost to maintain independently.
• What happens to the relevant feature if the licence expires.
• Whether your information can be exported from an external platform.

Where licence management is included in an ongoing service, the provider should also explain what it monitors and what would become your responsibility if that service ended.

What happens if you leave?

The real test of ownership is not what happens while everything is working smoothly. It is what happens if you decide to change providers, your provider closes or the relationship simply ends.

A website can legally belong to your business and still be difficult to move. Practical portability asks a more useful question:

Can another capable provider take over without rebuilding the website from the beginning?

Before that moment arrives, confirm the mechanics of leaving:

• Can the domain remain where it is or be transferred under your control?
• What files, export or database will be supplied?
• Is repository access relevant to this website, and will it be provided if needed?
• Can another suitable provider host the website?
• Which paid licences would need to be replaced?
• Will your data, form submissions and customer records be supplied in a usable format?
• Will your business retain access to analytics and other connected accounts?
• Is there a cancellation, transfer or buyout fee?
• Is there a minimum contract term?
• Does the website stop working when a hosting or subscription arrangement ends?

Not every provider structures its services in the same way, and not every subscription-based arrangement is a trap. Many are clear and reasonable commercial models.

The point is not to assume the worst. It is to understand the arrangement before you become dependent on it.

You can read how Noknok approaches this in our website ownership and guarantee terms.

Questions to ask before signing

Before signing an agreement or paying a deposit, put these ten questions to any provider — Noknok included:

1. Will our business be recorded as the domain registrant, with contact and recovery details we control?
2. What original project work transfers to us, and when does that transfer occur?
3. Which parts of the website remain licensed or owned by someone else?
4. Will our business control the important domain, analytics, form, payment and other business accounts?
5. Can the website be moved to another suitable provider?
6. What files, export, repository access or other transfer materials will be supplied?
7. Is there a cancellation, transfer or buyout fee?
8. What happens when hosting or ongoing care is cancelled?
9. How will we retrieve our website data, form entries and customer records?
10. Are any essential features tied to proprietary software or infrastructure, and what would happen if we left?

A provider confident in its arrangement should be able to answer all ten in plain terms.

The strongest answer is not necessarily, “You own absolutely everything.” A professional website may legitimately use pre-existing systems, open-source software and licensed third-party tools.

The strongest answer is one that identifies what you own, what you control, what remains licensed and what you receive if you leave.

How Noknok handles ownership

Here is our position, briefly and factually.

The client controls its domain. Ownership of the original project work covered by the agreement transfers to the client after full payment. Third-party assets, software and services remain subject to their respective licences.

There is no rental model. A client can move a paid website to another provider capable of hosting and supporting it. The relevant files, export, repository access or other transfer materials are supplied according to the type of website and the terms of the project agreement.

This reflects Noknok’s broader position:

Your domain. Your website. Your choice of provider.

The complete terms are set out in our terms.

---

If you are comparing providers or reviewing an agreement, ownership is worth settling before anything else.

See how website ownership works at Noknok

Get started

Related insights

• Website package or custom web design: which is right for your business?
• How can a website be built quickly without cutting corners?

---

This article provides general information for Australian businesses and is not legal advice. Website ownership and transfer terms should be reviewed against the circumstances of the individual project and, where appropriate, by an Australian commercial or intellectual-property lawyer.