Privacy Policy for Twitch VOD Downloader
Last updated: October 25, 2026
1. Who we are
Twitch VOD Downloader is an independent tool available at twitch-vod.download for downloading and processing supported Twitch videos and clips.
In this policy, "we," "us," and "our" refer to that operator. Twitch VOD Downloader is not affiliated with, sponsored by, or endorsed by Twitch.
This policy explains how we handle personal data when you visit the website, submit a Twitch link or channel name, use an extension-assisted download workflow, purchase or activate download credits, or contact us.
The companion extension's permissions and any additional extension-specific processing must also be read together with its Chrome Web Store disclosures. This policy describes the extension-assisted website workflow; it does not imply that every permission or independent behavior of the extension has been audited.
This policy provides information about data processing. Visiting the website does not, by itself, constitute consent to processing for which separate consent is legally required.
2. Information we process
Links, channel information, and download requests
When you use the downloader, we process the information necessary to resolve your request. Depending on the feature, this can include:
- The Twitch video or clip URL you submit.
- A channel name or identifier used to look up clips.
- Video, clip, or channel identifiers.
- Source metadata, such as titles, thumbnails, duration, available qualities, and playlist or media addresses.
- Your selected format, quality, and start/end range.
- Download, conversion, or file-saving status and related errors.
Some of this information describes public Twitch content, but it can still be personal data when it identifies a creator or is associated with your request, license, or other identifying information.
Submitting a public link does not make the download workflow fully offline. The website, its backend, the companion extension where required, Twitch, and media-delivery services can participate in resolving or transferring the requested content.
Technical and request information
Our hosting infrastructure and service providers process information needed to deliver and protect the service, such as:
- IP addresses and request timestamps.
- Requested pages, API endpoints, and query parameters.
- Browser, device, and operating-system information supplied with requests.
- Referrer information, where the browser provides it.
- Response status, errors, and diagnostic information.
Request addresses, query parameters, and diagnostic records can contain submitted Twitch links, channel names, media metadata, or license-related identifiers. Do not treat a submitted link or license activation link as anonymous.
Purchases, credits, and licenses
If you purchase or activate paid features, we process information needed to issue and manage your purchase, including:
- Your email address.
- Payment-provider customer, order, and checkout identifiers.
- Product, amount, currency, and payment or refund status.
- License keys, activation details, and credit allowances.
- License status, creation and expiration dates, where applicable.
- Video identifiers associated with licensed usage or credit consumption.
Stripe hosts the payment checkout and processes payment details you provide there. Our application receives customer and transaction information from Stripe to fulfill and manage the order; it does not ask you to enter a full card number into the downloader's own form.
Support communications
If you email us, we receive your email address, your message, and any information or attachments you choose to provide. Please do not send passwords, full payment-card details, or unrelated sensitive information. Share license details only when necessary to resolve your request.
Browser storage
The website uses browser storage for functions such as remembering a license, keeping submitted-link history, managing notices, and recovering from loading failures. Section 6 explains these uses.
3. Why we use this information
We use the information described above to:
- Deliver the website and resolve supported Twitch links.
- Retrieve clip or channel metadata and provide download options.
- Carry out supported download, trimming, and conversion workflows.
- Remember locally saved information and recognize an activated license.
- Issue credits and licenses, verify entitlements, and account for usage.
- Send transactional messages, including license activation and order information.
- Respond to support and privacy requests.
- Investigate errors, misuse, payment disputes, and service failures.
- Understand paid-order activity and maintain business records.
- Meet applicable accounting, tax, legal, and regulatory obligations.
We do not treat a purchase or support message as consent to unrelated marketing.
4. Legal bases where data-protection law requires them
Where the GDPR, UK GDPR, or similar rules apply, the legal basis depends on the purpose:
| Purpose | Applicable basis |
| Provide a requested service, fulfill an order, and manage a paid license | Performance of a contract, or steps you request before entering one, where applicable. |
| Operate the website, diagnose failures, protect the service, and handle support | Legitimate interests in operating a reliable service, where those interests are not overridden by your rights; contract where relevant. |
| Maintain required financial records and respond to legally binding requests | Compliance with a legal obligation. |
| Analyze paid-order activity | Legitimate interests in understanding and administering the business, where legally permitted and following an appropriate assessment; consent if the particular processing requires it. |
| Optional cookies, tracking, or other processing requiring permission | Consent, where required by applicable law. |
Where we rely on consent, you may withdraw it without affecting the lawfulness of processing carried out before withdrawal. Where we rely on legitimate interests, you may object as described in section 10.
Declining information necessary to fulfill an order or validate a license may prevent us from providing the corresponding paid feature.
5. Service providers and other recipients
We use external services to operate the website and fulfill purchases. They receive information relevant to their role and may have their own obligations and privacy notices.
Cloudflare
Cloudflare provides infrastructure used for website delivery, request handling, caching, and application storage. This can involve technical request information, cached source metadata, and license records stored through the service.
Twitch and media-delivery services
Twitch endpoints and associated media-delivery services receive the identifiers or requests needed to resolve and deliver supported content.
When your browser or extension connects directly to these services, they can receive your IP address, browser/request information, and any data your browser supplies according to its settings. When our backend resolves a clip, the backend communicates with Twitch on your behalf.
Stripe
Stripe processes checkout and payment activity. It can receive information you enter during checkout, technical and fraud-prevention information, and product or order metadata supplied by us. We receive the customer and transaction information needed to issue and administer your purchase.
Stripe may process some information for its own legal, security, and payment-service purposes as described in its notice.
Google-powered transactional email
The order-email workflow uses Google Apps Script and Google's email infrastructure to send purchase and activation messages. That workflow processes the recipient's email address and the message contents, which can include a license key or activation link.
PostHog order analytics
The paid-order workflow sends server-side events to PostHog. These records can include your email address as an identifier, customer and checkout information received from Stripe, order value, and identifiers linking a license to an order.
These events are not anonymous merely because they are analytics events. Server-side order events are also distinct from browser page tracking, advertising cookies, or session replay.
The integrations described here concern the Twitch service. Other websites we operate may have different analytics or advertising arrangements and should be reviewed under their own privacy notices.
Other disclosures
We may disclose relevant information where required by law, to respond to valid legal process, or where necessary and legally permitted to investigate fraud, protect the service, or establish or defend legal claims.
If ownership or operation of the service changes, relevant records may be transferred as part of that transaction, subject to applicable law and appropriate notice.
6. Cookies, local storage, and session storage
Cookies and browser storage are different technologies. A website can store information on your device without using a traditional cookie.
The reviewed website uses storage entries including:
| Entry | Purpose | Duration or removal |
license_key in local storage | Remember an activated license so it can be validated when you use paid features. | Persists across browser sessions until replaced, removed by the application, or cleared through browser settings. Server-side license validity is separate. |
kvd in local storage | Keep submitted-link history and associated timestamps for the website's history feature. | Persists until removed by the application or cleared through browser settings. |
twitch-premium-notice-last-close in local storage | Remember when a notice was dismissed to limit repeated display. | The notice uses a 48-hour repeat window; the stored timestamp is not necessarily deleted when that window ends. |
chunk_reload_attempted in session storage | Prevent repeated automatic reloads after certain application-loading failures. | Normally lasts for the browser tab's session, subject to browser behavior. |
Other session storage may support temporary in-progress download state. Your browser can also cache application resources.
Stripe, Cloudflare, or other providers may use cookies or similar mechanisms when you interact with their checkout or security services. Consult their notices for their own processing.
You can inspect or clear site data in your browser settings and restrict cookies or storage. Clearing local data may remove history, notice preferences, and a locally remembered license. It does not automatically cancel a purchase, delete server-side records, or remove a downloaded file.
Keep your purchase email or license information somewhere safe before clearing storage. Do not share license keys or activation links publicly.
If a feature requires consent for non-essential storage or tracking, that consent must be obtained separately; this privacy notice is not a substitute for that choice.
7. Downloaded files and browser processing
For the supported public VOD workflow, the extension helps obtain source details and playlist information, and the browser requests media and saves output to your selected destination.
For public clips, the website's backend resolves the source address before the browser opens or downloads the media. Supported MP3 conversion is performed in the page after the relevant media is downloaded.
Browser processing does not mean that no information reaches our infrastructure or third parties. Submitted requests, source metadata, technical logs, and paid-feature records are separate from the resulting media file.
Deleting information held by us does not delete files already saved on your device or content retained by Twitch. You control the copies you save and should only download content you are authorized to use.
8. Retention
We retain personal data for the period necessary for the relevant purpose, taking account of the data's sensitivity, license lifecycle, support needs, security requirements, and legal obligations.
Retention is determined by the following criteria:
- Cached source metadata: the cache lifetime needed to resolve requests efficiently; cached data can expire or be replaced. Cache expiry is not the same as deletion of request logs.