SkipZSGuides

SkipZS Privacy Policy

Effective Date: 24 September 2026

SkipZS ("SkipZS", "we", "us", or "our") is operated by Vijay V S, an individual developer and sole founder operating SkipZS without a currently registered corporate entity.

This Privacy Policy explains how SkipZS handles information when you install, access, or use the SkipZS Chrome extension, its features, and related SkipZS services or webpages.

Our goal is to explain clearly what SkipZS accesses, what is stored on your device, what is transmitted to other devices or third parties, and what is not transmitted to SkipZS.

For privacy questions or requests, contact:

Email: skipzs.inc@gmail.com
Website: https://skipzs.app/
Contact: https://skipzs.app/Contact

1. Scope of This Privacy Policy

This Privacy Policy applies to information handling associated with:

  • the SkipZS Chrome extension;
  • Auto Skip and Trusted Auto Skip;
  • Media Booster;
  • File Sharing;
  • SkipZS settings and locally stored statistics;
  • SkipZS onboarding and consent features;
  • SkipZS webpages and related services where this Privacy Policy is presented or incorporated by reference; and
  • SkipZS-related commercial offers, where applicable, to the extent information is handled by SkipZS rather than by a third-party payment or service provider.

This Privacy Policy does not replace the privacy policies of third-party services, websites, applications, browsers, operating systems, payment processors, or other services that you may use together with SkipZS.

In particular, third-party services used for payments, LocalSend-compatible file sharing, Chrome, YouTube, and other third-party platforms may process information under their own policies.

2. Information SkipZS Accesses

Depending on which features you use, SkipZS may access or process the following categories of information.

2.1 YouTube and Page Information

When Auto Skip is enabled and you use SkipZS on YouTube, SkipZS may inspect information available in the YouTube webpage, including:

  • the current YouTube page URL for determining whether the extension is operating on an eligible YouTube page;
  • advertisement state;
  • advertisement-related DOM elements;
  • the presence of eligible Skip buttons;
  • Skip button and element position or geometry;
  • player mute state;
  • information necessary to determine whether an eligible advertisement is currently being displayed.

This information is processed by the extension to perform its Auto Skip functionality.

SkipZS does not use Auto Skip to intentionally collect or store your YouTube watch history, account credentials, passwords, cookies, or YouTube account information.

SkipZS does not intentionally upload YouTube page content or advertisement content to a SkipZS-operated server.

YouTube page information used for Auto Skip is processed within the browser and is not recorded as a browsing-history database by SkipZS.

3. Auto Skip

Auto Skip uses information available from the YouTube webpage to determine whether an advertisement and an eligible Skip button are present.

The extension may temporarily process information such as:

  • whether an advertisement is active;
  • whether an eligible Skip button is available;
  • the Skip button's screen position;
  • the player's mute state; and
  • advertisement duration information used for local statistics.

SkipZS does not intentionally store YouTube URLs, video titles, watch history, or advertisement content as part of its local statistics.

Skip statistics are aggregate statistics rather than a record of the specific videos or webpages on which skips occurred.

4. Trusted Auto Skip

Trusted Auto Skip is an optional feature that uses Chrome's debugger capability to dispatch a native mouse interaction to an eligible YouTube Skip button when ordinary webpage interaction is insufficient.

Before Trusted Auto Skip can be used, you are asked to provide separate authorization through the SkipZS interface.

The extension stores the authorization state locally on your device.

Trusted Auto Skip may process:

  • the target YouTube tab identifier;
  • the target YouTube URL;
  • a short-lived request identifier;
  • a request timestamp;
  • click coordinates; and
  • information required to validate the target tab and perform the requested interaction.

SkipZS uses security checks to restrict this functionality to eligible YouTube tabs and to validate requests before a debugger interaction is performed.

The debugger interaction is performed locally through Chrome. SkipZS does not intentionally transmit debugger commands or debugger data to a SkipZS-operated server.

You may revoke Trusted Auto Skip authorization through the SkipZS settings or authorization interface.

5. Media Booster

