Privacy policy

Who we are

MadeinVox (madeinvox.com) is an online multilingual video dubbing studio operated by Ulamna LLC (30 N Gould St Ste R, Sheridan, WY 82801, USA), the controller of your data. This policy applies to the public website, the studio and the API of madeinvox.com. For any question about your data, write to us from the Contact page and select the “Personal data” category.

Data we collect

We collect only what is necessary to provide the service:

• Account: email address, password stored only as a hash (scrypt), role, creation date, and display name, company and bio if you provide them.
• Sign-in with Google: Google account ID, email address verified by Google and profile name (see the section “Data received from Google and YouTube”).
• Linked YouTube channel, if you link one: the channel’s ID, name, handle, picture and subscriber count, and the list of your recent videos (ID, title, thumbnail, duration, publication date, visibility).
• Project content: imported video or audio files, added YouTube links, selected languages, transcripts, translations, dubbing directions, selected voices, produced versions and edits.
• Voices: the recording of your personal voice (deleted from our servers as soon as the speech synthesis provider has answered), the reproduced voice made from it and its consent record; the voices of the people speaking in your videos, taken from those videos, when you ask for them to be reproduced (see the section “Reproduced voices”).
• Workspaces: workspace names, invited members and their roles.
• Billing, once available: selected plan, minutes used and payment identifiers provided by our payment provider. We never see or store your card number.
• Communications: messages sent from the Contact page, questions asked to the studio assistant and your feedback on its answers, and the notification address if you request an email when a video is ready.
• Technical data: active sessions (creation and expiry dates), security and error logs (time, request type, IP address in hashed form for rate-limiting sign-in attempts).

Why we use it

Each item of data serves a specific purpose:

• Creating and securing your account, signing you in (including with Google) and protecting the service against abuse (performance of the contract and legitimate interest).
• Preparing, dubbing, reviewing and exporting your videos, and showing the progress of each language (performance of the contract).
• Displaying your YouTube channel and offering its videos so you can choose the one to dub (your explicit request, which you may withdraw at any time).
• Sending you an email when a video is ready, only if you have requested it (consent).
• Managing subscriptions, minutes and payments once these are available (performance of the contract and accounting obligations).
• Replying to your messages and improving the assistant’s answers based on the questions asked (legitimate interest; no resale, no advertising profiling).

What we do not do

We do not sell your data, we do not rent it out and we do not use it for targeted advertising. We do not use your content or your Google or YouTube data to train generalized artificial intelligence models. No third-party advertising tracking tool is installed on the website.

Data received from Google and YouTube

If you choose “Continue with Google”, we request only the openid, email and profile permissions: they give us your Google ID, your verified email address and your name, used solely to create your account, sign you in and display your name in the studio.

If you choose “Continue with YouTube” or “Link my YouTube channel”, we additionally request the read-only youtube.readonly permission. It is used solely to read the public presentation information of the channel you select (name, handle, picture, subscriber count) and the list of your recent videos, in order to display them in your workspace and let you choose the video to dub. We do not publish, modify or delete anything on your channel.

Google access tokens are used only at the time of sign-in or linking and are then discarded: we do not keep any access token or refresh token. The information read is stored in our database, attached to your account, and is visible only to you.

This data is not shared with any third party, except our hosting providers for storage, or where required by law. No person accesses it, except with your consent to help you, for security reasons or to comply with the law.

MadeinVox’s use and transfer to any other app of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.

