Legal

Privacy Policy

What data the current AnyVidDL web product processes for link analysis, downloads, analytics, and operational logs.

Last updated
2026-10-12
Author
AnyVidDL content team

The current AnyVidDL web product processes submitted URLs as needed to analyze and deliver requested media, while product analytics are designed not to record the full submitted media URL, cookies, access tokens, or unnecessary personal data.

Direct answer

The current AnyVidDL web product processes the URL you submit when that is necessary to analyze the source and execute the download workflow. Product analytics are intentionally narrower: they must not record the full submitted media URL, cookies, access tokens, or unnecessary personal information.

Data used by the current web workflow

  • The submitted public or permitted URL, as required by the parser and download execution path.
  • Result metadata such as media kind, quality, delivery type, merge requirement, result code, timings, and request identifiers.
  • Operational server logs needed for reliability, abuse prevention, and troubleshooting.
  • Temporary files created by the download execution path when the runtime needs to prepare a file.

Product analytics boundaries

Analytics may record landing path, locale, platform category, format kind, quality bucket, merge requirement, result code, timings, and request identifiers.

Analytics must not record:

  • the full submitted media URL;
  • cookies;
  • access tokens;
  • platform passwords;
  • DRM keys;
  • unnecessary personal identity data;
  • sensitive information embedded in a downloaded file name.

Accounts and third parties

Any account or sign-in data is handled only where the site actually exposes that account flow. Third-party infrastructure may process requests needed to host the site, analyze a source, deliver a file, or collect permitted analytics. This policy does not claim that unlaunched Pro, extension, public API, or MCP products exist.

Retention

Retention must follow the operational need of the specific data class rather than an indefinite archive. Temporary download artifacts and logs should be removed according to the active server configuration. This page does not invent a retention duration that is not verified in the running environment.

Questions and deletion requests

A dedicated privacy request channel must be published before the site claims a guaranteed deletion-request workflow. Until that operational channel is verified, this page describes the current product behavior without inventing a contact mechanism.

Related pages