Auto-Lock the Browser When You Step Away (Idle and Focus-Loss) (2026)
Manual locks work until the one time you forget. The gap is almost always the same: you stand up for a coffee, get pulled into a conversation, and the browser sits open behind you.
VeilMate offers five automatic triggers for exactly that gap. One is free, four are part of the licence, and each one covers a different kind of absence.
The five triggers
- Idle auto-lock (free) — after a period without activity, the curtain engages on its own; the default is 10 minutes and the range runs from 1 to 240.
- Focus-loss lock (licence) — a few seconds after you switch to another application, the browser is covered.
- Lock at browser start (licence) — a new browser session begins covered, so a restart never opens straight into your tabs.
- System-lock link (licence) — when the operating system locks, the browser curtain follows.
- Scheduled lock (licence) — the browser is covered at a time you set, 18:00 out of the box, every day or on weekdays only.
They can be combined. A common setup is idle auto-lock for the coffee break, focus-loss for meetings, and the system-lock link for the end of the day.
Idle auto-lock: the free baseline
Idle detection is the least intrusive trigger. If you are reading a long page without typing or clicking, a short timeout may be too aggressive; a longer one covers the walk to the printer. Start with a value that matches your desk habits, then adjust after a week. Because the curtain is lossless, a false trigger costs you one password entry, not a reloaded page.
Focus-loss lock: for meetings and shared desks
Switching away from the browser is a strong signal that you are no longer watching it. The focus-loss lock waits a few seconds — enough for a quick app switch and back — then covers the browser. In an open office this is the trigger that earns its keep: the moment you turn to a colleague, the screen is no longer readable.
The same logic applies on a shared desk: when you hand the keyboard to someone else, the browser is already covered.
Set the triggers without locking yourself out
- Open VeilMate settings and set a password first; every automatic trigger depends on it.
- Enable idle auto-lock and choose a timeout that suits your work.
- Add the exempt domains that must stay readable — up to ten on the free tier.
- If you have a licence, enable focus-loss lock, the system-lock link and the scheduled lock.
- Test with a short timeout, then lengthen it once the behavior feels right.
Honest limits
Automatic locks only work while the extension is enabled. They cannot survive removal or disabling in chrome://extensions, cannot cover another browser profile or another Windows user, and cannot stop a forced quit. There is no password recovery. And no trigger can tell the difference between a trusted colleague and a stranger — the exempt list is the only place to encode that judgment.
Make the safe state the default
The best privacy setting is the one that engages when you are not thinking about privacy. Pick one trigger, test it for a day, then add the second. The goal is a browser that covers itself before you notice the visitor.
FAQ
Is idle auto-lock free?
Yes. Idle auto-lock, the lossless overlay, the restart-proof lock and the exempt list are part of the free tier. Focus-loss lock, lock at browser start and the system-lock link require a licence.
Will focus-loss lock trigger every time I switch apps?
It waits a few seconds after focus moves to another application, which tolerates a quick switch and back. If it still feels too eager, disable it and rely on idle auto-lock or the system-lock link.
Does the system-lock link cover the browser when I lock Windows?
Yes. When enabled, the browser curtain follows the operating system's screen lock, so the browser is already covered when you return and unlock the machine.
Can I still read a page while the lock is on?
Only the domains on the exempt list stay readable; everything else is covered. The list is capped at ten domains unless the licence's lock-scope feature is enabled.
More guides in the VKT blog; questions to [email protected].
