Transcription Privacy
Skribby only supports transcription providers that do not train on Skribby customer audio or transcripts.
For provider-side retention, Skribby uses the strongest retention control available for each provider:
- Zero Data Retention (ZDR) or zero-retention mode.
- Deletion after processing when the provider creates a stored job or artifact.
- Realtime streaming paths where audio is processed ephemerally instead of stored as a transcription job.
This page covers transcription-provider processing. Skribby's own recording and transcript retention is controlled separately by bot settings, workspace retention settings, storage add-ons, and delete requests.
Standard Providers
These providers meet Skribby's no-training and low-retention requirements without a provider-specific caveat:
- Groq
- Soniox
- AssemblyAI
- Deepgram
- Speechmatics
- Rev AI
- Gladia
- Mistral/Voxtral
- OpenAI
none
Realtime Transcription
Realtime transcription is part of Skribby's standard privacy posture. For realtime models, ephemeral streaming is the intended low-retention path: audio is processed live instead of being stored as a batch transcription job.
Realtime providers covered by this posture include:
- Soniox realtime
- AssemblyAI streaming
- AssemblyAI Universal-3 Pro streaming through the EU endpoint
- Deepgram realtime
- Speechmatics realtime
- Gladia realtime
- Mistral/Voxtral realtime
Important Caveats
Most supported providers meet the standard posture above. The following providers or models have additional caveats:
- Google Cloud Speech-to-Text: Google Chirp 3 uses EU routing and data logging is off by default. Skribby deletes batch GCS input and result objects; the accepted GCS-output path keeps transcripts out of completed long-running-operation records, but that operation metadata cannot be deleted. It is standard handling, not strict ZDR.
- AWS Transcribe: AWS Transcribe uses Frankfurt (
eu-central-1) with the account's Organizations training opt-out. Skribby deletes transient batch artifacts; streaming is ephemeral. It is standard handling, not strict ZDR. - OpenAI GPT-4o Transcribe Diarize: routed through Skribby's approved ZDR-backed OpenAI org and project and treated as global processing. Skribby does not present this model as EU regional processing.
- ElevenLabs: no-training is in place, but ElevenLabs transcription does not currently have a standard ZDR or deletion path.
- xAI: xAI speech-to-text retains API inputs and outputs for up to 30 days before automatic deletion. Treat it as low-retention with automatic deletion, not strict ZDR or immediate deletion after use.
For strict zero-retention requirements, choose one of the standard providers above or ask Skribby to restrict provider availability for your workspace.