نُطقnutq

Privacy Policy

Last updated 14 October 2026

This describes what nutq collects when you use the API or the dashboard, how long it is kept, and who else handles it. It is written to be checked against what the service actually does rather than to cover every eventuality.

The short version

Audio you send for transcription is deleted as soon as the request finishes. We do not store transcripts, and we do not store generated speech. We do not train models on anything you send. What persists is your account, a record of what each request consumed and cost, and any voice you explicitly chose to save.

The website itself works differently in two ways, both set out below: we record how the website and dashboard are used, and a recording captures what was on the page at the time; and we tell Meta which of our pages a browser visits, and when someone signs up, creates their first API key, first uses nutq from their own code or an AI agent, or pays us, so we can measure our ads on Facebook and Instagram.

What we collect

  • Account — your email address and sign-in identity, handled by our authentication provider. We do not hold your password.
  • Audio you send for transcription — held only while the request runs, in temporary storage on the inference machine, and removed when it completes or fails.
  • Text you send for synthesis — processed in memory to produce audio and not retained afterwards.
  • Voices you save — if you save a cloned voice, we keep the reference recording and the line of text that accompanies it, until you delete the voice.
  • Usage records — for each request: whether it was transcription or synthesis, its duration or character count, the compute it took, what it cost, and when. These carry no transcript and no audio.
  • Payment — handled by Stripe. We receive confirmation that a payment succeeded and its amount. Card numbers never reach us.
  • Technical logs — request metadata and errors, kept briefly for debugging and abuse prevention.
  • How the website and dashboard are used — pages visited, clicks, and recordings of sessions. See Analytics, below.
  • Advertising measurement — which of our pages a browser visited, and when you sign up, create your first API key, first use nutq from your own code or an AI agent, or pay us, sent to Meta. See Advertising, below.

What we do not do

  • We do not train models on your audio, text, or output.
  • We do not sell personal data. The only advertising service we use is Meta's, described below, and it is never sent your audio, your text, your transcripts or your keys.
  • We do not listen to your recordings, except where you ask us to help with a specific problem and give us the file.

Analytics

We use PostHog to understand how people use nutq and to find what breaks. In your browser it records:

  • the pages you visit and what you click, with the sentence typed into the front page's composer removed from page addresses;
  • recordings of sessions on the website and dashboard, so we can see where people get stuck. A recording captures what was on the page, so a recording of the dashboard can include text you typed or a transcript on screen. Password fields and API keys are never recorded;
  • errors, and how quickly pages load.

Like any request, these carry your IP address. When you are signed in, this is linked to your account, including your email address and name. Our servers also send PostHog a description of each request — its kind, length, language, duration and cost — but never the audio, the text or the transcript itself.

Advertising

We advertise on Facebook and Instagram, and use the Meta Pixel to measure whether those ads bring people to nutq. When you open a page of our website or dashboard, your browser sends Meta:

  • the address of the page, and of the page you came from;
  • your IP address, and technical details of your browser and device, such as its screen size;
  • an identifier Meta keeps in a cookie on our site (_fbp), and, if you arrived by clicking one of our ads, the click identifier Meta added to that link.

Our servers also tell Meta directly at four moments: when you sign up, when you create your first API key, when your own code or an AI agent first uses nutq successfully, and when you pay us. Each report carries:

  • a one-way hash (SHA-256) of your email address and of your nutq account id, which Meta uses to match the report to a Facebook or Instagram account, if you have one;
  • your IP address and browser, and the Meta cookies above — except the report of your first use from code or an agent, which carries the hashes alone, since that request came from your software rather than your browser;
  • for a payment, its amount.

So that a payment can be reported once Stripe confirms it, the Meta cookies, your IP address and your browser are stored with the order at Stripe.

Meta is not sent your audio, text you type, transcripts, generated speech, API keys, or your name or phone number, and your email address only as the hash above. The pixel does not record what you click, and it is kept off any page whose address carries something private: the sign-in screens for AI agents, upload links, and any address holding text you typed.

Meta uses what it receives under its own privacy policy, which includes showing you ads. You can control that in your Meta ad preferences. Blocking third-party cookies or scripts in your browser stops what your browser sends, and nutq works the same either way; the reports from our servers still go, without the cookies.

Cookies and browser storage

  • Signing in — cookies from Clerk that keep you signed in. Without them you cannot use the dashboard.
  • Preferences — your language, in a cookie, and light or dark theme, kept in your browser and never sent to us.
  • The front page's draft — a sentence typed into the composer before signing up travels in the address of the sign-up and studio pages, and in your browser's session storage, until the studio uses it.
  • Analytics — a PostHog cookie that recognises your browser between visits.
  • Advertising — Meta's _fbp cookie, and _fbc if you arrived from one of our ads.

You can block or delete any of these in your browser. Blocking the analytics and advertising ones changes nothing about how nutq works; blocking the sign-in ones signs you out.

Where it is processed

nutq is operated from the United Arab Emirates, but the systems that run it are not all in one place. If where your data is processed matters to you — and for regulated work in the Gulf it usually does — this is the current picture:

  • Website and API — Vercel. Requests enter at the nearest edge, but the code runs in Washington DC, United States.
  • Database — Neon, Virginia, United States (us-east-1). Accounts, usage records, voice metadata.
  • Inference — a rented GPU host in France. Audio passes through it and is deleted on completion.
  • Saved voice recordings — Microsoft Azure Blob Storage, currently in Pune, India, in a private container.
  • Analytics — PostHog, United States.
  • Advertising measurement — Meta, in the United States and elsewhere.
  • Authentication — Clerk. Payments — Stripe. Network — Cloudflare.

Traffic between our own components is encrypted in transit. Saved voice recordings are never publicly readable: each is reached through a signed link that expires within the hour.

None of that is in the UAE, and we would rather say so plainly than imply otherwise. We are moving voice recordings to an Emirati region, and the remaining components are constrained by what our providers offer. If your recordings may not leave a particular jurisdiction today, the hosted service is the wrong product for you: the same models can be deployed inside your own network, where nothing is sent to us at all.

Voice recordings, specifically

A saved voice is a recording of a person, and we treat it as more sensitive than the rest. You must confirm you have the right to use a voice before saving it. Deleting a voice removes the recording itself, not merely the entry pointing at it. We do not use saved voices for anything other than generating speech when you ask for it.

How long we keep things

  • Uploaded audio and generated speech — not kept.
  • Transcripts — not kept.
  • Saved voices — until you delete them, or until your account closes.
  • Usage and billing records — retained while the account exists, and afterwards where accounting rules require.
  • Account details — until you delete the account.

Your rights

You can ask what we hold about you, correct it, export it, or have it deleted. Deleting your account removes your voices and account details; usage records may survive in an aggregated form where we are required to keep them. Write to privacy@nutq.dev and we will respond within 30 days.

Children

nutq is not intended for anyone under 18, and we do not knowingly collect their data.

Changes

If this policy changes materially — particularly anything above about what is kept or where it is processed — we will email the address on your account before the change takes effect.

Contact

privacy@nutq.dev