Privacy Policy
What Chrome Extension Tools does and does not collect, how files are processed locally in your browser, and what our hosting provider logs.
Last updated: 5 October 2026
The short version
File tools run entirely in your browser. Files you choose are not uploaded. There are no accounts, no analytics, and no advertising. The one tool that makes a network request is theChrome Extension Downloader, and that request goes to Google's own extension endpoint, not to us.
What we do not collect
Concretely, this site has no code that:
- uploads the files you select, or their contents;
- stores anything you type into a tool, including manifests and permission lists;
- sets cookies, or uses local storage to identify you;
- runs third-party analytics, advertising, or tracking scripts;
- asks you to create an account, and has no database to store one in.
How files are handled
The CRX to ZIP converter,Manifest Viewer,Extension Inspector,Manifest V3 Validator andPermission Checker all accept files or pasted text. In every case:
- the file is read with the browser's File API into the page's memory;
- parsing happens in your browser using JavaScript that ships with the page;
- results are displayed in the page, and downloads are handed to the browser;
- nothing is transmitted, because the site has no server-side code to transmit it.
Closing or reloading the page discards everything. Opening a packaged extension in one of these tools does not extract files to your disk, does not install anything, and does not execute anything inside the package.
The download tool, and the one external request
When you select Download CRX file, your browser navigates to Google's Chrome Web Store extension endpoint at clients2.google.com. That request necessarily includes the extension ID you supplied, along with your normal IP address and user agent — exactly as if you had clicked download inside Chrome itself.
This site cannot read the response. Google's endpoint sends noAccess-Control-Allow-Origin header, so the browser will not let the page read it. That is why the tool reports "download requested" rather than "downloaded": it genuinely does not know the outcome.
No proxy or server-side component sits in between. The request goes from your browser to Google directly.
What our hosting provider sees
This site is hosted on Cloudflare Pages as static files. Like any web host, Cloudflare processes the network request needed to deliver each page. That necessarily includes your IP address, the URL requested, your user agent, and the time of the request.
We cannot see individual visitor records, and this site has no access to Cloudflare's account or analytics dashboards. We are not able to enumerate who visited, and we do not attempt to.
Cloudflare's handling of this data is governed by its ownprivacy policy.
Third-party links
Pages here link to Google's Chrome extension documentation and, from the downloader, to Google's endpoints. Following one of those links takes you to a site governed by that operator's privacy policy, not this one.
Children
The site is a developer tool and is not directed at children. We do not knowingly collect personal information from anyone, of any age.
Contact
Questions about this policy can go to the contact page. If a future change to this site ever introduces analytics, advertising, accounts, or file uploads, this page will be updated to say so before that feature is live.
This document describes the implementation on https://chrome-extension-tools.pages.dev as built on 5 October 2026. It is not legal advice.