Last revised: October 3, 2026 • Status: Active & Legally Binding
At Vidzory, privacy is not an afterthought or an optional toggle—it is built into the physical architecture of our codebase. We do not require registration, do not provide user login accounts, do not harvest passwords, and do not construct marketing profiles or sell user data to advertising exchanges.
When a user initiates a media processing operation (such as merging DASH video and audio, removing an audio track, or compressing an MP4), the target streams are handled in isolated, encrypted ephemeral scratch containers. All generated media packages are assigned automated TTL (Time-To-Live) expiration rules:
To defend our infrastructure against automated denial-of-service floods, credential stuffing, and web scraper attacks, we implement rate limiting. However, we do not store raw, unmasked IPv4 or IPv6 addresses in persistent database tables. Instead:
When you input a URL into the Vidzory resolver, that URL is held in transient memory only for the physical duration needed by yt-dlp and FFmpeg to inspect and remux the requested streams. We do not log, sell, share, or build browsing histories of the links you convert.
Because Vidzory does not store personally identifiable information (PII), create user accounts, or maintain persistent customer records, we practice aggressive data minimization under Article 5(1)(c) of the EU General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA). Any contact requests or takedown notices submitted through our high-security contact forms are retained solely for legal compliance and administrative resolution.