Privacy Policy

1. Who we are

MuteSkip is developed and operated by Ninghao Wang, an independent individual developer. In this policy, “we,” “us,” and “our” refer to that developer, who is responsible for the personal data processed to provide MuteSkip.

Contact address

Chenghan Taoyuan Garden, Wulian Community, Longgang District, Shenzhen, Guangdong, China

Privacy requests

support@muteskip.org

Product support

support@muteskip.org

This policy covers the MuteSkip Chrome extension, its account and license services, and this website. YouTube, Chrome, the Chrome Web Store, and payment providers have their own privacy notices for their services.

2. What happens inside your browser

Ad detection and playback controls

The extension examines the YouTube page locally to detect an ad, check whether YouTube's own Skip button is available, and locate that button. It also checks the page origin, tab and document identifiers, foreground status, and audio state. These checks allow it to mute the correct tab, attempt a Skip click, and restore the tab's previous mute setting.

The current version applies mute and skip actions only to the YouTube video tab you are viewing in a focused, non-minimized Chrome window. It does not record audio or video, build a watch-history feed, or send video content, video titles, YouTube search terms, or browsing URLs to the account or license server.

Browser permissions

• YouTube access: read the page state needed for ad detection and the native Skip button.
• Storage: save feature preferences, sign-in information, installation identifiers, and license verification state.
• Debugger: inspect the native Skip button and send a browser-generated mouse click to that button. Chrome grants this permission at installation and displays a debugging notice during use. Auto-skip is off by default. MuteSkip connects for the operation and disconnects afterward.
• Account-service access: contact the configured Supabase service over HTTPS for sign-in, trial and license checks, and checkout requests.

Chrome's debugger permission is broader than the actions MuteSkip performs. The extension's implementation restricts those actions to the requesting YouTube document; the permission is not used to monitor unrelated websites. The packaged account-link page can be opened from email websites for email confirmation and password recovery. Making that page accessible does not give MuteSkip access to your email messages or those websites.

Local storage

Chrome extension storage holds your email and account ID, access and refresh tokens, signed license tickets, trial and license status, feature settings, random installation identifiers associated with accounts used in that Chrome profile, and clock values used to check license validity. The identifiers are randomly generated, not hardware fingerprints.

Temporary session storage holds tab, document and ad-session identifiers, prior mute state, and click or restoration status. These records support audio restoration and prevent duplicate clicks. The extension removes session records during cleanup and when their tabs close.

Signing out removes the stored sign-in session and license state. Feature settings, installation identifiers and clock-check values remain in that profile. A ticket's expiration does not necessarily delete its stored record. Removing the extension removes its local extension storage; it does not delete your server-side account or purchase records.

3. Data our services receive

Account and authorization

When you register or sign in, the extension sends your email address and password to Supabase Auth over HTTPS. The extension does not save your password in Chrome extension storage or our license database. Supabase handles password authentication, confirmation and recovery, and returns the session credentials used to keep you signed in.

Our account and license services process your account ID, verified email information, account creation time, trial start and end, random installation ID, installation creation and last verification times, any revocation status, and compatibility releases available to your account. License requests identify the installation and requested release, not the video you are watching.

Purchases and refunds

When checkout is enabled and you choose to buy, we send Creem your account email, account and order identifiers, the selected product or compatibility release, and whether the purchase is an initial license or upgrade. Creem collects the billing and payment details needed to complete the transaction.

We receive payment confirmations and transaction references from Creem. Our database stores order type, amount, currency, release, timestamps, payment status, customer and checkout references, and refund or dispute records needed to determine access. The extension and our license database do not store full card numbers or card security codes.

Support and service logs

If you contact us, we process your contact details and the message, receipt reference, or other information you choose to send. Do not send passwords, session tokens or full payment-card details.

Local diagnostic records can include action times, permission state, click results and mute-restoration state. There is no automatic diagnostic-upload feature in the current extension. The local test build can copy a report after redacting common account, URL and token fields. Review a report before choosing to share it.

Account-service requests expose connection information, including IP addresses and request headers, to Supabase's infrastructure. Errors can generate console messages. The application does not create a separate activity-log table, save a history of each ad action, or store full payment-webhook payloads. Its webhook records contain event identifiers, types and processing times.

The service currently uses Supabase Free. Its published API and database log retention is one day, and its Auth audit-log retention is one hour. Other infrastructure and function records follow the provider's applicable settings and policies. We do not enable separate log drains or keep routine copies of platform logs under this launch plan. A necessary troubleshooting export is limited to seven days, with credentials and unnecessary personal information removed. An identified security incident may require restricted evidence to be kept until resolved.

