DubIQ

Privacy Policy

In effect from October 24, 2026. Version 2026-10-24.

This policy explains what Joshua Attlesey, doing business as DubIQ (“DubIQ”, “we”) collects when you use DubIQ at dubiq.io, what we do with it, who else receives it, and how you can delete it. DubIQ works with voices, so please read sections 3 and 6 in particular.

1. In short

  • We keep your account details, the videos you upload, and what DubIQ makes from them.
  • To dub a video we create a synthetic copy of each speaker’s voice. Other companies process your audio and text for us to do that.
  • We do not sell your data, show ads, or use tracking or analytics scripts. We set one cookie to keep you signed in, and a second only if you choose a language for the site.
  • You can delete projects and voices in the app. Nothing you make is deleted automatically, so it stays until you delete it or ask us to.

2. What we collect

Your account

  • Your email address, and your name if you give one.
  • Your password, stored only as a one-way hash that we cannot read back.
  • Your plan, subscription status, minute balance, and a history of minutes added and spent.
  • A log of each dub run: which project, the language, the video’s length, when it ran and what started it (for example a first dub, a re-dub or a retry). We use it to understand our costs and find problems. It holds no text, audio or file names.
  • The version of the Terms and this policy you accepted, and when.
  • When you created your account, and when you last used DubIQ while signed in (to within a few minutes). Our staff can see both.
  • If you use teams: who is on your team, and each invite’s email address and when it was sent and accepted.
  • Your word bank: the words you list there and how you want each language to say them. They stay until you remove them.
  • Your settings, such as which emotions Auto may use when it voices your lines.
  • If you connect the Premiere Pro panel or the DubIQ for YouTube browser extension: a key for it, stored only as a one-way hash, with when it was connected and last used. You can disconnect it on the Team page.
  • If you use the DubIQ for YouTube extension: it keeps which YouTube video each project is matched to, and its progress, in your own browser only. When you start a sync it fetches a project’s dubbed audio, subtitles and translated titles from us and adds them to your video through your own signed-in YouTube Studio. We don’t receive your YouTube sign-in or anything from your channel.

What you upload

  • The video and audio files you upload, or that we fetch from a link you give us, and the titles, file names and folders you give them.
  • If you upload a project as separate tracks: the video, each voice track and the name you give it, and a separate background-sound file if you add one.
  • Voice clips you upload to train a saved speaker.

What DubIQ makes from your uploads

  • The voices separated from the background sound, and the background on its own. For a project uploaded as separate tracks: the voices found in the video’s own sound and the rest of its sound, a copy of each track lined up with the video, where each track has its own sound, and each track's dub on its own.
  • A transcript with timings, who said each line, and your edits to it.
  • Translations, the generated speech for each line, and the finished dubs.
  • A thumbnail image and the data used to draw the waveform.
  • Smaller copies of your video and of each dubbed video, so they play on slower connections, and your video’s sound on its own. They are kept and deleted with the project.
  • A short label for each speaker so you can tell them apart, such as what they are wearing or a name shown on screen, and the gender you set for a speaker.

Payments

Payments are taken by a payment provider. We receive your subscription’s status and identifier. We never receive or store your card number.

Technical information

The companies that host DubIQ keep ordinary request logs, which include IP address and browser type. Our own processing logs record identifiers such as project and speaker ids.

When something goes wrong

  • Errors. When DubIQ hits an error while you are signed in (on our servers or in your browser), we record what failed, the page, the time, your browser type and which account and project it happened in, so we can fix it. We do not record what you type.
  • Problem reports. If you use “Report a problem”, we keep what you write, a screenshot if you add one, the page you were on, your browser, language, time zone and screen size, and your last steps in DubIQ in that browser tab: pages you opened, buttons you pressed (by their label, which can be a project, folder or speaker name), the results of what they asked our servers to do, and messages you were shown. Never what you type into a box. You can see the steps before you send. A report is kept for 90 days, even if you delete the project it is about.

3. Voice data

For each speaker in a video, DubIQ:

  • cuts short clips of that speaker’s voice from the video;
  • sends those clips to our voice-technology provider, which builds a synthetic voice model that sounds like the speaker and holds it for us; and
  • compares voices with software to tell speakers apart, to recognize the speakers saved in your library when they appear in a new video, and to check that a clip belongs to the speaker it is filed under.

The comparison produces numerical measurements of a voice. They exist only while a video is being processed and are not stored. We do keep the result of a check, for example that a clip matched a speaker, with its similarity score.

If you link a speaker in a video to a speaker saved in your library, a clip of that voice from the video is added to the saved speaker so its voice model can be improved. It stays there until you delete the clip or the speaker.

Some laws treat a voice model or a voice measurement as biometric information. We use voice data only to produce your dubs. We do not use it to identify people outside your own projects, and we do not sell, lease or trade it.

Voices of other people. If someone else speaks in your video, their voice is processed in the same way. Our Terms require you to have that person’s agreement first. If you believe your voice has been used in DubIQ without your agreement, write to support@dubiq.io and we will look into it and remove it.

4. How we use what we collect

  • To provide DubIQ: transcribe, translate, voice and mix your videos, and show you the results.
  • To run your account: sign you in, count minutes, and handle your subscription.
  • To send messages you ask for, such as a password-reset link.
  • To keep the service working and safe, fix problems, and handle complaints.
  • To meet legal obligations.
  • To show what DubIQ does: from November 1, 2026, dubs of videos you have published publicly yourself may appear on our website, social media and ads with your channel or account name, as described in section 4 of the Terms. Write to us to stop it at any time.

We do not use your content to train our own models and we do not sell it. Apart from showing dubs as described above, we do not use it for advertising.

5. Who else receives it