Media Booster is an optional feature that allows you to amplify audio from a browser tab.

When you explicitly start Media Booster, SkipZS may capture the audio stream from the selected browser tab using Chrome's tab-capture functionality.

The captured audio is processed in memory using browser Web Audio APIs.

Depending on the current implementation, the audio processing pipeline uses audio processing components including gain and dynamic compression.

Audio processing

The audio stream is:

  • processed temporarily in browser memory;
  • not intentionally recorded as an audio file by SkipZS;
  • not intentionally stored in persistent SkipZS storage;
  • not intentionally uploaded to SkipZS servers; and
  • not intentionally transmitted to a SkipZS-operated audio-processing service.

When Media Booster is stopped, SkipZS releases the relevant audio processing resources, including the captured media tracks and audio processing context.

Media Booster may operate on supported browser tabs containing active media and is not limited to YouTube.

6. File Sharing

SkipZS includes a File Sharing feature that implements a LocalSend-compatible file-transfer protocol.

The feature is designed to allow a user to receive files from a selected peer device.

When you use File Sharing, SkipZS may process:

  • the peer device's IP address;
  • the peer port;
  • LocalSend connection information;
  • pairing/session information;
  • transfer identifiers;
  • file name;
  • file size;
  • MIME type;
  • transfer progress; and
  • the contents of files being transferred to your device.

6.1 Direct Device-to-Device Transfer

File Sharing is designed around direct peer communication rather than a SkipZS cloud storage service.

When a file is transferred, the file data is sent between the participating devices through the LocalSend-compatible transfer process.

SkipZS does not operate a cloud file-storage service for files transferred through the extension.

The current SkipZS extension does not identify an operator-owned server to which transferred file contents are uploaded.

6.2 Peer Address

You may provide the peer device address manually or obtain connection information by scanning a compatible QR code.

Because the extension accepts a user-provided peer address, you are responsible for selecting the intended recipient device.

You should only initiate transfers with devices, addresses, and networks that you trust.

6.3 File Contents

When you use File Sharing, the file contents are necessarily transmitted as part of the requested transfer.

SkipZS does not use transferred files for advertising, analytics, profiling, or unrelated product purposes.

SkipZS does not intentionally retain transferred file contents as a cloud copy.

Received files are handled through the browser's download mechanism and may be saved to your device's normal download location.

6.4 Transport Security

The current SkipZS File Sharing implementation uses HTTP for its LocalSend-compatible peer communication rather than TLS-encrypted HTTPS transport.

A pairing PIN may be used during the transfer handshake to verify the transfer session. The PIN should not be understood as equivalent to transport-layer encryption.

You should therefore use File Sharing only with trusted devices and networks and should consider the security characteristics of the network over which the transfer takes place.

6.5 LocalSend

SkipZS uses a LocalSend-compatible protocol implementation for its File Sharing functionality. The SkipZS extension does not bundle the LocalSend application as a runtime dependency.

If you separately download, install, or use the LocalSend application, that application is a separate third-party product and is governed by its own terms, privacy policy, and other applicable policies.

You are responsible for reviewing and complying with the applicable LocalSend terms and privacy information when using the LocalSend application.

LocalSend's published privacy policy states that the LocalSend application itself does not collect personal or non-personal data, while also noting that other third parties such as operating systems and other applications may have their own data practices.

Nothing in this Privacy Policy makes SkipZS responsible for the independent data practices of LocalSend or other third-party services.

7. Information Stored on Your Device

SkipZS stores certain information locally in Chrome's extension storage so that the extension can remember your preferences and provide its features.

7.1 Settings

SkipZS may store settings such as:

  • extension enable/disable state;
  • Auto Skip settings;
  • mute and notification preferences;
  • Trusted Auto Skip authorization state;
  • consent information;
  • theme preference;
  • popup-size preference; and
  • other supported extension preferences.

7.2 Keyboard Shortcuts

SkipZS may store your customized keyboard shortcut configuration.

7.3 Statistics

