What FeedInspector does not keep as a product feature
No user accounts.
No saved workspaces or dashboards.
No user-facing history of previous runs.
Privacy
Last updated April 12, 2026
FeedInspector is built for live checks of public feed and channel URLs. This page explains what the site has to process to answer a request, what may show up in logs, and what not to send through a public tool.
What you submit
When you use a tool, you submit a public URL or a related input such as a YouTube handle. FeedInspector uses that input to fetch, resolve, parse, or convert the requested resource and return the result on the page.
What the service processes during a request
- The input needed to run the tool, such as a feed URL or YouTube identifier.
- The fetched response, parse output, and tool-specific derived fields needed to build the result.
- Standard server, reliability, and security logs used to keep the service running and to detect abuse.
Logs, analytics, and ads
Basic analytics and performance tooling may be used to understand traffic, uptime, page speed, and failures.
Google AdSense scripts may load on some public tool pages.
About, Methodology, Privacy, and Terms stay ad-free.
What not to submit
Do not submit secrets, authenticated URLs, private endpoints, signed URLs, or confidential feed sources. FeedInspector is meant for public or otherwise non-sensitive inputs.