Privacy, without the fine print
MoniTweak doesn't have a privacy policy in the usual sense, because it doesn't collect anything to write a policy about. Here's the actual, verifiable detail.
No telemetry
No usage analytics, no crash reporting service, no A/B testing, no “anonymous” pings home. MoniTweak has no code path that sends data anywhere.
No account
No sign-in, no email address, no license key tied to your identity. Download it, run it, that's the whole relationship.
No internet connection required
Every control talks to your monitors over DDC/CI or to your GPU driver — both entirely local. MoniTweak runs the same with the network cable unplugged.
No admin rights
MoniTweak installs and runs entirely inside your user profile. It never asks Windows for elevated privileges.
One JSON file. That's it.
%LocalAppData%\MoniTweak\settings.json
Your presets, schedules, hotkeys, display names and preferences — written atomically, with a settings.json.bak backup. This file never leaves your machine unless you copy it yourself.
%LocalAppData%\MoniTweak\logs
Rotating local diagnostic logs, with your Windows username redacted. Useful if something goes wrong; useless to anyone but you, because nobody but you can read them.
The diagnostics export, when you trigger it
Settings > Diagnostics can build a ZIP with your configuration, display snapshots, raw MCCS capability strings and logs — for troubleshooting you choose to do, shared however you choose to share it. MoniTweak flags if it contains hardware IDs or custom names before it's written, and never sends it anywhere on its own.
Verify it yourself
Run MoniTweak with a network monitor (Wireshark, or even Windows' own Resource Monitor → Network tab) open. There's nothing to see — no outbound connections, ever.
MoniTweak's application source stays private for now, but the release artifacts you download are checksum-verified — see Download for the SHA-256 values published with every version.
Judge it with your firewall open
Free, local, and happy to be watched while it runs.