Most people asking “do I own my website?” are really asking one question, and there are actually four. They have different answers, and the differences only matter at the exact moment they matter most, which is when you want to leave.
The four things, separately
Your domain. The name itself. This should be registered to you, in an account you control, always. If your agency holds the registration, they hold your business identity, your email routing, and your search ranking. There is no defensible reason for this arrangement. If a proposal has it, push back.
Your content. Text, photos, logo, brand assets, the things you supplied or paid to have written. Yours, and it should not be conditional on anything.
Your data. Customer records, form submissions, order history, anything your site collected. Yours, and you should be able to get it out in a standard format without an argument.
The code. The actual software. This is the one with a real answer that varies, and the one worth reading carefully.
Why code ownership legitimately varies
If you paid a fixed price for a build, you should normally receive full ownership of the custom work on final payment. That is the standard arrangement and you should expect it.
If you paid nothing up front and are on a monthly plan, the economics are different. Somebody carried the cost of building that site, and it was not you. Under our plans we own and maintain the code while you are subscribed, and that is precisely what makes a zero deposit possible.
That arrangement is only fair if two things are true: the boundary is stated plainly before you sign, and there is a way out with a published price. Ours is three months of your plan rate, available any time, including after you cancel.
What should worry you is not an agency retaining code. It is an agency that will not say clearly whether they do, or will not name a buyout number.
The clauses to actually read
- Termination. Is there a minimum term? What happens after it? A 12-month initial term is reasonable when there was no upfront cost. A perpetual lock with no month-to-month conversion is not.
- What you receive on exit. Vague language here is the warning sign. It should name domain, content, images, and data specifically, and give a timeframe.
- Hosting and DNS release. Some arrangements bundle hosting on proprietary infrastructure and then make DNS or database access difficult to retrieve. Ask directly what happens to DNS control on cancellation.
- Code buyout. If the agency keeps the code, is there a price, and is it written down? “We can discuss it” is not a price.
- Scope of included changes. Not ownership, but the same category of surprise. What is included, and what quietly becomes an invoice?
The test that cuts through it
Ask one question: “If I cancel next year, walk me through exactly what I keep, what I lose, and what it costs to take the code.”
A straight answer takes about thirty seconds. Hesitation, or a reply that stays abstract, tells you what the contract will say when you finally read it closely.
We put ours in writing on the plans page rather than leaving it for the agreement, because it is the objection most worth answering before somebody has to ask.