LEGAL
Privacy Policy
A clear account of what EveryVids processes when you use its tools.
Public links and YouTube data
The homepage link check runs in your browser. When you submit a YouTube metadata tool, EveryVids sends the normalized public video or channel link to its server. The server requests public metadata through YouTube API Services. It does not request your YouTube password, account access, private videos, or media streams.
Short-lived storage
Normalized public video and channel metadata may stay in an in-memory cache for up to five minutes. This avoids repeating the same provider request. The cache does not contain API keys, request headers, raw provider errors, video or audio bytes, thumbnail files, cookies, or user accounts.
Abuse protection and logs
The current service uses a server-side salted anonymous rate-limit identifier for about one minute, plus bounded cleanup time. It does not intentionally retain raw IP addresses in application rate-limit state. Application logs use a random request ID, operation, timing, cache status, and safe error category. They do not intentionally include submitted links, video titles, descriptions, API keys, provider bodies, or DNS answers.
Other services
YouTube metadata tools use YouTube API Services. Their use is also covered by the Google Privacy Policy. Thumbnail and channel images load directly from an approved YouTube image host, so that host receives connection details such as your IP address. EveryVids does not proxy or store those image files.
Hosting limits
A hosting provider or reverse proxy may keep ordinary access logs. EveryVids sends submitted links in a POST body rather than a query string, but hosting-level body logging must still be disabled and reviewed before public metadata activation. Retention for hosting logs depends on the selected production provider.
Your choices
Do not submit a link if you do not want the server and YouTube API Services to process it. You can still use the local Video ID Finder and direct Channel ID Finder without a metadata request. See the Terms of Use for the product boundaries.