Blog
Licence & commercial guides
Guides drawn from our Software Licence & Services model and day-to-day App Store / cloud reality. Capsules on pricing stay short; these pages explain why the rules exist — Apple, Google, privacy law and standard B2B licensing — not LMS White inventing unfair limits.
Back to pricingCommercial guide
What the one-time fee buys
Why LMS White’s one-time price is a perpetual software licence for your institution — not a sale of source code or the right to resell the platform.
Read guide →
Commercial guide
Upgrades vs updates explained
How LMS White Version Upgrades and Corrective Fixes differ from chargeable Maintenance Updates driven by OS, App Store and vendor changes.
Read guide →
Commercial guide
What is not included in the one-time price
Why SOC monitoring, unlimited maintenance, training and forensics are scoped services — and why permanently deleted data cannot always be recovered.
Read guide →
Commercial guide
Third-party costs and App Store approval
Why cloud, CDN, SMS and Apple/Google fees are paid to vendors — and why app listing is never guaranteed by LMS White.
Read guide →
Commercial guide
Payments inside Android and iOS apps
Why Razorpay or external billing is not always allowed inside mobile apps for digital courses — Apple and Google store billing rules explained.
Read guide →
Commercial guide
Ownership, handover and acceptance
Who owns brand, data and platform IP after go-live; why you manage MFA and backups; and how the 7-business-day acceptance window works.
Read guide →
Commercial guide
Why Pro uses a shared LMS White iOS app
How Apple App Store rules on template-style apps shape the Pro plan: white-label Android, shared iOS experience for learners.
Read guide →
Commercial guide
Why the Apple Developer fee is paid by you
Apple requires the Developer Program under your organisation. Why LMS White cannot create or pay that membership for Enterprise clients.
Read guide →
Commercial guide
Upgrading from Pro to Enterprise
How Pro→Enterprise moves prefer official Apple/Google app transfer, why transfer is not guaranteed, and when the shared publishing fee stops.
Read guide →
Licence guide
Source code and production delivery
Why a licence includes a production Deployment, not human-readable source code, build pipelines or private keys — and why reverse engineering is restricted.
Read guide →
Licence guide
White-label branding vs software ownership
White labelling puts your name, logo and domain on the product. It does not transfer ownership of the underlying LMS White software.
Read guide →
Licence guide
Security model: no absolute security warranty
Why no LMS can honestly promise “100% secure” or “unhackable” — and how shared responsibility works after handover.
Read guide →
Licence guide
Credential creation, handover and access
Why infrastructure accounts should be in your name, what you must secure at handover, and how temporary access works for later fixes.
Read guide →
Licence guide
Backups, redundancy and protected content
Why LMS White does not keep an independent archive of your student DB or lecture videos after handover — and how vendor-side redundancy works.
Read guide →
Licence guide
Data protection and privacy roles
You decide what student data to collect and why. LMS White processes data on your instructions for implementation and support — including DPDP considerations in India.
Read guide →
Licence guide
Client content and educational services
You are responsible for course content legality and teaching outcomes. LMS White is the software provider — not the school, teacher or refund desk.
Read guide →
Licence guide
Warranties and limitation of liability
What LMS White warrants at delivery — and why liability is capped at fees paid for the affected order, excluding third-party vendor charges.
Read guide →
Licence guide
Using LMS White after optional support ends
A fully paid perpetual licence can continue even if you stop buying optional support — you still maintain third-party services and future maintenance.
Read guide →
Licence guide
Security patches and client delay
When LMS White notifies you of a material security fix, timely access matters — delay or refusal can shift responsibility for resulting loss.
Read guide →