Back to blog
November 11, 2026•19 views

WordPress Backup and Data Ownership Playbook: Protecting Client Sites Before Disaster Strikes

WordPressbackup strategydata ownershipdisaster recoveryweb developmentagency
WordPress Backup and Data Ownership Playbook: Protecting Client Sites Before Disaster Strikes

I have restored more broken WordPress sites than I care to count. Some were hacked. Some were killed by a plugin update at 2am. A few were wiped because someone clicked "delete" on the wrong hosting account. In almost every case, the difference between a two-hour fix and a two-week nightmare came down to one boring question: did anyone actually have a working backup, and did they have the right to use it?

That second part is where most people get caught. A backup you cannot access, cannot export, or legally do not control is not a backup. It is a promise. This WordPress backup and data ownership playbook covers both halves of the problem: a real backup strategy you can run for client sites, and the data ownership questions that decide who holds the keys when things go wrong.

Why "we have backups" is usually a lie

I have heard "the host handles backups" from founders in Dhaka, Sydney, Austin and Toronto, and it is almost always half true. The host takes a snapshot. That snapshot lives on infrastructure you do not control, under a retention window you did not choose, and it can disappear the moment the account is suspended for non-payment or the client cancels.

A backup is only real if three things are true:

  • It exists somewhere outside the host you are trying to recover from.
  • You can restore it without asking a vendor for permission.
  • It is recent enough that restoring it does not destroy a week of orders, signups or content.

If any of those fail, you are gambling, not backing up.

Data ownership vs. data custody: get the distinction right

This is the part that lawyers care about and most developers skip. Ownership and custody are not the same thing.

Ownership means the client (or whoever paid for the site) holds the legal right to the data: the content, the customer records, the media, the database. Custody means someone else is physically holding a copy: your hosting provider, your backup plugin vendor, or you as the agency.

You can have custody without ownership. Your host holds a copy of the site and you still own it. That is normal. The problem starts when custody turns into lock-in, meaning you cannot get your own data back without paying, begging, or filing a support ticket that goes unanswered for four days.

A clean way to think about it: the client owns the data, you and the vendors hold copies under agreed terms. Every backup decision should protect that ownership, not quietly transfer it.

Where the plugin vendors actually store your backups

This trips up agencies constantly. When you install a backup plugin, the backups usually live in one of three places, and each has different ownership and access implications.

Storage location Who can access it Risk if you cancel Ownership note
Local (wp-content/backups) Anyone with server or FTP access Lost if the server dies You own it, but it dies with the site
Plugin vendor cloud (UpdraftPlus, BlogVault, Jetpack) You, plus the vendor per their terms Backups may be deleted after cancellation You own the data, vendor holds custody
Your own offsite (S3, Backblaze, Google Drive) Only you and whoever you grant access None, it stays yours Cleanest ownership story

The middle row is where most agencies sit, and it is fine as long as you read the retention and deletion terms. Some vendors purge backups a set number of days after a subscription lapses. If a client leaves and you forget to export, that history is gone. I have seen this happen.

Building a WordPress backup strategy that survives real disasters

A strategy is not a plugin. A strategy is a set of decisions about what you back up, how often, where it lives, and how you prove it works. Here is the model I run for client sites.

1. Decide what gets backed up

Back up the database and the uploads folder at minimum. That is where all the irreplaceable content lives. Plugin and theme files can be reinstalled from the repo, so backing them up is convenient but not critical. The database is the crown jewel: posts, pages, users, WooCommerce orders, form submissions, settings.

2. Set a frequency that matches how much data you can afford to lose

This is the recovery point objective, in plain language. A brochure site can survive a daily backup. A store taking orders every hour cannot. Match the schedule to the business, not to the default the plugin ships with.

Site type Database frequency Files frequency Retention
Brochure / blog Daily Weekly 30 days
Lead-gen site with forms Every 6 hours Daily 30 to 60 days
WooCommerce store Hourly Daily 60 to 90 days
Membership / SaaS-like Hourly or real-time Daily 90 days

3. Push backups offsite, always

Local backups are a convenience, not a backup. If the server is compromised or the disk fails, local copies die with it. Configure the plugin to send copies to storage you control: an S3 bucket, Backblaze B2, or a Google Drive the client owns. Offsite storage is the single most important WordPress backup decision you will make.

4. Test restores on a schedule

An untested backup is a hope. Once a quarter, restore a recent backup to a staging environment and confirm the site actually loads, the database imports cleanly, and logins work. I keep a simple checklist and run it before any major plugin or core update on a client site.

5. Automate the boring parts

Manual backups get skipped the week you are busiest, which is exactly the week something breaks. Use WP-CLI in a cron job or a scheduled task if you want a vendor-free option:

# Dump the database to a timestamped file
wp db export /var/backups/db-$(date +%F-%H%M).sql --path=/var/www/site

# Archive uploads
tar -czf /var/backups/uploads-$(date +%F-%H%M).tar.gz /var/www/site/wp-content/uploads

# Sync to offsite storage
aws s3 sync /var/backups s3://client-backups/site-name/ --delete

That is not glamorous, but it runs forever, it is cheap, and you own every byte of it. For most client sites I pair a plugin for convenience with an offsite bucket for safety. If you want the same cron-to-script discipline applied to other business ops, this scheduled automation with n8n and Claude Code is a good pattern to borrow.

The shared responsibility model nobody explains to clients

Here is the honest breakdown of who is responsible for what. Most disputes happen because nobody wrote this down.

