Privacy Policy
Last updated: September 3, 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 URL shorteners and file hosts, skips countdown timers and waiting pages, or waits and clicks Continue for you when the site still requires that. It is available from the Chrome Web Store. After install you may use 5 free bypasses per local calendar day with no key. Unlimited bypass while a free trial (30 minutes) or $1.50 per month license from EAS Store is live; activate an optional key in the extension popup. No separate website 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 (which pages were opened and how often)
- traffic source and approximate location (for example organic, direct, and country)
- device and browser information
- Add to Chrome clicks as separate events for header, hero, and bypass pages; footer Chrome Web Store link clicks; contact CTA clicks (GitHub, Telegram, email); and Supported Sites search terms
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
- Nitro Link
- ShortXLinks-style flows
- the cached supported-site list downloaded from the public
hosts.jsonfile in the extension repository, plus the last refresh time - a local daily count of free bypasses used while no license is live (calendar day and number used), so the free daily limit can be enforced on this device
- license session data when you activate a key: license key, browser instance ID, activation ID, activation token, signed offline lease, lease nonce, plan type (trial or monthly), and lease or entitlement expiry times
That data stays on your device and is not sent to us for analytics. License activation sends the key and instance ID to EAS Store as described below. There is no global on/off preference stored.
Alarms
Uses the alarms permission to clear access when the signed offline lease or entitlement expires. Bypass reads the verified local lease and does not call EAS on every page. Alarms are not used for ads, tracking, notifications, or unrelated background work.
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 a remote supported-site list and only runs on matching 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:
localStoragesessionStorage- 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) - the public supported-site list at
raw.githubusercontent.com/sharoon7171/skip-wait-bypass-timers-countdowns/main/extension/public/hosts.jsonwhen the extension starts and when you tap Refresh in the popup - EAS Store license endpoints at
https://eas-x.com/api/v1/licenseswhen you activate, validate, or remove a license (license key, instance ID, activation token, and a one-time nonce). Bypass itself reads the verified local lease and does not call EAS on every page - the EAS public-key endpoint at
https://eas-x.com/api/v1/licenses/public-keywhen needed to verify a lease signature
License requests are processed by EAS Store under its terms. 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:
- Email: sharoon7171@gmail.com
- Telegram: https://t.me/sharoon1998
- GitHub: https://github.com/sharoon7171/skip-wait-bypass-timers-countdowns
Related: Terms of Use.