Secure Product Delivery

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.

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.

503 SESSION_VERIFICATION_UNAVAILABLE means verification could not finish. Retry after service recovery; it does not mean that the purchase disappeared or the session was confirmed revoked. A confirmed revoked session returns 401 LIBRARY_SESSION_REVOKED and requires sign-in again. Do not grant access on either response.

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.