Home › Blog › VeilMate Guides › Why an Overlay Beats a Redirect
EN中文日本語DeutschESFR

Why a Privacy Curtain Beats a Page Redirect (Nothing Reloads) (2026)

Two privacy locks can look identical on screen and behave nothing alike under the hood. One navigates the tab to a lock page; the other draws a layer over the page that is already there. The difference shows up the moment you unlock.

This is a plain-language explanation of the two architectures, their trade-offs, and why the overlay model preserves work.

Architecture one: navigate to a lock page

The simplest implementation redirects the tab to an internal lock URL. There is no overlay to maintain, and the original page is gone from view. It is also destructive:

Architecture two: overlay in place

An overlay keeps the page loaded and covers it with a layer. VeilMate uses a closed shadow DOM, so the covering UI is isolated from the page's own styles and scripts, and the page cannot easily read or remove it. Clicks, scrolling, typing, wheel, drag, copy and right-click are swallowed while the lock is on.

Because the tab never navigates, unlocking returns to the exact state: the half-written form, the paused video at its timestamp, the scroll depth. No reload, no resubmit prompt, no lost draft.

Why the lock survives a restart

The lock state is stored locally, so a browser restart does not clear it. A new session starts covered until the password is entered. The same storage is what makes the automatic triggers possible: idle, focus-loss, browser start and the system-lock link all set the same state.

The trade-offs, stated plainly

Which model fits

If the lock is meant to protect a kiosk or a shared terminal where losing page state is acceptable, either model works. For a working browser with forms, videos and long reading sessions, the overlay is the only one you will keep using — a lock that costs you the draft is a lock you disable after the second interruption.

Cover the screen, keep the work

Privacy should not charge you a reload every time. An overlay covers what is on screen and leaves everything underneath exactly as it was — which is why it survives contact with a real workday.

FAQ

Is an overlay as secure as a redirect lock page?

They protect against different things. Both hide the screen from a bystander. A redirect removes the page from the tab; an overlay leaves it loaded underneath. Neither is encryption, and both can be bypassed by disabling the extension.

Why does a redirect lock lose my form data?

Because navigation replaces the document. Unless the site saved a draft, the input values live only in the page that was navigated away. An overlay never navigates, so the values stay.

Does the overlay work on every website?

VeilMate draws a closed shadow-DOM layer over each page, which isolates it from the site's styles and scripts. Pages with unusual full-screen behavior can still be covered; the overlay is independent of the page's layout.

Can the page detect or remove the overlay?

The shadow root is closed, so the page cannot easily read or modify the covering UI. The extension still runs in the browser, so disabling or removing it is the real bypass — which is why the honest note says this is a privacy screen, not encryption.

More guides in the VKT blog; questions to [email protected].

Keep reading

Password-Protect Browser Tabs Without Closing Them (2026)
How to Hide Every Browser Tab Instantly (Boss Key) in Chrome and Edge (2026)
All VeilMate guides