1. Who we are
mydubly is operated by Shivam Kumar Singh, an individual based in India (“we”, “us”). We decide how and why your personal data is processed, which makes us the “data fiduciary” under India’s Digital Personal Data Protection Act, 2023 (DPDP Act) and the “controller” under laws such as the EU and UK GDPR.
This policy explains what we collect when you use https://mydubly.com and the mydubly service, why, who we share it with, how long we keep it and the choices you have. Questions go to support@mydubly.com.
2. Privacy by design
- By default your video stays on your device. Your browser extracts the audio track and only those chunks go to our servers. If you turn on optional Server assist (for example when a phone cannot decode the file locally), the media file for that job is uploaded, processed on our servers, and deleted with the usual retention window.
- Audio and results are temporary. Audio, transcripts, translations, subtitles and generated voices are deleted from our servers as soon as your browser has the results, and within 120 minutes after a job ends even if you close the tab. A translated voice (dub) is kept so you can fine-tune it in the dub editor, and deleted 120 minutes after you last use the editor.
- No training, no selling. We do not use your audio or text to train models, we do not sell or rent personal data, and we do not use analytics trackers.
- Ads stay in their own box. Free users see ads from Adsterra in a sandboxed frame that cannot read your account, your files or the rest of the page. In the EU, EEA, UK and Switzerland, ads load only after you accept them. Paid plans, and the 30 days after a credit purchase, are ad-free.
3. What we collect
Account information
- Email sign-in: your email address, the name you enter (optional) and your password, which we store only as a salted one-way hash — we cannot read it.
- Google sign-in: the name, email address, profile picture URL and Google account identifier that Google shares with us, and whether Google has verified your email. We never receive your Google password.
- Sessions: a sign-in token kept in your browser, of which we store only a hash, with its expiry date.
Files you process
- Temporarily: the audio extracted from your file, in chunks, and everything produced from it — transcripts, translations, timings, subtitles and voice audio. For a translated voice, this includes a short sample of each speaker’s voice taken from the audio, used only to speak that person’s lines of that job’s translation in a copy of their voice. These are deleted as described in How long we keep data. Audio may contain personal data about you or others (voices, names, anything said in the recording).
- Kept with your account (job records): the file name, length, source and target language, output type, status, time, and credits charged or refunded. We keep these for billing, your “My files” history, support and fraud prevention. We do not keep the content of the file.
Community chat
- When you write in the chat, we store your message, the time, and any message it replies to or people it tags. Messages are public: anyone visiting the site can read them, shown with your account name (never your email address). The mydubly team can see account email addresses when tagging people in replies.
Payments and credits
- Payments are handled by Cashfree Payments (in India) or PayPal (elsewhere). They collect your card, UPI, bank or PayPal account details directly — we never see or store them.
- We store payment records: the amount, currency, credits bought, payment provider, their order and payment identifiers, status and time, plus a ledger of credit changes (purchases, job charges, refunds, bonuses).
Technical information
- Our servers receive your IP address, browser user-agent and request details with every request. We use them for security, rate limiting, preventing abuse and fixing errors, and they may appear in server logs.
- Visitor counts: while a mydubly page is open and visible, it tells our server once a minute, so we can show how many people are on the site and how many visit each day. To tell visitors apart, our server combines your IP address and browser user-agent with a random value that changes every day and keeps only the resulting code. We do not store the IP address with it, the code cannot be linked to your account or to another day, and nothing is stored in your browser for this.
- Your browser stores a few items for the Service to work (your sign-in token and the job in progress). See our Cookies & Storage page.
- When an ad is shown to you, Adsterra and the advertisers it works with receive your IP address, browser details and the address of the page, and may use cookies, to choose, limit and measure ads. We do not give them your email, your account details or your files.
When you contact us
Your email address and whatever you write to us, so we can reply and keep a record of the request.
4. Why we use it
We use personal data only for these purposes:
- To provide the Service — create and secure your account, process your files, deliver results, and keep your balance and history. (Basis: performing our contract with you, and your consent when you submit a file.)
- To take payments and keep records — add credits, issue refunds and meet tax and accounting obligations. (Basis: contract and legal obligation.)
- To keep the Service safe — prevent fraud, abuse of free credits, attacks and overuse, and enforce our Terms. (Basis: our legitimate interests and legal obligation; under the DPDP Act, legitimate uses permitted by law.)
- To communicate with you — reply to requests and send important notices about your account, payments or changes to our policies. We do not send marketing email without your consent.
- To fund free use — show ads to visitors and free accounts. We use your plan and the date of your latest credit purchase only to decide whether to show them. (Basis: your consent in the EU, EEA, UK and Switzerland, which you can withdraw at any time from Cookie settings at the bottom of every page; our legitimate interest in funding free use elsewhere.)
- To comply with the law — respond to lawful requests from courts and authorities.
We do not use automated decision-making that has legal or similarly significant effects on you. The machine learning in the Service only transcribes, translates and generates speech from your files.
6. International transfers
Our providers may process data in India, the United States, the European Union or other countries. Where data leaves the country you live in, we rely on safeguards the law recognises, such as standard contractual clauses, and we do not transfer data to any country the Government of India has restricted under the DPDP Act.
7. How long we keep data
- Audio, transcripts, translations, subtitles, voice samples and voice audio: deleted as soon as your browser has collected the results, and within 120 minutes after a job finishes, fails or is cancelled. A job that stops making progress is expired after 24 hours and deleted the same way.
- Dubs you can still edit: a finished translated voice (dub) keeps its audio, translated script, voice samples, voice audio and subtitles on our servers so the dub editor can re-voice and re-mix it. They are deleted 120 minutes after the dub finishes or after you last use its editor, whichever is later, or at once when you press “Delete files” in the editor.
- Sign-in sessions: expire after 30 days, or when you sign out.
- Account information and job records: kept while your account is open. When you close your account, we delete or anonymise them within 30 days, except what we must keep by law.
- Chat messages: kept and shown until the mydubly team removes them, or deleted with your account when you close it. Ask us at any time to remove a message you wrote.
- Payment and credit records: kept for as long as Indian tax and accounting laws require (generally up to 8 years), then deleted.
- Visitor codes: deleted with that day’s random value shortly after midnight India time; only the number of visitors for each day is kept.
- Server logs: kept for a short period for security and debugging, then deleted, unless needed to investigate abuse.
8. Security
We use encryption in transit (HTTPS), hashed passwords and session tokens, short-lived signed links for temporary files that are never public, access controls so only your account can see your jobs, and automatic deletion of file content. No system is perfectly secure, but if a personal data breach affects you, we will notify you and the authorities as the law requires.
9. Your rights
Depending on where you live, you have the right to:
- get a summary of the personal data we hold about you and how we use it, and a copy of it;
- correct or update inaccurate or incomplete data;
- have your data and account deleted;
- withdraw consent at any time (this does not affect processing already done);
- object to or restrict certain processing, and receive your data in a portable format (EU/UK users);
- nominate someone to exercise your rights if you die or become incapable (India);
- complain to us first, and then to a regulator — in India the Data Protection Board of India, or your local data protection authority elsewhere.
To use any of these rights, email support@mydubly.com from the address on your account. We may need to confirm it is you. We will respond within 30 days. Deleting your account permanently removes any remaining credits, so ask for a refund first if you are eligible under our Refund Policy.
10. Children
The Service is not meant for anyone under 18, and we do not knowingly collect personal data from children. If you believe a child has created an account, contact us and we will delete it.
11. Changes to this policy
We will update this page when our practices change and revise the “Last updated” date. For significant changes we will tell you by email or on the website before they take effect.
12. Contact and Grievance Officer
Under the Information Technology Act, 2000, the rules made under it and the DPDP Act, our Grievance Officer is Shivam Kumar Singh, reachable at support@mydubly.com or by post at Dharwad, Karnataka 580001, India. We acknowledge complaints within 24 hours and aim to resolve them within 15 days. See also Contact & Grievances.