SkipZS may store aggregate statistics including:

  • total advertisements skipped; and
  • estimated time saved through skipped advertisements.

Daily statistics are maintained locally and older daily records are automatically pruned according to the extension's current retention configuration.

The current implementation uses a 60-day retention period for daily statistics. Aggregate totals may remain until you reset the statistics or uninstall the extension.

SkipZS does not intentionally include individual YouTube URLs or video titles in these statistics.

7.4 Popup Position

If supported by your settings, SkipZS may store the popup's position so that it can restore the interface position later.

7.5 Temporary Session Information

Some temporary information may be stored in Chrome session storage while features are operating.

This can include File Sharing transfer/session state such as:

  • transfer identifier;
  • peer information;
  • file name; and
  • transfer progress.

Session information is intended to be temporary and is cleared when the relevant session ends or the browser session ends, subject to the behavior of Chrome's extension storage system.

8. What SkipZS Does Not Intentionally Collect for Its Own Servers

The current SkipZS extension does not identify an operator-owned analytics or telemetry endpoint.

Based on the current extension implementation, SkipZS does not intentionally transmit the following to a SkipZS-operated analytics or backend service:

  • browsing history;
  • YouTube watch history;
  • YouTube account credentials;
  • passwords;
  • YouTube video content;
  • advertisement content;
  • Media Booster audio recordings;
  • File Sharing file contents;
  • local SkipZS statistics;
  • extension settings;
  • keyboard shortcut configurations; or
  • onboarding consent state.

The absence of an operator-owned telemetry endpoint does not mean that no information is ever processed or transmitted when using SkipZS. For example, File Sharing necessarily communicates file data and connection information to the peer device selected by the user.

9. Analytics and Statistics

SkipZS currently provides local statistics for the extension's own functionality.

The current statistics include:

  • advertisement skip count;
  • estimated time saved; and
  • daily skip statistics.

These statistics are processed and stored locally.

The current implementation does not use an external analytics service such as Google Analytics, Sentry, PostHog, or Firebase for extension usage analytics.

SkipZS does not intentionally transmit these statistics to an operator-owned analytics service.

10. Network Communications

SkipZS may communicate with external systems or devices when necessary for a feature or when you explicitly open an external SkipZS webpage.

10.1 File Sharing

File Sharing may communicate with the peer address selected by you using the LocalSend-compatible HTTP protocol.

This communication may include file-transfer data, file metadata, session information, and pairing information necessary to perform the transfer.

10.2 SkipZS Websites

The extension may open SkipZS webpages such as:

  • the SkipZS website;
  • Privacy Policy;
  • Terms of Service;
  • Contact/Support;
  • documentation;
  • and other SkipZS pages that you explicitly choose to open.

Opening these webpages may result in the ordinary browser communications associated with visiting a website.

This Privacy Policy describes the current extension's own data handling. The web pages themselves may have separate technical processing associated with hosting, security, analytics, payment, or other website services. Where applicable, those practices should be described by the relevant website privacy notices.

11. Commercial Offers and Version 2 Pre-Booking

The current SkipZS Chrome extension does not contain an integrated payment gateway, subscription system, or in-extension payment processor.

SkipZS may nevertheless operate separate webpages through which users can purchase or pre-book products, services, or future versions of SkipZS.

At the time of this Privacy Policy, SkipZS may offer a Version 2 pre-booking offer through a separately hosted webpage.

Payment processing for such an offer may be handled through third-party payment providers selected for the applicable offer, which may include providers such as Dodo Payments, Razorpay, or Lemon Squeezy.

When you make a purchase through a separately hosted payment or checkout page:

  • the payment provider may collect payment and transaction information;
  • the payment provider may process personal and financial information necessary to complete the transaction;
  • the payment provider may have its own privacy policy and terms;
  • information required to provide the purchased product or service may be shared with or processed by relevant service providers where necessary; and
  • the specific terms, pricing, refund conditions, delivery conditions, and other commercial conditions applicable to a purchase will be presented with the relevant offer or plan.

