Data controller
The controller of the personal data processed by Doing Dumb Dubs is the operator of this service. This policy describes what the software running the service actually does.
No contact email address for the operator has been published on this instance yet.
Data we process
- Account: username, email address, password (hashed, never readable), creation and last-login dates, date you accepted the terms, date your email was verified, whether you want notifications by email.
- Two-factor authentication (if you turn it on): the secret that generates your codes.
- Sessions: for each open session, the IP address, the browser (user agent), and the opening and expiry dates — the “Your sessions” list in My account › Security.
- Audit log: the actions carried out with your account (sign-in, take upload, pages viewed…), with their time. The IP address is recorded for sign-in, password-reset request and completion, email verification, joining a workshop and session management.
- Imported videos: the file (uploaded or imported from a link), its name, title and technical characteristics, the original address for a link import, and what processing derives from it (extracted audio, separated voice and background tracks, scene cuts).
- Texts: transcribed and adapted lines, characters and assigned actor, revision history, suggestions and votes, glossary, rythmo band marks, comments — with their author.
- Voice: the takes you record in the studio (with their quality measurements and the reviewer’s note), your auditions for a role, your karaoke performances — voice, and camera image if you film yourself.
- Exports: the files produced (dubbed video, separate tracks, subtitles).
- Gallery: what you publish — title, credits (role and pseudonym), date, view count. The view counter does not record viewers’ IP addresses.
- Projects: name, language, visibility, each member’s role, invitations.
- Workshops: the first name entered by the student and the date they joined.
- Notifications: notifications received in the app and, if you turn on push on a device, that browser’s subscription.
- Subscription: the plan, its status, its dates, the plan scheduled for the next renewal, the date from which the song counter counts, the proof of your request for the plan to start right away (the time, the plan, the reference of the Stripe session or invoice), and the subscription and customer identifiers at Stripe; the version of the terms is kept for 180 days in the activity log, and at Stripe. No card number.
- YouTube publishing (if you link your channel): the Google refresh token and access token (“upload videos” scope).
- Preferences: your karaoke display settings.
- Remote access keys (created only by the administrator, on the server): their name, a fingerprint — never the key itself — and when they were last used.
- Server technical logs: for each request, the IP address, date, requested address, response code, referring page and browser.
Purposes and legal bases
- Running your account, hosting and processing your videos, texts and voice, collaboration within your projects, producing your exports — performance of the contract (the terms of service you accept).
- Managing plans and payment — performance of the contract.
- Emails for password reset and address verification — performance of the contract.
- Securing the service: sessions, audit log, attempt limits, two-factor authentication, preventing abuse — legitimate interest of the operator in protecting the service and its users.
- Keeping proof of your acceptance of the terms and of your request for immediate performance (right of withdrawal) — legitimate interest.
- Keeping the server’s technical logs (security, diagnosing failures) — legitimate interest.
- Notifications by email or push — consent, which you give and withdraw in My account › Notifications.
- Publishing in the gallery or on YouTube — consent: nothing is published without your explicit action, and you can withdraw it (unpublish, revoke access in your Google account).
A username, an email address and a password are needed to create an account: without them there is no account (a workshop student gives only a first name). The rest of the data comes from your use of the service. No decision producing legal effects concerning you, or similarly significantly affecting you, is based solely on automated processing.
Answering your messages to support, and keeping our exchanges for a possible dispute: legitimate interest (see Messages to support).
Recipients, processors and providers
Within the service
- Members of your projects see what their role allows, including your email address.
- Only a project’s members see its videos and texts, listen to its studio takes, to the auditions submitted to its casting calls and to its karaoke performances, and download its exports. Where the site allows public projects, a signed-in account that is not a member of a public project sees only its overview (name, language, list of videos and their progress, members’ pseudonyms, casting calls). The raw camera recording of a performance is shown only to the singer and to project members.
- Members of the project behind a casting call listen to the auditions submitted to it.
- A workshop teacher sees their students and their progress, and is notified of each arrival (first name and username).
- Platform administrators see the list of accounts (with email addresses) and the audit log, and can suspend an account.
- During the closed beta, the team sees the feedback you send, your beta access, your usage measured against the beta limits and the errors your browser reports (see Closed beta).
- What you publish in the gallery can be seen, depending on the site’s setting, by everyone or by signed-in accounts only (by no one if the gallery is closed): in the list if the publication is public, only by people who have the link if it is unlisted (the default).
Hosting, processors and other providers
The server is hosted by a provider chosen by the operator of this service.
Automatic speech transcription and track separation run on the service’s own server, without an outside provider.
No outside service is enabled on this instance.
The other services the software can use — DeepL (machine translation), AI rewriting service (“Adapt” button), Text-to-speech service (guide voice), Email delivery provider, Stripe (payments), Google (publishing to YouTube), Browser push services, Cloudflare (traffic routing) and Video hosts (import from a link) — are not used on this instance.
The service contains no advertising and no audience-measurement tool.
Transfers outside the European Union
For a provider based in the United States, the transfer relies on the European Commission’s adequacy decision (EU–US Data Privacy Framework) where that provider is certified under it, and otherwise on the standard contractual clauses adopted by the Commission; elsewhere outside the Union, on an adequacy decision or on those same clauses. The operator of this service will tell you on request which safeguard applies to each provider and give you a copy.
Where the server itself is located depends on the hosting provider chosen by the operator.
Messages to support and beta feedback: alerts, feedback and its analysis go through Discord, in the United States, and validated feedback may be copied to GitHub, in the United States (see Messages to support and Closed beta).
How long we keep data
- Account: as long as it exists. When you delete it, it is not erased from the database but pseudonymised and deactivated: the record keeps its internal identifier; username and email address are replaced, the password made unusable, two-factor authentication and sign-in dates cleared. This pseudonymised record is kept with no time limit: it is still personal data, not anonymous data. The account’s audit log stays linked to it for 365 days after the deletion, then it is deleted, except the entry that records the deletion (see below).
- Sessions: until you sign out of that session, change or reset your password, the account is suspended or deleted. Sessions that have merely expired are not erased automatically.
- Audit log: records of pages viewed are erased after 90 days, IP addresses after 365 days; other actions are kept as long as the account exists. When the account is deleted, the details and IP addresses in its log are erased; 365 days after the deletion, that log is deleted, except the entry that records the deletion, kept without an IP address. These periods are default settings, which the operator can change (AUDIT_COMPTE_EFFACE_JOURS, AUDIT_IP_RETENTION_JOURS).
- Videos, derived files and exports: until you delete them (video or project). The administrator can turn on automatic deletion of the oldest ones; it is off by default. Some files the service can make again are erased sooner: a transposed track nobody has listened to for 30 days; an advanced download nobody has opened for 7 days (1 day if it failed) and, beyond 6 per video and per account or 20 per account, the one opened least recently.
- Texts: until the video or project is deleted. When you delete your account, your comments are erased; your revisions, suggestions, glossary entries and rythmo marks stay in the projects, attached to the pseudonymised profile. In comments that other members wrote in the projects you were a member of, mentions of “@your username” that can only refer to you become “@Deleted account” (in the language of the comment’s author), and so does the start of those comments shown in their notifications on the site; a mention that could also refer to another member or that runs into the next word, your username written without “@”, the rest of their text, and the emails and alerts already received on a phone or in a browser, do not change.
- Takes and karaoke performances: until they are deleted, and at the latest when your account is deleted (along with karaoke exports and publications derived from them). Dubbing exports already produced from your takes (mixed video, voice track) stay in the project.
- Auditions: until the casting call or the project is deleted by those in charge of it, and at the latest when your account is deleted. You cannot withdraw a single audition yourself: ask the operator of this service.
- Gallery: unpublishing removes the dub from the gallery (the entry is deactivated, not erased). When you delete your account, your pseudonym becomes “Deleted account” in the credits.
- Notifications: no automatic deletion; erased with the account. Push subscriptions are removed when the browser’s service reports them invalid, or when the account is suspended or deleted.
- Subscription: erased with the account, the Stripe cancellation then being scheduled for the end of the paid period. The identifiers of payment events received from Stripe, which are not linked to your account, are kept. Stripe keeps its own data under its own policy.
- YouTube tokens: until the account is deleted.
- Workshop accounts: permanent — closing the workshop deletes neither the accounts nor their work.
- Closed beta: browser errors (all visitors), 30 days; the details of the activity log, erased 180 days after they are written (the log entry itself stays, as above); feedback sent from the site, 12 months after the end of your beta access; copies of feedback in Discord and in the bot’s database: as long as your account exists, then rewritten without your username or your texts; the Discord link, until you unlink it or delete your account.
- Server technical logs: how long they are kept depends on the operator’s server configuration; the software sets no period.
Messages to support: at most one year in the support mailbox, then a separate archive, erased at most five years after the last message.
Closed beta
When this instance runs a closed beta, testers join with an invitation code, in a cohort, for a limited time (six weeks by default), with a Karaoke or Studio plan. When the beta ends, the account moves to the Discovery plan: nothing is deleted. Within a cohort, limits can differ from one group of testers to another (a variant): your group is assigned by your invitation and does not change afterwards; the team draws indicators aggregated per variant from it, and the export of these data reserved for administrators contains neither username nor email address. Joining the beta means accepting what follows; the date of your acceptance and the version of these terms are recorded.
- Detailed activity log: the audit log also records the details of what you do with the service (for example the length of the videos prepared, the plan chosen, a plan change) to measure use against the beta limits and to improve the service. It is neither an advertising tracker nor a third-party audience measurement: it stays on the service’s server.
- Browser errors (for every visitor, tester or not): when the application fails in your browser, a technical report (message, location in the code, page path without parameters, browser version) is sent automatically to our own server, with no outside tool. Anything that looks like a sign-in token or a link parameter is removed first.
- Feedback: what you write with “Give feedback” is sent with the page and the version of the service, without a screenshot. To sort and summarise it, feedback is analysed by Anthropic (Claude, United States); the transfer relies on the EU–US adequacy decision (Data Privacy Framework) where Anthropic is certified under it, and otherwise on the European Commission’s standard contractual clauses. Your email address is never sent.
- Discord: each piece of feedback sent from the site is posted, with your username, the text of your feedback (as an attachment) and its analysis, in a private team channel and as a direct message to the person who validates it, on Discord (a company established in the United States; see Transfers outside the European Union). These messages stay as long as your account exists; if you delete it, they are rewritten without your username, your texts or the quotations (the technical analysis stays). If the team validates it, feedback may also be copied, with your username and your text, to its task tracker at GitHub (a company established in the United States), where it is not rewritten. Discord also receives data if you link your account (your Discord ID and name are then kept with your account) or if you write there yourself. Discord applies its own policy. An addition you make to feedback while it is being analysed is passed on as is to the team on Discord; those relays are not rewritten.
How long these data are kept is set out under How long we keep data; export and deletion (My account › My data) include them.
Gallery reports
Anyone, with or without an account, can report a gallery publication with the “Report” button on its page.
- Data collected: the reason, your name and email address, the capacity in which you act, the description of the problem and your good-faith declaration, with the date and the title of the publication concerned; if you are signed in, the report is linked to your account. Your IP address is used only to limit the number of reports (five per hour): it is not recorded with the report.
- Purpose: reviewing the report, contacting you if needed and keeping a record of the decision (hiding, removal or rejection). Legal basis: the legal obligation to handle notices of unlawful content (French LCEN, article 6; Digital Services Act, article 16).
- Recipients: platform administrators only. The publisher receives neither your name nor your email address: they are only told, with the reason, that their publication has been hidden or removed.
- Retention: while the report is open, then one year after the decision (default period, which the operator can change); your name, email address, capacity and description are then erased. Only a minimal record remains: reason, decision, dates and publication concerned.
- Your rights: access, rectification, erasure and restriction, as described under Your rights. A report made from your account is included in your data export (My account › My data).
Karaoke parties
When the host of a karaoke party opens it, guests join from their phones with the party code, without an account.
- Guests without an account: only the nickname chosen for the party is recorded, with the time of arrival and the songs suggested; nothing else (no name, no email address, no account). The IP address is used only to limit the number of attempts: it is not recorded. The guest’s browser keeps an access token for the party (see Storage in your browser).
- Purpose: running the party (shared queue, TV screen). Legal basis: performing the service requested by the host, and the guests’ legitimate interest in taking part.
- What the host sees: the nicknames of their guests and their suggestions, during the party. Guests see the titles of the songs in the queue and the nicknames, never the lyrics or the names of the host’s projects.
- Retention: the party closes when the host ends it, after 12 hours without activity, or at the latest 24 hours after it opened; nicknames, queue and linked screen are erased 24 hours after it ends. A screen code that is never linked is erased after one hour.
- Export and deletion: the host’s data export (My account › My data) includes their parties still present, without the guests’ nicknames; deleting the host’s account erases their parties.
Messages to support
When you write to support — by email to the address on the help page, or through the form on that page:
- Data: your email address, your message and its attachments, the topic and language chosen; if you are signed in and use the form, your username and your account’s number and address. Your IP address is used only to limit the number of messages sent through the form: it is not recorded with your message, and the counters that hold it erase themselves within 25 hours at most.
- Purpose: answering you, and keeping a record of our exchanges in case of a dispute. Legal basis: the legitimate interest in answering the people who write to us and in being able to defend our rights, and performance of the contract for questions about your account.
- Hosting: the support mailbox and the email sent by the site are hosted by the site’s host (see the legal notice).
- Retention: an exchange stays in the support mailbox for at most one year after its last message. It then moves to a separate archive, opened only for a dispute or a request to exercise your rights, and it is erased at most five years after its last message (the general limitation period, article 2224 of the French Civil Code), unless a dispute is ongoing: the exchange is then kept apart until the dispute ends.
- Your rights: you can ask for access to your exchanges with support, or for their erasure, at the address on the help page (see Your rights). An archived exchange may be kept despite an erasure request for as long as it is needed to establish, exercise or defend legal claims (article 17(3)(e) of the GDPR).
Security
- Passwords are hashed (bcrypt) and never stored in readable form.
- On an instance published online, exchanges go over HTTPS, through the relay the operator places in front of the server; the software itself does not enforce this redirect.
- Optional two-factor authentication, sessions you can close one by one, attempt limits on sign-in, sign-up and password reset.
- Encrypted at rest: studio takes, auditions and karaoke performances (voice and camera) are encrypted on disk, with one key per file kept in the service’s database.
- Not encrypted by the application: imported videos, the audio and tracks derived from them, exports (which contain the mixed voices), and the database contents (texts, email addresses, IP addresses, two-factor secret, YouTube tokens). Their protection relies on the security of access to the server.
- Remote access keys and invitation links are stored only as fingerprints.
Minors and workshops
The service does not ask for or check anyone’s age. If you are under 15, ask a parent or guardian for permission before creating an account.
Workshop mode is designed for classes: a teacher opens a session and students join with a code and a first name, without an email address. The student account gets a placeholder address that no email can reach (a forgotten-password request for that account still hands a message to the email delivery provider, if there is one, but it arrives nowhere). The teacher sees the students and their progress, is notified of each arrival and can give a student a new password. Students record their voice in the teacher’s project. Closing the workshop disables the code, but the accounts and their work remain: to erase them, each student deletes their account from My account › My data, with their password.
A teacher who uses workshop mode with minors is responsible for obtaining the necessary permissions from the school and families, and for telling students about this policy.
On a shared computer, pending takes are kept per account and erased when you sign out.
Your rights
You have the right to access, rectify and erase your data, to restrict or object to its processing, to data portability, and to withdraw any consent at any time.
- Access and portability: My account › My data, “Download my data”, gives a JSON file — profile, projects and roles, information about your takes (without the audio files), comments, notifications, sessions (IP and browser), YouTube connection, workshops, settings, invitations, performances, auditions, subscription, publications, and the last 1,000 audit log entries (without IP addresses). Not included: imported videos, audio and video files, revisions, suggestions, glossary, rythmo marks — you can ask the operator of this service for them.
- Rectification: change your email address and password in My account › Profile; for anything else, contact the operator of this service.
- Erasure: My account › My data, “Delete my account”, with your password. Deletion is refused while you still own projects: delete or transfer them first (project settings); the last platform administrator must appoint a successor. What is erased and what is kept is set out under How long we keep data.
- Withdrawing consent: notifications in My account › Notifications; the gallery by unpublishing; YouTube by revoking access on your Google account permissions page.
- Objection and restriction: contact the operator of this service.
No contact email address for the operator has been published on this instance yet.
You can also lodge a complaint with the CNIL (www.cnil.fr) or with the data protection authority of your country of residence in the European Union.
Changes
This policy changes with the service; the date at the top of the page shows the last update. The operator of this service informs you of any significant change.
Contact
No contact email address for the operator has been published on this instance yet.