Security & Privacy
Exactly what happens to your audio and transcripts at every step. No marketing fluff — just how it actually works.
Three Levels of Privacy
Standard
- HTTPS (TLS 1.3) for all data in transit
- Audio deleted immediately after processing
- Transcripts stored in our database
- We can read stored transcripts
- Data never sold or used for training
- Delete your data anytime
Private Transcript
- Everything in Standard, plus:
- Transcript encrypted in your browser (AES-256-GCM) before saving
- We store only encrypted data — we cannot read it
- Key derived from your password, never sent to us
- ⚠ Audio is still processed on our servers during transcription
Private Cloud / Self-Hosted
- Audio never leaves your infrastructure
- Transcription runs on your GPU
- No data sent to STT.ai servers
- Air-gapped support available
- True end-to-end privacy
What Actually Happens to Your Data
A transparent, step-by-step breakdown of how your audio and transcript are handled.
Steps 1-2 are the same — your audio must be processed on our servers to generate the transcript. The difference is what happens next:
What We Can and Can't See
We CANNOT see (with Private Transcript)
- Your stored transcript text
- Speaker names or labels (stored)
- Timestamps or word-level data (stored)
- Your encryption key or password
We CAN see (even with Private Transcript)
- Your audio during processing (deleted after)
- File name, size, duration (metadata)
- Language detected, model used
- Timestamp of transcription
- Your account info and billing
Technical Details
| Encryption algorithm | AES-256-GCM (authenticated encryption) |
| Key derivation | PBKDF2 with SHA-256, 100,000 iterations |
| IV (nonce) | Random 12 bytes per encryption (never reused) |
| Key storage | Never stored — derived from password on each session |
| Transport encryption | TLS 1.3 (HTTPS) + HSTS (1 year, preload) |
| Audio retention | Processed in memory, never written to disk, deleted immediately |
| Implementation | Web Crypto API (browser-native, no external libraries) |
| Source code | github.com/sttaigit/stt-encryption (MIT license) |
Private Transcript Trade-offs
Private transcript is opt-in because encrypting the stored transcript limits some features:
- Viewing your transcripts
- Exporting (TXT, SRT, VTT, etc.)
- Downloading
- Editing (decrypted in browser)
- Server-side search across transcripts
- AI summaries and chat (server can't read data)
- Public sharing via link
- Team workspace collaboration
Need Audio to Never Leave Your Servers?
Private transcript protects the transcript at rest, but audio still passes through our GPU during processing. If your compliance or security requirements demand that audio never touches third-party infrastructure, these are your options:
Private Cloud
Dedicated GPU server managed by us. Your audio never leaves your isolated environment.
- Dedicated A100 GPU
- Isolated — no shared infrastructure
- Audio processed on your hardware only
- Full API access + SLA
Self-Hosted
Docker image. Your servers. Your GPU. Nothing leaves your network.
- Docker — runs on any NVIDIA GPU
- Air-gapped support — no internet required
- Model updates included
- Full control, full privacy
Our Commitments (All Users, All Plans)
- Audio files are never stored permanently. Processed in GPU memory, deleted immediately after transcription.
- Your data is never used for AI training unless you explicitly opt in via Voice Lab.
- We don't sell your data. Ever. To anyone.
- All traffic encrypted in transit via TLS 1.3 with HSTS.
- Delete your data anytime from Privacy Settings or by deleting your account.
- Encryption code is open-source — audit it yourself (MIT license).
Open-Source Encryption
Our encryption library is fully open-source under the MIT license. Don't trust us — verify the code. No trust required, just math.
View on GitHub | View SourceReady to transcribe securely?
Upload your first file free. Private transcripts available on Pro and Business plans.
Start Transcribing