Our Chrome Extension "RoboX" is a client-side SEO analysis tool. The protection of your data is central to its design architecture:

• Local Processing: All analyses (e.g., HTTP status & redirect checks, robots.txt parsing, meta tag/canonical evaluation, sitemap validation, link extraction, and search engine/AI crawler rendering simulation) are performed exclusively locally in your browser.
• Local Storage & Caching: To improve performance, enable monitoring features, and save your preferences (e.g., language selection, background check settings, UI preferences, custom User-Agents), the extension caches data locally in your browser using the Chrome Storage API. For features like "Technical SEO Change-Monitoring" and the "Robots.txt Archive", explicitly saved SEO snapshots (baselines) are stored persistently on your local device. Volatile data, such as HTTP headers and redirect chains, is held in the temporary session storage strictly for the active tab and is cleared automatically. This data never leaves your device.
• No Data Transmission: The extension does not transmit any personal data, browser history, or analyzed content to Wingmen servers or third parties (no tracking, no analytics).
• Technical Requests & Simulation: To function, the extension must perform HTTP requests to the URLs involved in your current page load (this includes the website you are actively visiting, its redirect hops, and target URLs of canonical tags) to fetch necessary technical files like the /robots.txt or Sitemap XML. For the custom bot simulation features ("Simulate Bot" / "Render as..."), the extension temporarily and locally modifies your browser's User-Agent and blocks specific resource requests to simulate the selected crawler's behavior. These requests originate directly from your IP address to the respective target servers and are technically necessary to retrieve the required SEO data.
• Permissions: The extension requests permissions to access website data solely to read the technical SEO directives (HTTP Status Codes, Redirect Chains, Meta Robots, Link Canonicals, and X-Robots-Tags) as well as on-page links and web performance resources of the page ecosystem you are actively analyzing, and to temporarily modify network requests for the rendering simulation.