In short
- No MixClap account is required to build, pay for or download a mix.
- For manual editing on the website: Audio files are not uploaded to MixClap servers: editing, preview and final encoding run in your browser.
- Projects, source files and exports are kept in IndexedDB on your device until you delete them, clear site data or the browser evicts them.
- Stripe hosts checkout and sends the receipt. As the merchant, MixClap can access transaction data made available by Stripe for support, refunds and accounting.
- When enabled, Google Analytics and Meta Pixel receive navigation and product-usage events plus technical identifiers. MixClap does not intentionally send them audio, file names or email addresses.
Local in-browser processing
For manual editing on the website: Import, decoding, trimming, BPM detection, transitions, preview and final-file generation all run locally in your browser. No audio file is uploaded to MixClap servers. Exception — ChatGPT plugin: if you choose this workflow, authorized tracks are transferred to private MixClap storage to prepare an import link. That link grants access to the files; keep it private. Rendering still takes place in your browser.
To support resume and re-download, the browser keeps source files, settings and the latest export in IndexedDB. Closing the tab does not delete them. Delete a mix from My mixes or clear the site data; MixClap cannot view or erase this local data remotely.
Help and user feedback
When you contact us, your message, optional email, language and current screen are sent to handle your request. Messages use Crisp, with Sentry as a fallback. Crisp chat, when available, loads only at your request and uses cookies to maintain conversations. Crisp also receives technical conversation and visited-page information. The Sentry form does not attach audio files, file names or payment parameters. You can request deletion of your conversations at contact@mixclap.com.
Payment (Stripe)
Payment takes place on a Stripe-hosted page. The information requested depends on the checkout configuration and payment method. When you pay:
- Stripe collects the receipt email and the transaction, billing, device and fraud-prevention data needed for payment.
- Card or other payment-method details are entered directly with Stripe and do not pass through the MixClap application.
- Stripe emails the receipt. MixClap does not email the audio file: the download is unlocked in the browser after payment returns.
- MixClap can view transaction information made available in its Stripe account, including email, amount, currency, date, status, Stripe identifiers and some billing information.
Stripe processes and retains these data under its policy, regulatory obligations and the instructions applicable to the payment service.
Orders and administration (Supabase)
When checkout starts, MixClap saves project metadata in Supabase: file names and sizes, durations, trims, BPM, transitions and export or duration settings. No source or generated audio file is transmitted.
Contact details supplied to Stripe, payment identifiers and statuses, refunds, navigation context and internal notes are stored for order tracking, support and accounting. Access is limited to authorized administrators with two-factor authentication.
To track download requests, MixClap stores a server timestamp, order and payment references, the file name, size, duration and SHA-256 digest computed on your device, together with browser, language and the network address supplied by the host. No audio is uploaded. A browser launch signal does not confirm that a file was saved to disk.
Cookies and local storage
Strictly necessary
IndexedDB and localStorage keep projects, source audio, exports, the current mix and technical payment-return references on your device. Without this storage, project resume and re-download do not work. An essential HttpOnly cookie binds the order to this browser (up to one year). Local payment references remain usable for seven days. Administrator accounts use secure session cookies.
Audience measurement
When Google Analytics 4 is configured, it receives viewed pages and product events (steps, track counts, export success or error), plus session, device, browser and approximate-location information. Its standard configuration can set a _ga cookie containing a client identifier.
Advertising measurement (Meta Pixel)
When Meta Pixel is configured, Meta receives page views and selected funnel events (creation, track addition, export, checkout and purchase), plus technical, browser, device and network identifiers and cookies under Meta’s rules. No audio file is transmitted.
Delete a project from My mixes and clear or block site data in your browser settings. Blocking local storage prevents project saving and recovery; blocking third-party services does not prevent audio editing.
Provider information:
Hosting and support requests
Vercel hosts the site. Like any host and network intermediary, it may process the IP address, requested URL, date and time, user agent and technical logs needed for delivery, security and diagnosis, according to its configuration and policy.
If you email support, MixClap receives your email address, message content and any attachment you choose to send in order to answer the request and meet applicable obligations.
Your rights (GDPR)
MixClap has no customer account and no remote copy of your audio projects. Data may nevertheless exist with Stripe, Google, Meta, Vercel or in support correspondence. Depending on the processing and applicable law, you have the following rights:
- Right of access
- Right to rectification
- Right to erasure
- Right to data portability
- Right to object
- Right to restriction of processing
To exercise these rights, or for any question, contact us at: contact@mixclap.com
Data retention
Local projects remain on the device until deletion, site-data clearing or browser eviction. A local pending-payment reference is considered valid for seven days. Payment, support, analytics, advertising and hosting data are retained under the settings, policies and legal obligations applicable to MixClap and each provider. For projects created through the ChatGPT plugin, temporary access expires after at most 24 hours. Files are then removed by scheduled cleanup, run at least hourly. Copies saved in your browser follow the local project retention rules.
Security
MixClap applies the following measures to protect your projects:
- Communications with the site are protected by HTTPS / TLS.
- No mandatory MixClap account. ChatGPT imports are accessible through a private link.
- Manual edits stay local. ChatGPT imports use temporary private storage. Order metadata is protected by access controls.
- Payment data is entered and processed on Stripe infrastructure.
- Analytics events are designed not to include audio, file names or email addresses.
Contact us
For any question regarding this policy or to exercise your rights:
Email : contact@mixclap.com
You may also lodge a complaint with the French data protection authority (CNIL): www.cnil.fr