legal

Privacy Policy

Privacy expectations for AnyVidDL web, extension, API, and MCP workflows.

Last updated
2026-06-14
Author
AnyVidDL content team
Reviewed by
AnyVidDL Trust Review

AnyVidDL should not ask for your platform account password to analyze public or permitted links. Advanced workflows may need temporary task data, API keys, queue metadata, and logs, but should avoid storing private media or credentials unless explicitly documented.

Direct answer

AnyVidDL should not ask for your platform account password to analyze public or permitted links. Advanced workflows may need temporary task data, API keys, queue metadata, and logs, but should avoid storing private media or credentials unless explicitly documented.

Data AnyVidDL should avoid collecting

  • Platform account passwords.
  • Private account content.
  • DRM keys or paywall credentials.
  • Unnecessary personal profile data from source platforms.

Operational data that may be needed

  • Submitted public or permitted URLs for parsing.
  • Temporary task status, output options, and failure reasons.
  • API keys, rate-limit metadata, and audit logs for approved advanced workflows.

Retention principle

  • Keep task data only as long as needed for parsing, delivery, support, abuse prevention, or audit requirements.
  • Do not use submitted links to claim ownership over the original content.
  • Document retention separately for web, extension, Pro, API, and MCP workflows.