About this plugin
VPS Snaps backs up WordPress sites that cannot run a shell — the shared hosting where
exec() is disabled, there is no mysqldump, and nobody can add a cron job.
Backups are written to your own cloud storage (S3, Cloudflare R2, Backblaze B2,
DigitalOcean Spaces, Wasabi, any S3-compatible bucket, Google Drive, Box, Dropbox, or OneDrive). The plugin never
holds your storage credentials: it asks VPS Snaps for a short-lived, single-file upload
link each time it needs one, so a break-in on this site cannot reach the rest of your
bucket. A restore from Google Drive is given a Google token that expires within the hour
and reaches only the files VPS Snaps created, never the rest of your Drive. An upload to
Box is given a token that expires within the hour and can only upload into the backup’s own
folder; a restore from Box is given a download link for the one file, with no token at all.
An upload to Dropbox goes to a one-time upload link for that one file, or, for a backup over
150 MB, with a token that lasts at most four hours and reaches only the VPS Snaps app folder
in your Dropbox; a restore from Dropbox is given a download link for the one file, with no
token at all. An upload to OneDrive goes to an upload session VPS Snaps opens for that one
file, with no Microsoft token; a restore from OneDrive is given a download link for the one
file, with no token at all.
What this plugin sends to an external service
com and does not work
without one. There is a free tier that covers one site, one backup job and one storage
destination, which is everything this plugin needs; paid plans exist for people running
more than one site. Nothing in this plugin is switched on or off by which plan you are on.
You paste a site token from your dashboard into the plugin, and the plugin then talks to
com to:
- register this site — its URL, WordPress version, and plugin version;
- ask whether there is a backup or restore to run;
- report progress and results;
- request a temporary upload or download link for one file at a time;
- report a fatal error raised by this plugin’s own code, so a backup that has
silently stopped working can be found and fixed. This is sent only when the
plugin itself fatals, and carries the error message, the file name and line,
your PHP and WordPress versions, and nothing else. Fatal errors from other
plugins and from WordPress are not sent.
Your site’s content is uploaded to the storage bucket you configure in your VPS Snaps
account. com.
- Terms: https://vpssnaps.com/terms
- Privacy: https://vpssnaps.com/privacy
When that storage is Google Drive, the plugin uploads backups to, and downloads them for a
com, in the Google account you
connected in VPS Snaps. Nothing else is sent to Google.
- Google Terms of Service: https://policies.google.com/terms
- Google Privacy Policy: https://policies.google.com/privacy
When that storage is Box, the plugin uploads backups to Box’s upload API at
com, in the Box account you connected in VPS Snaps, and downloads
com ).
Nothing else is sent to Box.
- Box Terms of Service: https://www.box.com/legal/termsofservice
- Box Privacy Notice: https://www.box.com/legal/privacypolicy
When that storage is Dropbox, the plugin uploads backups to Dropbox’s content API at
com, into the VPS Snaps app folder of the Dropbox account you
connected in VPS Snaps, and downloads them for a restore from the temporary link Dropbox
com ). Nothing else is sent to Dropbox.
- Dropbox Terms of Service: https://www.dropbox.com/terms
- Dropbox Privacy Policy: https://www.dropbox.com/privacy
When that storage is OneDrive, the plugin uploads backups to the upload session Microsoft
com
address), into the VPS Snaps app folder of the OneDrive you connected in VPS Snaps, and
downloads them for a restore from the link OneDrive gives for that file, on the same
Microsoft addresses. Nothing else is sent to Microsoft.
- Microsoft Services Agreement: https://www.microsoft.com/servicesagreement
- Microsoft Privacy Statement: https://privacy.microsoft.com/privacystatement
Security
Every instruction this plugin receives is signed with your site token and verified before
anything runs. An instruction that does not verify is refused and reported, not executed.