Backup & Data Recovery Policy
Effective 10 November 2026
This policy is part of our Terms of Service. It explains what we back up, what we do not, and what happens when data has to be recovered. Please read it carefully: you are responsible for keeping your own copies of your data, and our backups are a safety net, not a guarantee.
1. What we back up
| Service | Backed up by us? | Frequency | Kept for |
| Web hosting, Business Email, Developer hosting | Yes: website files, databases, email and account settings | Once a day (overnight) | 14 days |
| Cloud VPS | No, unless you have ordered the backup add-on for that server | As provided by the add-on | As provided by the add-on |
| Domain names, SSL certificates | Not applicable | – | – |
Backups are copied to separate storage from the hosting server. Backup times, frequency and retention may change for operational reasons; the current schedule is always published here.
2. What is not backed up
- Changes made after the last backup. Anything created, changed or received between two backups (for example the same day's orders or emails) cannot be recovered from our backups.
- Accounts that are suspended for more than 14 days, cancelled or terminated, once their last backup has passed the retention period.
- Cache, temporary and log files, and files that change while the backup is running (such as an active database being written to), which may be incomplete.
- Data on Cloud VPS servers without the backup add-on, and data stored outside our Services (for example in third-party email, CDN or website builders).
3. Backups are not guaranteed
- We take reasonable care, but a backup can fail, be incomplete or be unusable for reasons including hardware faults, software errors, files that were damaged or locked at the time, or accounts exceeding their storage limit.
- We do not check the content of your backups. A backup is an exact copy of your account at that moment. If your website was already infected with malware, defaced, misconfigured, or your data was already deleted or corrupted when the backup ran, the backup contains the same problem.
- Malware often stays hidden for weeks before it is noticed. If every backup within the 14-day retention period already contains the infection, there may be no clean backup to restore.
- If no usable backup exists for the date you need — because of the retention period, a failed backup, an infection or any other reason — we have no obligation to recover the data and are not liable for its loss.
4. Restoring data
- Request a restore by opening a support ticket, stating what to restore (a folder, file, database, mailbox or the whole account) and from which date.
- Restoring overwrites the current version unless you ask us to restore to a separate folder. Download anything you want to keep before asking for a full restore.
- Restores are carried out as soon as reasonably possible during support hours and are not covered by any response time guarantee. Large accounts can take several hours.
- Up to two restore requests per account each calendar month are free. Additional or very large restores, and restores from a specific point for investigation, may be charged; we will tell you the fee before we start.
- If an infected backup is restored at your request, the infection is restored too. Cleaning it is your responsibility; see the Malware & Security Policy.
5. Server failure and disasters
If a server fails, we restore affected accounts from the latest available backup as quickly as reasonably possible. Data created after that backup is lost. Restoring every affected account after a major incident can take time, and we restore in the order that best returns service to the most customers.
6. Your responsibilities
- Keep your own up-to-date backups, stored somewhere other than our servers. In cPanel, use Files › Backup to download a full account backup and copies of your databases and email.
- Take a backup before every major change: updating WordPress, plugins or themes, changing your shop, or moving your site.
- Keep at least one older copy as well as the latest one, so you can go back to a point before an infection or mistake.
- Check from time to time that your backups can actually be restored.
- For Cloud VPS, set up backups on the server yourself or order the backup add-on.
7. Liability
To the fullest extent permitted by law, we are not liable for any loss of or damage to data, or for any loss arising from it (including lost sales, business interruption or the cost of rebuilding a website), whether or not a backup exists. Where a loss is caused by our own failure, our liability is limited as set out in section 12 of the Terms of Service.