Who operates the service

Mix Analyzer provides web and API tools for audio analysis, mix feedback, AI-assisted recommendations, and optional paid token or Supporter features.

For privacy requests, account questions, billing questions, or data deletion requests, use Customer Support.

Information we collect

• Account information: username, email address, password hash, email verification status, reset tokens, newsletter preference, account status, user group, token balance, profile/avatar metadata, and account creation date.
• Audio upload and analysis information: original filename, internal filename, SHA-256 file hash, selected analysis settings, analysis results, generated visualizations, AI model choices, timestamps, and records needed to show or delete your analysis.
• API information: API key name, hashed API key, scopes, creation and expiry dates, usage count, last-used timestamp, endpoint, method, response status, response time, IP address, and user agent for API usage logs.
• Billing information: Stripe customer ID, Stripe subscription ID, subscription status, renewal or cancellation status, credit purchases, token transactions, and Stripe webhook event metadata used to fulfill purchases and subscriptions.
• Support information: name, email address, category, subject, optional account or receipt reference, message content, IP address, user agent, and generated support reference.
• Newsletter information: email address, name or username, subscription status, and sync status when newsletter features are enabled.
• Technical and analytics information: session cookies, CSRF tokens, cookie consent choices, interface preference data, local visit/session counters, page views, browser and device information, language, timezone, referrer domain, and product interaction events.

How we use information

• Provide audio analysis, reports, visualizations, AI-generated mix feedback, comparison tools, and API responses.
• Operate accounts, login, email verification, password reset, API keys, support requests, and account security controls.
• Process token purchases, Supporter subscriptions, billing portal access, credit balances, refunds or corrections, and Stripe webhook fulfillment.
• Run rate limits, fraud prevention, abuse prevention, CSRF protection, upload limits, and security logging.
• Improve reliability, product quality, performance, analytics, and troubleshooting.
• Send transactional emails such as confirmation emails, password reset emails, billing-related notices, and support replies.
• Send newsletter or product emails only when you opt in or where permitted by law.

Audio processing and third-party processors

Most technical analysis is performed by Mix Analyzer using local audio-processing libraries such as librosa, NumPy, SciPy, FFmpeg, and related tooling.

When AI insight features are enabled, Mix Analyzer may send analysis data to AI providers such as OpenAI or OpenRouter. For voice classification, a short extracted vocal segment may be sent to OpenAI if that feature is configured.

Payment processing is handled through Stripe. Newsletter and transactional email functionality may use SMTP and Listmonk. External documentation links are governed by their own policies when you visit them.

Cookies, localStorage, and analytics

Mix Analyzer uses strictly necessary cookies for sessions, authentication, CSRF protection, security, account state, and remembering your cookie choices. Some browser localStorage is used for requested interface preferences such as theme, and optional localStorage may be used for product update prompt state when you allow it.

Browser analytics is optional. When you allow analytics, Mix Analyzer may use Matomo-compatible analytics and local visit/session counters to understand page views, consent-safe funnel steps, feature usage, device/browser characteristics, and product performance. Browser funnel events use allowlisted action names and coarse context; they do not include application user IDs, uploaded filenames, email addresses, form values, or raw error messages.

Mix Analyzer separately records requests made by supported user-triggered AI assistants to reviewed public HTML pages. This server-side telemetry contains the requested URL without query parameters, the assistant User-Agent, response status, response size when available, and processing time. It does not create a human visit or session and does not include cookies, account identifiers, uploaded filenames, IP-address overrides, referrers, form values, or private routes.

Independently of the browser analytics choice, Mix Analyzer records a limited set of server-side account, checkout, purchase, and subscription lifecycle events needed to measure service operation and product outcomes. These aggregate event rows contain allowlisted categorical context only. They do not contain email addresses, usernames, application user IDs, uploaded filenames, or raw Stripe identifiers; operational Stripe identifiers used for deduplication are stored as one-way hashes.

How long information is kept

• Source audio files: deleted after analysis completes, with retry logging if deletion fails.
• Analysis records: kept so you can access history, compare results, use API responses, and manage reports, unless deleted by you or through a support request.
• Account, billing, and token records: kept while your account is active and as needed for security, accounting, dispute handling, tax, and legal obligations.
• Support messages and logs: kept as needed to answer requests, investigate abuse, protect the service, and maintain records of billing or account decisions.
• Newsletter records: kept while subscribed or blocklisted so unsubscribe preferences can be honored.
• AI-assistant request telemetry: follows the raw-data retention and cleanup settings configured in Matomo.
• Aggregate product event rows: automatically deleted after 400 days. Underlying account, analysis, billing, and token records follow their separate retention rules above.

Your choices and rights

• You can delete individual analysis records from the app where deletion controls are available.
• You can manage newsletter preference from your account, and Listmonk unsubscribe/privacy tools may also be available on newsletter pages.
• You can request account deletion, access, correction, export, or privacy help through Customer Support.
• You can manage paid subscription status through the Stripe customer portal when available in your account.
• You can change cookie choices from the Cookie settings link in the site footer.
• You can clear browser localStorage and cookies in your browser, but doing so may reset anonymous analytics state or sign you out.

Security

Mix Analyzer uses HTTPS in production, password hashing, CSRF protections, rate limits, signed tokens, API key hashing, webhook signature verification, security headers, upload limits, and restricted file handling. No internet service can guarantee absolute security, so report suspected account or billing issues through support.

International use

Mix Analyzer can be accessed from different countries. Your information may be processed where Mix Analyzer, hosting providers, Stripe, email providers, analytics providers, or AI processors operate.

Changes to this policy

We may update this policy when the product, billing model, processors, or legal requirements change. The updated version will be posted on this page with a new last-updated date.