Site Abode policy
Site Abode Backups are recovery points for routine WordPress changes or mistakes. Keep independent copies of critical content. Review the available recovery points and verify that they contain the information you need before relying on a restore.
Depending on your selected service, you can create database backups, file backups or both, manually or on the configured automatic schedule. Database and file schedules can differ. Setting automatic frequencies to zero leaves manual creation available while the backup service and sufficient capacity remain available. A schedule is not proof a backup succeeded; check the operation's result and the available recovery points.
Backup storage is a purchased capacity allowance, not automatic pay-as-you-go overage. New backups can be refused when there is insufficient room. At or above the purchased amount, creation remains blocked until usage is below it. Remove unneeded backups or increase storage when the account reports a capacity problem. A blocked backup does not itself delete your existing recovery points or cancel the paid backup service.
Backups contain the selected database/files, subject to supported exclusions. Excluded caches, directories or other content will not be restored from that backup. External services, domain registrations and content stored elsewhere are not included merely because your WordPress site uses them. Verify that the selected modes and exclusions cover what you need.
Configured retention removes expired managed backups of the same type after a new backup of that type is successfully published. Database and file histories therefore need not have identical dates. Failed creation does not make a new recovery point. Retention is not a guarantee that an old backup will remain available indefinitely or an exact deletion deadline after it ages.
Restoration replaces the selected current database and/or files with the chosen recovery point. Later changes in those selected sources can be lost. Confirm the correct App and backups, preserve newer content you need, and check the restored website afterward. A completed job alone does not establish that the backup contained every item you expected.
Selected backup deletion is permanent within the available product recovery flow. Removing the backup service does not by itself silently delete existing artifacts. When paid App service ends, associated backups are retained with its files and database for 90 days, then scheduled for permanent deletion. Explicit App deletion and Create New follow their separate warnings and dates. Whole-App physical cleanup removes associated backups; restarting service afterward does not recreate them. Other billing, security or support records may remain as described in the Privacy Policy.
Operational infrastructure backups are managed separately from the recovery points shown in your App and are not additional customer-selectable restore points. Contact Support if a recovery operation fails; do not assume an unverified or unavailable copy can be restored.