Skip to content
SoundSyncAudio software platform

Customer Library and Secure Product Delivery

Customer Library and Product Access

Give customers one account for owned products, downloads, licenses, device actions and subscription management.

Customer library - Example data; no live transaction or account change.
JUCE library example - Native interface example, not a live licensing test.
HISEScript library example - Interface example, not a live HISE runtime test.

One place for owned products

The customer library connects purchases and entitlements to supported downloads, serial information, device access, subscriptions, and support. A customer can own a product without being a marketing subscriber.

Support with the actual access context

Developers can search their scoped customer records, inspect purchases and serials, review device activations, resend verification, and use permitted import/export workflows. Portal visibility, device deactivation, access removal, and refunds have different effects.

Access inside and outside the plugin

Hosted and embedded account surfaces and supported HISE/JUCE My Products integrations connect to the same ownership model. A browsing session and an audio license are separate; each must use the correct authentication path.

SoundSync

Customer documentation

Customer operations

Records, devices, invoices, and deliberate access actions.

Ownership model

Orders and access are distinct.

Delivery

Authorized product files.

SoundSync

The web account is the customer home base

The customer-library interface example shows owned access and available file actions using public product artwork. Its ownership and delivery state are fictional; it is not a production customer account.

SoundSync

HISE My Products brings ownership into the plugin

HISE customers can see owned products, downloads, serial counts, subscription state, and machine context without leaving the product experience.

SoundSync

JUCE My Products carries the same ownership model

The JUCE customer screen shows logged-in ownership, serial state, and device deactivation actions inside the native package UI.

Customer activation resets, when enabled

Developers can allow customer self-service resets for supported serial and entitlement licenses, with a configured cooldown. Only the signed-in owner of the license can request a reset. The confirmation clears the affected device activations and sessions together while preserving the license and product ownership.

A reset is not a refund, a new serial, or unlimited extra devices. Customers must reload the current state and wait for the next eligible reset when a cooldown applies.

Current access and previous records

The customer account separates current licenses and plans from Previous licenses and Previous subscriptions. Ended or inactive records stay available in expandable history; a plan with remaining eligible paid-through access is not hidden merely because cancellation is scheduled.

A signed-in marketplace customer who already owns a product can open their library and downloads from its product page. This is an account-specific lookup, not a public ownership list. License-reset cooldowns show the next eligible date; resetting activations does not create another license.

Purchases and marketing preferences

Owned-product access and necessary service messages remain separate from marketing preferences. A purchase can enroll a customer in the relevant developer list, but an existing unsubscribe or suppression must remain protected.

SoundSync

Marketing information and choices

Audience and suppression guide

Automatic enrollment, sending permission, and protected preferences.

Privacy policy

How customer and contact information is used.

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.

Make the purchase clear in the account

Show the customer what their purchase or plan currently provides, alongside the products they already own. Active access and previous licenses or subscriptions have different places in the account; a retained transaction is not automatically a current download permission.

A one-time purchase and a subscription can provide independent rights to the same product. The library must not remove the purchased copy merely because the plan ends, and an expansion still needs any required parent instrument.

Keep owned products when a plan ends

The library can show effective access from a collection without creating a second paid purchase. When an independently available one-time offer exists, an eligible subscriber can use Buy to keep. It appears only where the product and offer are currently sellable; it is not a promise that every subscription item is sold separately.

Downloads select currently permitted product-version files and can use the supported current-file fallback for older releases without attachments. Protected-only expansion access delivers its .sspc package rather than exposing the raw source archive. A missing file, incompatible bank and missing ownership are different support cases.

Customer access follows the services you use

Licensing supports customer serial and activation management while your checkout and downloads remain elsewhere. Licensing + Hosting adds authorized SoundSync delivery. Full Store connects managed checkout receipts, the customer library and supported purchase or subscription access. Choosing a developer service does not itself grant a customer a product.

SoundSync

Export complete filtered records

Customer, serial and purchase exports

Date meanings, progress and source identities.

Redeem through the customer account

Customers redeem outside serials from their signed-in customer account. Knowing a serial and typing an email into an old form is not proof of account ownership. The retired anonymous forms now direct customers to the current account journey; existing purchases remain available under their usual access checks.

HISE/JUCE native claims, activation, validation and deactivation use their own documented licensing conversations. Retiring the old web form does not change product Access settings, signed offline grace, protected-content grants or current library downloads.