SkipZS does not claim that payment information entered into a third-party payment processor is stored by the Chrome extension.

You should review the applicable payment provider's privacy policy and the terms shown at checkout before completing a purchase.

The commercial terms of a specific Version 2 pre-booking or future paid offer may differ from the free functionality of the current SkipZS Chrome extension.

12. Third-Party Services and Platforms

SkipZS interacts with or may be used alongside third-party platforms and technologies.

These may include:

  • Google Chrome and Chrome browser APIs;
  • YouTube;
  • LocalSend-compatible devices or the LocalSend application;
  • third-party payment providers;
  • hosting providers;
  • websites linked from SkipZS; and
  • other services that you independently choose to use.

These third parties operate independently from SkipZS and may have their own terms, privacy policies, security practices, and data-processing practices.

Your use of those services is subject to their applicable terms and policies.

SkipZS is not operated by, affiliated with, sponsored by, or endorsed by Google, YouTube, Google Chrome, or LocalSend, except where explicitly stated otherwise.

13. Chrome Permissions

SkipZS requests certain Chrome permissions because particular features require access to Chrome APIs.

Storage

Used to store settings, shortcuts, consent information, and local statistics.

Debugger

Used by Trusted Auto Skip to dispatch the required native mouse interaction to an eligible YouTube Skip button.

Tab Capture

Used by Media Booster to capture audio from the browser tab you choose to boost.

Active Tab

Used to identify and interact with the browser tab relevant to supported extension features.

Scripting

Used by Media Booster for limited tab metadata collection, including obtaining the title of the selected tab for the feature interface.

Downloads

An optional permission used when receiving files through File Sharing so that received files can be saved using Chrome's download system.

YouTube Host Access

Used to operate the Auto Skip content script on YouTube pages.

Local Network HTTP Host Access

An optional host permission used when File Sharing needs to connect to a peer device's HTTP address.

SkipZS requests permissions for feature-related functionality and does not intentionally use these permissions to build a separate browsing-history or advertising profile.

14. Data Retention

SkipZS uses different retention periods depending on the type of information.

Persistent local settings

Settings and shortcut configurations remain stored on the device until they are reset, changed, or removed through extension/browser lifecycle actions.

Local statistics

Daily statistics older than the current 60-day retention period are automatically pruned.

Aggregate statistics may remain until the user resets them or the extension is uninstalled.

Session information

Temporary File Sharing session information is stored in Chrome session storage and is intended to be cleared when the relevant session ends or the browser session ends.

In-memory information

Temporary information such as active audio processing state, media streams, and active transfer state exists only while required by the relevant feature and is released through the feature's cleanup mechanisms.

Extension uninstall

Chrome manages the removal of extension storage when an extension is uninstalled, subject to Chrome's own platform behavior.

15. Your Controls

Depending on the feature, you can control your information and feature use by:

  • changing SkipZS settings;
  • disabling Auto Skip;
  • disabling Trusted Auto Skip;
  • revoking Trusted Auto Skip authorization;
  • stopping Media Booster;
  • choosing whether to use File Sharing;
  • choosing the files you transfer;
  • choosing the peer device/address used for File Sharing;
  • resetting local statistics;
  • resetting extension settings where supported;
  • declining optional permissions; and
  • uninstalling the extension.

You remain responsible for the choices you make when selecting files, devices, recipients, networks, and third-party services.

16. Security

SkipZS uses technical measures intended to protect the extension's internal operations and reduce unauthorized use of sensitive capabilities.

Examples include validation of Trusted Auto Skip requests, restriction of Trusted Auto Skip to eligible YouTube tabs, temporary debugger attachment, filename sanitization for received files, transfer validation, and cleanup of temporary media-processing resources.

However, no software, network, device, or method of electronic transmission can be guaranteed to be completely secure.

In particular, the current File Sharing implementation uses HTTP peer communication rather than TLS transport encryption. Users should therefore use File Sharing with devices and networks they trust.

You are responsible for maintaining the security of your own devices, browser, operating system, network, and any third-party applications you use with SkipZS.

