Skip Wait

Privacy Policy

Last updated: August 1, 2026

This policy describes how the Skip Wait Chrome extension (“Extension”) and the Skip Wait marketing website (“Website”) handle information.

1. Scope

Skip Wait is a Chrome extension that, on supported link shorteners and file hosts, bypasses countdown timers and waiting pages or automates waits and continue clicks. It is available from the Chrome Web Store. No account is required.

The Website is the marketing site at skip-wait-website.vercel.app. It describes the Extension and supported flows. Third-party shortener, mediator, and file-host sites have their own policies.

2. Website Analytics

When configured, the Website uses Google Analytics 4 (GA4) via the Google tag (gtag.js) to understand how visitors use the site.

GA4 may collect:

  • page views and in-site navigation
  • approximate location, device, and browser information
  • interaction events such as Chrome Web Store clicks and outbound contact or support links

That data is processed by Google under Google’s terms and privacy policy. See Google Privacy Policy and Google Business Data Responsibility. The Extension does not use Google Analytics.

3. Extension Permissions

The Extension declares these permissions in its Chrome manifest. Each is used only as described below.

Scripting

Runs helpers in the page context on supported unlock flows (for example main-world hooks or visibility helpers). Used only to complete those flows—not for advertising or analytics.

Storage

Uses chrome.storage.local on your device for short-lived progress during multi-step shortener chains, including:

  • Arolinks
  • Cut4Money
  • Nitrolink
  • ShortXLinks-style flows

That data stays on your device and is not sent to us. There is no global on/off preference stored.

Cookies

The cookies permission lets the background worker call chrome.cookies.getAll on certain TipsGuru-family prolink pages when the destination URL is stored in an HttpOnly cookie that page scripts cannot read. Values are processed locally to finish the redirect.

The Extension does not upload those values. It does not use the chrome.cookies API to set or delete cookies.

Web Navigation

Observes supported navigations early enough for bypass flows (for example fast shortener hops and early main-world injects on specific unlock hosts). It is not used to build a browsing-history profile.

Host Access

Declares <all_urls> because supported wait pages and mediators span many domains. Content scripts can load broadly; bypass logic still gates on host checks and only runs on supported flows. Unrelated sites are not modified for that purpose.

4. Extension Data Handling

The Extension does not collect or transmit your personal data, browsing history, or page content to the developer for analytics, advertising, or resale. It does not include analytics, tracking, or telemetry SDKs.

Page Storage and Cookies

On some supported flows, the Extension may read, write, or clear data that those sites already use in the page context, including:

  • localStorage
  • sessionStorage
  • cookies via document.cookie

That happens only to complete the unlock. The data stays in your browser for that site’s flow and is not sent to us.

5. Extension Network Requests

The Extension does not operate a developer backend that receives your browsing data.

Network requests it makes are limited to:

  • the page you are on, or related shortener, mediator, unlock, or file-host endpoints in that same flow
  • helper endpoints required by a supported site’s unlock logic (for example an IP lookup used by the LinkNext mediator via ipv4.icanhazip.com)

Those requests are not used by the Extension for advertising or analytics.

6. Contact Links

The Extension popup can open GitHub, email, or Telegram when you choose those links. The Extension does not auto-send messages on your behalf.

7. Changes

This policy may be updated when the Extension changes. The “Last updated” date at the top is the current version.

8. Contact

Questions about this policy:

Related: Terms of Use.