Mixurly - Shaping Sound Across URLs Privacy Information

Mixurly's single purpose is to boost, shape, and manage audio across websites through user-controlled per-site audio controls, equalizer features, and Mixurly Player.

Local Handling and Account Data

Mixurly's audio controls work locally in your browser. Account, sign-in, and purchase data are used only for optional account linking, restore, and Pro access features. Mixurly does not sell or transfer user data to third parties outside approved use cases necessary to provide its single purpose, does not use or transfer user data for unrelated purposes, and does not use or transfer user data to determine creditworthiness or for lending purposes.

• If you sign in or unlock Pro, your email address may be used for Zohsik account sign-in, restore, and Pro access.
• If you stay signed in, secure session information may be used to confirm your account-linked access.
• If you purchase Pro, purchase and entitlement records may be used to confirm, restore, refund, or manage your Pro access.

What Mixurly Does Not Record, Upload, or Use for Unrelated Purposes

• Mixurly does not record, transcribe, or upload the audio or video you play.
• Mixurly does not send raw audio bytes or webpage media data to Zohsik, Supabase, Stripe, advertising services, or analytics services.
• Mixurly does not collect or transfer unrelated webpage text, images, links, forms, cookies, credentials, or network-request contents.
• Mixurly does not send tab URLs, tab titles, favicons, or per-site audio settings to the Zohsik account or payment backend.
• Mixurly does not build a remotely stored browsing-history or user-activity profile.
• Mixurly does not access Spotify login credentials, authentication headers, private account data, or raw audio bytes.
• Mixurly does not collect health information or precise GPS location.
• Mixurly does not collect or store a Zohsik account password.
• The Mixurly extension does not store raw payment-card numbers or card security codes.
• Mixurly does not download or execute remotely hosted JavaScript, WebAssembly, or CSS.
• Mixurly does not contain an advertising network or general product-analytics endpoint.

Permissions Explanation

Mixurly uses the storage, tabs, and scripting permissions, together with HTTP and HTTPS host access, only to save user-selected settings, operate its audio features, and display its packaged controls on supported pages.

Permission	Purpose
storage	Saves user-selected audio settings, per-site preferences, equalizer profiles, interface choices, continuity state, and optional account, authentication, Pro entitlement, checkout, and device-session state. Settings Backup excludes account, authentication, entitlement, checkout, device-session, and temporary tab data.
tabs	Identifies the active page and currently open audible tabs so Mixurly can operate Mixurly Player, send audio controls to the correct tab and frame, focus a selected audio tab, and mute or restore tabs for Focused Audio Mode. Relevant tab details are used locally and are not sent to the Zohsik account or payment backend.
scripting	Injects only extension-packaged JavaScript and CSS needed to apply audio behavior, display or reopen Mixurly Player and page controls, and update user-selected site-specific behavior. Mixurly does not download or execute remotely hosted JavaScript, WebAssembly, or CSS.
http://*/* and https://*/*	Allows Mixurly to find playable audio or video on websites and embedded media frames, create and control the local audio graph, apply user-selected settings, display its optional page controls, and coordinate audio across tabs. Mixurly does not use this access to collect unrelated page content, form data, cookies, credentials, or network-request contents, and it does not upload webpage audio or media data.

Browser Extension Storage

Mixurly uses browser extension sync, local, and session storage so user-selected audio preferences, interface choices, account state, and live tab coordination remain available in the appropriate browser context. Eligible settings stored in browser-managed sync storage may follow the user across signed-in Chrome browsers when extension sync is enabled.

• Per-site origins, gain, and audio preferences
• Bass, clarity, mono, and MixearLy ear-balance settings
• Headroom Protection and Limiter Protection settings
• Full Range Audio Slider and page-slider settings
• Theme, appearance, language, popup, and Player preferences
• Focused Audio Mode state
• Equalizer values, presets, profiles, and Profile Packs
• Startup continuity and temporary Player or tab state
• Basic account, sign-in, entitlement, checkout, and device-session state when those optional features are used

Browser-managed sync storage is used for eligible preferences and per-origin setting maps. Per-install account, authentication, entitlement, checkout, device-session, larger profile, and Player state use local extension storage. Live tab coordination uses session storage. Mixurly's Settings Backup excludes account, authentication, entitlement, checkout, device-session, and temporary tab data.

Website and Audio Interaction

Mixurly runs on supported HTTP and HTTPS pages so it can find media elements, create and control the local audio graph, apply your selected settings, render the optional page slider and Mixurly Player, and coordinate audio across tabs. Playable media can appear inside child frames, so Mixurly can also work with supported embedded media.

While providing those features, Mixurly locally accesses and temporarily processes tab identifiers, website URLs or origins, page titles, favicons, audible and muted state, playback state, webpage sounds, videos and media elements, and local Web Audio or MediaSource objects. Website origins associated with user-selected per-site settings may be stored in browser-managed sync storage. For Chrome Web Store disclosure purposes, this handling is disclosed as Web history and Website content. Mixurly does not send tab titles, favicons, webpage audio, or webpage media data to the Zohsik account or payment backend and does not build a remotely stored browsing-history profile.

