Snapshot 19220
Normalized text
Scripts and page chrome removed; this is what change detection compares.
TranscriptFetch Start fetching Independently monitored 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: GET /api/v2/health Confirms that the API service is reachable. GET /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. Policies and documentation 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. Pricing & Refund Policy Subscriptions, upgrade charges, credit rollover, cancellation, and the 30-day money-back guarantee Terms & Privacy Service terms, acceptable use, billing practices, and data collection Security API-key handling, encryption, retention, subprocessors, and current certification status Data Processing Addendum GDPR Article 28 terms governing personal-data processing on your behalf API stability and versioning 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. Security 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. Evidence policy Every positive claim links to a public authority or an independently observable endpoint. Missing certifications must remain explicit. No self-published testimonials, invented customer logos, aggregate ratings, or deleted registry entries. Reviewed as of 2026-09-12. Independent records 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. Official MCP Registry com.transcriptfetch/youtube-transcripts, status: active PyPI transcriptfetch-sdk, with public release history and download counts npm transcriptfetch, with public release history and download counts npm (n8n) n8n-nodes-transcriptfetch, the community node Postman API Network Published collection and publisher profile GitHub SDK source, public issue history CSA STAR Registry Level 1 CAIQ self-assessment, published on the Cloud Security Alliance registry Wikidata 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. Put the spoken web to work 50 free credits a month. No card required. Failed fetches are never billed. Start fetchingRead the docs