WinLevers — privacy policy

WinLevers has no network code in it at all. There is no HTTP client, no update check, no telemetry endpoint and no crash reporter, so there is nothing for it to send and nowhere for it to send it. Everything it reads about your machine stays on the machine, in four files under your own user profile.

What WinLevers collects about you

Nothing. There is no account, no telemetry, no analytics, no crash reporting and no identifier of any kind. The app has no server of its own to send anything to, and it does not phone home to check for updates — there is nothing to check for — you pull the source and rebuild when you decide to.

What it stores, and where

The journal: A SQLite database under %LOCALAPPDATA%\WinLevers, one row per registry write, each holding the value that was there immediately before it. This is the record of what the app did to your machine, and it is what History reverts from.
Snapshots: A JSON file per batch, written and flushed to disk before the first registry write of that batch. Kept apart from the journal on purpose, so the two cannot be lost together.
Its own settings: Theme, table options and window placement, in a JSON file under %LOCALAPPDATA%. Deliberately not in the registry: a bug in the code that edits the registry must not be able to corrupt the settings you would need to recover.
A diagnostic log: On the same machine, under the same folder. Nothing sends it anywhere; if you want someone to see it you attach it yourself.
Exports: CSV and Markdown of what the grid shows, written wherever you choose in a save dialog. They list the applications installed on the machine, so treat them as you would any inventory of it.

Everything it can connect to

Nothing. There is no network code in WinLevers — no HTTP client, no update check, no telemetry endpoint, no crash reporter and no analytics. It cannot reach anything, and that includes us.

What never leaves your PC

No list of your installed applications, no permission state and no machine identifier leaves the PC, because the app has no means of sending one.
No telemetry, no usage statistics, no update check and no crash reports.
Nothing is written under HKEY_LOCAL_MACHINE. Every value the app writes is a per-user value under HKEY_CURRENT_USER — the same one the Windows Settings app edits.
No registry key has its ownership taken or its access control list rewritten. The app runs without administrator rights on purpose, and a key it cannot read or write as you is reported and left alone.

Safeguards

Nothing is written without a preview: Every route to the registry — bulk edit, the selection bar, the privacy advisor, a saved profile — ends at the same preview dialog, and that dialog is the only place an Apply button exists. The command-line tool prints the same plan and asks first.
A snapshot before every batch: The values a batch is about to overwrite are written to disk and flushed before the first write lands, so an interrupted batch still has a complete record of what it was about to change.
Every write is journaled, then read back: Each write is committed to the journal individually and then read again and compared. A key that accepted the write and kept its old content is recorded as a failure, not a success, and the batch names every one at the end.
A revert never writes blindly: Before putting a value back, the app re-reads it. If something else changed it since, the revert shows the expected and actual values and leaves it alone — a setting you changed back yourself is not silently undone.
It fails closed on shapes it does not recognise: A key holding something the lever does not expect is shown as Unreadable, counted in the preview, and never written into. The consent store is undocumented and can change between Windows updates.

Your rights, and who to ask

Because the app holds nothing about you, there is nothing for the controller to access, correct or erase on your behalf: everything it knows is in files on your own PC, under your own control. Deleting %LOCALAPPDATA%\WinLevers removes everything the app ever wrote: the journal, the snapshots, the diagnostic log and its own settings. Registry values it changed stay as they are, so put back anything you want reverted from History before you delete the folder. For anything else, write to hello@flosforge.eu. The site-wide privacy policy covers this website, your rights under the GDPR, and the supervisory authority you can complain to.

Changes

This statement is checked against each release. If a version changes what the app stores or what it can connect to, the version and date at the top change with it.