Licensing and domain binding
How Sense CMS verifies, stores and renews license validation.
A license comes first
The installer checks the key against the canonical domain and the registered product identity: Sense CMS / Sense CMS System / 1.0. Development Core versions are separate from this licensed product version.
Private by design
License checks travel from your server to Chivale over verified HTTPS. Keys are not included in URLs or echoed back in pages. Local license data is encrypted with an installation-specific key outside the public directory.
Validation and availability
Successful validation is cached for up to seven days, bounded by any license expiry. Expired or stale validation requires a fresh remote check. There is no unlimited offline grace period; allow outbound HTTPS to the licensing endpoint.
Changing a key or domain
An authenticated installation owner can replace the key from the License page. A domain move also requires corresponding license and server configuration changes. Copying encrypted license files between unrelated installations is not supported.
Protect your backups
Preserve the installation’s encryption key with the private storage backup. Store the database and private files securely; never include either in an extension package or public download.