Legal

Privacy Policy

What Audial collects, why, who processes it, how long it is kept, and how to access or delete your data.

Last updated: 5 November 2026

Audial ("we", "us") provides hosted audio tools through audialmusic.ai, a REST API, a Python SDK, an MCP server, and two plugins (Audial Synth and text2vox). This policy explains what we collect, why, and what you can do about it. It applies to all of those surfaces.

What we collect

Account details. When you sign up we collect your email address and name through Firebase Authentication. If you sign in with Google, Google shares your name, email and profile picture with us.

Billing details. Subscriptions are processed by Stripe. Stripe collects your payment card and billing address; we never see or store full card numbers. We keep your subscription status and Stripe customer ID so we know what your account is entitled to.

Audio and files you send us. Anything you upload or send to the API (audio, MIDI, JSON) and everything we generate from it (stems, masters, MIDI, sample packs, presets, vocals, songs, analyses with their audio features, tags and lyrics) is stored in your account so you can download it again. Stems are created automatically for each analysis and kept in your account like other results. Text you send, such as lyrics, prompts and reference transcripts, is stored with the job it belongs to.

API keys. You can create API keys from your dashboard. We store a hash of each key, not the key itself.

Usage and technical data. Our servers log each request with its timestamp, endpoint, your user ID, your IP address, and the user agent of the client. We use these logs to run the service, prevent abuse and debug problems.

Support and newsletter forms. The contact and unsubscribe forms on the site are delivered to our inbox by FormSubmit. We keep your message and the email address you provide.

Site analytics. We use PostHog to see how people move through the site: pages viewed, where they came from, what they clicked, and recordings of visits to public pages, which we watch to find what is confusing or broken. Text typed into forms is hidden in those recordings, and we do not record your dashboard, your profile or your API keys. PostHog links this activity to your user ID once you sign in, and uses browser storage to recognise you between visits. Vercel Web Analytics also counts page views and product events without cookies. We keep a record of how you first reached the site (the referring site, the landing page and any campaign tags) and attach it to your account.

If your browser sends a Do Not Track signal, PostHog does not run.

We do not run advertising scripts on the site.

How we use it

  • To provide the service: run your jobs, store your results, and show them in your dashboard.
  • To bill you and manage your subscription.
  • To keep the service secure: rate limiting, abuse detection and investigating problems.
  • To answer support requests.
  • To send occasional product updates, if you have opted in. Every such email has an unsubscribe link.

We do not sell your data, and we do not use the audio you send us to train models.

Who processes it for us

We rely on these providers. Each one only receives what it needs to do its job.

  • Google Cloud / Firebase (authentication, database, file storage)
  • Stripe (payments)
  • RunPod (GPU servers that run the audio processing; your audio is sent there for the duration of a job)
  • MusicBrainz (a public music database; when you ask for a track's tags, we send it the track's title and artist, read from the file's own tags or name, to find its artist and recording tags; never the audio)
  • OpenAI (when you ask for a track's tags and the file's own tags do not name its title and artist, we send the file name, and nothing else, so a model can guess them)
  • DigitalOcean (API hosting)
  • Vercel (website hosting)
  • GitHub (plugin downloads and source code)
  • FormSubmit (contact and unsubscribe forms)
  • PostHog (site analytics and session recordings)

The plugins and the MCP server

Audial Synth, text2vox, the Python SDK and the MCP server run on your machine. They send data only to api.audialmusic.ai, and only when you ask them to: the audio or MIDI you choose, your user ID and API key, and the job's settings. Results are written to your disk. Audial Synth works without an account; only the Resynth panel talks to our API. The plugins do not collect analytics or crash reports.

How long we keep it

Files and results stay in your account until you delete them or ask us to. Account details and subscription records are kept while your account is open. Request logs are kept for a limited period for security and operations, then deleted. If you close your account, we delete your files and account details within 30 days, except what we must keep for tax or legal reasons.

Your choices and rights

You can download or delete your files from the dashboard at any time. You can revoke API keys from the dashboard. You can cancel your subscription from the billing portal. To access, correct, export or delete your personal data, or to close your account, email contact@audialmusic.ai and we will respond within 30 days. If you are in the EU, UK or California, you have additional rights under local law and can exercise them the same way.

Children

The service is not directed to children under 13 and we do not knowingly collect their data. If you believe a child has given us data, contact us and we will delete it.

Changes

If we change this policy in a way that matters, we will update the date above and, for significant changes, email account holders.

Contact

Audial, contact@audialmusic.ai