We use other companies to run parts of DubIQ. Each receives only what its job needs:

  • Voice technology. Audio from your videos, to transcribe it and to build voice models; the translated text to be spoken; and the generated speech, to check it.
  • Transcription (backup). Audio from your videos, when the main transcription is unavailable.
  • Language models. Transcript text, project titles, translations, the word bank’s words a project uses, speaker names and genders, and a description of how a line was delivered. Also a small number of still frames from your video, used to label who is speaking; only the label is kept.
  • Computing. Your media while it is being processed.
  • Storage, database and hosting. Your files, transcripts and account records.
  • Email. Your email address and the message we send you.
  • Payments. Your email address and account identifier when you start a checkout.

These companies handle the data under their own terms and privacy policies. Write to support@dubiq.io for the current list.

Share links. If you create a share link for a project, anyone who has the link can watch the dub and the original video, read the transcript, and download the project’s files and subtitles, including the video you uploaded. A link keeps working until you delete the project.

Team editors. If you invite someone to your team, they can open all of your projects: watch and listen to them, read and edit the transcripts and translations, and download the project’s files and subtitles. They can also open your saved voices, listen to them and to their training clips. They don’t see your billing or minute balance. When you remove them, or they leave, their access ends at once. An invite stores the email address you sent it to.

Our staff. A small number of DubIQ administrators can open your account to help you and to fix problems: your projects and their videos, transcripts and translations, your saved voices and your word bank. They can look at it, or sign in to it to make changes for you, for example fix a translation, redo a dub or delete a project. What they do for you never uses your minutes, and they can’t change your billing, your team or your connected apps that way. Each time they open your account, and every change they make while signed in to it, is recorded. They can also add free minutes to your account; which administrator added them, and why, is recorded too.

Our team. People at DubIQ who run the service can see account details such as your email, plan and token use, and can access your content when that is needed to fix a problem or handle a complaint.

Law and business changes. We disclose information when the law requires it. If DubIQ is sold or merged, your information may pass to the new owner, under this policy.

6. How long we keep it, and deleting it

We keep your account and content for as long as your account is open. Nothing you make expires automatically, except the temporary voice models described below. Error records are deleted after 30 days, and problem reports (with their screenshots) after 90.

  • Deleting a project deletes its files, transcript, translations, generated speech, finished dubs, and its share link. Voice clips that were added to a saved speaker stay with that speaker. The record of minutes the project used is kept, and so is the log of its dub runs.
  • Deleting a saved speaker deletes the speaker and its voice clips. Its voice model at our voice-technology provider is deleted about a day later (later if one of your projects still uses that voice).
  • Deleting a voice clip deletes the clip. The voice model is rebuilt without it the next time the speaker is trained.
  • Temporary voice models, made for speakers you have not saved to your library, are deleted from our voice-technology provider about a day after a project finishes.
  • A line you delete from a transcript is hidden, and is removed for good when the project is deleted.

Closing your account. Settings → Delete account removes your account, projects, saved speakers, voice models and problem reports right away, and any error records tied to the account within 30 days. You can also write to support@dubiq.io from your account’s email address and we will do it within 30 days. We keep payment records for as long as tax and accounting law requires. Copies in our providers’ backups are overwritten on their own schedules.

7. Cookies and browser storage

  • One cookie, set when you sign in, that keeps you signed in for up to 30 days. Scripts on the page cannot read it.
  • A language cookie, only if you choose a language for the site (with the language button, or a link that names one). It holds that choice and nothing else, for a year. Without it, the site picks its language from the country your connection comes from, as our host reports it, and from your browser’s language settings. Neither is stored.
  • Browser storage on your own device holds your display preferences, such as the languages you last chose and the video quality you picked, how fast your connection was the last time a video loaded (so the player can pick a size that plays smoothly; it is not sent to us), and any transcript text you typed that has not been saved yet. Clearing your browser’s site data removes it.
  • No advertising cookies, analytics, or tracking pixels.
  • Do Not Track and Global Privacy Control. We do not track you across other sites or sell or share your information, so there is nothing for these browser signals to switch off; every visitor is treated as opted out of tracking.

Media files are uploaded to and played from our storage provider directly, using links that expire after a few hours.

8. Your choices and rights

You can ask us for a copy of your data, to correct it, or to delete it, by writing to support@dubiq.io. We answer within 30 days. We will not treat you differently for making a request.

California. We do not sell personal information or share it for cross-context behavioral advertising, and we do not disclose it to third parties for their own direct marketing (California Civil Code section 1798.83). You have the rights to know what we hold about you, to delete it, to correct it, and not to be discriminated against for exercising those rights; write to support@dubiq.io to use them.

Europe and the United Kingdom. We process your data to perform our agreement with you, on the basis of consent where voice data is concerned, and for our legitimate interest in keeping the service secure. You may withdraw consent, object, and complain to your data-protection authority.

9. Children

DubIQ is not for anyone under 18, and we do not knowingly create accounts for them. If a child appears or speaks in a video you upload, our Terms require the agreement of their parent or guardian.

10. Where data is processed

DubIQ and its providers process data mainly in the United States. If you use DubIQ from another country, your data is transferred there.

11. Security

Connections to DubIQ are encrypted. Passwords are stored as one-way hashes. Every request for a project or a voice is checked against the account that owns it. No system is perfectly secure; if you think your account has been accessed by someone else, write to support@dubiq.io. If a security breach affects your personal information, we will notify you as the law requires.

12. Changes

If we change this policy in a way that matters, we will tell you by email or in the app before the change takes effect.

13. Contact

Joshua Attlesey, doing business as DubIQ, DubIQ, 2618 San Miguel Drive #2177, Newport Beach, CA 92660, United States. Email: support@dubiq.io.