Security & Privacy

If you are suspicious,you are right.

The optimizer category has a bad record: software that gets people banned, installers that bring extras, promises with no measurement. Our answer is not to ask for trust — it is to show what we do, what we refuse to do, and why.

Check it with a network monitor open What we refuse to do

Nothing injected into the game Backs off from kernel anti-cheat 100% local No bundleware Game Mode always reverts Defender untouched

Anti-cheat

Why Maximize does not flag you

The automatic back-off

Deep hardware sensor reading uses a driver that kernel anti-cheat may consider suspicious. So on detecting one, the app switches that reading off by itself — you lose some telemetry charts and gain peace of mind. The app decides, not you.

From the outside

What gets a program detected by anti-cheat is touching the game: injecting a library, reading or writing process memory, altering files, drawing an overlay. Maximize does none of those. It configures Windows — services, power, drivers, timer, and the game never knows it exists.

Overlays are never frozen

Suspending Discord, Steam, NVIDIA or OBS hangs the game when it tries to sync with the overlay. Those processes can be closed, if you choose, never frozen. We learned that by breaking it.

The honest limit

No third-party developer can guarantee the behaviour of an anti-cheat they do not control, and anyone who guarantees it is lying. What can be stated is what the program does, and Maximize does none of the things that typically trigger detection. If a specific anti-cheat objects to the app, we want to hear about it: that becomes a fix, not an excuse.

Privacy

Your data never leaves the machine

This is not a privacy-policy promise — it is an architectural property. There is no server to send anything to. An older version of the product had a cloud layer; it was removed entirely.

Network traffic the app generates

01Licence check, the key only, and deferred while you playrequired

02Update check — deferred while Game Mode is activerequired

03Usage telemetry, behavioural profile, advertising identifierdoes not exist

04Uploading files, program lists or disk contentsdoes not exist

You can verify this without trusting us: open any network traffic monitor and use the app.

The refusals

What we refuse to do, and why

Every row here is a feature that could be sold and that we decided not to have. It is the part of the product that cost the most to exist.

Deliberate decisions not to do something
We do not	Why
Pin CPU affinity	On hybrid processors, a wrong mask hurts performance.
Touch Windows Defender	Tamper protection blocks it; it is a real security risk; and some anti-cheats check antivirus state.
Write CPU, RAM or motherboard clocks and voltages	That is firmware. Software cannot do it safely: we point you to the BIOS instead.
Offset NVIDIA GPU clocks	It would require an API whose structures could not be validated on hardware. An error there corrupts memory and takes down the driver.
Auto-overclock video memory	The driver accepting a value does not mean stability. GDDR corrects errors silently: it does not crash, it just loses FPS. Rebound effect in its most expensive form: you would blame the optimizer, correctly, with no error showing anywhere.
Flash the BIOS automatically	An interrupted write bricks the board. We detect and warn; we never write.
Obfuscation, anti-debug, VM detection	Negative return. They delay releases, break diagnostics and get bypassed with off-the-shelf tools.
Bring the cloud layer back	Removed by decision. The product is local; the only service is licensing.

The removals

And what was in the product and left

These were implemented, tested and removed — each made worse what it promised. The list exists internally so nobody repeats the experiment three months later.

periph-input-queueRemoved

Looked like: Smaller input queue = less buffering = less input lag. A widespread forum myth.
What happened: The queue does not reduce latency; it is overflow capacity. With a 1000 Hz mouse and a queue of 20, a DPC spike above ~20 ms drops events, including the click. In CS2: crosshair on target, shot does not register.

net-disable-nagle · net-tcp-tuningRemoved

Looked like: Less network latency, less bufferbloat.
What happened: They are TCP-only settings, and competitive games use UDP. And they only applied after restarting the interface, which Game Mode never does. Worse: verification reported “applied” because it read the registry instead of the effect.

sys-dynamic-tickRemoved

Looked like: More predictable timer, less jitter.
What happened: Raised interrupt and DPC frequency: microstutter and more irregular frametime, the opposite of the promise.

Restart-NetAdapterForbidden practice

Looked like: The network driver only re-reads its configuration on interface restart, so restart it.
What happened: It drops the link for 5 to 15 seconds, worse on Wi-Fi. And Game Mode usually activates after the game opened its connection: it disconnected the player mid-match. We traded "harmless" for "actively harmful".

The frametime lab lets you switch each one back on and watch the damage happen on the trace.

Safeguards

What must never regress

Some guarantees cost a lot to exist and are locked down by automated tests. If one disappeared in a refactor it would be a regression, not a decision.

Reverting is never paid, including with an expired licence.
Network never demotes a paying customer: offline is "awaiting revalidation", never "expired".
The snapshot stores your value, and reverting removes the key if it did not exist before.
Restore point before destructive change: registry, services, privacy, bloatware.
Protected processes and overlays are never touched.
The tool stays out of the match: updater and scheduler defer heavy work while Game Mode is active.
Verified signature on any external binary the app loads.

And what does NOT revert

Game Mode, overclock and auto-tune revert by themselves, always, that is what the snapshot is for. But deleting files, removing pre-installed apps and shredding files are final operations. The Cleaner does not go through the recycle bin; the bloatware remover does not reinstall what it removed (you reinstall from the store); and a Windows restore point does not bring packages back.

That is why those operations create a restore point first, warn first, and never run unless you tell them to. We would rather say it here than have you find out later.

The best way to check is to use it

The free version asks for no sign-up and uninstalls cleanly. Leave a network monitor open while you use it, if you like.

Check it with a network monitor open See pricing