Who Owns a Website Built with AI?
Separate ownership of an AI-built website's domain, content, code and customer data from the platform rights and access needed to operate it.
There is no single ownership rule for every website built with AI. Your rights depend on the builder's terms, the agreements with anyone creating the site and the licences attached to its components. Separate the domain, business content, generated code, customer data and platform technology. Owning some of those parts does not automatically give you control over all of them.
For a Niwa-supported WordPress site, discuss the accounts, hosting arrangement and handover explicitly when you define the project. Niwa Business is USD 150 for a custom WordPress site or migration, hosting, maintenance and AI adaptation. The offer still needs a clear agreement about the assets and access your own business requires.
Put the domain under a business-controlled account
The domain is the address customers use, not the website files themselves. Establish who is the registrant, who controls the registrar account and which recovery contact receives important notices. Keep records and access in an arrangement your business can maintain if a contractor or employee leaves.
Ask how DNS changes are managed and who can authorise a move. A website can be hosted by one company while the domain is registered with another. Those relationships should be understandable before you need to change either service.
ICANN's domain-transfer guidance explains the transfer process for applicable domains. Check the rules for your registrar and domain rather than assuming that changing the website host automatically transfers the domain.
Separate your content from the builder's technology
Your business may supply the descriptions and images while the builder supplies the editor and the technology that serves the website. Rights to your content and permission to copy the complete platform are different questions.
Wix's export documentation makes this distinction: the proprietary technology behind a Wix site cannot simply be exported as a functioning Wix site on another host. That constraint can exist even when your original business material remains yours.
Ask what you receive on departure: page text, original media, structured records, source code or a complete working project. Confirm the format and whether someone can actually use it elsewhere. "You own your website" needs a concrete explanation before it can guide a business decision.
Read code ownership together with third-party licences
Lovable's ownership and deployment documentation states that users own their apps, code and content, subject to third-party rights. It also distinguishes the frontend, backend and editing service. This is a useful example of why ownership and operation must be assessed separately for the platform you choose.
Your project may include open-source software, fonts, images, plugins or other licensed material. A generated project does not erase those conditions. Ask the implementer to identify the important licences and any services that must remain active for the site to function.
WordPress is distributed under the GPL. That provides software freedoms under its licence; it does not mean that every image, commercial extension or third-party service in a WordPress website has the same terms. Do not confuse the platform licence with exclusive ownership of every component.
Copyright in generated material is a separate question
In the United States, the U.S. Copyright Office's January 2025 conclusions distinguish human expression from material generated by AI. Sufficient human creative contributions can qualify for protection; merely providing prompts does not establish copyright in generated output. Using AI assistance does not by itself prevent protection of a larger human-authored work.
That is U.S. guidance, not a universal rule for every country. The applicable law and the details of authorship matter. If exclusivity in a logo, illustration or other valuable creative asset is central to the project, obtain appropriate advice for the jurisdiction involved.
Keep records of the original material your business supplied and the human work performed. Also check that you have rights to source photographs and other inputs. A tool's ability to generate or import material is not proof that the material is free of third-party claims.
Include customer records and operational access
An owner needs to know where forms, orders, appointments and conversation records are stored. Determine which account can retrieve them, what can be exported and what happens when the service ends. Rights and responsibilities concerning personal data require their own review; a code-ownership statement does not resolve them.
Niwa's capabilities guide describes supported customer and owner operations, while its help documentation explains setup and connections. Use those materials to identify the components in your own installation, then agree the access and handover you require.
Keep recovery access under business control and restrict ordinary editing permissions to what people need. Having an administrator account is useful operational control, but it is not a substitute for the relevant contract or licence.
Request a written asset and access handover
Before accepting an AI-built site, ask for a clear record of the domain account, content sources, code or editor access, connected services and customer-record export arrangements. Name any component you cannot take with you.
If you already have WordPress, adding the standalone Niwa plugin can preserve your existing site arrangement while introducing supported assistance. Discuss your ownership and handover requirements before selecting a new site or migration. The useful answer is a documented set of rights and working access for your particular website.
