Blog · Licence guides
Backups, redundancy and protected content
Updated 5 September 2026 · Based on our Software Licence & Services model
Why LMS White does not keep an independent archive of your student DB or lecture videos after handover — and how vendor-side redundancy works.
What this means for you
After handover, LMS White does not maintain an independent archival backup of your student database, restricted lecture videos or other protected Client Content — unless a separate written service says otherwise.
During implementation we may configure redundancy, replication, versioning or backup policies inside your Third-Party Services where supported and in scope. Those replicas stay in your vendor environment. You pay associated storage/egress charges and, after handover, you choose retention, test restores and decide if you need extra disaster recovery.
We will not accept a separate safekeeping copy of restricted lecture videos or bulk student data “just in case.” Temporary support access is not an independent backup.
Why we refuse a shadow archive
Holding a second full copy of every client’s student database and lecture library creates enormous privacy, security and legal risk — and blurs who is the data controller. Client-controlled redundancy (for example multi-region storage on your CDN/cloud) keeps resilience where the data already lives, under your billing and access policies.
Examples
- Bunny or cloud storage replication configured on your account → resilience without LMS White holding a private mirror.
- An admin permanently deletes courses without backups → restoration depends on vendor versioning/your retention settings, not a secret LMS White vault.
What LMS White can configure: initial backup/redundancy settings in scope.
What we will not do: become the long-term offsite archive of your protected student and lecture content by default.