WPLaunch

Privacy Policy

Effective date: July 2026

WPLaunch is a Chrome extension that runs a pre-launch audit on WordPress websites. This policy explains what the extension accesses and what it does not collect.

What WPLaunch accesses

When you click "Run Audit" on a WordPress site, WPLaunch reads the HTML of the active tab to detect WordPress signals, meta tags, OG tags, analytics presence, and other page properties. It also sends HTTP HEAD requests to check whether your site's sitemap.xml and robots.txt files exist. All requests go directly from your browser to the target server. No data passes through or is seen by WPLaunch.

What WPLaunch does NOT do

Does not collect, store, or transmit your browsing history
Does not send any data to external servers — there are no WPLaunch servers
Does not use analytics, telemetry, or crash reporting
Does not share any information with third parties
Does not read page content beyond what is needed for the audit checks

Local storage

WPLaunch uses chrome.storage.local to remember which manual checklist items you have ticked for each site. This data stays entirely on your device and is never transmitted anywhere.

Permissions explained

Permission	Why it is needed
activeTab	To read the HTML of the tab you are auditing, only when you click Run Audit.
scripting	To inject the detection script into the active page.
storage	To save your manual checklist progress per site on your device.
host_permissions (<all_urls>)	To send HEAD requests to check sitemap.xml and robots.txt on any domain you are auditing.

Contact

Questions? Open an issue at github.com/amitsharma130291/extension_wp_launch