Concept page
Licenses, Activations, and Devices
Distinguish ownership proof, licensing identity, and active machine use.
Serial and login paths prove different things
A serial flow may require email verification or proof of the existing owner. Customer login establishes account identity before entitlement/activation checks. Product credentials authenticate the integration itself, not the person requesting access.
Activation records authorized device use
The product's machine policy and limits govern whether another device can activate. Validation checks current access; confirmed server deactivation releases the selected activation. Neither operation is automatically a purchase refund.
JUCE locks locally when deactivation is requested. A local lock or pending request is not server confirmation and does not prove that a device slot is available elsewhere. Retain the pending proof through the maintained runtime until confirmation.
Use the package's stable device identity and supported reset/deactivation controls. Inventing a new machine ID for every launch can consume device allowance and make support harder.
Access policy is package-specific
JUCE 0.9.3 supports signed offline access. In the bounded grace mode, successful online activation or validation applies the period selected in product Access settings, up to 90 days and capped by any earlier entitlement or subscription deadline. Zero, disabled, missing or expired grace requires online authorization in that mode. An explicitly authorized permanent-device purchase is different: its signed product/content grant can have no recurring offline deadline. Never infer permanent access from a cached date, a catalog response or an unsigned success flag. Confirmed denial and local deactivation lock access.
HISEScript grace starts from prior valid access. A network failure, expired subscription, revoked entitlement, and a customer-identity mismatch must remain distinguishable.
