YT Video Downloader
privacy policy.

Last updated: November 2, 2026.

Who handles your information

YTVideoDownloader at ytvideodownloader.cc is an independently operated product run by an individual. In this policy, “we” means the individual operating the website under that product name. Contact support@ytvideodownloader.cc for privacy questions or requests. This YT Video Downloader privacy policy explains the information used for video processing, Google sign-in, our own usage analytics, account services, and Waffo checkout when available.

Our responsibility covers the processing we carry out and the providers we engage for it. Third-party websites have their own practices when you visit or use them directly. Linking to another service does not make us its operator, but outsourcing a task does not automatically remove our own obligations. This notice describes the current website rather than promising universal anonymity, zero logging, or deletion of every record when a temporary video expires. The service terms explain delivery and billing separately.

Information needed to prepare a video

When you submit a video address, the website receives that link and sends the relevant source information to the processing service to prepare your requested MP4. Supported addresses are normalized to identify the individual video. A job includes operational information such as a random job identifier, processing status, timestamps, temporary file data, and a delivery capability used to retrieve the result. Paid processing is also associated with the signed-in account through credit-reservation and usage records.

Hosting, network, and processing systems handle technical request information needed to respond, protect the service, and diagnose errors. This can include an IP address, request headers, and device or browser information available in a request. An IP address is used for rate limiting on selected account and analytics endpoints. We do not ask you to upload Google passwords, YouTube session cookies, or private source-platform credentials. Avoid submitting links or support attachments that contain personal information unnecessary for the task.

Usage analytics in YT Video Downloader

Our first-party analytics records selected interactions: page views, link submissions, jobs started or failed, files ready, download-link clicks, pricing views, and checkout clicks. An event stores its name, timestamp, allowed site page path, random visitor identifier, and country when available. The browser sends its referring address with the analytics request; the server extracts and stores only the external referring hostname, not the full referring URL, in the analytics event table. Submitted video addresses are not included in those stored analytics event records.

The visitor identifier is kept under ytv_visitor_v1 in browser local storage. It helps estimate repeat visits from a browser; it is not a verified identity, and it can persist until browser storage is cleared. The analytics event table does not store an account email or Google account identifier. This does not make all website requests anonymous, because hosting and account operations process separate information. Usage counts help us understand demand, errors, and the download-to-checkout path. A click is an interaction record, not proof that a download or payment finished.

If you choose Google sign-in, we verify Google's identity response and receive the verified account identifier and email address. Account records contain an internal user identifier, Google identifier, email, role, creation time, and last sign-in time. Roles distinguish ordinary accounts from administrators. We use this information to identify the account, display its records, assign purchased credits, and protect access to administrative information. The current integration does not request access to your Gmail inbox, Google Drive files, or YouTube account content.

YT Video Downloader uses a Secure, HttpOnly, SameSite session cookie named __Host-yt_session, normally valid for up to 30 days, and a short-lived sign-in challenge cookie named __Host-yt_nonce, normally valid for five minutes. The server stores hashed session tokens and expiring challenge records. Signing out invalidates the relevant site session; it does not sign you out of Google everywhere or delete purchase records. Google may process sign-in requests under its own privacy notice. Browser settings can block or remove storage, though blocking necessary session cookies prevents account sign-in from working correctly.

Checkout, credits, and support correspondence

When checkout is enabled, we send the account email, internal buyer identifier, product identifier, order reference, purchase amount, currency, and product or credit metadata needed to create a Waffo checkout. Waffo collects payment information through its payment service. This website does not collect or store full payment-card numbers or card security codes. We retain order references, amounts, currency, payment status, provider identifiers, credit-ledger entries, and paid-job records to deliver and reconcile a purchase, prevent duplicate allocation, investigate disputes, and handle refunds.

If you email support, the mailbox receives your sender address, message, and any attachments you choose to send. Include an order or job reference where relevant rather than a password, full card number, or unrelated identity document. Incoming support mail is stored in our administrator-only inbox, with original messages and included attachments archived in private Cloudflare R2 storage where archiving succeeds. A separate copy is forwarded to the operator’s Gmail mailbox so inquiries can still be received if one storage path fails. Replies sent from the website are recorded in the inbox; replies sent separately from Gmail are not automatically synchronized back to it. Support correspondence can be retained while resolving the inquiry and where reasonably needed for an associated dispute or legal obligation. We may ask for proportionate account-ownership information before disclosing records or making account changes, so another person cannot obtain your history merely by knowing an email address.

