Trust
Evaluate TranscriptFetch using verifiable evidence rather than marketing claims. The information below brings together independent monitoring, public technical checks, published documentation, and third-party records.
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:
/api/v2/health
Confirms that the API service is reachable.
/api/v2/health/deep
Runs a live transcript extraction and returns 200 only when transcript segments are received.
The deep check measures the core extraction path rather than web-server availability alone.
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.
Subscriptions, upgrade charges, credit rollover, cancellation, and the 30-day money-back guarantee
Service terms, acceptable use, billing practices, and data collection
API-key handling, encryption, retention, subprocessors, and current certification status
GDPR Article 28 terms governing personal-data processing on your behalf
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.
No self-published testimonials, invented customer logos, aggregate ratings, or deleted registry entries. Reviewed as of 2026-09-12.
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.
com.transcriptfetch/youtube-transcripts, status: active
transcriptfetch-sdk, with public release history and download counts
transcriptfetch, with public release history and download counts
n8n-nodes-transcriptfetch, the community node
Published collection and publisher profile
SDK source, public issue history
Level 1 CAIQ self-assessment, published on the Cloud Security Alliance registry
Q141470122, the knowledge-graph entry: classification, identifiers and references, publicly editable and reviewed
Registry download figures may include mirrors, automated scanners, and CI systems. Treat them as directional indicators rather than verified user counts.