Backup destination and admin transfers
Where WordPress backup plugins send copies of your site
Backups can include customer details, orders, and account records. Some setups save a copy on your host; others send it to connected storage. This table compares documented backup setups. Check backup destinations separately from cookie-banner settings.
Based on plugin documentation, not tests of your site. Not legal advice.
Scan a public pageThis scan does not inspect backup files or scheduled backup transfers.
How we group backup plugins
We compare the backup setups named below. Local export keeps the archive on your host for download. Remote-storage setups send that copy to storage you connect. Some features must be enabled in plugin settings. We have not tested consent timing, encryption strength, or how long backups are kept.
Backup plugins
No paid placement. Local export first, then cloud destinations, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin | Documented behavior | Visitor requests | Backup destination | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|---|
| All-in-One WP Migration (local export) Documented local-export setup builds an archive on the WordPress host for download or import. Optional remote storage extensions are out of scope for this local-export verdict. | Local export | The documented path builds a local archive. It does not describe a visitor-page script. | Archive stays on your host for download. | Not assessed | Not tested |
| Vendor docs |
| Duplicator (local export) Documented local-export setup builds a package (archive + installer) on the WordPress host for download or migration. Optional remote storage add-ons are out of scope for this local-export verdict. | Local export | The documented path builds a local archive. It does not describe a visitor-page script. | Archive stays on your host for download. | Not assessed | Not tested |
| Vendor docs |
| BlogVault BlogVault docs describe cloud backups managed from the WordPress connection. The linked listing does not name a verified receiving endpoint. | Cloud destination | The documented path does not describe a visitor-page script. Backup transfers start from the dashboard or a schedule. | Endpoint not verified | Not assessed | Not tested |
| Vendor docs |
| Jetpack Backup Jetpack Backup docs describe cloud backup storage for site copies. The linked guide does not name a verified receiving endpoint. | Cloud destination | The documented path does not describe a visitor-page script. Backup transfers start from the dashboard or a schedule. | Endpoint not verified | Not assessed | Not tested |
| Vendor docs |
| UpdraftPlus (remote storage enabled) This row covers UpdraftPlus with remote storage enabled. Documented storage options include UpdraftVault, Dropbox, Google Drive, and Amazon S3. Local-only schedules are not covered here. | Cloud destination | The documented path does not describe a visitor-page script. Backup transfers start from the dashboard or a schedule. | Storage options: UpdraftVault, Dropbox, Google Drive, Amazon S3 | Not assessed | Not tested |
| Vendor docs |
| WPvivid (remote storage enabled) This row covers WPvivid with remote storage enabled. Documented options include uploads to storage providers you select. Local-only schedules are not covered here. | Cloud destination | The documented path does not describe a visitor-page script. Backup transfers start from the dashboard or a schedule. | Storage options: Amazon S3, Google Drive, Dropbox, Microsoft OneDrive, FTP | Not assessed | Not tested |
| Vendor docs |
What this table does and does not prove
This table describes documented backup setups. It does not show what your live schedule sends. Local export is separate from shipping a full site copy to connected storage. We have not tested consent timing, encryption strength, or how long backups are kept.
Documentation snapshot: Sep 28, 2026. Sources are linked in each reviewed row.
Scan a public page/wp-backup-plugin-privacy