Supabase also offers an optional Postgres copy of authentication audit events. Its dashboard log windows do not establish how long an enabled database copy is kept. The selected launch configuration disables that additional copy to reduce stored data; the live setting still needs verification. Provider-side security processing remains separate.

4. The static website

This website presents product information and legal documents. It has no account database, sign-in form or embedded checkout. The website code does not set cookies, store visitor identifiers, or load advertising pixels, analytics scripts, remote fonts or embedded video players. Its interactive demonstration runs in your browser without sending the selected demo state to us.

Cloudflare Pages serves this static website. Cloudflare processes technical request and security information, which can include IP addresses, request paths, timestamps, browser headers and traffic-routing data. Its infrastructure processing and retention are described in its Privacy Policy. We do not receive website visits in the MuteSkip license database or keep separate raw access-log exports. We do not operate website accounts, advertising pixels or our own visitor-tracking database.

The deployment includes a content-security policy that permits only local page resources and blocks background network connections from page scripts. Cloudflare's own network and security processing still applies. Before enabling a new analytics or data-collection feature, we will update this notice and obtain any consent required by law.

Following a link to another service takes you to that service's own privacy practices. Visiting this website alone does not create a MuteSkip account or start a trial.

5. Why we use this information

We use local page state to provide the mute and skip controls you enable. We use account, installation and purchase information to sign you in, run the trial, verify and restore access, fulfill purchases, handle refunds and answer support requests. We use necessary security and transaction records to prevent abuse, reconcile payments and meet legal obligations.

Where data-protection law requires a legal basis, processing needed to provide your account and purchased service is based on performing our contract with you; required accounting and regulatory records are based on legal obligations. Proportionate fraud prevention, service security and handling legal claims rely on legitimate interests only where the applicable law recognizes that basis. Otherwise we must establish another valid basis, including consent where required. A privacy-policy link does not replace required consent or agreement to retain data after account closure.

Access checks automatically compare trial and purchase status with license rules. They do not use browsing behavior to profile you. If an access decision appears wrong, contact support for review.

6. Service providers and transfers

We use the following providers for the purposes described above:

• Supabase: account authentication, database hosting and license-service infrastructure. Project region: [SUPABASE_REGION].
• [EMAIL_DELIVERY_PROVIDER]: delivery of account-confirmation and password-recovery messages, including the email address and link required for delivery.
• Creem: planned hosted checkout, payment records, tax handling, refunds and payment disputes. For transactions it sells as merchant of record, Creem handles payment-related data under its Privacy Notice.
• Cloudflare Pages: delivery and security of the static website.
• [SUPPORT_EMAIL_PROVIDER]: receipt and storage of support and privacy correspondence.

We disclose information only as needed for these services, legally required requests, or protection against fraud and security threats. We do not send YouTube viewing content to these providers for license verification.

MuteSkip is operated from China. The primary Supabase database region is the project region identified above, which still needs confirmation. Supabase may also process operational information outside that region, including logs in the European Union and support or service operations elsewhere. See its data-location and transfer information.

Cloudflare operates globally and describes processing in the United States, the European Economic Area and other operating locations. Creem is an Estonia-based merchant of record; its payment and service providers can process information in additional countries under its privacy notice. The selected email providers and their locations must be added before launch. Hosting an account database in Asia does not mean that all service data remains in Asia.

Before the service launches, we must confirm applicable provider data-processing agreements, subprocessor locations, and any transfer safeguards required by law, such as applicable standard contractual clauses and required UK arrangements. A provider's published safeguards do not automatically cover every transfer by MuteSkip. We will obtain any legally required separate consent or complete another required transfer procedure before that processing begins. Contact the privacy address above for information about safeguards once confirmed. Use of the website or extension is not blanket consent to international transfers.

7. Chrome Web Store Limited Use

MuteSkip's use and transfer of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

We limit extension user data to the disclosed mute and skip purpose and necessary account, licensing, reliability and security operations. We do not sell it, use it for personalized advertising, share it with data brokers, or use it for credit or lending decisions. We do not use it to train AI models.

Human access to extension user data is limited to your specific consent, such as a support request, security needs, legal requirements, or anonymized aggregate internal operations allowed by the policy. Transfers must be necessary for the disclosed purpose, legal compliance, or fraud prevention. A transfer of extension user data in a business sale or acquisition would require your explicit prior consent.

8. Retention and security

We keep personal data only for a service, security or legal purpose and for no longer than that purpose requires. The following is the retention schedule selected for launch. It sets our operational targets; it is not a claim that every period is required by law.

Account email, trial status and purchase entitlements

