Mowiklip Logo
MowiKlip
Privacy Policy

Your data.
Your control.

In effect
Version 1.0.1 Last updated: April 2026
TL;DR

MowiKlip collects limited data (such as your Google account name and email) only for authentication and core functionality. Your editing preferences are stored locally and on our servers to enable features. We do not sell, or your personal data. No tracking. No analytics. No advertising.No surprises.

01 — DATA COLLECTION
🛡️

Data Collection

  • This extension collects limited personal information, specifically your name and email address, when you sign in using Google OAuth.
  • This information is used solely for account creation and authentication.
  • We do not sell your personal data. Your information is securely transmitted to and stored on our backend servers only for the purpose of providing core functionality.
  • We do not collect or track your IP address, browsing history, viewing habits, or any other unrelated personal data.
02 — USER DATA
🔒

Your Edits and Data Storage

All user-defined data — including your custom skip, mute, and loop segments — is stored locally on your device using Chrome's built-in chrome.storage.local API and may also be securely transmitted to and stored on our backend servers to enable account-based functionality and data persistence.
This data is associated with your account and used solely to provide core features of the extension. We do not use this data for advertising, tracking, or profiling purposes. If additional data-sharing features are introduced in future updates, you will be clearly informed and asked for consent where required.

03 — TRACKING & ANALYTICS
👁️

Zero Tracking. Zero Analytics.

We only process data required for authentication and core functionality. The extension does not use analytics, advertising or tracking technologies of any kind. There are no third-party SDKs, no telemetry, no crash reporting services, no advertising networks, and no session recording tools embedded in this extension.
However, the extension communicates with our backend servers solely to support authentication and core features. This communication is limited to what is necessary for the service to function. We do not track user behavior or monitor how you interact with content beyond what is required to provide the extension’s features.

04 — PERMISSIONS
🔑

Permissions Used Only as Needed

Permissions requested by the extension are used solely to enable core functionality as described below. No permission is requested speculatively or for future use.

Permission Why it's needed
storage Save your edit segments (skip, mute, loop timings) locally on your device.
tabs Detect when you navigate to a Netflix video page so the player panel can be shown
identity Used for Google sign-in (OAuth) to authenticate users and enable features such as account-based functionality.
netflix.com access Read the video player state (current time, duration) to apply your edits at the right moment


In addition to the above, authentication data (such as your name and email) and user-defined data may be securely transmitted to and stored on our backend servers to enable core functionality.

05 — Data Sharing
👁️

Zero Data Sharing/Selling/Advertising

We do not sell user data. However, limited data may be shared with the following parties:


  • Google — for authentication via Google OAuth
  • Our backend servers — to securely process login and provide core functionality

The data involved may include your name and email address obtained during authentication. We do not share data with advertisers, analytics providers, or third-party tracking services.

06 — FUTURE UPDATES
🔄

Policy Updates

If future updates involve changes to how data is collected, used, or shared, this privacy policy will be updated accordingly before those changes take effect.
Where applicable, users will be given clear choices regarding optional features that involve additional data usage. Where required, users will be informed of significant changes through the extension interface or release notes. Continued use of the extension after such updates constitutes acceptance of the revised policy.