AssemblyAI Security and Data Governance

Overview

Govern speech and derived data across every AssemblyAI surface. Keep consent, credentials, region, training posture, retention, and deletion as explicit decisions.

Prerequisites

• The target repository or integration path and the requested operator outcome.
• The AssemblyAI project, environment, region, data classification, and accountable owner.
• Current first-party documentation plus credentials only for a narrowly approved live check.

Current Contract

Speech, transcripts, prompts, and derived intelligence are governed data. Long-lived keys stay server-side; US and EU hosts are explicit decisions. Retention, training posture, transcript deletion, and downstream copies require policy evidence. Infrastructure TTL processing means physical deletion should not be described as instantaneous without confirmation.

Authentication

For live work, inject ASSEMBLYAI_API_KEY from an approved secret manager and send the raw value only in the AssemblyAI Authorization header to the configured first-party host. Never print, commit, place in a URL, or expose it to an untrusted client. Callback secrets and temporary streaming tokens are separate credentials.