Party Owns the data Responsible for backups Responsible for restore
Client (site owner) Yes Ultimately yes Ultimately yes
Agency / developer No, holds custody Usually yes, per contract Usually yes, per contract
Hosting provider No Sometimes (snapshots) Rarely, and only within window
Plugin vendor No Provides the tool No

Read that table out loud to a client once and half your future arguments disappear. The client owns the data. You and the host hold copies. Nobody else is on the hook for a restore unless the contract says so.

The contract checklist: assert ownership and deletion rights

If you run an agency, put these clauses in your agreements. If you are a founder hiring a developer, ask for them. This is the data ownership WordPress question that actually matters, and it is almost never in the boilerplate.

  • Ownership clause: the client owns all site content, data and databases at all times.
  • Access clause: the client receives full admin, database and hosting credentials on request and at project handover.
  • Backup clause: state who runs backups, how often, where they are stored, and the retention window.
  • Export clause: the client can request a full export (database plus uploads) at any time, in a standard format.
  • Deletion clause: on termination, backups are either handed over or deleted within a stated number of days, with confirmation.
  • Portability clause: the site can be migrated to another host or developer without penalty.

That last one matters more than people think. A site you cannot move is a site you do not own, no matter what the contract says. The same vetting instinct applies when you hire a WordPress developer in 2026: ask who controls the backups and credentials before you sign, not after.

WordPress disaster recovery: the first 30 minutes

When a client site goes down, panic is the enemy. I run the same sequence every time.

  1. Confirm the scope: is it the whole site, one page, or the database only?
  2. Take a fresh backup of the broken state before touching anything. You want evidence.
  3. Check recent changes: plugin updates, theme edits, DNS, hosting status.
  4. Restore to staging first, verify, then push to production.
  5. Document what happened and update the backup schedule if it was too slow.

Restoring to staging first has saved me from turning a small outage into a data-loss incident more than once. The broken state backup in step two is the detail most people skip, and it is the one you will wish you had.

Bangladesh considerations (and cross-border notes)

Most of my clients are in Bangladesh, the US, Australia, Canada and New Zealand, and the data residency question comes up more than you would expect. A few practical points, not legal advice:

  • Storing backups on AWS or Backblaze means data crosses borders. For most marketing sites that is fine. For sites handling personal data, check what your client's own policy and their customers expect.
  • If a client insists on local custody, an in-country server plus an encrypted offsite copy is a reasonable middle ground.
  • Encrypt backups at rest if they contain customer records. It is one checkbox in most tools and it removes a whole category of worry.

I am not going to pretend I can give you a definitive read on BTRC or ICT Act obligations for every case. Talk to a lawyer for anything sensitive. The engineering part, which is making sure the backup exists, is encrypted, and is exportable, is squarely in my lane. If your client needs a security baseline to demand from whoever touches the site, pair this with the NIST cybersecurity guide for solopreneurs.

FAQ

Who legally owns a WordPress site's data and backups?

The client who paid for the site owns the content and data. Hosting providers and backup plugin vendors hold custody, meaning they store copies under their terms, but they do not own it. Your contract should state this clearly and give the client export and deletion rights.

How often should I back up a client WordPress site?

Match it to how much data the client can afford to lose. A brochure site can run daily. A store taking orders should back up the database hourly. Whatever the schedule, push copies offsite and test a restore every quarter.

Can a hosting provider delete my backups if I stop paying?

Often yes. Many hosts purge snapshots a set number of days after an account is suspended or cancelled. That is why offsite copies in storage you control are non-negotiable for any site you care about.

What is the fastest way to back up WordPress without a plugin?

Use WP-CLI to export the database and tar the uploads folder, then sync to S3 or another offsite bucket on a cron schedule. It is free, scriptable, and you own every byte of the result.

What to do next

If you are a founder, go check your site right now. Confirm you have an offsite backup from the last 24 hours and that you can log into the storage account holding it. If you cannot answer both in under five minutes, you have a problem worth fixing this week.

If you are hiring a developer or agency, put the ownership and export clauses in the contract before work starts. It is the cheapest insurance you will ever buy. And if you are weighing a rebuild or a migration, read how to hire a WordPress developer in 2026 alongside this playbook so the handover terms are settled up front.

I build and maintain WordPress sites and automation for clients across Bangladesh, Australia, the US, Canada and New Zealand, and I set up backup and recovery systems as part of the handover, not as an afterthought. If you want a second pair of eyes on your current setup, or you are planning a migration and want the backups done right, get in touch through the site and tell me what you are running. I will tell you honestly whether it is safe.

Frequently asked questions

Who legally owns a WordPress site's data and backups?

The client who paid for the site owns the content and data. Hosting providers and backup plugin vendors only hold custody, meaning they store copies under their terms but do not own the data. Your contract should state this clearly and give the client export and deletion rights.

How often should I back up a client WordPress site?

Match the schedule to how much data the client can afford to lose. A brochure site can run daily backups. A store taking orders should back up the database hourly. Whatever the schedule, push copies offsite and test a restore every quarter.

Can a hosting provider delete my backups if I stop paying?

Often yes. Many hosts purge snapshots a set number of days after an account is suspended or cancelled. That is why offsite copies in storage you control are essential for any site you care about.

What is the fastest way to back up WordPress without a plugin?

Use WP-CLI to export the database and tar the uploads folder, then sync to S3 or another offsite bucket on a cron schedule. It is free, scriptable, and you own every byte of the result.

Share this post

Native Web Share is available on mobile, so that share sheet includes Instagram and any other app you have installed.

Let's Connect

Get In Touch

Let's build something premium together.

Contact info

Follow me
Chat on WhatsApp