Skip to content
SoundSyncAudio software platform

Guide

Storing Plugin Activation State

What to store after activation, what never to store, and how local cache affects startup validation and offline grace.

SoundSync

Cache fields

Custom HTTP field concepts, not the generated JUCE cache schema. Use the maintained JUCE runtime to store and verify its native state; separate product, device and test/live records.

FieldUseRule
license_keyRequired for serial flowsSensitive. Encrypt/redact. Delete on deactivation.
instance_idRequiredMachine identity. Must match current machine.
tokenOptional but used for validation fast pathSensitive validation token. Rotate when server returns a new value.
statusRequiredDescribes the last decision; a stored status alone cannot authorize offline access.
activationIdOptionalUseful validation identity. Delete on deactivation.
licenseReferenceOptionalUseful validation identity. Delete on deactivation.
productIdRequiredMust match current product config.
graceExpiresAtOptionalServer deadline from successful activation/validation. In JUCE it must match a verified signed grant; the timestamp alone cannot unlock.
offlineLeaseRequired for JUCE offline accessOpaque signed offline_lease from the API. The maintained JUCE runtime stores and verifies it; do not construct or edit it.
offlineGraceDaysOptionalDisplay/diagnostic value. Do not use to reset grace locally.
subscription_* fieldsOptionalDisplay/status values. Explicit inactive/payment-required states lock.

A signed grant is not an editable cache date

The current JUCE 0.9.3 package maps the API offline_lease to its opaque offlineLease state. Its verifier checks the trusted public key, signature, issuer, product, activation, device and expiry. Neither status: activated nor a future graceExpiresAt can replace that verification.

An older unsigned cache requires successful online activation or validation before offline use. Do not hand-edit the native cache or delete a valid device activation merely to upgrade. HISEScript and custom HTTP have separate storage and authorization contracts.

SoundSync

Sanitized activation record

Illustrative custom HTTP record, not a serialized JUCE cache. The offlineLease placeholder is deliberately not a valid signed grant and cannot authorize access. Use protected platform storage and atomic writes rather than saving this example as plain JSON.

JSON
{
  "schemaVersion": 1,
  "environment": "test",
  "productId": 23794,
  "appId": "ss_prod_demoapp123",
  "license_key": "DEMO-SERIAL-0001",
  "instance_id": "machine-demo-001",
  "status": "activated",
  "activationId": 123,
  "licenseReference": "lic_demo_123",
  "token": "validation-token-from-activation",
  "graceExpiresAt": "2026-08-23T15:00:00.000Z",
  "offlineLease": "ILLUSTRATIVE_PLACEHOLDER_NOT_A_VALID_SIGNED_GRANT",
  "offlineGraceDays": 30,
  "lastValidatedAt": "2026-07-24T15:00:00.000Z"
}

SoundSync

Storage requirements

Local storage is part of the security boundary.

AreaRequirement
EncryptionUse platform secure storage where possible. At minimum encrypt sensitive fields at rest.
Atomic writesWrite to a temp record and replace atomically to avoid corrupting the last valid cache.
CorruptionTreat corrupt or schema-invalid cache as locked; do not unlock from partial JSON.
SeparationSeparate by productId, appId, environment, customer/account where applicable, and machine identity.
Deactivation cleanupJUCE locks locally and persists deactivation intent immediately, then completes server deactivation online. Keep the local block authoritative across restarts; only server confirmation proves slot release.
Pending claim persistenceStore claim_id, license_key, instance_id, email, productId, and started time only while the flow is pending.
Never storeCustomer passwords, plugin secrets outside generated config, or plugin key/secret in logs.

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.

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.