What data it uses and where it stays

  • The pages you visit. To show the status code and redirects, the extension reads the headers of the main page of each tab. That information is kept in Chrome's session memory and is deleted when you close the tab.
  • The content of the page you analyze. Only when you open the extension: headings, metadata, links and HTML are processed in your browser and are not sent anywhere.
  • Your DataForSEO credentials, if you add them. They are stored in Chrome's local storage, on your computer. They are used only to request volumes from DataForSEO from your browser. Volumes are cached for 30 days on your computer to avoid repeat queries.
  • Your own user agents, if you add them. They are stored in Chrome's local storage, on your computer.
  • Your Google Natural Language API key, if you add it. It is stored in Chrome's local storage, on your computer. When you ask for the top 10 entities on a Google search, the extension downloads those results from your browser and sends their text to Google's API with your key. At most 100 pages a day.
  • AI assistant searches (fan-out). On ChatGPT, Perplexity and Claude, the extension reads the responses your browser already receives to extract the web searches the model runs and your question. They are kept in Chrome's session memory, for that tab only, and cleared when you close it. They are not sent anywhere.
  • Core Web Vitals metrics. They are measured in the tab with the browser's performance API and are only shown in the extension.

Requests the extension makes

All of them leave your browser, over your connection, and their results stay on your computer: the robots.txt and the unrendered HTML of the page you analyze, the other language versions to check hreflang and, if you have set it up, the DataForSEO API. It never requests addresses on your local network (routers, private IPs), not even when a site redirects to them.

What it doesn't do

  • It has no analytics, no cookies and no user identifiers.
  • It doesn't sell or share data with anyone.
  • It doesn't run code downloaded from the internet: all the code ships inside the extension.

Permissions

  • Access to websites: read headers and redirects and download robots.txt, HTML and hreflang.
  • Active tab and scripting: read the page you analyze when you open the extension.
  • Web requests and navigation: record the main page's redirects.
  • Content settings: disable a site's JavaScript when you ask for it in JS vs HTML.
  • Network rules (declarativeNetRequest): change a tab's user agent when you choose to browse as a bot, and let the page show inside the JS vs HTML comparison. Each rule only affects its own tab and is removed when you close it.
  • Storage: save your settings and the volume cache on your computer.

When you uninstall it

Chrome deletes everything the extension stored on your computer and opens a page where you can tell me, if you want, why you are removing it. That form is optional and reaches me by email.

Contact

Data controller: Nacho Mascort, [email protected]. For the website, the general privacy policy still applies.