Privacy and licence.

Qwerty Tweaks has no account, no sign-in and no telemetry of its own. Nothing about your PC is sent to us, because there is nowhere for it to go. This page is the detail behind that sentence: what the app writes to your PC, what touches the network and when, and the terms it ships under.

Every claim below about the app is taken from its own source, and the build checks this page against it. The one claim about the company that serves these pages was measured on the live pages instead, and says so where it stands.

What is not collected

There is no analytics service, no crash reporting service and no account system in this app. That is not a setting you can turn on, it is the absence of the machinery.

No account and no sign-in. The app has never asked anyone for an email address, and there is no field to enter one.
No telemetry of ours, no usage statistics, no crash reports. Nothing you switch on, switch off or clear is reported anywhere.
No advertising identifier, no device fingerprint and no attempt to identify you or this PC.
Nothing reads your documents, messages, browsing history or files, except the pages that measure disk space, which count file sizes and never open a file.
The app does not run in the background for us. It has no service of ours behind it and no scheduled task of ours.

Windows itself reports diagnostics to Microsoft by default. Two of the app's settings, Telemetry and Error reporting and crash dumps, are what turn that off. That traffic is between your PC and Microsoft, and it exists whether or not you install anything from here.

What the app writes to your PC

One folder holds everything the app keeps, and nothing is written outside it except the Windows settings you switch on yourself. The folder is %APPDATA%\Qwerty Tweaks.

preferences.json: Your settings and which optimizations you have switched on. If the file is missing or unreadable the safe choice is used instead, never the last one.
saved-values.json: The Windows value each setting had before the app changed it. This is what makes a change reversible, including after a restart.
tweak-states.json: A snapshot of the states the app saw last time, so the window paints immediately instead of scanning first. The live check still runs and corrects it.
driver-install-history.json: Which driver updates the app installed for you, and when, so a rollback has something to work from.
logs\qwerty-tweaks.log: What the app did, in plain text, trimmed to the newest 400 lines or 200 KB, whichever comes first. Export logs copies it to the clipboard for a support message.
Reset all app data: The button in Settings deletes all of the above, along with the theme and every warning you have acknowledged. It cannot be undone, and the app says so before it does it.

Restore points are Windows' own, not the app's. The app can ask Windows to create one before a risky change, and can list and roll back to the ones Windows already holds, but they live in Windows and are cleared by Windows. Registry backups the app takes before a change are written under the same folder.

What touches the network

Seven things, and none of them sends anything about what you have switched on.

Windows Update, when you open the driver page. The app asks Windows what updates exist for your hardware, exactly as Settings does. That conversation is between your PC and Microsoft.
The app's own update check, which is not configured here. There is no update server in this build, and the app says so rather than pretending to look. If a feed is ever configured it asks that one address for a small JSON document, sends nothing but the version in its user agent, and gives up after eight seconds.
A support link you click. It opens the vendor's site in your browser, and your browser makes that request. The app itself sends nothing.
The download button on the overview page. The page asks this website's own server whether the installer is there before it offers it to you, and the file comes from here as well. A download is a request to us, and to nobody else.
Making an account, and signing in and out. These three go to this website's own server rather than to anyone else's, which is why they are here at all: the account is what stops the contact form being spent by a script. What is kept is an email address and a password stored only as a salted hash. The session you are given is one cookie, and the section below on this website says exactly what it holds.
The contact page's form, which sits behind an account. No script from the form host sits on that page, or on any other: the form posts to this website's own server, which passes the message on to the form host - SplitForms - which stores it for us to read and forwards it to us by email, so it sits on their servers as well as arriving in ours. What you type is sent only when you press Send, and only a signed-in reader can send at all, which is what stops the form's allowance being spent by a script. The reply address is the one on your account, so the form no longer asks for one. The credit at the foot of the form is a link, not a request: following it is your choice and nothing here loads anything from it.
This website's own pages, as the company serving them measures them. One host answers on .freebuff.page and adds Cloudflare Web Analytics to every page on the way out; the other answers on qwertytweaks.pages.dev and adds nothing at all. Which one you are talking to is the address in your browser bar, and the section below on this website sets out both.

The CPU temperature sensor

Windows has no way to read a CPU temperature, so the app can install a sensor when you ask it to. It is optional: without it the CPU card shows a dash, and everything else works the same.