No automatic expiry while needed to maintain your account or honor a valid purchase. We retain the minimum account link, trial-used status, licensed release, purchase and confirmation times, and refund or dispute status needed to verify access. This is long-term service retention, not an unconditional promise to keep an identifiable account forever. Valid deletion rights remain available.

Account closure and deletion requests

We act without undue delay once a cancellation or deletion request is valid and verified, including immediate deletion where the law requires it. We aim to complete straightforward request handling within seven calendar days and respond within any shorter applicable deadline or, where applicable, one calendar month. Necessary verification is proportionate; a lawful extension must be explained. Records required for an ongoing legal obligation or claim are limited and separated from ordinary account use.

Repeat-trial prevention after account deletion

Where a valid legal basis permits it, a minimal trial-used marker is retained for 30 days after closure, then deleted. The planned marker consists of a server-keyed hash of the verified email, a trial-used flag and an expiry time. It is pseudonymous personal data, not anonymous information. We obtain any agreement or consent required for this retention, do not retain it when no lawful basis applies, and do not use it for marketing or browsing profiles.

Installation records

Ordinary installation records become eligible for removal after 90 days without a license verification. Necessary revocation markers remain while needed to enforce account security; they must not be removed in a way that silently restores revoked access. Removing an inactive installation record does not remove an independently valid purchase entitlement.

Orders, refunds and disputes

Closed transaction records are reviewed for deletion or anonymization three years after payment, refund or final dispute resolution, whichever is later. This is a product retention choice, not a universal legal minimum. Minimal entitlement and reversal records remain while needed to honor a purchase or prevent an invalid restoration. Applicable tax, accounting or legal-hold duties may require specific records for longer; only those records are retained for that purpose.

Support correspondence

Ordinary messages and attachments are deleted 90 days after the case is resolved. Information needed for an unresolved privacy request, payment dispute or legal obligation is separated and retained only for that purpose. We do not copy the support inbox into the license database.

Operational logs

No separate persistent database of ad activity, browsing history or routine request logs. Supabase platform logs follow the plan-specific periods described above. Necessary developer-held troubleshooting exports are deleted within seven days; narrowly retained incident evidence is an exception only while needed. Cloudflare's independent infrastructure records follow its own disclosed retention criteria.

Backups controlled by the developer

Any recoverable backup we create is encrypted and kept outside the live Supabase database on a rolling cycle of no more than 14 days. Data already deleted from the live system ages out of those backups within that cycle. Backups are restricted to recovery and must not be used to reactivate deleted accounts; deletion restrictions are reapplied after a restore. Supabase Free does not include the customer-accessible automatic backups offered with paid plans. This 14-day rule does not misrepresent or override a provider's own infrastructure-retention duties.

The planned account-deletion process, 30-day repeat-trial protection, scheduled cleanup and backup rotation are not yet operational. They must be implemented and tested before this draft takes effect. Until then, development records are not automatically removed under this retention schedule.

Once information is no longer needed, it must be deleted or irreversibly anonymized. If deletion is temporarily restricted by a legal obligation or a technical recovery requirement, its use is restricted to that purpose and security. Creem's own retention duties are separate and are described in its privacy notice; a MuteSkip deletion request cannot erase records Creem is legally required to retain.

The extension uses HTTPS for account-service requests and restricts local account storage to trusted extension contexts. The license database is accessed through authenticated server operations. Chrome storage is not an end-to-end encrypted vault; anyone with access to your device or Chrome profile may be able to access local data. Protect your device and sign out on shared computers.

9. Your choices and rights

You can switch muting and auto-skip on or off separately, sign out, or disable or remove the extension in Chrome. Signing out or uninstalling does not submit an account-deletion or refund request.

Contact support@muteskip.org to request access to, correction of, or deletion of your personal data. Depending on applicable law, you may also request a portable copy, restriction of processing, object to processing based on legitimate interests, withdraw consent for consent-based processing, or complain to your data-protection authority. We will verify requests proportionately and respond within the applicable legal deadline.

Account deletion requires a support request; the current extension does not have a self-service account-deletion button. Deleting the account used to verify a license can prevent further access or restoration. We will explain the effect on your purchase and any records that must be retained before completing the request. Your statutory privacy and consumer rights remain available.

Email and the information needed to verify a trial or paid license are required for those services. You can read the public website without creating an account.

10. Changes and contact

We will update this page and its effective date when our practices change. Material changes will be brought to users' attention through the website or extension, and through email where appropriate. If a new use requires consent, we will obtain it before starting that use.

For privacy questions, contact support@muteskip.org. For purchase and refund information, read our Terms & Refunds.