DRAFT for owner review, not yet in force. Have a lawyer review before launch.
API privacy notice
Effective date: [date]. This notice covers audio and data sent to the Saidwire Speech-to-Text API. Our general Privacy page covers the rest of saidwire.com, including payments and contact forms.
The short version
- Audio: processed in memory, never written to disk, gone when your stream ends.
- Transcripts: sent back to you, not logged by us.
- Training: we don't train or tune models on your audio or transcripts.
- What we keep: usage records for billing and technical logs without transcript text.
Roles
For audio and transcripts you send through the API, you decide what is sent and why, and we process it on your behalf to provide the API (for data protection law purposes, you are the controller and we are your processor). For your account details (name, work email, company, billing), we are the controller, as described on our general Privacy page.
What we process and keep
| Data | Why | How long |
|---|---|---|
| Audio you stream | To transcribe it and detect speech and turns | Only in memory while your stream is open; never written to disk |
| Transcripts and word timings | Returned to you over the stream | Not stored after they're sent; not written to our logs |
| Usage records: key id, account id, minute, seconds of audio, number of streams | Billing, limits and abuse prevention | As long as tax and accounting law requires (typically 7 years) |
| Technical logs: request id, key id (never the full key), IP address, stream start and end, audio format, timing statistics, error codes | Running, securing and debugging the service | 30 days |
| API keys | Checking access | We store only a one-way hash and the public key id, until you revoke the key or close your account |
| Account details and messages you send support | Running your account and answering you | Until you close your account, then as our general Privacy page describes |
If you ask us in writing to help debug a specific problem, we may turn on transcript logging for your key for a limited time you agree to, then turn it off and delete those logs.
Where it's processed
On servers in the United States, run by us on a major cloud infrastructure provider. Data moves between your client and our servers, and between our servers, over encrypted connections.
Who we share it with
We don't sell data or share it for advertising. Audio and transcripts are not shared with anyone. Usage and account data is shared only with the service providers we need to run the API (cloud hosting, payment processing, email), under contracts that limit them to that purpose, and if the law requires it.
Security
Keys are stored only as hashes, all traffic is encrypted in transit, servers are reachable only through the ports the service needs, and staff access is limited to what running the service requires. We'll notify you without undue delay if we learn of a security incident affecting your data.
Your choices
To see, correct or delete account data we hold about you, or to close your account, email support@saidwire.com; we'll respond within 30 days. Requests from your own end users about audio you sent us should go to you first; since we don't keep audio or transcripts, there is usually nothing on our side to delete, and we'll help you confirm that.
Children
The API is for businesses and developers. Don't send us audio of children under 13 unless you have the consent the law requires.
Changes
If we change how we handle API data in a way that matters, we'll email account holders at least 30 days before the change takes effect.
Contact
Saidwire, Kansas City, Missouri · support@saidwire.com