Purposes and the legal basis where required

We process links and relevant account or order information to respond to your requested service and fulfill purchases. We use proportionate technical records to secure the site, manage capacity, investigate misuse, reconcile payments, and establish or defend claims. Usage analytics helps assess demand and improve the product. Where data-protection law requires a legal basis, the relevant basis depends on the activity: performance of a contract or requested pre-contract steps, legitimate interests subject to applicable safeguards, legal obligations, or consent where required.

This policy is not a substitute for any consent required for non-essential storage or other processing in a visitor's jurisdiction. Merely browsing the site is not treated by this notice as consent to every described activity. If consent is relied on, you may withdraw it without affecting earlier lawful processing. Browser storage controls let you remove the local visitor identifier, but clearing storage alone does not send an account-deletion instruction or remove previously collected server-side events. Contact us for requests concerning those separate records.

Providers, disclosures, and international processing

Cloudflare supplies hosting, edge delivery, database, and associated infrastructure. Our processing server and its hosting provider handle source requests and temporary MP4 preparation. Google supplies identity verification, Waffo supplies checkout and payment services, and the support mailbox provider handles email correspondence. These providers receive information needed for the functions they perform. The current first-party analytics does not send its event table to an advertising network, and we do not sell that table as a data product or use it for cross-site behavioral advertising.

Information may also be disclosed where reasonably necessary to comply with applicable legal process, investigate fraud or abuse, protect rights and security, or respond to a substantiated rights complaint. A complaint does not by itself authorize unrestricted disclosure of an account's records. Providers can process information in countries outside your own, depending on their infrastructure. Where applicable law requires transfer safeguards or another valid transfer mechanism, those requirements must be met; this notice is not a claim of certification, guaranteed local-only hosting, or universal adequacy of every destination.

Retention, temporary files, and deletion

Prepared MP4 files are normally scheduled to expire about 15 minutes after becoming available. File expiry is an operational delivery rule, not a guarantee that every related log, support message, account record, or payment record disappears at the same moment. Analytics events are scheduled for daily cleanup after they become more than 90 days old, so actual deletion can occur after that threshold if a scheduled task is delayed. Expired sessions and sign-in challenges are also subject to cleanup.

Account records remain while needed to operate the account and deal with related obligations. Payment, credit, support, security, and dispute records may need longer retention for reconciliation, fraud prevention, legal requirements, or the establishment and defense of claims. There is no single fixed deletion period covering all those categories. We assess the relevant purpose and obligations when handling a deletion request, remove or de-identify information where appropriate, and explain material retention exceptions. Provider backups and logs can have separate lifecycle controls; temporary file expiry should not be understood as an immediate purge of all provider systems.

Security, account choices, and your rights

We use measures including encrypted HTTPS connections, hashed site-session tokens, verified Google identity responses, access-controlled account routes, and separate administrator permissions. No internet transmission or storage system can be guaranteed perfectly secure. Keep your Google account and devices secure, treat temporary download links as private access links, and report suspected unauthorized access promptly. These precautions do not waive our duties concerning security incidents or permit us to disregard legally required notifications or remedies.

Depending on applicable law and your circumstances, you may request access, correction, deletion, restriction, portability, or an objection to certain processing. You may also complain to a competent data-protection authority. Email support@ytvideodownloader.cc with a clear description and the account email or relevant identifier. We will verify requests proportionately and respond within the period applicable to the request. Some rights have legal exceptions, but making a privacy request does not require a purchase or surrendering a mandatory consumer right.

Children and policy updates

The service is not directed to children, and accounts and purchases are intended for adults with legal capacity. We do not knowingly collect children's information for an account or purchase. If you believe a child has provided personal information, contact us with enough detail to locate the relevant record without sending unnecessary sensitive documents. We will review the report and take steps required by applicable law, including deletion where appropriate.

We will date revisions to the YT Video Downloader privacy policy on this page and provide additional notice where a material change or applicable law requires it. A policy update does not retroactively supply consent for a new incompatible use of information already collected. For current purchase and delivery conditions, read the terms and refund policy; for your balance and recent paid records, use the account page. Questions about this policy, provider processing, or retention can be sent to the published support address.

YT Video Downloader privacy policy.