Who Actually Owns Your Website - Code, Domain, and CRM Data After the Project Ends

Why most clients never ask this in time

When a business signs with a studio or agency to build a website or set up a GHL system, all the attention goes to design, timelines, and price. The question "what happens if we stop working together" almost always gets asked only once it's actually happening - and by then it's too late to negotiate. Actual ownership of the three core digital assets - code, domain, and customer data - isn't determined automatically by who paid. It's determined by what the contract says and how the accounts were set up from day one.

Website code - payment doesn't equal ownership

A common and mistaken assumption: "I paid for the work, so the code is mine." Per U.S. Copyright Office Circular 30 (Works Made for Hire), work created by an independent contractor - including software and website development - is not automatically classified as "work made for hire". For the rights to transfer to the client, either a signed written contract with an explicit IP assignment clause is required, or the work must fall into one of nine specific categories the law defines - and website development usually falls into none of them (source: copyright.gov).

In practice, that means: if your contract with the developer or studio doesn't explicitly transfer copyright in the code, the code may still legally belong to whoever wrote it - even if you paid for it in full. This isn't theoretical. It's exactly why a serious website contract always includes a clear IP assignment clause, not just a payment clause.

The domain - whoever is listed as Registrant is the owner

The domain is the easiest asset to check, and the easiest to overlook. Per ICANN policy, only the party listed as the Registered Name Holder can approve a transfer request to another provider, and only that party is entitled to receive the Auth-Code (TAC) required to complete the transfer (source: icann.org). If the domain was registered under the studio's own registrar account rather than an account in the business's name, the studio holds official ownership - even if the business paid for the purchase and every annual renewal.

• Check WHOIS or the registrar panel to see who is actually listed as the Registrant.
• Confirm you have management-level access (not just view access) to the registrar account, in the business's name.
• If the domain is registered under the studio's name, get the transfer to the business written into the contract as a condition - not promised as a future favor.

CRM data in GoHighLevel - Agency-Level vs. an independent Location

GoHighLevel has a structural distinction most clients aren't aware of. A studio or agency managing clients in the platform can run them as a Sub-Account nested entirely inside its own main Agency account, or give the business its own independent Location account that it controls directly. In the first case, all the data - leads, conversations, automations, customer history - sits on infrastructure the studio owns, and if the relationship ends, exporting that data depends on the studio's cooperation. In the second case, the account stays with the business even if it switches automation providers.

There's also a regulatory angle worth knowing, particularly relevant for businesses handling Israeli customer data: since August 2025, with Amendment 13 to Israel's Privacy Protection Law taking effect, the term "database owner" was replaced with "database controller" - the party that determines the purpose of processing the personal data. In most setups, the business itself, not the studio running its CRM, is the controller that carries legal responsibility toward the customers whose data is collected (source: pearlcohen.com). Carrying legal responsibility for data sitting in an account you don't technically control is an uncomfortable position - another reason to make sure the CRM account is registered directly in the business's name.

What to check before you sign

• Does the contract explicitly transfer copyright in the code to the business once payment is complete?
• Was the domain registered, and does it stay, under a registrar account in the business's name, with full management access?
• Is the CRM account (including GoHighLevel) an independent Location in the business's name, not a Sub-Account inside the studio's own account?
• Is there a clear, written process for a full data export if the relationship ends?

How we handle this at May I

The domain, hosting, and GHL account are opened in the client's name from day one - not transferred at the end of the project. The code itself is delivered along with full copyright ownership, as written into the contract. This isn't a "nice to have" clause - it's why a business working with us can switch providers at any point without losing access to the assets it built.