Skip to content
SoundSyncAudio software platform

Licensing Reliability

Licensing Reliability

Understand how ownership, devices, offline authorization, revocation and reconnection interact.

Updated 2026-11-17

A connected licensing lifecycle

A purchase or approved claim establishes product access. Activation associates permitted access with a device; validation checks the current state. Deactivation stops permitted use, but the server device slot is released only after server confirmation. A serial is a claim or activation input, not a substitute for entitlement checks.

Reconnect without inventing ownership

The client can use a previously valid cached state within configured offline grace. It must distinguish a network problem from a confirmed invalid response. Device changes, revoked access, expired subscriptions, and refund outcomes require their own handling.

SoundSync

Offline access during the grace period

JUCE offline example - Native interface example, not a live licensing test.

Use the policy supported by the installed package

JUCE bounded grace requires a valid signed allowance; an explicitly authorized permanent-device purchase has a separate product/content authorization. Do not infer either permission from a cached date or an unsigned response.

HISEScript and native HISE follow their own package contract and the selected Access grace. Prior valid access, expiry and confirmed denial still matter. JUCE protected-bank behavior is not a promise about HISE runtime behavior.

Support needs the right context

For activation problems, provide the product, package version, platform, and non-sensitive error code. Share serials only through the appropriate private support process, never in public screenshots. Test Connection confirms credentials and product binding, not customer ownership.

SoundSync

Licensing guides

Follow the specific state you need to implement.

Validate on startup

Startup checks and product gating.

Offline grace

Valid cache and expiry.

Device deactivation

Device access and slot release.

Refresh HISE grace through a valid online check

HISEScript and native HISE use the offline grace selected in Access after prior successful activation or validation. Zero or disabled grace requires online authorization, and the cached access cannot outlast the server-issued deadline or subscription access.

Changing a policy reaches an installed client at its next successful online validation. A disconnected build cannot learn about a later revocation immediately. Older binaries need the appropriate package update, rebuild and target-host testing; HISE and JUCE package behavior must not be assumed identical.

Know when an offline allowance ends

Bounded JUCE grace starts at the successful online activation or validation that issued it, not the first failed connection. The selected Access period can be up to 90 days; an earlier entitlement or subscription deadline shortens it. Restarting the plugin does not refresh the signed expiry.

Confirmed denied access is different from an unreachable server. Reconnection applies the current decision, and local deactivation locks the product without claiming that the server device slot has already been released.

An existing plugin needs the matching verification support and public keys. Regenerate, rebuild, test and distribute when upgrading the package; a website update cannot replace an installed customer binary.

The manifest offlineAccess: true flag describes verification support, not an entitlement. Reconnect an older unsigned cache for valid authorization. If the signer changes, ship replacement public keys through the matching regenerated package instead of editing signed local state.

SoundSync

Update an existing JUCE product

Regenerate and update JUCE

Package readiness, saved activations, offline tests, and customer distribution.

Account security and product access stay separate

JUCE 0.9.3 and HISE Native C++ 0.5.2 account login can request an authenticator or recovery code when the customer has enabled two-factor authentication. Completing account sign-in still requires an entitlement and device activation for the selected product. Use the current package sources and rebuild existing plugins; a sign-in challenge does not create offline permission. See the package update and account-security guides for the required versions.

Keep independent ownership when another grant ends

A timed manual keep-products grant awards its original product snapshot without a payment and retains it after cancellation, expiry or incomplete billing setup. Explicit developer access removal can revoke that grant. A lifetime access grant and an unpaid trial are not the same ownership model.

Paid ownership follows its own invoice snapshot. Refunding that purchase does not erase an independent manual grant; later products and future billing benefits are not silently added to the original gift. Review the removal confirmation and identify the affected grant before completing that action. The ownership guide explains the full lifecycle.

SoundSync suspension and store restrictions

A SoundSync-wide customer-account suspension blocks customer library and download authorization, including requests made with an existing signed-in session. A restriction imposed by one store remains scoped to that store; unrelated stores remain available unless the SoundSync account is also suspended.

Suspension does not delete purchase history or create a refund. Contact SoundSync support about a platform restriction and the developer about a store restriction. A previously issued storage link can remain usable until it expires; already downloaded files cannot be recalled by an account restriction.

A message cannot unlock or install a product

Notice tokens are independent, short-lived capabilities. A notice response does not activate a device, refresh offline grace, authorize audio or create a paid entitlement. Licensing controls, serial fields, passwords and payment controls cannot be registered as notice triggers.

Content downloads use current ownership checks and private expiring links. The maintained companion saves the selected file and checks its available size/checksum; it never automatically installs, extracts, imports or executes it. Import remains a deliberate customer action. A selected Windows or macOS instruction set is shown, otherwise General; the sets are not concatenated.

Bounded grace and explicit permanent ownership

Offline grace is not deactivation. A disconnected permanent-device grant cannot learn about a later server revocation instantly; reconnection applies the new decision. Local deactivation still locks immediately and retains the pending server-release proof. HISE has its own package contract and runtime-verification boundary; JUCE protected-bank behavior must not be assumed for HISE.

SoundSync

Match the integration to the policy

Ownership modes

Permanent grants, recurring rights and compatibility.

Package upgrade

Integrate, rebuild and release the matching package.

SoundSync

Product Access settings

Product Access contains licensing requirements, activation rules and the selected offline grace period. These settings are separate from product pricing and account two-factor authentication.

Access and offline grace

A reachable licensing server is not an activated product

The public licensing ping checks request parsing and reachability only. Actual activation and validation still require the matching product identity and authorized customer/device proof. An email verification link confirms the claim, not the machine activation. Offline access requires the supported generated client and its valid grant; an older API URL does not add offline capability.