External Services – BackupRidge

BackupRidge is designed to keep your backup data under your control. Services below are only used when you enable related features.

LemonSqueezy

Data sent: License key, site domain, purchase/account metadata for validation and billing.
When: During license activation/validation and customer portal/payment flows.
Terms: https://www.lemonsqueezy.com/terms
Privacy: https://www.lemonsqueezy.com/privacy

Amazon S3

Data sent: Backup archive files and object metadata configured by the site owner.
When: When S3 storage is configured and backup uploads run.
Terms: https://aws.amazon.com/service-terms/
Privacy: https://aws.amazon.com/privacy/

Cloudflare R2

Data sent: Backup archive files and object metadata configured by the site owner.
When: When R2 storage is configured and backup uploads run.
Terms: https://www.cloudflare.com/website-terms/
Privacy: https://www.cloudflare.com/privacypolicy/

FTP

Data sent: Backup archive files uploaded via FTP using host, port, path, and credentials you supply.
When: When FTP remote storage is configured and backup uploads run.
Terms / Privacy: No single third-party Terms or Privacy URL applies — the destination is a server endpoint you choose (self-hosted or a provider you select).

SFTP

Data sent: Backup archive files uploaded over SSH file transfer using host, credentials or keys, and path you configure.
When: When SFTP remote storage is configured and backup uploads run.
Terms / Privacy: No single third-party Terms or Privacy URL applies — the destination is a server endpoint you choose (self-hosted or a provider you select).

HTTP Webhooks

Data sent: Backup status payloads (job id, status, size, duration, etc.) POSTed to a URL you configure; format can be generic JSON, Slack, or Discord.
When: When webhooks are enabled in Settings and a backup completes or fails (per your toggles).
Terms / Privacy: If you point webhooks at Slack or Discord, those services’ terms and privacy policies apply to the received data.

REST Cron Trigger

Data sent: Same-site REST requests with a secret key so backup segments can run without WP-Cron or loopback (no backup payload leaves your site).
When: When you call the cron-trigger URL from system cron or another local automation.
Terms / Privacy: No third party receives data — requests go only to your WordPress site.

Google Drive

Data sent: Backup archives in app-scoped storage plus OAuth token metadata.
When: When Pro Google Drive integration is connected and uploads run.
Terms: https://policies.google.com/terms
Privacy: https://policies.google.com/privacy

Dropbox

Data sent: Backup archives in app folder plus OAuth token metadata.
When: When Pro Dropbox integration is connected and uploads run.
Terms: https://www.dropbox.com/terms
Privacy: https://www.dropbox.com/privacy

OneDrive

Data sent: Backup archives in connected Microsoft storage plus OAuth token metadata.
When: When Pro OneDrive integration is connected and uploads run.
Terms: https://www.microsoft.com/servicesagreement
Privacy: https://privacy.microsoft.com/privacystatement

Backblaze B2

Data sent: Backup archive files and object metadata configured by the site owner.
When: When Pro Backblaze B2 integration is connected and uploads run.
Terms: https://www.backblaze.com/company/policies/terms-of-service
Privacy: https://www.backblaze.com/company/policies/privacy

WordPress.org

Data sent: Standard update-check request metadata for plugin update discovery.
When: During WordPress update checks.
Terms: https://wordpress.org/about/terms-of-service/
Privacy: https://wordpress.org/about/privacy/