Exit this page quickly

Problem Context

• Quick exit is most relevant for pages about domestic abuse, stalking, harassment, sexual assault, child abuse, reporting crime or fraud, whistleblowing, immigration risk, debt coercion, health disclosure, or escape planning.
• The pattern protects mainly against immediate over-the-shoulder or room-entry exposure; it cannot by itself erase browser history, network records, device monitoring, spyware, screenshots, downloaded files, or account logs.
• The exit destination must be neutral enough for the local context and should not reveal the sensitive service through title text, referrer behavior, page copy, or obvious related branding.
• The control may appear inside a larger service journey, but the user should learn what it does before the first sensitive page where they may need it.

Selection Rules

• Choose exit this page quickly when being seen on the current page could cause abuse, retaliation, coercion, stalking, harassment, or discovery of plans to avoid harm.
• Use the standalone component on sensitive content pages where the page itself is the risk and the user needs immediate escape.
• Use a full exit-a-page-quickly pattern with an interruption page and safety content when the user enters a sensitive transactional journey.
• Use security warning when the product is warning about unsafe sites, downloads, phishing, malware, mixed content, or certificate risk.
• Use sensitive-data reveal when the user intentionally exposes a secret value for short-term inspection.
• Use session timeout when inactivity or unattended authenticated access is the core risk.
• Use privacy settings for planned control of sharing, tracking, visibility, retention, and data-use preferences.
• Use back link only for ordinary navigation, not as a safety exit from sensitive material.

Required States

• Persistent visible exit control on sensitive pages.
• Secondary assistive-technology activation link or equivalent reachable control.
• Immediate content-covering loading or transition state.
• Neutral destination redirect state.
• Interruption page explaining what the control does before first sensitive exposure.
• Safety content page explaining limitations and safer browsing steps.
• Keyboard focus and screen-reader label state.
• No-JavaScript or slow-network fallback state.
• Mobile compact persistent control state.
• Exit activated, destination failed, blocked popup, and analytics bypass states.

Interaction Contract

• The quick exit control is reachable before the user reaches sensitive content in both visual order and keyboard order.
• Activating the control immediately hides sensitive page content and starts navigation to a neutral destination.
• The exit path does not require confirmation, login, form submission, animation completion, or analytics completion.
• A secondary link or equivalent control provides the same behavior for assistive technology users.
• The interruption page explains the control, its destination, and its limitations before users encounter it in a sensitive transactional journey.
• The safety content explains that quick exit does not clear browser history, stop device monitoring, remove downloaded files, or protect against malicious software.
• The fallback state still gives users a neutral route if scripts fail, navigation is blocked, or the destination cannot load.
• The control avoids using ordinary back navigation as the escape route because history may contain more sensitive pages.

Implementation Checklist

• Identify the sensitive pages, threat model, likely observer scenario, neutral destination, referrer policy, and surfaces where quick exit must be persistent.
• Place the visible control consistently on every sensitive page and ensure it is reachable early in DOM and keyboard order.
• Provide an assistive-technology activation route with the same immediate behavior.
• Implement activation to cover sensitive content immediately before redirecting and bypass nonessential analytics or delayed transitions.
• Create an interruption page before first sensitive exposure and safety content that explains limitations, browser history, monitoring, and safer-device guidance.
• Test mobile compact layout, zoom, keyboard order, screen-reader labels, slow network, failed destination, no-JavaScript fallback, history behavior, and referrer leakage.
• Choose a neutral destination that does not reveal the sensitive service and verify tab title, loading state, and browser history labels.
• Document why the pattern is used, what it does not solve, and what adjacent safety controls handle outside the page.

Common Generated-UI Mistakes

• Using an ordinary Back link or footer Close link as the safety exit.
• Hiding the exit control below sensitive content or making it reachable only after scrolling.
• Showing a confirmation dialog, survey, animation, or analytics wait before hiding content.
• Overpromising that quick exit clears browser history or protects a monitored device.
• Opening a related site, branded page, blank page, or suspicious destination that reveals the sensitive context.
• Forgetting keyboard, screen-reader, no-JavaScript, slow-network, or mobile compact behavior.
• Putting the safety explanation after the user has already entered the sensitive service.

Critique Questions

• What immediate observer risk does this page create, and where does quick exit reduce that risk?
• Can pointer, keyboard, touch, and screen-reader users activate the exit before reaching sensitive content?
• What exactly appears between activation and destination load, and does it hide sensitive content instantly?
• Which neutral destination is used, and could it reveal the sensitive service through title, URL, referrer, or history?
• What does the service tell users about browser history, monitoring, spyware, downloads, and limits of the control?
• What happens if JavaScript fails, navigation stalls, a popup is blocked, or the user is on a compact mobile viewport?
• Is the quick exit pattern paired with other safety content rather than treated as a complete safety solution?