17. Children's Privacy and Age Requirements

SkipZS is intended for users aged 16 or older.

If you are under 18, you should use SkipZS only with the permission and involvement of a parent or legal guardian where required.

This is particularly relevant to future commercial products, subscriptions, pre-booking offers, or other transactions involving payment.

If applicable law in your location establishes a different minimum age or additional requirements for a particular activity, those legal requirements take precedence.

SkipZS does not intentionally use the extension to collect children's personal information for advertising or behavioral profiling.

18. International Users

SkipZS is operated by an individual developer in India.

Users may access SkipZS from other countries or regions. If you use SkipZS outside India, you are responsible for ensuring that your use of the extension and any related services complies with laws applicable to you.

Privacy rights and legal requirements may vary depending on your location.

Where applicable law gives you privacy or data-protection rights that differ from or provide additional protections beyond this Privacy Policy, those rights remain applicable to the extent required by law.

19. Privacy Rights and Requests

Depending on your location and applicable law, you may have rights concerning personal information processed by SkipZS.

If you have a privacy question, believe information has been handled improperly, or want to make a privacy-related request, contact:

skipzs.inc@gmail.com

Please provide enough information for us to understand and respond to your request.

Because the current extension does not use a user-account system or maintain an operator-owned database of extension users, some requests may concern information stored locally on your own device rather than information held by SkipZS.

20. Data You Share With Other People or Services

SkipZS provides functionality that can cause information or files to be sent to another device or third-party service based on your actions.

For example:

  • File Sharing sends selected file data to the peer device you choose;
  • visiting a third-party website communicates with that website;
  • using a payment or checkout service may provide information to the applicable payment processor;
  • using YouTube or Chrome remains subject to Google's applicable systems and policies; and
  • using the separate LocalSend application remains subject to LocalSend's own policies.

You should review the recipient, destination, and applicable third-party privacy terms before sharing sensitive information.

21. Changes to SkipZS and Its Data Practices

SkipZS is actively developed.

We may add, modify, replace, restrict, suspend, or remove features, technologies, integrations, or services over time.

Changes to the product may result in corresponding changes to the information that SkipZS accesses or processes.

This may occur because of:

  • new or removed features;
  • security requirements;
  • technical changes;
  • changes to Chrome or browser APIs;
  • changes to YouTube or other third-party platforms;
  • changes to LocalSend or compatible technologies;
  • new commercial services;
  • legal or regulatory requirements; or
  • other operational reasons.

If our data practices materially change, we may update this Privacy Policy and may provide an in-extension notice where appropriate.

The updated Privacy Policy will display a new effective date.

22. Changes to This Privacy Policy

We may update this Privacy Policy from time to time.

When we make changes, we will publish the updated Privacy Policy at:

https://skipzs.app/Privacy

The updated version will include a revised effective date.

For material changes, we may also provide an appropriate notice through the SkipZS extension.

Your continued use of SkipZS after an updated Privacy Policy becomes effective means that you acknowledge the updated policy to the extent permitted by applicable law.

Where applicable law requires renewed consent or another specific notice method, we will follow those requirements.

23. Contact Us

For questions, support requests, privacy requests, or concerns about SkipZS:

SkipZS
Operator: Vijay V S
Email: skipzs.inc@gmail.com
Website: https://skipzs.app/
Contact: https://skipzs.app/Contact

For privacy-specific matters, you may use the same email address:

skipzs.inc@gmail.com

24. Important Third-Party Notice

SkipZS is an independent product and is not Google, YouTube, Google Chrome, LocalSend, or any payment provider.

Third-party applications and services that you choose to use with SkipZS have their own privacy policies and terms.

If you separately download or use the LocalSend application, you should review the applicable LocalSend privacy information and terms before using that application. LocalSend publishes its own privacy policy separately from SkipZS.

Likewise, if you make a purchase through a separate SkipZS commercial webpage using a third-party payment provider, the payment provider's applicable privacy policy and terms may govern its processing of your payment and transaction information.

Last Updated: 24 September 2026