Who owns your website and content? Export and lock-in questions to ask before you build
Short answer: You own your content, your domain name and your customer data only if the platform's terms and your own accounts state it. Lock-in means the work you paid for cannot leave with you. Some website builders, such as Wix, a hosted drag-and-drop site builder, say a site must run on their servers. Others let you take the code. Before you build, ask who holds your domain, whether you can export the pages and the data, what stops working after you export, and what happens when you cancel.
You are about to put your business website on a platform, or hand it to an agency, and you want to know now whether you can leave later with your work.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Ownership has four parts, and they are easy to mix up: the domain name (your address), the content (text, images, posts), the code and design (how the site looks and works), and the accounts (hosting, analytics, forms). A platform can give you one part and keep another. This page gives you the questions to ask, what the main builders say in their own help pages as of November 2026, the terms to read, and a backup plan.
It also covers Ploy, an AI marketing platform that builds and hosts websites, as one example. Ploy is not the point of the page: the same questions apply to every platform, and the answers below show where it sits next to the others. This is information, not legal advice. If a contract matters to you, have a lawyer read it.
This page may contain affiliate links from which Blur Studio earns commissions.
If you already have a site and want to check what you hold today, start with how to check who owns your website code. If you are already leaving a platform, see how to cancel, downgrade or export.
The four things you want to own
| What | Why it matters | Safe state |
|---|---|---|
| Domain name | It is your address. If someone else registered it, they can hold it hostage | Registered in your own account at a registrar, with you as the registrant |
| Content | Text, photos, blog posts, product data take time and money to make | You have copies in a format you can open, outside the platform |
| Code and design | This is what lets another developer or host rebuild the site | You can download it or hold it in your own code repository |
| Accounts and data | Hosting, analytics, search tools, forms and customer records | Your login is the owner login, and the agency is a guest |
The domain rule is the one people most often get wrong. ICANN, the body that sets domain rules, says in its registrant rights page that the registrant is the person or business responsible for the registration and use of the name. It also says you must give accurate contact details and respond to your registrar within 15 days when it asks. So the name on the registration matters. If your agency registered it under its name "to make setup easy", you are a customer, not the owner. Ask to have it moved into your own registrar account, and look up the registration record to confirm.
What the main platforms say about export (as of November 2026)
These statements come from each vendor's own page. Plans and policies change, so check the current page before you decide.
| Platform | What it is | Export, in the vendor's words or close to it |
|---|---|---|
| Webflow | A visual website builder with hosting | You can export your site and host it elsewhere on its paid Workspace plans. Dynamic content (CMS items) exports collection by collection and forms stop working. Exported code cannot be imported back |
| Framer | A visual website builder with hosting | Its help page says it does not offer HTML export for self-hosting, and that if you need to export source code it may not be the right fit |
| Wix | A hosted drag-and-drop site builder | Its help page says the site must be hosted and operated on Wix's servers. You can connect a domain you bought elsewhere |
| Squarespace | A hosted drag-and-drop site builder | It exports content to an XML file for use in WordPress. Some content does not export, and you cannot import an export into another Squarespace site |
| Lovable | An AI tool that writes web app code from chat prompts | Its docs say you are never locked in and can export your code, migrate your data and self-host |
| Ploy | An AI marketing platform that builds and hosts sites | Its docs say you can get the site's source with a command-line tool on every plan, including Free. See the next section |
I left WordPress, a very common website system, out of the table because the answer depends on where it runs. WordPress.org is open-source software you run yourself, so the files and database sit in your own hosting account. WordPress.com is a hosted service with its own rules, so check its current export page.
Read each answer as a trade, not a verdict. A hosted builder that takes care of servers, security and updates is doing work for you, and the price is that the site lives there. Code you can export is more portable, but someone must then host, update and fix it.
What an export usually leaves out
Even where export exists, it is rarely the whole site. Webflow's page itself says forms stop working and CMS items go out one collection at a time. Think of an export as a copy of the pages, not a working site. Before you trust one, list what still needs a home: forms, email notifications, search, member logins, shop and checkout, redirects, and tracking tags.
How Ploy answers the questions
As one fair example, here is what Ploy's own pages say, so you can compare them with the table above.
- Source code. Its docs say on any plan you can install its command-line tool and run a git clone command (git is a tool that copies and tracks code) to get the site's full source. You need the Member role or higher in the workspace. Keeping the code in your own GitHub repository uses Code Sync, a link to GitHub (a service that stores code), which its docs say is free on every plan when set up through the command line, while connecting it from the app needs a paid plan.
- Data ownership. Its terms of service say you keep all right, title and interest in the data and content you put in, and give Ploy a limited licence to run and improve the service. Ploy also says it does not use customer data to train its AI models on any plan, though its privacy policy separately says aggregated, de-identified data may be used to improve AI models. Read both documents.
- After you end the contract. The terms say it will make your customer data available for export for 30 days, then may delete it. The privacy policy says 60 days. Those two numbers do not match, so plan on the shorter one and export before you cancel. Whether the code route still works after cancellation is not stated, so do not count on it.
- Database export. Its database docs say tables can be exported as CSV (a plain spreadsheet file) up to 10,000 rows per view, and call CSV a format for moving data and not a backup. Version history is a 30-day rolling window.
- Fees. Its terms say fees are in US dollars and non-refundable except where stated, and subscriptions renew unless you give notice. Cancellation is done in account settings and takes effect at the end of the billing period.
- Domain. You use your own domain by pointing DNS records to it. The docs say the nameservers stay with you. DNS is the address book that tells browsers where your site lives.
What I would not assume: that exporting the code gives you a site that runs anywhere with no work. Its docs describe sites built with React, Tailwind and Astro (common web building tools), so a developer can host it, but forms, the database pages and its analytics may be tied to its platform, so test before you rely on it. If you are weighing it against others, see Ploy versus Webflow and whether Ploy is legit and safe. For how a move off a platform works, read Ploy site migration.
The questions to ask (copy and send)
Send these to the platform's sales or support team, or to your agency. Keep the written answers. A vague reply is an answer too.
Domain and accounts
- Who is the registrant on my domain name? Is it registered in my own account?
- Will you give me full owner access to hosting, analytics, search console, tag manager and form tools? Which of these sit under your logins?
- If I leave, how long do you take to hand over logins, and is there a fee?
Content and code
- Can I export all pages, blog posts, images and product data? In what format?
- Can I download the code and design files? Do they run without your platform?
- What stops working after an export: forms, search, shop, member logins, redirects, scripts?
- Is there any custom work (plugins, scripts, templates) that you own and I only license?
Data and privacy
- Who owns the customer data collected by forms, shop or chat? Can I export it?
- Do you use my content or data to train AI models? On which plans? Where is that written?
- Which companies process my data, and is there a data processing agreement I can sign?
Money and exit
- What is the contract term? When do I need to give notice to stop a renewal?
- Can the price change, and with how much notice?
- What happens to my site on the day I cancel? Is there a grace period for export?
- If I move, what happens to my domain, my rankings in search and my redirects?
Terms to read in the contract
You do not need to read every page. Search the terms of service for these words, and read the sentences around each one.
| Search for | What you want to see | Red flag |
|---|---|---|
| Ownership, intellectual property | You keep rights in your content. The platform has only a licence to run the service | The platform owns the design or the AI output, or you only get a licence |
| Termination, export | A clear window to export your data, and how | Data may be deleted right away, with no export route |
| Refund, renewal, notice | A fair notice period and clear renewal rules | Auto-renew with a long notice window and no refunds |
| Changes to the terms or prices | Advance notice and the right to leave | Changes at any time with no notice |
| Subprocessors, training | A named list and a no-training promise on your plan | Silence, or training allowed on your content |
| Governing law, arbitration | A place and process you can live with | A distant court or forced arbitration you did not expect |
For an agency contract, add: ownership passes to you on payment in full, tools and templates the agency owned before your job stay with the agency but you get a licence to use them with your site, and any AI-generated parts are covered by the same transfer. Ask a lawyer how this works in your country.
Worked example with made-up numbers
This is a made-up case to show the method. Maya runs a small bakery chain and pays an agency 4,000 dollars to build a site on a hosted platform with a 29 dollar monthly plan. She asks the 14 questions. The answers:
- The domain is in the agency's account. Fix: ask for a transfer to her own registrar account before launch.
- The platform exports pages but not the shop. Impact: she keeps a monthly CSV of products and orders.
- Terms give 30 days to export after cancelling. Impact: she sets a reminder to export the full data 60 days before the renewal.
- The agency owns its page templates but licenses them to her. Fix: she asks for that in writing and files it.
Scoring: each answer is green (fine), amber (fixable with a written promise or a habit) or red (a blocker). She has two ambers fixed by paperwork and two fixed by a habit. No reds, so she goes ahead. If one answer were red, for example "you cannot export your customer list", she would pick a different platform or negotiate before paying.
Backup plan: what to run every month
- Domain. Check the expiry date and that auto-renew is on and the card works. Look at the registrant name once a year.
- Content. Export pages, posts and product data. Save them in a folder you own, with the date in the folder name.
- Code. If your platform gives a code route, pull the latest copy. If you use Git, push it to a repository you own.
- Forms and customers. Export leads, orders and form entries to a spreadsheet. Do this weekly if you take orders.
- Settings. Save a list of your redirects, DNS records, tracking IDs and plugin or integration names.
- Test a restore once. Once a year, ask: could someone rebuild the site from this folder? If not, fix the gap.
Keep a second copy in a different place from the first, such as a cloud drive plus an external disk, so one lost account does not lose everything.
Who should worry most, and who can relax
- Worry more if your site earns money directly, you rely on a blog with years of posts, you have thousands of customer records on the platform, or an agency runs everything for you.
- Relax a little if you run a five-page brochure site with your own domain and you can rebuild the text in a weekend. Lock-in costs you less because there is less to move.
- Pick a platform with code export if you expect to hire developers later. Pick a hosted builder if you want no technical work, and accept that leaving means rebuilding.
How I'd approach this
I would treat lock-in as a price tag, not a ban. A hosted platform that saves you 10 hours a month may well be worth it, as long as you know the exit cost before you start and you keep your own copies. The mistake is not choosing a closed platform. It is finding out on the day you want to leave.
If your site is custom or your agency holds the keys, Blur Studio builds the custom version, with software you own, connections to your CRM and calendar, and ongoing care. See what that includes. For a wider view of avoiding lock-in, read how to avoid website vendor lock-in.
First-week plan
- Day 1. Look up your domain registration. Confirm you are the registrant and you hold the login.
- Day 2. Send the 14 questions to your platform or agency. Ask for written replies.
- Day 3. Search the terms for the six word groups in the table. Mark each green, amber or red.
- Day 4. Run your first full export of content, forms and customers. Save it in your own folder.
- Day 5. If you are choosing a platform, shortlist two. A code-export option such as Ploy can be one of them if you want AI help building and need a way to take the source, next to a hosted builder you already know.
- Day 6 and 7. Put the monthly backup tasks in your calendar. Decision rule: if any answer is red and cannot be fixed by a written promise, do not build on that platform.
I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.
Questions people ask
Do I own my website if I build it on a website builder?
You usually keep rights in the content you put in, but the platform decides what you can take out. Wix says the site must run on its servers. Webflow lets you export code on paid plans, but forms stop working and CMS content exports in pieces. Read the terms and the help page on export before you build.
Can I export my website from Wix or Squarespace?
Wix's help page says a site must be hosted and operated on Wix's servers, though you can connect a domain bought elsewhere. Squarespace exports content to an XML file for WordPress, and some content does not export. Plans change, so check the current help pages. See moving off Wix or Squarespace.
Who should own the domain name?
You should. Register it in your own account at a registrar, with your business as the registrant, and give your agency or builder delegate access if needed. ICANN says the registrant carries the responsibility for the registration and use of the name, and must keep contact details accurate.
What happens to my site if I cancel the platform?
It depends on the platform. Some keep your data for a short window and then delete it. For example, Ploy's terms give 30 days to export customer data and its privacy policy says 60 days, so plan for the shorter. Export before you cancel, not after, and confirm the window in writing.
Does Ploy let me export my site?
Its docs say you can get the site's full source with its command-line tool on every plan, including Free, if you have the Member role or higher. Whether that works after you cancel is not stated, and forms or database pages may need separate work. If you want to look at it, you can see Ploy's plans and test the export on a free site first.
Is a CSV export a real backup?
Not by itself. A CSV holds rows of data but not your design, settings, redirects or files. Ploy's own docs call CSV a format for interchange, not backup. Combine it with a code or page export, a settings list and a tested restore.
What should an agency contract say about ownership?
At least: who owns the finished site and when ownership passes, who holds the domain and hosting accounts, what happens to tools and templates the agency owned before, how AI-generated parts are covered, and how fast logins are handed over when you leave. Ask a lawyer to review it for your country.
How often should I back up my website?
Monthly for a brochure site, weekly for a site that takes orders or leads. Test a restore once a year. Keep two copies in different places, and keep them where you hold the login.
More in this topic: Websites: Google rules, privacy and ownership (6 guides) →
Sources
- Webflow pricing and FAQ, export and import answers (Webflow)
- Can I export my website to HTML and self-host it (Framer help)
- Exporting or embedding your Wix site elsewhere (Wix help)
- Exporting your site (Squarespace help)
- Deployment, hosting and ownership (Lovable docs)
- Registrants' benefits and responsibilities (ICANN)
- Ploy docs FAQ, source code and Git (Ploy)
- Ploy terms of service (Ploy)
- Ploy privacy policy (Ploy)
- PloyDB database docs (Ploy)