What is collected
When enabled, ALEVRB records coarse, aggregated counts such as plugin format and version, operating-system family, host family, sample-rate and buffer-size ranges, time spent in broad control ranges, routing mode, and bypass state. Counts are sampled while audio is active and uploaded about once per day.
What is not collected
ALEVRB does not collect audio, MIDI, project or preset names, file paths, parameter automation, account details, email addresses, advertising identifiers, or precise hardware fingerprints. The telemetry service does not store client IP addresses.
Offline behavior and identity
The plugin works fully offline. Pending aggregate counts are kept locally within a bounded queue and retried later. Each installation creates a random signing key used only to authenticate its anonymous batches and prevent replay; it is not tied to a person or ToolingDev account.
Control and retention
Turning analytics off stops collection and removes the local telemetry queue and installation key. Server-side aggregate batches are retained for up to 400 days for product analysis and security monitoring.
ALEVRB may fetch a public software-update manifest over HTTPS. The request is separate from analytics and adds no account, telemetry installation identifier, installed-version query, project or preset data, or device identifier. Origin access logging is disabled for the manifest route, and automatic checks can be disabled from the update controls.
Contact
Questions or deletion requests can be sent to [email protected]. Because no account or contact identifier is collected, a server-side deletion request requires the anonymous installation identifier shown by the plugin.