WPColt Cache Inspector is planned as a read-only diagnostic plugin. That matters. A cache diagnostic tool should not need to rewrite your configuration, purge private data, or send unnecessary site information to an outside service just to explain whether a page is being cached.
Read-only philosophy
The first version is designed to inspect active plugins, public request behavior, safe WordPress environment signals, and HTTP response headers. It should not change cache settings, edit server configuration, create CDN rules, or modify content.
What the plugin scans
- Public homepage and post responses as a logged-out visitor.
- Cache-related response headers such as Cache-Control, Age, X-Cache, X-Varnish, and CF-Cache-Status.
- Known WordPress cache plugins and object-cache drop-ins.
- Signals that indicate Redis, Memcached, server cache, CDN cache, or bypass behavior may be present.
What data leaves the site
The target design is local diagnosis first. If future versions add remote reporting, account sync, alerts, or hosted history, those features should be documented separately and should explain exactly what is transmitted, stored, and deleted.
Sensitive pages
WooCommerce cart, checkout, account, login, admin, and personalized pages should not be cached as shared public HTML. Cache Inspector treats those patterns as safety-sensitive because a fast page is not useful if it exposes the wrong visitor state.
Responsible reporting
If you believe WPColt has a security issue, use the Contact page with a concise description and reproduction steps. Do not include live customer data, private credentials, or unnecessary server secrets.