Mixxi v2.7
  • Home
  • Privacy Policy
  • Terms of Service
Try 30s X-Ray Get Mixxi — $55
Official Google OAuth & Studio Privacy Disclosure

Mixxi — Privacy Policy & Google User Data Disclosure

Effective Date: November 15, 2026 · Studio Contact: solomonron@gmail.com

1. Local-First Studio Architecture (Zero Audio Uploads to Mixxi Servers)

Mixxi is built as a local-first mixing and mastering workstation companion. Your core acoustic DSP analysis (MixEngine, ForensicMixingEngine, Live Bridge WASAPI loopback capture, Cubase .cpr X-Ray inspection, Taste DNA calibration, and .mixxi song session archives) runs entirely on your local Windows computer.

Mixxi operates no external servers or cloud databases for storing your music, stems, mixes, .mixxi session archives, or client PDF certificates. Files you save or export stay on your local drives in folders you control (for example your configured sessions directory or exports directory).

2. Sign in with Google & Google API Services User Data Policy (Limited Use)

Linking a Google account inside ⚙️ Settings → 3. Studio Identity & Google Account is completely optional — you can skip Sign in with Google and use Local DSP or paste a personal Gemini API key directly.

When you choose to sign in using OAuth 2.0 Desktop loopback authentication (openid, email, profile scopes):

  • Data Requested: Only your Google display name and primary email address (along with standard basic profile metadata returned during sign-in).
  • How It Is Used & Stored: Mixxi uses your name and email solely inside the local application to display and label your Studio Identity / Profile on your machine. Your email is stored locally in config/secrets.json alongside your studio preferences. Mixxi does not persist OAuth access or refresh tokens to disk.
  • Zero External Sharing or Scope Creep: Mixxi does not access your Gmail, Google Drive, Contacts, Calendar, or files, does not transfer your Google profile data to any Mixxi server, never sells or rents user data, and never uses Google user data for advertising, profiling, or training AI models.
  • Google Limited Use Compliance: Mixxi's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3. Bring-Your-Own-Key (BYOK) Gemini API & Multimodal Privacy

  • Your personal Google AI Studio API key is encrypted on your PC using machine-bound Fernet symmetric encryption (AES-128-CBC + HMAC-SHA256) inside config/secrets.json.
  • When you trigger an AI analysis (such as Analyze, Generate Diagnosis, or follow-up chat), Mixxi sends the selected 24 kHz stereo WAV audio excerpt, anonymous DSP metrics, and (only when explicitly enabled/captured for plugin inspection) downscaled active DAW plugin screenshots (max 1024px) directly from your computer over HTTPS to Google's Gemini API under your own Google AI Studio / Google Cloud account terms and zero-training/paid-tier billing settings.
  • If no API key is configured, Mixxi stays in offline Local DSP Mode with zero external AI network calls.

4. Crash Diagnostics, 1-Click Support Uploads & Opt-In Sentry Telemetry

  • When Automatic Crash Logging is enabled in Settings, Mixxi records unhandled exceptions and audio/DAW diagnostic events locally to logs/mixxi_diagnostics.log.
  • Automatic Redaction: Before writing diagnostic logs, uploading support reports, or forwarding opt-in Sentry crash events, Mixxi automatically scrubs sensitive credentials (AIza... API keys, Fernet tokens, OAuth client secrets, bearer/access tokens, Sentry DSNs, and OS account folder names).
  • 7-Day Retention: Diagnostic log files and log entries older than 7 days are automatically pruned/overridden on startup and log rotation.
  • Manual 1-Click Support Reports: Diagnostic reports are never uploaded automatically — they are only shared when you explicitly click Send Crash / Support Logs in Settings (uploaded over HTTPS directly to solomonron@gmail.com with optional reply email, or saved locally with mailto: fallback when offline).
  • Strictly Opt-In Anonymous Crash Grouping (Sentry): Off by default. Only when you explicitly enable Anonymous Crash Grouping (Sentry · Opt-In) in Settings does Mixxi transmit anonymized Python exception tracebacks (send_default_pii=false, zero audio, zero mix files, zero DAW screenshots).

5. How to Access, Revoke, or Delete Your Data Anytime

  • Unlink Google Account in Mixxi: Open ⚙️ Settings → 3. Studio Identity & Google Account and click Sign Out. This immediately removes your Google email/name profile from local storage while preserving your studio settings and BYOK API key.
  • Revoke Google OAuth Permission: Visit your Google Account Third-Party Connections page at myaccount.google.com/connections, select Mixxi, and choose Remove Access.
  • Delete API Key: Open ⚙️ Settings → 4. Gemini API Key and click Clear.
  • Delete Saved Sessions & Logs: Delete .mixxi archives individually inside Sessions ▾ or directly in your sessions folder, and optionally remove config/secrets.json or logs/ from your Mixxi workspace directory.
Mixxi v2.7 mixxiai.com
Home Privacy Policy Terms of Service solomonron@gmail.com