@dannytaurus SoundSync can currently receive information related to the product’s operation and the customer journey, including:
When the plugin is opened or connects to SoundSync
Activation, validation, restoration, and deactivation activity
The installed plugin version
The product and license associated with the activation
A hashed installation/device identifier for managing activations
Interactions with SoundSync-provided areas such as activation, account, store, support, and update interfaces
Timestamps showing recent validation or connection activity
This can be combined with information already created elsewhere in SoundSync, such as purchases, products owned, downloads, customer accounts, support activity, email engagement, and marketing consent.
That makes practical things possible. For example, a developer could notify customers using an outdated version, help somebody who purchased but never activated, exclude existing owners from a promotion, or create a re-engagement flow based on meaningful customer activity, cart recovery, etc, etc.
SoundSync does not inspect or collect the customer’s audio, MIDI, presets, parameter changes, DAW projects, filenames, or what they are creating. We are interested in product lifecycle events that help with licensing, updates, support, and relevant communication, not the customer’s creative activity.
We also try to keep the principle fairly simple, collect the minimum information needed for the feature, be clear about how it is used, and give developers the controls they need to handle consent and privacy properly.
Some of this varies by integration. For example, the HISE package can report plugin-open and SoundSync interface events, while licensing integrations naturally generate activation and validation events whenever they communicate with SoundSync.
