External services: Backup & Restore
This is the full reference for every external service the CloudScale Backup & Restore WordPress plugin can contact: each endpoint, the data sent and when it is sent. The plugin readme on WordPress.org carries the summary of each one.
This plugin optionally connects to third-party services when those features are configured by the site administrator. No data is sent to any external service unless the administrator has explicitly enabled the relevant integration.
1. Telegram Bot API (optional notifications)
Service: Telegram Messenger, https://telegram.org/
When a Telegram bot token and chat ID are entered, the plugin sends backup, restore, rollback and error alerts to that chat. A message holds the site name, event status and, for errors, the PHP error, file and line. No visitor data, post content or backup data is sent.
API endpoint contacted: the sendMessage method on api.telegram.org, addressed with the administrator's own bot token.
Terms of Service: https://telegram.org/tos
Privacy Policy: https://telegram.org/privacy
2. Amazon S3 (optional cloud backup)
Service: Amazon Web Services, https://aws.amazon.com/
When S3 settings are configured, the plugin uploads backup zips to the administrator's own S3 bucket via the S3 REST API. Only the backup zip is sent. The credentials are stored on the site and sent only to the AWS S3 endpoint.
API endpoint contacted: the Amazon S3 host for the bucket's own AWS region, for example s3.eu-west-1.amazonaws.com.
Terms of Service: https://aws.amazon.com/service-terms/
Privacy Policy: https://aws.amazon.com/privacy/
3. S3-compatible storage (optional cloud backup)
Services: Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, Google
Cloud Storage, Hetzner Object Storage, or another S3-compatible service the administrator names. When one is chosen on the S3 card, backup zips go to the administrator's own bucket there through the S3 API, as for Amazon S3. Access keys go only to the endpoint the administrator entered.
API endpoint contacted: the endpoint shown in the S3 card.
Cloudflare: Terms https://www.cloudflare.com/terms/ Privacy https://www.cloudflare.com/privacypolicy/
Backblaze: Terms https://www.backblaze.com/company/policy/terms-of-service Privacy https://www.backblaze.com/company/policy/privacy
Wasabi: Terms https://wasabi.com/legal/customer-agreement Privacy https://wasabi.com/legal/privacy-policy
DigitalOcean: Terms https://www.digitalocean.com/legal/terms-of-service-agreement Privacy https://www.digitalocean.com/legal/privacy-policy
Google Cloud: Terms https://cloud.google.com/terms Privacy https://policies.google.com/privacy
Hetzner: Terms https://www.hetzner.com/legal/terms-and-conditions/ Privacy https://www.hetzner.com/legal/privacy-policy/
4. Your own SFTP, FTP or WebDAV server (optional cloud backup)
When the administrator enters a server on the SFTP / FTP or WebDAV card, backup zips are uploaded to it, and listed, downloaded and deleted there. The sign-in details go only to that server. No other party is contacted; the server owner's terms apply.
5. Google Drive (optional cloud backup)
Service: Google, https://workspace.google.com/products/drive/
When Google Drive settings are configured, the plugin transfers backup zip files to the administrator's own Google Drive account using the Google Drive v3 REST API and OAuth 2.0. No data is sent unless the administrator has completed the OAuth authorisation flow (entered a Client ID and Client Secret from Google Cloud Console and clicked "Connect to Google Drive"). Only the backup zip file is uploaded. OAuth tokens (access token and refresh token) are stored in the WordPress options table.
API endpoints contacted: www.googleapis.com (Drive v3) and oauth2.googleapis.com (OAuth 2.0 tokens).
Terms of Service: https://policies.google.com/terms
Privacy Policy: https://policies.google.com/privacy
6. Dropbox (optional cloud backup)
Service: Dropbox, https://www.dropbox.com/
When Dropbox settings are configured, the plugin transfers backup zip files to the administrator's own Dropbox account using the Dropbox v2 REST API and OAuth 2.0. No data is sent unless the administrator has completed the OAuth authorisation flow (entered an App Key and App Secret from the Dropbox App Console and clicked "Connect to Dropbox"). Only the backup zip file is uploaded. OAuth tokens are stored in the WordPress options table.
API endpoints contacted: api.dropboxapi.com and content.dropboxapi.com (Dropbox v2 REST API).
Terms of Service: https://www.dropbox.com/terms
Privacy Policy: https://www.dropbox.com/privacy
7. Microsoft OneDrive (optional cloud backup)
Service: Microsoft, https://learn.microsoft.com/en-us/onedrive/
When OneDrive settings are configured, the plugin transfers backup zip files to the administrator's own Microsoft OneDrive account using the Microsoft Graph REST API and OAuth 2.0. No data is sent unless the administrator has completed the OAuth authorisation flow (entered an Azure App Client ID and Client Secret and clicked "Connect to OneDrive"). Only the backup zip file is uploaded. OAuth tokens are stored in the WordPress options table.
API endpoint contacted: https://graph.microsoft.com/ and https://login.microsoftonline.com/
Terms of Service: https://www.microsoft.com/en-us/servicesagreement/
Privacy Policy: https://www.microsoft.com/en-us/privacy/privacystatement
8. CloudScale Managed Cloud Backup (optional, paid service)
Service: CloudScale Consulting, https://cloudscale.consulting/
When subscribed, the plugin asks the CloudScale broker for a short-lived, prefix-scoped Amazon S3 token, then uploads backup zips straight to CloudScale's S3 storage; backup bytes never pass through the broker. It times ten HEAD requests per storage region and sends the averages, to pick the nearest region. Nothing is sent until a licence key is entered. Storage is encrypted at rest. For extra security, Encrypt backups adds AES-256 encryption with the site owner's own password before upload. Leave us a message sends the typed email and message, hostname and licence key on Send. Clicking the PayPal button sends the product name, hostname and the optional email typed above it to /checkout-start, so a failed checkout can be followed up.
API endpoints contacted (broker): https://api.cloudscale.consulting/backup/token, https://api.cloudscale.consulting/backup/list, https://api.cloudscale.consulting/status, https://api.cloudscale.consulting/checkout, https://api.cloudscale.consulting/checkout-start, https://api.cloudscale.consulting/recover, https://api.cloudscale.consulting/recover/verify, https://api.cloudscale.consulting/refund-request and https://api.cloudscale.consulting/contact.
Storage and timing requests go to CloudScale's Amazon S3 storage in its ten regions: Cape Town, Ireland, Frankfurt, N. Virginia, Oregon, São Paulo, Mumbai, Singapore, Tokyo and Sydney.
Terms of Service: https://cloudscale.consulting/terms/
Privacy Policy: https://cloudscale.consulting/privacy/
9. PayPal (optional, payment for Managed Cloud Backup)
Service: PayPal, https://www.paypal.com/us/home
Subscription payments for the optional CloudScale Managed Cloud Backup service are processed by PayPal on its own hosted checkout; card details never reach this plugin or the site. When the administrator starts a subscription, the subscriber's email and the order amount ($5.00 USD) are sent from the WordPress server to the PayPal REST API (api-m.paypal.com) to create a checkout session. Nothing is sent unless the administrator chooses to subscribe.
API endpoint contacted: api-m.paypal.com (live) or api-m.sandbox.paypal.com (sandbox testing), the PayPal REST API: https://developer.paypal.com/api/rest
Browser-loaded script: PayPal's JavaScript SDK from www.paypal.com/sdk/js, loaded into the plugin's admin screen only after an administrator opens the subscription checkout. PayPal requires the SDK be served from its own origin so a compromised build can be revoked, so it cannot be bundled with the plugin.
Terms of Service: https://www.paypal.com/us/legalhub/paypal/useragreement-full
Privacy Policy: https://www.paypal.com/us/legalhub/paypal/privacy-full
10. AWS EC2 / AMI snapshots (optional, AMI snapshot feature only)
Service: Amazon Web Services, https://aws.amazon.com/
When the AMI snapshot feature is used, the plugin reads instance metadata (instance ID and region) from the local EC2 Instance Metadata Service at the link-local address 169.254.169.254. This address is only reachable from within an EC2 instance and no data leaves the server at this step. AMI creation, status poll, deregister, and snapshot delete requests are then issued directly to the AWS EC2 REST API (no external tools required). The same AWS credentials (access key ID and secret key) used for S3 are used; if none are configured the plugin attempts to use the EC2 instance role via IMDS.
API endpoint contacted: the Amazon EC2 host for the instance's own AWS region, for example ec2.eu-west-1.amazonaws.com.
Terms of Service: https://aws.amazon.com/service-terms/
Privacy Policy: https://aws.amazon.com/privacy/
11. Automatic Crash Recovery: health check probe (optional)
When Automatic Crash Recovery is enabled, the plugin periodically sends an HTTP request to the administrator-configured health check URL to verify the site is responding. The URL defaults to the site's own home URL. No personal data is transmitted. The request is a plain GET with no authentication payload. The same probe is made when the administrator clicks "Test Health Check" in the plugin settings. A system-cron watchdog script, if installed, probes this URL too.
No Terms of Service or Privacy Policy apply (the request goes to a URL you own).
12. Gmail SMTP port check (only when sending a test email)
Service: Google, https://workspace.google.com/gmail/
When the administrator clicks Send Test in the Notifications card, the plugin opens a TCP connection to smtp.gmail.com on ports 587, 465 and 25 and closes it at once, to tell whether this server can reach an outside mail server at all. No email, login or data of any kind is sent; only the connection is attempted. Nothing happens until the button is clicked.
Terms of Service: https://policies.google.com/terms
Privacy Policy: https://policies.google.com/privacy
Anything here that is unclear, or that you want in writing differently, ask.
Get in touch