By using the YouTube features of MadeinVox, you agree to the YouTube Terms of Service (https://www.youtube.com/t/terms). Google also processes your data in accordance with its own Privacy Policy (https://policies.google.com/privacy).

You can unlink your channel at any time in the studio (My account → YouTube channel → Unlink): the channel and the list of videos are then deleted from our servers. You can also revoke MadeinVox’s access to your Google account at https://myaccount.google.com/permissions.

Google and YouTube user data (summary)

Sign in with Google requests only the openid, email and profile scopes, used to create your account, sign you in and show your name. Continue with YouTube also requests the read-only youtube.readonly scope, used only to display the channel you select (title, handle, picture, subscriber count) and your recent videos so you can choose which one to dub. MadeinVox never uploads, edits or deletes anything on YouTube.

Google access tokens are used once during sign-in or linking and are not stored; no refresh token is kept. The data read is stored in our database, attached to your account, visible only to you, never sold, never used for advertising and never used to train generalized AI models. It is shared only with our hosting providers for storage or when required by law.

MadeinVox’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. By using the YouTube features you agree to the YouTube Terms of Service (https://www.youtube.com/t/terms); see also the Google Privacy Policy (https://policies.google.com/privacy).

You can unlink your channel at any time in the studio (My account → YouTube channel → Unlink), which deletes the stored channel data, and revoke MadeinVox’s access at https://myaccount.google.com/permissions. You can also delete your account yourself in the studio (My account → Delete my account).

Who we share data with

Only with service providers that need it to deliver the service, bound by contract and limited to that use:

• Hosting of the website, database and files: our server provider.
• Audio processing and voices: transcription and speech synthesis providers (for example ElevenLabs), and rented GPU compute servers used to separate the voice from the background. They receive the audio excerpts needed, including the recording of a personal voice, or the voices of the people in a video when you ask for them to be reproduced.
• Payments, once available: Stripe, which processes card data directly.
• Transactional emails: our email delivery provider, only for messages you have requested.
• Sign-in with Google: Google, in accordance with its own policies.

Retention periods

• Account and profile: until you delete your account (My account → Delete my account). Deletion is immediate (see the section “Account deletion”).
• Project videos and audio files (imported file, separated tracks, generated voices, dubbed versions, edits, logos): a period that depends on your plan, counted from the last completed dub (or, failing that, from the creation of the project). Current periods: 7 days with the free trial, 30 days with Créateur, pay-as-you-go minutes and Pack 45, 90 days with Pro, Pack 160 and Pack 550, 180 days with Studio. They are shown on the Pricing page.
• This period is frozen at each delivered dub: it never becomes shorter if you change plan, if your subscription stops or if your minutes run out; moving to a plan with a longer period lengthens it. Projects created before October 21, 2026 keep 30 days, whatever the plan.
• Before deletion, the countdown is shown on each project and a reminder email is sent to you within the 24 hours beforehand (a single grouped email per inbox every 24 hours). Deletion waits for that reminder to have gone out, for 7 days at most. A project with processing in progress is never deleted.
• A project deleted by you or with your account: its files (server and storage), transcript, translations, title, file name and video link are deleted at once. Only a technical record remains (dates, languages, duration, voice settings), to which the minutes used and the invoicing refer.
• A project’s transcript and translations: until the project is deleted, even after its videos are deleted at the end of the keeping period.
• Personal voice: until you delete it, until the owner of the workspace where you recorded it removes you from that workspace, or until you delete your account; it is then erased at our speech synthesis provider, then on our side. The recording sent to create it is deleted from our servers as soon as the provider has answered.
• Voices of the people in a video: the copy is deleted at the provider as soon as all the project’s languages are dubbed (a new dub creates it again), and at the latest with the project’s files.
• Voice consent record: kept as proof, including after the voice or the account is deleted (it is closed, not erased).
• Linked YouTube channel and list of videos: until the channel is unlinked or the account is deleted.
• Sign-in sessions: 30 days without a visit, extended with each visit; temporary Google sign-in states: 10 minutes.
• Contact messages and questions to the assistant: 24 months at most.
• Technical and security logs (emails sent, paid provider calls, GPU processing): 12 months at most. The log of administrative actions (minutes granted, refunds, deletions) is kept as evidence, like billing data.
• Billing data: the period required by accounting obligations.
• Database backups: 35 days in our Cloudflare storage, 3 days on the server disk. Data erased from the database may therefore remain in a backup for that time.

Reproduced voices

A reproduced voice can identify a person. We treat it as biometric data, that is, sensitive data: it is reproduced only with explicit consent (see the Voice consent page).

• Personal voice: created only from your own recording, after you have confirmed in the studio, with the statement shown in your language, that the voice is yours. It stays private until you share it with your team.
• Voices of the people in a video: a copy is made only after you confirm that every person speaking has agreed to have their voice reproduced (or that you are that person). This confirmation is recorded for the project, or for the channel with automatic dubbing, where it is asked again every year.
• Consent record: who consented, when, a fingerprint of the network address (never the address itself), the version and language of the statement shown and, for a personal voice, the fingerprints of the recording and its duration.
• Provider: the recording or the voice is sent to our speech synthesis provider, a third-party company, which makes from it a copy used only for your dubs.
• Withdrawal: deleting your personal voice withdraws your consent and erases the voice at the provider, then on our side; it is also erased if the owner of the workspace where you recorded it removes you from it, or if you delete your account.

Account deletion

You can delete your account yourself in the studio (My account → Delete my account). For your security, you must have signed in within the last 15 minutes and type the account’s email address. Deletion is immediate and final.

• Your personal voices, and those recorded in the workspaces that close with your account, are deleted at the speech synthesis provider. If the provider does not answer, the account is not deleted and you can try again.
• Your subscriptions are stopped; if Stripe fails to stop an active subscription, the account is not deleted.
• The projects in the workspaces you own are deleted (videos and files, transcripts, translations, titles, file names and links), and those workspaces are closed: their other members are removed from them.
• Erased: your sessions and sign-in identities (including Google), your profile and customer details, your onboarding answers, your YouTube channel and its list of videos, automatic dubbing, your favorite voices, your questions to the assistant, your referral codes with the payout details they hold, and your email preferences.
• Anonymized: your address in the log of emails sent, in your contact messages and support conversations, and the notification address of your projects.
• Kept, because the law or a proof requires it: orders and invoices, payments made to an affiliate, voice consent records, the log of administration actions, and the workspace’s minute and credit ledgers, to which these records are attached. Your account then stays in the database under an address that can never be used to sign in again.

Security

Communications are encrypted (HTTPS), passwords are stored as hashes, sessions are managed server-side with protection against cross-site requests, sign-in attempts are rate-limited and provider keys remain on the server. Files are stored in a private space, accessible only to members of your workspace.

Your rights

You may request access to your data, its correction, deletion or portability, or object to certain processing. You can delete your account yourself (see “Account deletion”). For anything else, write to us from the Contact page (“Personal data” category); we reply within one month. You may also lodge a complaint with the data protection authority of your country (in France, the CNIL). Several settings are available directly in the studio: editing your profile, closing sessions, unlinking your YouTube channel, deleting your personal voice and unsubscribing from notification emails.

Cookies

We use only necessary cookies: sign-in session, protection against cross-site requests and temporary Google sign-in state. Your light or dark theme preference is kept in your browser. See the Cookies page.

Changes

We will publish any change to this policy here, together with its date. If a change affects how we use your Google data, we will notify you before applying it. Last updated: October 30, 2026.