The driver is PawnIO, a third-party signed kernel driver. The app ships the vendor's own unmodified installer and runs it silently. It is not our code, and we do not modify it.
Two small modules travel with the app and are loaded by that driver. Each exposes one read-only operation: the Intel module reads the temperature registers, the AMD one reads the thermal control register of a Zen chip. Nothing in this app can write to a CPU register through them.
The driver is GPLv2 with a linking exception, the modules and the library it talks to are LGPL-2.1, and their source is published by the PawnIO project.
Remove, on the same page, takes the driver back out through the vendor's own uninstaller and returns the card to a dash.

The licence

You may install and use the app on your own computers. You may not redistribute it, sell it, or ship it inside another product.
The portable build writes nothing to Program Files and leaves no Start Menu entry. It is the same app with the installer's shortcuts left out.
There is no promised performance improvement. The app turns on settings Windows already has, and how much you notice depends on your PC and what you run on it.
The installers are not code-signed, so Windows may warn the first time. The overview page publishes the SHA-256 hash of each file this build produced, which is how you check you got the one we published.

The same summary is set out on a page of its own, with what you may and may not do with the app: the terms.

What ships inside it

Electron and Chromium: The window and the rendering engine. Electron is MIT licensed, and the installed app carries its licence file and Chromium's notices beside the executable, as those licences require.
PawnIO: The optional CPU temperature driver, its library and the two sensor modules, under the licences described above.
IBM Plex Sans: The typeface this website is set in, under the SIL Open Font Licence. The full text ships with the font file as OFL.txt.
Nothing else: No advertising library, no analytics library, no crash reporter and no autoupdater. The build refuses to run if a third party is added to this page; the rest of the app is checked the same way.

This website

No analytics of ours. No page counter, no tag manager, no heat map and no advertising pixel, and nothing here follows you onto another site. Every file these pages use is one this site ships.
What the company serving these pages measures is theirs and not ours, and this page gives both answers rather than one. Nothing in these files counts anything. What is added to them as they are served depends on the address you arrived at. This site's own address, qwertytweaks.pages.dev, adds nothing at all: what your browser receives is the file in this repository, and looking at the page's source will show you that for yourself. On an address ending in .freebuff.page the host inserts Cloudflare Web Analytics, which records a page view and how long the page took to load; by Cloudflare's own published description it sets no cookie, stores nothing on your device, recognises nobody and does not follow you onto another site, and that description is theirs rather than something this build can check. Neither host asks us first, and the script is not ours to remove - which is why this page names it rather than quietly leaving it out. If you would rather not be counted, an ad blocker or a privacy browser blocks it, and nothing here breaks when it does, because no page on this site depends on it.
Every file these pages need is served from the same place as the page, and there is no exception left among the files themselves: the form host's own script used to sit on the contact page, and putting the form behind an account removed it. A build check fails on any third-party script in this site's own files, which is why anything a host adds is described on this page rather than caught by a check: it is not in the files, and it arrives after the checks have read them.
No page here writes anything to your browser by itself: no local storage, no session storage, and no cookie set by a script. There is exactly one cookie, and it is the session you are given when you sign in to the contact form: the server sets it, it is marked so no script can read it, it carries nothing but a random identifier, it is not used to follow you anywhere, and signing out throws it away. Every page you can read without signing in sets nothing at all. That one is measured rather than assumed. Because the only thing stored is a session you asked for, which this site cannot work without, there is nothing here to ask you to consent to - which is why there is no cookie banner rather than one that would have nothing to switch off.
Nothing on this site sends anything anywhere on its own. Your message is carried to the form host by this site's own server rather than by your browser, and that one request happens when you press Send. Both are described above, where the things that touch the network are listed.
The host that serves these files may keep ordinary server logs, as every web server does, and may count the pages it serves. That is the whole of it.

Anything on this page that looks like a promise is also a rule the build checks: the counts come from the app's catalogue, the file names come from the code that writes them, and the privacy and licence statements are read against both. The measurement a host may add is the one exception, and it is the reason it is named here in plain words: it is added to a page by a host rather than written in it, so no check in this repository can see it - the one that reads this page only makes sure this paragraph is still here, and the served pages were measured by hand in a browser instead.