NoWait Privacy Policy

Effective date: 21 October 2026

This policy describes NoWait version 0.5.0, a Chrome extension that filters matched advertising interruptions and provides on-demand inspection of public links. NoWait has no developer-operated backend, accounts, analytics or telemetry.

Information processed

• Website content: Link Finder reads public hyperlinks, labels, download options, relevant public metadata and media/player URLs on pages the user chooses to scan. Permitted embedded documents can also be scanned. Explicit Find through pages inspections fetch and parse bounded public HTML. Page scripts are not executed, and fetched HTML is not saved.
• Web history-related information: NoWait processes current and scanned page URLs, candidate destinations, observed redirect URLs, website hostnames and timestamps to display results and apply protection. It does not request Chrome's browsing-history database or build a complete browsing-history record. Selected scan results and source URLs are retained temporarily in browser session storage.
• User activity: With protection enabled, NoWait uses trusted pointer/click intent and limited navigation/network protection events to identify advertising popups, invisible links and applicable filtering actions. Click intent contains a target hostname, a link/control/background classification and timing; it is processed locally. A bounded session log records protection types, hostnames, reasons and timestamps. NoWait does not record typed text, passwords or a continuous mouse-movement/keystroke history.
• Settings: Theme, protection mode, category switches, pause expiry, website exceptions, streaming compatibility choices and custom blocked domains are stored locally. Temporary tab playback recovery state is stored in browser session storage. Chrome manages granted website permissions.

NoWait does not intentionally collect names, email addresses, health or financial information, location information, personal communications, passwords, authentication cookies or authorization headers. URLs and public labels can themselves contain personal information or signed query parameters. Original destination URLs and fragment keys are preserved where needed for functional copying/opening; they are not extracted for identity profiling. Do not inspect links you are not authorized to access.

Purpose and processing location

Information is used only to provide the advertised protection, link discovery, destination inspection, compatibility and recovery features. Processing and extension storage occur on the user's device. We do not receive scan results, page content, click data or protection logs on a developer-operated server. NoWait does not sell user data or use it for advertising profiles, unrelated purposes, creditworthiness or lending decisions.

Network requests and third-party websites

Scanning the existing page does not send candidate inspection requests. When the user explicitly chooses Check destination or Find through pages, NoWait contacts the selected destination and permitted subsequent hosts. These requests can reveal the requested URL, the user's network IP address and ordinary HTTP connection information to those websites. Those websites handle the requests under their own privacy policies. HTTP(S) inspection requests omit browser credentials and referrers; redirects and new-host permission boundaries are handled explicitly. URL fragments are not sent as part of HTTP requests.

Response status and selected headers, such as Location, Content-Type and Content-Disposition, are read to explain redirects and identify potential files. HTML inspections read bounded HTML in memory, discard it after parsing and do not submit forms or execute site scripts. No file is saved automatically. Opening a link is a user action and uses the browser's normal navigation/download behavior, which can involve that website's own cookies and policies.

Filter lists, fonts and executable extension code are packaged with the extension. NoWait does not download remote executable code, analytics libraries or filter updates during browsing. Filter updates arrive through extension updates. Ordinary browsing and Chrome's extension distribution services remain governed by their respective providers.

Storage and retention

• Preferences and domain exceptions remain in local extension storage until changed, reset where supported or removed with the extension.
• Scan snapshots are held in browser session storage. They become expired after 20 minutes without a snapshot update; expired snapshots are removed on the next access. They are also removed when the source tab closes, through Clear session scans, or when the browser session ends. The 20-minute rule is a logical expiry, not a guarantee of immediate timed deletion.
• Protection history is limited to 100 session entries. Entries older than 24 hours are filtered when the log is updated. Users can clear it through Clear local event history; it ends with the browser session.
• Tab playback recovery ends when the user leaves its hostname, closes the tab, explicitly re-enables filtering or resets recovery. It does not persist across browser sessions.
• Click correlation and other short-lived working state are kept in memory for protection decisions, rather than sent to analytics services.

User choices

Users can keep Shield disabled, choose protection categories and mode, pause filtering, allow sites, enable compatibility, clear local event history and session scans, and revoke website grants in NoWait or Chrome's extension settings. Link Finder scanning and destination inspection require explicit actions. Removing the extension removes its browser-managed extension storage.

Limited Use

NoWait's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only for the disclosed user-facing features and is not sold, used for personalized advertising, or transferred for unrelated purposes. Destination requests described above are necessary to perform the inspection chosen by the user.

Changes and contact

This policy will be updated if NoWait's practices change. Material changes will be disclosed as required before introducing the changed processing. For questions, use the publisher contact information or support options shown in NoWait's Chrome Web Store listing.