transcript-yt-com · Privacy & Data
transcript-yt-com privacy & data
Read from transcript-yt-com's own page on 2026-11-10. 20 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Role
The page states nothing on this.
Data categories
category: identifying
When you sign in with Google, we receive your name, email address, profile image, and Google account identifier.Read from transcript-yt-com's own page on 2026-11-10
category: financial
We receive billing details needed to provide access, including your email, plan, payment or customer identifiers, subscription status, and payment-event records.Read from transcript-yt-com's own page on 2026-11-10
category: location
Our own first-party analytics record each page view with the referring site, approximate location from your IP address, and device typeRead from transcript-yt-com's own page on 2026-11-10
category: device
device type, under an identifier derived from your IP address and browser that changes every dayRead from transcript-yt-com's own page on 2026-11-10
category: behavioral
For every API request, we record the video ID, requested language, response status, cache status, response time, and proxy-bandwidth measurements.Read from transcript-yt-com's own page on 2026-11-10
Purposes
purpose: Provide the Service and enforce quotas
This helps us provide the Service, enforce quotas, prevent abuse, and diagnose faults.Read from transcript-yt-com's own page on 2026-11-10
purpose: Error monitoring
We also use Sentry to receive technical error and performance reportsRead from transcript-yt-com's own page on 2026-11-10
Retention
scope: Redis transcript cachesperiod: seven days
Redis transcript caches expire after seven daysRead from transcript-yt-com's own page on 2026-11-10
scope: Database cache entriesperiod: 30 days
database cache entries are treated as stale after 30 daysRead from transcript-yt-com's own page on 2026-11-10
scope: Account, usage, and security records
Account, usage, and security records are generally kept while your account is active.Read from transcript-yt-com's own page on 2026-11-10
Residency
The page states nothing on this.
International transfers
mechanism: other
These providers may process information in countries other than yours under their own terms and privacy practices.Read from transcript-yt-com's own page on 2026-11-10
Subprocessors
Google (authentication and translation), Dodo Payments (billing), Upstash (caching and rate limiting), Neon (database hosting), Vercel (application hosting and aggregated analytics), DeepInfra and Groq (speech-to-text for videos without captions, and AI summaries), DataImpulse (network proxy for retrieving public YouTube data), PostHog (cookieless analytics), and Sentry (error monitoring).Read from transcript-yt-com's own page on 2026-11-10
Data processing agreement
Deletion
route: Email aadit@techiseasy.co.in to request deletion of account data, subject to records we must retain.
you may request access, correction, or deletion of your account data by emailing aadit@techiseasy.co.inRead from transcript-yt-com's own page on 2026-11-10
Data subject rights
right: Access
you may request access, correction, or deletion of your account data by emailing aadit@techiseasy.co.inRead from transcript-yt-com's own page on 2026-11-10
right: Correction
you may request access, correction, or deletion of your account data by emailing aadit@techiseasy.co.inRead from transcript-yt-com's own page on 2026-11-10
right: Deletion
you may request access, correction, or deletion of your account data by emailing aadit@techiseasy.co.inRead from transcript-yt-com's own page on 2026-11-10
right: Revoke API keys
You can revoke API keys at any time from your dashboard.Read from transcript-yt-com's own page on 2026-11-10
Sale or sharing
stance: prohibited
We do not sell or rent personal information.Read from transcript-yt-com's own page on 2026-11-10
Document
Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page