Skip to main content

​
Overview

The ai-coustics SDK processes audio locally. In core SDK 0.24.0, the authorization, usage and SDK error-reporting payloads described here do not include audio samples, recordings, transcripts or model input/output features. Each network channel is controlled separately: This description covers SDK traffic. Your application, speech-to-text provider and agent framework may send audio or other data independently.

​
What we collect

Product and usage records include:
  • Core SDK version and wrapper type, such as Python or Node.js
  • Model identifier, such as quail-vf-2.2-l-16khz
  • Operating system and CPU architecture
  • Processing-session identity and processed or disallowed audio duration
  • Whether the session uses a dedicated voice activity detection (VAD) model

​
Authentication and metering

A session associates processing activity with the authorized account. Treat SDK keys, decoded API keys and bearer tokens as secrets. Network failure behavior depends on the credential and session requirements. Core SDK 0.24.0 requires activation for JWT credentials; failed activation can disable processing. Explicit authorization rejection can also disable processing. Where usage reporting is required, sustained reporting failure can disable processing too. Do not use a temporary grace period or tolerated failure as an offline deployment contract. For disconnected operation, contact ai-coustics about an appropriate offline license and verify its validity period and deployment conditions. Preprovision model files as well. An offline entitlement does not automatically prevent your application or an enabled customer metrics exporter from making network requests. See authentication for token handling and deployment for restricted-network validation.

​
Error reporting

SDK error reporting was added in core SDK 0.24.0. It covers failed session activations, failed usage reports and rejected bearer-token updates. Reports contain the error class and message, core SDK version, wrapper type, model identifier, operating system and CPU architecture. Account identity is included when available and trusted. The reporting path excludes credential material and audio. To disable SDK error reporting:
Set this before your process loads the SDK. The setting is read once per process. Licenses with an offline entitlement and WebAssembly builds do not use this error-reporting channel.
DO_NOT_TRACK=1 does not turn off authorization or usage reporting, grant an offline entitlement or disable your OpenTelemetry exporter.

​
What we do not collect

The SDK reporting channels to ai-coustics described above do not send:
  • Audio samples, recordings or buffered audio
  • Transcripts or speech content
  • Model input/output feature data
Customer-controlled OpenTelemetry export includes derived processing and audio metrics. Hashes and session IDs remain correlatable identifiers: apply access controls, retention limits and appropriate redaction in your own observability system.

​
Network review and contractual sources

For a deployment with restricted outbound access, validate model provisioning, activation, usage reporting and optional exporters independently. Obtain the current destination requirements for your SDK release and entitlement from ai-coustics before finalizing firewall rules. This page is not an exhaustive hostname allowlist. The Privacy Policy and your applicable license agreement govern data and privacy terms. This technical reference does not establish retention periods, certifications, service levels or contractual offline rights.