Independent guide, not affiliated with the ExplorerPatcher developers. Downloads link only to the official GitHub release.

Privacy policy

This site uses Google Analytics 4 to count visits, loaded only after the page has finished rendering. We run no ads, ask for no accounts and set no cookies ourselves. Our tools work in your browser, so files you drop on them are not uploaded. Last updated 6 Nov 2026.

Checked against ExplorerPatcher 71.1 (26100.9711.71.1) · Nov 6, 2026
On this page

Last updated: 6 November 2026.

The short version

  • We measure visits with Google Analytics 4 (GA4).
  • We show no ads and sell nothing.
  • We have no accounts, comment forms or newsletter.
  • Files you drop on our tools never leave your device.
  • We set no cookies ourselves. Google Analytics sets its own.

Google Analytics 4

The site loads one small script of ours after the page itself. The script waits until the browser has finished loading the page. Only then does it fetch Google’s measurement code from googletagmanager.com. It does this only if a Measurement ID was set when the site was built. If none was set, nothing is loaded and no data goes to Google.

When GA4 is on, we configure it to anonymise IP addresses. Google receives the usual information a web analytics tool receives: the page you viewed, the time, the page that sent you, your approximate location, and your browser and device type. We add no custom events and no user identifiers of our own. Which standard measurements GA4 records is decided in our Google Analytics account, under Google’s terms and privacy policy.

We use the numbers to see which guides people read and which pages are not helping, so that we can improve them.

Cookies and local storage

  • Cookies: we set none. Google Analytics sets its own cookies in your browser when it runs.
  • Local storage: if you press the light or dark button, your browser stores the choice (theme) on your device so the next page matches. We never read it on a server.
  • We do not show a cookie banner at launch. If you do not want analytics, block googletagmanager.com in your browser or with a content blocker, or use your browser’s Do Not Track and tracking protection features. The site works the same without it.

The tools

Our tools run in your browser.

  • The Download Verifier reads the file you pick and computes its SHA-256 with your browser’s own cryptography. The file is not uploaded and its name is not sent.
  • The Configurator, Build Checker, Message Decoder, Cleanup Script Builder, Black Screen Rescue and Which tool? chooser load a small data file from this site and then work on your device. What you type or select stays on your device. The Configurator’s Copy link button puts your choices after the # in the address; browsers do not send that part to a server.

What we do not collect

  • No names, email addresses or accounts, unless you email us.
  • No files, no hashes, no tool inputs and no settings you choose.
  • No payment details. We sell nothing.
  • No advertising identifiers, social media pixels or tracking from ad networks. We show no ads.
  • No fonts or scripts from other companies except Google’s measurement code described above. Our fonts and search index are served from this site.

Download links and many references go to GitHub, Microsoft and other sites. Those sites have their own policies. Our guides link to the project’s GitHub page because it is the only official place to get ExplorerPatcher.

Email

If you email us at hello@explorerpatcher.dev, we receive your address and message, and keep them as long as needed to answer and to fix the page. We do not share them or add them to a list.

Hosting

Like any web host, ours may record technical details such as your IP address, the page you asked for and the time, to deliver and protect the site. We do not use those records to identify visitors.

Your choices and questions

You can use the site with analytics blocked. To ask what we hold about you, or to ask us to delete an email, write to hello@explorerpatcher.dev. If our practice changes, for example if we add ads, we will change this page first and log the change on the corrections page.

Related guides

Report a problem with this pageUpdated Nov 6, 2026