Audio has a purpose.
So does every metric.

01 / AUDIO AND RECORDINGS

We process the far-end audio you send.

Kooya Answer analyzes the opening audio to produce a human, machine or unknown judgment. The detector decision window is capped at 15 seconds. If recording is enabled, recording continues until the client ends the transport, so full session audio can be retained separately from the audio analyzed for the decision.

• Audio is stored in a private object-storage bucket with server-side encryption.
• Full-session audio is retained without automatic expiration; completed recordings remain in private storage unless manually removed.
• Authorized playback uses short-lived access links; recordings are not public.
• Partial recordings and storage failures are recorded as status, not presented as a complete recording.

Agree on recording behavior and access before sending production caller audio. For data-handling requests, contact Kooya at Contact the Kooya Answer team.

02 / RESULTS AND USAGE

Operational measurements stay tied to the evaluation.

Service records can include client and source identifiers, your call reference, the classification, detector version, byte counts, received/analyzed/recorded audio duration and processing timings. Usage is measured in completed evaluations and analyzed audio milliseconds; it is not metered by AI tokens.

Whole-call recording duration and decision audio duration are separate. Aggregate research pages expose cohort totals only; they do not publish call identifiers or raw recordings.

03 / ACCESS AND SECURITY

Credentials are scoped to their purpose.

• API credentials are stored as non-reversible hashes and can be revoked.
• Webhook and provider secrets are encrypted at rest and omitted from normal read responses.
• Administrative access is limited to approved Kooya operators through the protected console.
• Customer audio is used to provide the configured detection and recording service. No public claim is made that recordings train or improve the detector.

04 / QUESTIONS AND REQUESTS

Set handling terms before a pilot.

Pilot onboarding confirms the processing scope, retention needs, access contacts and deletion procedure for your deployment. For a data-handling question or request, email Contact the Kooya Answer team with your organization and evaluation reference; do not email caller audio or credentials.

This operational summary describes the current service configuration. Pilot-specific written terms govern the data handling for an enabled customer integration.