Backup Policy
This page explains server-managed daily copies and customer-managed website backups. It states storage, copy limits, coverage, recovery and exclusions. Server-level copies are best-effort.
Last updated: October 2026
1. How to read this policy
Keeping a working independent copy of your website, databases and email remains your responsibility. Server-level copies are best-effort and must not be your only backup.
Marketing cards that say Daily backups mean the frequency and retention for that plan below — not an offsite vault or a recovery-time contract. The Terms of Service remain the legal baseline.
- Frequency — how often a copy is taken
- Retention / restore points — how many copies remain listed
- Coverage — files, databases, email and DNS
- Storage location — where the copy lives
- Restoration method and fees
- Exclusions
2. Customer-managed website copies in your own disk space
Customer-managed website backups are available in Dashboard → Hosting → Backups. Select an individual website, then website files, its database, or both. Files and database together count as one saved copy.
Copies, database export working files and temporary archives use the customer’s existing hosting disk allowance. They are stored inside the hosting account, outside website document roots. Creation is refused when space or the plan’s per-website copy allowance is exhausted; failed creation does not replace a completed copy.
The live hosting package controls the copy count. Personal currently allows 1 saved copy per website, Business 3 and Professional 5. Other packages display their own allowance in the dashboard. Manual copies stay while the hosting account remains active until the customer deletes them; they do not rotate automatically. The manual archive folder is excluded from server-level backup copies to avoid storing backups inside further backups.
Customers can restore files, the backed-up database, or both, and delete copies to free space. Restore and deletion require explicit confirmation. File restore overwrites backed-up paths and leaves files added later; database restore can remove later database changes and affects any other website using that same database. Email, DNS, symlinks and special files are excluded from these per-website copies.
Download archives through the control panel file manager or SFTP using the location shown in the dashboard. Local copies remain on the same hosting server and are not offsite disaster-recovery copies. No additional backup-storage allocation or recovery-time SLA is included.
6. WordPress hosting (WP Starter, WP Business, WP Pro)
Frequency: Daily automated copy
Retention: Daily copies listed in the dashboard
Restore points: The restore points still listed in the dashboard
Files: Website files on the hosting account
Databases: Databases on the hosting account
Email: Mailboxes on the hosting account when email is hosted with us
DNS: DNS zone data when DNS is hosted with us
Storage location: On-site on the hosting server. This is not a separate customer-controlled offsite vault.
Restoration method: Restore assistance from copies still listed in the dashboard.
Restoration fees: Restores from copies still listed are included. If no copy remains, recovery is scoped with support.
Best-effort restore. There is no contractual recovery-time SLA. Keep an independent copy of anything you cannot afford to lose.
- Exclusion — Guaranteed older archives beyond listed copies
- Exclusion — Plugin, theme or WooCommerce version history
- Exclusion — Customer-controlled offsite archives
- Exclusion — A contractual recovery-time SLA
7. Reseller hosting
Frequency: Daily automated copy on the reseller platform
Retention: Copies listed for the reseller account
Restore points: Listed restore points for that account
Files: Website files on the hosting account
Databases: Databases on the hosting account
Email: Mailboxes on the hosting account when email is hosted with us
DNS: DNS zone data when DNS is hosted with us
Storage location: On-site on the hosting server. This is not a separate customer-controlled offsite vault.
Restoration method: Restore assistance from copies still listed, via support.
Restoration fees: Restores from listed copies are included. Extra recovery work is scoped with support.
Best-effort restore. There is no contractual recovery-time SLA. Keep an independent copy of anything you cannot afford to lose.
- Exclusion — Per-client offsite vaults unless separately agreed
- Exclusion — A contractual recovery-time SLA
- Exclusion — Customer-owned archives we do not host
8. Cloud VPS
Frequency: None included. Optional paid daily snapshot add-on.
Retention: Typically the latest daily copy when the add-on is active
Restore points: Typically one latest-copy snapshot unless the add-on says otherwise
Files: Server disk snapshot when the add-on is active
Databases: Included only as part of the disk snapshot
Email: Included only if mail is stored on that disk
DNS: Not included unless DNS data lives on the same disk
Storage location: Provider snapshot storage for that VPS — not a customer offsite vault.
Restoration method: Restore assistance on request from the active snapshot.
Restoration fees: The paid add-on price is shown at checkout. Extra recovery work beyond a listed snapshot is quoted.
Best-effort restore. There is no contractual recovery-time SLA. Keep an independent copy of anything you cannot afford to lose.
- Exclusion — Multi-week retention unless the add-on description says so
- Exclusion — Self-serve snapshot scheduling unless listed
- Exclusion — A replacement for your own off-server backups
10. Dedicated servers
Frequency: Only if written on the inventory quote
Retention: As written on the quote
Restore points: As written on the quote
Files: Only if backup is in the written quote
Databases: Only if backup is in the written quote
Email: Only if backup is in the written quote
DNS: Not included unless specified
Storage location: As written on the quote.
Restoration method: As written on the quote, usually via support.
Restoration fees: Backup and restore fees are confirmed in the written quote before payment.
Best-effort restore. There is no contractual recovery-time SLA. Keep an independent copy of anything you cannot afford to lose.
- Exclusion — Implied daily backups on the base server price
- Exclusion — A contractual SLA unless separately agreed
Questions about this policy? Contact us at support@pkhosting.com and our team will be happy to help.