Most daily computer frustration is a mode error. You typed a paragraph in the wrong alphabet. Caps was on. A shortcut did the destructive thing because the window underneath was not the one you thought it was. ModeGuard makes the machine state visible, undoes the mistakes that come from getting it wrong, and holds back the ones you cannot undo.
Free tier forever. Pro is a one time $24, not a subscription.
ModeGuard started as one request, rebind a key to switch keyboard language, and grew into the layer that should have been there all along.
Caps, the active keyboard layout and the modifiers you are holding, shown where you can see them, before you write three paragraphs in the wrong alphabet.
Typed a line in the wrong layout? ModeGuard rewrites it in the right one instead of making you delete it and start again.
The shortcuts that delete, overwrite or close without saving can be held for a confirmation, set per application rather than globally.
A low level keyboard hook, so a bound shortcut is genuinely captured rather than fired a moment too late. The layout toggle runs inside the engine, so it is instant.
If a binding collides with something your browser or editor already owns, ModeGuard tells you instead of quietly winning the fight and confusing you later.
Graphite, Midnight, Phosphor, Daylight and Linen. All driven by design tokens, so a theme is data rather than a fork of the interface.
The tray icon is the product. Its colour is the state your machine is in, so you find out before you type the paragraph, not after.
Intercept active, Latin input, nothing being held back. The safe running state.
A secondary layout is live, Arabic or otherwise. This is the light that saves the paragraph.
A protected destructive combination is being held for release. Let go and nothing happens.
An app that sits on your keyboard owes you a straight answer before it asks for anything else. This is ours.
Processed locally, in memory, and discarded. ModeGuard reads key events to work out what state your machine is in. It does not write them to disk, it does not build a history, and it does not transmit them anywhere.
There is no account and no server. The app does not sign you in, and there is no backend for your typing to be sent to even if it wanted one.
The hook exists to detect state, not to record input. That is the whole difference between this and a keylogger, and we would rather say it plainly on the front page than bury it in a policy.
The rescue buffer is the one exception, and it is small. To rewrite a mistyped line, ModeGuard has to remember the last few words you typed. That buffer lives in memory only, is capped, and is cleared the moment you use it or move on.
Full policy: modeguard.app/privacy
The shortcut engine is not what you are paying for. PowerToys and AutoHotkey do that part for free and they do it well. You pay for the guard layer and the rescue, the things that give you back the twenty minutes you lost retyping a paragraph.
No subscription because there is no server behind it. You buy the app, you own the app.
The engine works and the build runs. It is not on the Microsoft Store yet, and we would rather say that plainly than dress it up as shipped.
We are looking for a small group of people who lose real time to mode errors every day. Leave your email and we will send the build over, plus the launch price when Pro opens.
One email when the build is ready, one when it hits the Store. Nothing else.