Privacy policy
Draft: have this reviewed before launch. The items in brackets still need filling in.
Last updated: [TODO: date]
This policy explains what the Dubloo apps for Android and this website collect, why, and what you can do about it. There are two apps, with one account:
- Dubloo (free) is where you play: rooms, recording your lines, premieres and your saved dubs. It shows ads.
- Dubloo Studio only creates, edits and publishes clips. It doesn't use the microphone and shows no ads.
Who we are
Dubloo is run by ZENTAG LTD, a company registered in England and Wales (company number 08141713), registered office Unit 7 Navigation Business Village, Navigation Way, Ashton-on-Ribble, Preston, PR2 2YP, United Kingdom. ZENTAG LTD is the controller of your personal data. You can reach us at support@dubloo.party.
This website
dubloo.party sets no cookies and runs no analytics, trackers or ads. Our web server keeps standard logs (IP address, browser, the page requested) for security for 30 days.
What the apps collect
- Sign-in. We use Firebase Authentication from Google. In Dubloo you can play as a guest: the app signs you in anonymously and we only get a random account ID. If you sign in with Google or email, we store only your email address. We don't store your Google name or photo. Firebase sends the email verification messages for email sign-in.
- Your profile. The display name you choose (we check it against a list of banned words), a profile colour and, for signed-in accounts, an optional profile photo. We also store whether you turned on "Show 18-rated clips and rooms".
- Game content (Dubloo). The Dubloo app uses your microphone only while you record a line. Takes you don't submit stay on your phone. We receive the recordings you submit for your lines, the rooms you join, the lines you're given and the reactions you send.
- Dubs (Dubloo). When a game finishes, the dub (the clip plus everyone's recordings) is saved to the host's My dubs, and players can find it under I'm in. Everyone who played in a dub can replay it.
- Clips you publish (Dubloo Studio). Studio processes your video on your phone. It detects faces (with Google ML Kit) only to crop one picture of each character from the video, and it transcribes the speech to find and time the lines. It doesn't recognise faces or identify voices, and none of this leaves your phone until you publish. When you publish, we receive the finished clip: the video, a backing track, the original dialogue track, a thumbnail, the character pictures, the line text and timings, the age rating you chose, and the names and versions of the tools the app used.
- Device information. A notification token so we can send you game alerts (Firebase, from Google, uses a Firebase installation ID to deliver them), a random install ID created by the app, used to stop banned players from simply reinstalling, and a scrambled (hashed) device identifier the app may send, which we store only in hashed form and use only to give the Studio welcome credit once per device. The apps use no analytics or crash-reporting tools.
- Purchases. When you buy credits or remove ads through Google Play, we receive the purchase token, order ID, product and status from Google so we can confirm it. We keep your credit balance and a history of how credits were added and used. We never see your card details.
- Safety. Reports you make about clips (including "Wrong age rating"), people you block, players removed from rooms, and any moderation decisions about your account.
Videos you save or share from the app are made on your phone. We don't receive them unless you send them to us.
Ads in the free Dubloo app
The free Dubloo app shows banner ads from Google AdMob. In the UK, EEA and Switzerland we ask for your consent with Google's consent form the first time you open the app. If you agree, Google may show personalised ads using your device's advertising ID. If you don't, you'll still see ads, but they're limited, non-personalised ads. You can change your choice any time in Settings → Ads & privacy → Privacy options.
Ads are limited to content suitable for teens, and we don't show ads during 18-rated games. Buying Remove ads (£6, one-off) turns ads off for your account on every device. Dubloo Studio shows no ads.
Google explains how it uses this data in How Google uses information from sites or apps that use our services.
How we use it
- To run the game: rooms, recordings, premieres, dubs, notifications and your account.
- To publish and show clips, and to keep Dubloo safe: checking uploads, moderating reports and enforcing our terms.
- To process purchases and keep your credit balance right, including when Google tells us a purchase was refunded.
- To answer you when you contact support.
Legal bases
Under the UK GDPR and the EU GDPR we rely on:
- Contract: your account, the game, publishing clips, dubs, purchases and credits, and support.
- Legitimate interests: keeping Dubloo safe (moderation, reports, blocks, bans, and the install ID that stops banned players re-registering), security logs and fraud prevention.
- Consent: personalised ads (you can withdraw it at any time in the app) and notifications (through Android's notification permission).
- Legal obligation: keeping purchase and tax records.
Who can see what
- Players in your room see your display name, profile colour or photo, and hear your recordings in the premiere. Everyone who played in a dub can replay it.
- If you host a public room, anyone using Dubloo can see the room, the clip, your display name and how many players have joined, and can join it. People you play with in a public room may be strangers; they hear your recordings in the premiere and can replay the dub.
- The host can remove a player from a room; we record that it happened.
- Public clips you publish can be found and played by anyone using Dubloo.
- Your email address, credit balance and purchases are private to you.
Age ratings
Clips carry an age rating (PG, 12, 15, 18) chosen by the creator. 18-rated clips and rooms are hidden unless you turn on "Show 18-rated clips and rooms" and confirm you're 18 or over. This is self-declared and we don't verify your age. We store that setting with your account. If a clip's rating looks too low, report it with "Wrong age rating".
Service providers and transfers
These companies process data for us, only to provide their service to Dubloo:
- OVHcloud hosts our servers (a virtual private server in France (EU), OVHcloud Gravelines): the database and the API the apps talk to.
- Cloudflare stores the files (clips, recordings, profile photos and our encrypted database backups, in Cloudflare R2) and runs the DNS for our domain.
- Google Firebase: Firebase Authentication for sign-in and Firebase Cloud Messaging for push notifications.
- Google Play handles payments for credits and Remove ads. We receive the purchase details described above, never your card details.
- Brevo sends the emails our server sends (transactional email, such as alerts to our moderators). It receives each recipient's email address and the message.
- Google AdMob shows the ads in the free Dubloo app only (Dubloo Studio has no ads). In the UK, EEA and Switzerland it asks for your consent through Google's consent messages (see Ads in the free Dubloo app).
Our servers are in the EU. Google, Cloudflare and Brevo may process data outside the UK and EEA. These transfers rely on the UK International Data Transfer Addendum and the EU Standard Contractual Clauses and, for US providers, the EU-US Data Privacy Framework (and its UK Extension) where the provider is certified.
How long we keep things
- Recordings that are part of a saved dub: kept until the host deletes the dub, the clip is removed, or the account that recorded them is deleted. When a dub or its clip is deleted, its recordings are removed within about two days.
- Recordings from games that never finished: deleted 30 days after the room ends or expires.
- Unpublished clips (drafts): removed 7 days after you start them, together with their uploaded files. We remind you the day before.
- Private clips nobody has used for 6 months (no game played with them and no dub of them replayed): we warn you, and delete them 14 days later unless you choose to keep them. Public clips are never deleted this way.
- Published clips: kept until you delete them or your account (or, for private clips, under the rule above).
- Guest accounts: deleted after 60 days without use.
- Notification tokens: deleted after 60 days without use.
- Web server logs: 30 days.
- After you delete your account we keep a one-way hash of its sign-in ID for 30 days, only to stop the old sign-in from re-creating it.
- Purchase records and credit history: 6 years (UK accounting rules). After that, and as soon as you delete your account, they are no longer linked to you; after 6 years the Google order details are removed too. We keep the anonymous totals.
- Moderation records (reports, warnings, removals from rooms and our audit log of moderation decisions): 2 years after the decision, or longer while a ban or Studio block on the account is still in place. After that they are no longer linked to you: the record of what was decided stays, without your account ID. The reports you made, the people you blocked and your removals from rooms are deleted straight away when you delete your account.
- Database backups: encrypted, and kept for up to 6 months before they are deleted. Data you delete disappears from the backups as the older ones are deleted.
Deleting your account
In the app, go to Profile → Delete account. This deletes your recordings, your clips and their files, the dubs you hosted, your profile photo, your notification tokens and your sign-in account, and removes your name from past rooms. The reports you made and the people you blocked are deleted too. Purchase and credit records and our moderation audit log are kept, no longer linked to your profile (see How long we keep things).
Your recordings in other people's dubs are deleted too: those lines play the original voice, and your name in the cast shows as "Former player". See Delete your account for the other ways to ask.
Your rights
You have the right to access your data, correct it, delete it, restrict how we use it, object to how we use it (including processing based on our legitimate interests), get a copy to take elsewhere (data portability), and withdraw your consent at any time.
To ask, email support@dubloo.party. We reply within one month.
You can also complain to the UK Information Commissioner's Office (ico.org.uk) or, in the EEA, your local data protection authority.
Children
Dubloo is not intended for children under 13. If you're under 13, please don't use Dubloo. If you think a child under 13 has an account, contact us and we'll delete it.
Users aged 13 to 17 can't see 18-rated clips or rooms: they stay hidden unless the user turns on "Show 18-rated clips and rooms" and declares they are 18 or over (see Age ratings).
Security
Traffic between the apps and our servers is encrypted. Stored files are private and only reachable through short-lived links.
Changes
If we change this policy we'll update the date above, and tell you in the app for anything important.