Privacy Policy boring Cache Check

Prominent in-product disclosure

Before the user starts a check, the initial popup visibly states:

Checks this page’s URL, response headers, supported cache markers, WordPress login context, and local load timing. Processed locally and kept only for this browser session.

Selecting Check this page starts the processing described in that disclosure. Version 0.2.4 adds this prominent in-product notice without changing which data the extension handles, how it is used, or how long it is kept.

Data the extension handles

When the user selects Check this page, the extension temporarily handles:

• the active tab identifier;
• the current page URL and hostname;
• the next main-frame response URL;
• the HTTP response status code;
• the local start and completion time of the requested check;
• the HTTP response headers visible to the extension for that response;
• narrowly scoped cache metadata from the loaded document, currently WP Rocket generator metadata and its cache-footprint comment;
• standard WordPress login markers, currently the logged-in body class and presence of the WordPress admin bar;
• the current document’s local Navigation Timing values for page load, first response byte, and completed DOMContentLoaded;
• the locally generated cache interpretation.

This information is used only to provide the cache-check result requested by the user.

Local, temporary processing

All analysis happens locally in the browser. The page-level check looks only for supported cache-identification patterns. It does not retain unrelated page markup.

WordPress login detection is limited to whether the page exposes a standard logged-in marker. The extension does not read a username, account identifier, role, capability, or whether the user is an administrator. Navigation Timing contains browser-generated durations for the single user-requested reload.

Cookie and authentication response-header values are replaced with [redacted] before the response report is stored, displayed, or copied. The extension may show the corresponding header names so the report remains technically useful, but it does not keep their sensitive values.

The current check state and result are kept in chrome.storage.session, an in-memory extension storage area. This lets the result remain available after the popup closes during the page reload. The extension does not use persistent local storage or synchronized storage for URLs or results.

Session data is cleared when the tab navigates or closes, and Chrome also clears session storage when the extension is disabled, reloaded, or updated, or when the browser restarts.

What the extension does not collect or share

boring Cache Check:

• does not send URLs, headers, results, or any other data to the developer;
• does not send data to third parties;
• does not use analytics, telemetry, advertising, or tracking;
• does not create a persistent browsing or check history;
• does not extract visible page text, form data, request cookies, request bodies, or personal communications;
• does not retain cookie or authentication response-header values;
• does not read WordPress account names, roles, or capabilities;
• does not treat local load timing as analytics or retain a performance history;
• does not sell data;
• does not use data for credit decisions or advertising;
• does not allow humans to read user data; and
• does not load remote code, remote scripts, remote fonts, or remote assets.

The only network activity initiated by the extension is the normal reload of the page the user explicitly asks it to check.

Permissions

• activeTab provides temporary access to the current page after the user invokes the extension.
• webRequest lets the extension observe the response headers for the user-requested main-frame reload.
• storage provides temporary in-memory storage.session state so the result survives the popup closing during reload.
• scripting runs a read-only, user-initiated main-frame check for supported cache metadata, HTML comment footprints, standard WordPress login markers, and local Navigation Timing after the page loads.

The extension does not request permanent host access.

Limited use

The extension’s handling of the current page URL, response metadata, supported cache footprints, WordPress login context, and local navigation timing is limited to its single user-facing purpose: showing the cache check the user requested. Data is not transferred, used for advertising, or made available for human review.

boring Cache Check’s use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Changes

Any material change to these practices will be documented here and in the Chrome Web Store disclosure before it takes effect.

Contact

For privacy or support questions about boring Cache Check, contact: tools@boringworks.eu

Chrome Web Store policies can change. This policy should be reviewed against the current Chrome Web Store user data policy before publication or material updates.