Trust & reliability

Uptime, service status, and incident history are published at status.transcriptfetch.com. An independent monitoring provider records this information, so the history is maintained outside this site.

Two unauthenticated endpoints are also available for direct monitoring:

The deep check measures the core extraction path rather than web-server availability alone.

Breaking changes, additive releases, and deprecation procedures follow our API stability commitments. Any version retirement includes at least 12 months’ notice through the changelog and email, together with a Deprecation response header.

No API version is currently deprecated. Legacy unversioned routes remain available, and shipped changes are documented in the changelog.

The security page documents API-key hashing, encryption in transit, data-retention practices, and the complete subprocessor list, including the speech-recognition provider used when captions are unavailable.

Vulnerability reports are accepted at the address published in /.well-known/security.txt. The policy includes a three-business-day response commitment and safe-harbor terms for good-faith security research.

TranscriptFetch is not currently certified under SOC 2 or ISO 27001. Organizations that require either certification should account for this during procurement.

Current legal, security, and data-processing documents are collected here for procurement review. Each document identifies, where relevant, whether information is self-assessed or independently audited.

Rather than relying on testimonials or ratings, this section links to third-party registries and public repositories that document TranscriptFetch’s releases, activity, and published integrations.

Registry download figures may include mirrors, automated scanners, and CI systems. Treat them as directional indicators rather than verified user counts.