Skip to content
SoundSyncAudio software platform

Guide

Device Limits and Deactivation

Control active device use without confusing it with a refund or ownership transfer.

Use stable device identity

The integration submits the machine identity used by its generated contract. Keep it stable across ordinary restarts. Randomizing it on every launch can consume device allowance and produce confusing activation history.

Activation checks the product allowance and existing device use. A limit rejection is not a network outage. Show the customer the supported deactivation/support path rather than silently inventing another identity.

SoundSync

Access and offline grace

Access and offline grace

SoundSync

Resolve a full allowance

  1. Inspect active devices

    Use the permitted customer library or developer customer context.

  2. Request deactivation

    Select the intended activation through the supported action. JUCE can lock locally first; keep pending proof for its retry.

  3. Confirm server release

    Wait for confirmed server deactivation before expecting the device slot to be available elsewhere. A local lock or pending request alone does not release it.

  4. Activate again

    Use the current customer proof and stable machine identity after the required server release.

  5. Revalidate access

    Check the exported product and the former device state under the package policy.

Different actions, different consequences

Resetting activations, suspending product access, removing an entitlement, and refunding an order are not interchangeable. Review the specific customer/product before taking an administrative action.

Package-specific access policy

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.