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; deactivation releases the selected activation. Neither operation is automatically a purchase refund.
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.7.3 supports signed offline access for the grace period selected in product Access settings, through 90 days. A prior successful activation or validation and the matching package verification keys are required. Startup uses a verified unexpired grant or online authorization. Zero, disabled, missing or expired grace requires online authorization; confirmed denial or deactivation locks access. Regenerate and rebuild older plugins to use this release.
HISEScript grace starts from prior valid access. A network failure, expired subscription, revoked entitlement, and a customer-identity mismatch must remain distinguishable.