Skip to content
SoundSyncAudio software platform

Secure Product Delivery

Secure Product Delivery

Understand who can request product files, how private download links work and what happens when access changes.

Updated 2026-11-17

Downloads follow ownership

SoundSync connects a purchased or claimed product to a customer entitlement. Download authorization uses that access and the product's delivery configuration; a copied page URL should not become permission to retrieve a private file.

The customer library is the access point

Customers use their branded account/library to find owned products, configured downloads, serial information, subscription state, and support links. Developers choose delivery files and product compatibility information; the library does not create a license for an unrelated product.

Refunds and access changes

Refunded or revoked entitlements can change later download and licensing access. Handling must be scoped to the affected purchase. Removing a delivery-file entry and removing a customer entitlement are different actions.

Delivery troubleshooting

Check the customer identity, entitlement, product file configuration, file availability, and authorization result. Do not publish signed download URLs or customer identifiers in a support screenshot.

SoundSync

Owned products in the customer library

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.

Customer library - Example data; no live transaction or account change.

SoundSync

Delivery contracts

See the actual authorization and customer-access routes.

Downloads API

Authorized delivery requests.

Entitlements API

Product access records.

Customer library

Account and ownership context.

Delivery files up to 10 GB each

Each private delivery file can be up to 10 GB (10,000,000,000 bytes). Local multipart uploads retry interrupted parts. After a page reload, reselect the same file to reuse completed parts within 24 hours of starting the upload; the browser cannot silently reopen a local file.

Upload history shows the product, progress, and resume deadline. A remote-link import copies the file into private storage; retrying it may restart from the source rather than resume at the same byte. Protected or expired download links need a new direct link.

A file is attached only after its stored object, size, and upload session are checked. Incomplete uploads are not customer downloads. Public artwork and demos remain separate from private delivery files; attaching a file does not publish the product or grant ownership.

Account sessions must be verifiable

A signed account token is not enough on its own: customer account requests also check that the session is still allowed. If that check is unavailable, protected library, invoice, review, device-reset, download and customer-token activation requests stop before returning private data or performing the protected action.

If account verification is temporarily unavailable, retry after service recovery; this does not mean the purchase disappeared or the session was confirmed revoked. A confirmed revoked session requires signing in again. Neither outcome authorizes private access.

Shared library/download tokens retain their separate token and ownership checks. Optional storefront personalization can fall back to anonymous browsing when customer identity cannot be established; that does not authorize a private download. This account-session check does not replace the signed JUCE offline-grant policy.

SoundSync

The protected archive controls

Set the release revision and software compatibility in the product editor. This example shows the upload form, not a completed publication or a playback authorization.

Protected expansion content - Example data; no live transaction or account change.

Product storage and customer downloads

Full Store includes 500 GB of product storage per developer; Licensing + Hosting includes 100 GB. Storage is shared across products and retained versions. Each delivery file can be up to 10 GB. Customer downloads are included without bandwidth or per-download fees. New uploads stop at the storage allowance while existing customer downloads remain available. Contact SoundSync about larger catalogs; there are no automatic storage-overage charges.

A private storage key is not ownership proof

Attaching a private delivery file requires a verified object available to the selected workspace and product scope. A copied key from another developer cannot be used to grant that file to your customers. Identical files can still be deduplicated after your own upload has been verified; source product assignments continue to apply.

New-policy products use the managed attachment workflow and the chosen storage allowance. Historical file references remain intact; adding a different file still requires ownership proof. This does not change already-issued offline licensing grants.