On open.spotify.com, Mixurly uses an extension-packaged bridge in the page's main JavaScript world because Spotify playback can use page-owned MediaSource and Web Audio objects that are not accessible from the normal isolated extension world. The bridge is used only to identify real song playback, avoid visual-loop media, and connect playback to Mixurly's local audio graph.

Zohsik Account, Pro Access, and Payments

Mixurly Free can be used without creating a Zohsik account. A Zohsik account is only needed if you choose to unlock, restore, or use account-linked Mixurly Pro access.

• Zohsik uses Supabase for email magic-link sign-in, session handling, account restore, Pro entitlement checks, and device-session lifecycle updates.
• Mixurly does not collect or store an account password.
• Zohsik uses Stripe for hosted checkout and payment processing. Mixurly does not collect card numbers or security codes directly in the extension.
• Zohsik may retain customer, checkout-session, payment, invoice, amount, status, refund, entitlement, billing-event, and audit records needed to manage Mixurly Pro access.
• Zohsik website pages help complete account sign-in, checkout, success, cancellation, restore, and return-to-extension flows.
• Mixurly Pro access is confirmed through Zohsik's backend rather than stored as a permanent local unlock.
• Basic device/session records may be used for account security, restore behavior, support, and abuse prevention.

Privacy Explanations

Mixurly's Chrome Web Store Data usage disclosures are Personally identifiable information, Financial and payment information, Authentication information, Web history, and Website content. These disclosures include data that Mixurly accesses, uses, processes, or stores locally, not only data transmitted to an external service.

Category	How It Is Handled
Personally identifiable information	If you use an optional Zohsik account, your email address and account ID may be used for sign-in, restore, and Pro access. Account profile information may also include a display name, avatar URL, profile metadata, and profile preferences.
Financial and payment information	Stripe handles payment-card and billing information on its hosted checkout page. Zohsik uses related transaction, purchase-status, refund, and entitlement records to confirm and manage Mixurly Pro access.
Authentication information	Secure access and refresh tokens, token expiration, authenticated user ID, email address, and account-session state may be used to keep you signed in and confirm account-linked access.
Web history	Mixurly locally accesses the active page and currently open audible tabs, including the tab ID, URL or origin, title, favicon, audible state, and muted state, only to provide Mixurly Player, cross-site audio controls, and Focused Audio Mode. Website origins associated with user-selected per-site settings may be stored in browser-managed sync storage and may follow the user when Chrome extension sync is enabled. Mixurly does not send tab titles or favicons to the Zohsik account or payment backend and does not build a remotely stored browsing-history profile.
Website content	Mixurly locally accesses and processes webpage sounds, videos, media elements, playback state, and Web Audio or MediaSource objects only to find playable media, create and control the local audio graph, apply user-selected audio settings, and render its optional page controls. Mixurly does not record, transcribe, upload, or transfer webpage audio or media data, and it does not collect or transfer unrelated page text, images, links, forms, cookies, credentials, or network-request contents.
Tab information	Tab identifiers, URLs or origins, titles, favicons, audible state, and muted state are used locally for active-audio controls and Mixurly Player. They are not sent to the Zohsik account or payment backend.
Website access and embedded frames	Mixurly accesses supported HTTP and HTTPS pages and frames only to find playable media, apply local audio behavior, and render its optional page controls.
Spotify-specific handling	Mixurly's packaged Spotify bridge works locally with page-owned playback objects. It does not access Spotify credentials, private account data, authentication headers, or raw audio bytes.
Extension storage	Mixurly saves audio settings, interface preferences, equalizer data, continuity state, and optional account/Pro access state in browser extension storage.
Device and session information	Optional account sessions may include a client-instance identifier and basic browser, platform, extension-version, language, and session-status details used for security, restore behavior, support, and abuse prevention.
Official Zohsik website bridge	Approved pages on zohsik.com may return a completed account session or checkout result after Mixurly verifies the official origin and supported message type.
Service providers	Mixurly may use trusted providers for website hosting, account sign-in, transactional account email, payment processing, restore flows, and Pro entitlement checks.

Service Providers

Mixurly may use trusted service providers only to operate the extension, website, account, payment, restore, and Pro access system. This may include Zohsik hosting, Supabase for account sign-in and Pro access checks, Stripe for hosted checkout and payment processing, and transactional email infrastructure for account emails.

Independent Product Notice

Mixurly - Shaping Sound Across URLs is an independent Zohsik product. References to third-party websites and streaming services identify compatibility contexts only. Mixurly is not sponsored by or affiliated with those services unless expressly stated.

Future Updates

This page may be updated if Mixurly's permissions, Chrome Web Store disclosures, local audio behavior, account flow, payment flow, service providers, production backend, or product features change.

Contact

Questions about Mixurly privacy can be sent to: support@zohsik.com