YourBeats privacy policy
Effective date: 2 November 2026
Last updated: 3 November 2026
This policy explains what information YourBeats collects when you play, why, who else sees or handles it, how long we keep it, and what you can do about it. It covers the YourBeats app, our server, and our web pages at yourbeats.net, including for people who visit them, or write to us, without playing. If anything is unclear, write to us at support@yourbeats.net.
The short version
- You can play without telling us who you are. When you first open YourBeats, it asks your year of birth, which stays on your phone. If you are 13 or older, it then makes a guest account for you so that your progress is kept safe; the account has no email address. You can play songs from YouTube once you reach YouTube's own minimum age in your country (13 in most countries).
- An email address is optional. If you add one, or let Google give us your Google account's address with "Continue with Google", we use it to sign you in and to find your account if you ask us to delete it. Other players never see it, and we never use it for marketing.
- Other players see your handle, avatar and level, and more depending on your privacy settings, which start more private for players under 18.
- If the app goes wrong, it sends us a crash report that says nothing about who you are. It also sends usage data, with Google Analytics for Firebase, from 13, or from YouTube's minimum age or the age at which you can agree to it yourself where you live, if either is higher, until you switch it off (section 2.9).
- Notifications only if you say yes. Apart from a few your phone makes itself, they come through Google's Firebase Cloud Messaging, only for an email account, and you can switch each kind off (section 2.13).
- Videos play in YouTube's own player. YouTube collects some information when the player loads and may show its adverts. The Google Privacy Policy covers that.
- Google Play Games, if you use it. On Android, from 13, if your phone has a Play Games profile, Play Games signs you in when YourBeats starts, as it does in other games, and Google collects its own information about that. YourBeats then signs you in to your own account with it, so that your progress comes back on another phone. Our server keeps your Play Games ID only in scrambled form, and never your Play Games name (sections 2.1 and 2.14).
- We never sell your information or use an advertising ID. Without Premium, you may see adverts from Google AdMob: from 13 (or YouTube's minimum age where you live, if that is higher, and 15 in Denmark), full-screen ones at some breaks in the game, and, if you choose, ones that add a song (one or more adverts for each song). They never show during a song and are never personalised (section 2.15).
- You can delete your account from inside the app, and, with an email account, download a copy of your data.
Contents
- Who we are
- What we collect, and why
- Why we are allowed to use it
- YouTube
- Who else sees or handles your information
- How long we keep it
- Deleting your account
- Your rights, and how to complain
- Children and teenagers
- Security
- Information that leaves the UK
- Changes to this policy
- Contact us
1. Who we are
YourBeats is a rhythm game played along to music videos on YouTube. It is published by Unbelievable Media LTD ("YourBeats", "we", "us"), a private limited company registered in England and Wales, company number 16790553, whose registered office is at 29 Riverside Walk, Wickford, England, SS12 0DU. Under UK data protection law, and the EU's for players in the European Union and the rest of the European Economic Area, we are the controller of the personal information described here: we decide why and how it is used.
- Email: support@yourbeats.net, for questions, requests and complaints about your information.
- Registered with the UK's Information Commission (the ICO): ZC265145
- Our representative in the European Union: NordRep Data Protection Services B.V. (trading as NordRep — EU Authorised Representative), Attn: EU Authorised Representative, Barbara Strozzilaan 201, 1083 HN Amsterdam, Netherlands
- We do not have a data protection officer. Write to support@yourbeats.net about anything in this policy.
2. What we collect, and why
2.1 Your account
Your age. When you first open YourBeats, before any account is made, it asks for your year of birth (and, if you turn 13 or 18 this year, whether you have had your birthday yet). The answer stays on your phone. If you are under 13, the app makes no account for you (section 9). Your age also decides whether YourBeats' YouTube features are open to you, by YouTube's own minimum age for your country (section 9). Our server only ever learns your age group, 13 to 17 or 18 and over, and only for an email account. We use it to keep accounts for players aged 13 and over, to give players under 18 safer settings (section 9), and to decide who may see the adverts at breaks (section 2.15).
Your guest account. Once you have answered, and if you are 13 or older, the app makes a guest account for you, so that your progress is kept safe from the start. It has a random account ID, an automatic handle made of two words and some digits (other players see it in rooms, and anyone can look it up: section 5), and a secret that stays on your phone (our server keeps only a scrambled form of it, with the label "YourBeats app"). Your runs, progress, achievements, avatar and chart drafts are kept with it on our server. It has no email address, and only a phone that holds its secret can use it, or, on Android, a phone that Google Play Games signs in with the profile it is linked to (below). To limit abuse, when a guest account is made we keep a scrambled form of the internet (IP) address it came from for one day.
An email account. If you add an email address to your account, or sign in with one, we keep:
- your email address, to send you sign-in codes, to recognise you when you come back, and to find your account if you ask to delete it on our web page. Our team can also look an account up by its email address when you write to us for help;
- the six-digit code we email you, in scrambled form only, until it is used or for 15 minutes at most;
- a record of each sign-in: a scrambled form of its key, when it started, and a short label your phone's app sends (for example "Android 16 YourBeats app"). A sign-in lasts 120 days, and its record stays until you sign out or delete your account.
If you played as a guest first, signing in moves the guest's progress into your account, and we keep a note of the move (the guest's old ID, when, and how much was moved); the same happens when Google Play Games brings two of your accounts together (below). We never show your email address to other players and never use it for marketing.
Signing in with Google Play Games. On Android, if Play Games has signed you in on your phone (section 2.14), YourBeats uses it to sign you in to your own YourBeats account when it starts or you come back to it, without a button. You can also connect it yourself where you save your progress or sign in, or in Settings, then Account. It never does so for a player under 13 or whose age is not known, and it does not do it by itself on a phone where you tapped Sign out (Settings, then Account), deleted your account or chose "Not you?", until you sign in or connect it there. To sign you in, the app asks Google for a one-time code and sends it to our server with the label "YourBeats app" (for a guest account, also its ID and secret, which our server checks only if the guest's sign-in has lapsed, as when the app renews it). Our server gives the code to Google, which tells it your Play Games player ID. Google's answer also carries other details of your Play Games profile, such as its name and picture, which our server does not read or keep. We keep only a scrambled form of the player ID, made with a secret key of our own, with the account it opens, when it was linked and last used, and the app's label. Then:
- a profile that is new to YourBeats is linked to the account this phone already has (if that account already has another Play Games profile, this one is added only when you connect it yourself) or, if it has none, to a new guest account made for you as above;
- on another Android phone with the same profile, or after you reinstall YourBeats, Play Games signs you in to that same account, so that your progress comes back without an email address. A phone that a guest account comes back to gets a key of its own for it: our server keeps only a scrambled form of that key, with the app's label and when it was made and last used, for at most 10 phones (the ones unused longest go first);
- if your profile already opens another account: when this phone's guest account has no progress yet, it joins that account; when this phone has an email account and the other one is a guest account with no progress yet, the guest joins it (with the note of the move, above). Otherwise two accounts are never brought together without asking you: the app shows you both (each one's handle and its style, avatar, level, medals and bests, and a masked form of its email address, never its ID), and you choose whether to bring them together or keep them apart. If both are email accounts, nothing changes, and Settings, then Account shows the other account's handle or masked email, with Switch, which signs this phone in to that account instead.
Settings, then Account also shows your Play Games name, which the app reads from Google on your phone and never sends to us, and lets you unlink Play Games (section 2.14).
"Continue with Google". On Android, where you save your progress or sign in, "Continue with Google" lets Google give us your email address instead of you typing it. In the current version of the app, Google shows its own list of the Google accounts on your phone each time, and you choose one; the first time you use an account with YourBeats, Google tells you what it shares. Google then gives the app a sign-in it has signed, with your Google account's email address, whether Google has verified it, an ID for your Google account, your name and your profile picture, and the app sends it to our server with your age group, as adding an email address does. Our server checks Google's signature and uses only the email address, whether it is verified, whether it belongs to an organisation's Google Workspace, and the account ID: it does not keep your name or profile picture. Earlier versions of the app ask Google Play Games instead (signing you in to it first, if it has not) for a one-time code that also covers your email address; our server gives that code to Google, which tells it your Google account's email address, whether Google has verified it, an ID for your Google account and your Play Games player ID. Either way, if Google has verified the address and it is a Gmail address, or belongs to an organisation's Google Workspace, we take Google's word that it is yours; otherwise we first email it a six-digit code, as when you type an address. The address then becomes your account's email address or, if it already has a YourBeats account, this phone's guest progress joins that account (as above). We keep only scrambled forms of the IDs we receive (your Google account's, and with earlier versions your Play Games player ID), with your account, as for Play Games. If you close Google's list or decline its consent screen, we receive no address and keep nothing, and you can type your address instead. We use what Google gives us only to sign you in and to keep your account, never for advertising, and we never sell it or give it to anyone except as section 5 says, in line with the Google API Services User Data Policy.
Your profile. Your handle (unique, 3 to 16 characters) and the handles you have held before; your avatar (a set of shapes and colours you choose in the app, never a photo); with an email account, your profile page: its look (a stage set, a style for your handle and a status) and what it shows (up to three of YourBeats' own songs as its soundtrack, a wall of your records, rankings, achievements, skill or shared charts, the order of its parts and which ones you hide, a crew of up to eight of your friends, whether you appear in your friends' crews, and whether it takes cheers), each chosen from what YourBeats offers, never words of your own; your privacy choices (kept on your phone, and on our server for an email account); and a name you set in an earlier version of the app, if you did. Every new account gets an automatic handle made of two words and some digits, never anything from your email address. With an email account you can change the automatic handle at any time, and after that once every 30 days; your old handle is kept for you for 30 days so that nobody else takes it straight away. As you type a new handle, the app asks our server whether it is free, so the handles you try reach our server.
We also note when each account was last active, when the app signs in or sends runs. Friends see it only if you share your activity with them (section 2.3).
Your preferences. The difficulty you play songs at (and whether you chose it), your note speed, and what you have told the "Ready for more" suggestions (switched off, not now, or not again) are kept with your account, guest or email, so that they follow you to another phone.
Favourites. With an email account, the songs you mark as favourites are kept with your account, so that they follow you to another phone; a song you take off the list keeps a note of that for 400 days, so that an older change from another phone cannot put it back. A guest's favourites stay on the phone.
2.2 Playing
Runs. When you finish a song, alone or in a room, your phone sends the run to your account, guest or email: the song and chart, the difficulty and mode, your score, accuracy, longest combo, whether it was a full combo or all perfect, the phrases you played cleanly, your medal, whether Assist or "never stop the music" was on, whether part was skipped or interrupted, the day and time you played, and the phone's own number for the run. The first time a phone sends runs, it also sends the bests, achievements and weekly challenge progress it already holds. Practice runs, and the runs the game plays by itself in demos, are never sent. We use runs to work out your XP, level, skill, achievements and weekly challenges, and to keep your bests safe across phones. They also help choose songs, counted with everyone's and never shown by player: Ranked's weekly set leans towards the languages players played most the week before, and quick play picks a song in a language every player in the match has been playing.
Playing without a connection. Runs you finish offline wait on your phone and are sent when you are back online, with the time of your last sync, so that their dates stay honest.
The YourBeats Originals. Our own songs play from the app itself, without YouTube, with or without a connection, and nothing of their music is sent anywhere. A run of an Original is sent and counted like any other run (above): it adds to your XP, level, skill, achievements and weekly challenges. A run you play online, with a connection when it starts and when it ends, also counts for song records and friend challenges, as a run of any song does (below, and section 2.3); a run played offline never goes on song records. If you share usage data, it names the Original you played, as it names a catalogue song (section 2.9). A version of the app that includes the Originals checks its offline settings with our server when it starts and when you come back to it; that check sends no account or ID, and our server reads your country from it only to answer YouTube's minimum age (section 9). Under 13, no account is made, and the runs and usage data of an Original are never sent, not even after the player turns 13; only crash reports, which carry nothing that could identify anyone, are sent as for every player (section 9).
Your own copy of a song. If you have bought a song as a music file, "Use your own copy" on that song's page lets you choose the file in Android's own file picker, and the song can then play from it. YourBeats reads only the file you choose, only on your phone: it never copies the file, and never sends any of it anywhere (if you tap "Find it" below, sound prints made from it go to Apple: section 2.7). For a song we hold a print of, the check below tells whether your file is that song. For any other song, the app first reads the file's own title and artist (its tags) on your phone, and uses the file if they name the song. If they cannot say which song it is, the app may ask you whether to find the song by its sound (section 2.7) and, if you tap "Find it", uses the file if it is the song. Otherwise the file is not used and nothing is kept. A file you bring in through "Use your own music" is checked instead for the song you find or add there (section 2.7). Your phone then checks the file against the song: it downloads from our server the song's charts and the timing data the check compares your file with (for a song we hold a print of, the print too, which our server sends only with your account's sign-in and counts for an hour to limit overuse: section 2.11), and the check itself runs on your phone. A file the check refuses is not kept. If it passes, the song plays from your file when you have no connection, and also when YouTube will not play the song's video inside YourBeats. A run played from your own copy is sent like any other run (above), but it never goes on song records. If the file carries a cover picture, the app shows it as the song's cover, read and kept small on your phone only. What the app keeps about the file stays on your phone (section 2.10); "Forget" on the song's page removes it, and your file stays where it is.
Song records. With an email account, your best run on each chart goes on that chart's public song record. It shows your handle, your avatar, your handle's style and your public player ID (or "A player", and none of these, if you hide your name), and your result: score, accuracy, longest combo and streak, whether it was a full combo, and when you set it. We also keep a compact log of your timing on each note, and we check each record against its chart with that log, keeping the result with the record, so that scores stay genuine. Anyone can see the song records of YourBeats' own songs, including each chart's full rankings and the records set on its earlier versions; the records of a song players added are seen only by the players who added it (section 2.7). For the top three rows that show a name, our server also gives out an internal account number. If you finish a run as a guest and choose to sign in to post it, your phone keeps that run (at most five, each for up to 24 hours) and posts it once you have signed in, with the phone's own number for the run, so that it counts only once.
Ghost races. You can race a saved run as a "ghost" beside you: your own record, a friend's, or another player's record just above yours or at the top. To race one, your phone receives that record's score and its per-note timing log, with its player's handle, name and avatar as the song records show them. "Ghost races", among your privacy choices, decides who can race yours: everyone, your friends or nobody. It starts at everyone for players known to be 18 or over, and at friends for younger players and while your age is not known. A player who is not your friend can race only a record that has passed our score checks, and never across a block in either direction. You can always race your own.
Most played. We count how many players played each song this week. The list shows songs and numbers, never names.
2.3 Friends, challenges, blocking and reports
Friends, your inbox, challenges and your activity need an email account. Blocking and reporting are open to guest accounts too.
- Friends. Your friend code and public player ID, your friends and since when, and the players you have blocked. A friend request stops working after 30 days; the note of it is removed when either of you deletes your account.
- Your inbox. Friend requests, challenges, "a friend beat your score", cheers sent to your page (with who sent them), room invitations, reminders of the events you asked about, Ranked results, news about the songs you added (for example, that a song's video has gone) and notes from our team. Once our notifications are switched on, it also shows what they tell you about (such as your song being ready, your results in an event, or news from YourBeats if you have switched it on), whether or not your phone shows the notification itself (section 2.13). Messages older than 60 days are removed the next time you open your inbox.
- Challenges. The chart and the score to beat, who was challenged, and how each player did. A challenge can be answered for 7 days, and it is kept until the accounts in it are deleted.
- Your activity. Only while "Show my activity to friends" is on (it starts switched off, and is offered only from 13, or from YouTube's minimum age where you live if that is higher: section 3), we keep your new bests, medals and challenges won from the last 30 days, and your friends can see the last 14 days and when you were last active. Switching it off hides it at once. What was kept is removed once it is 30 days old, the next time your runs reach our server, or when you delete your account.
- Blocking is silent: the other player is not told. It ends your friendship, any friend request between you and any open challenge between you.
- Reports. If you report a player, a run, a chart or a room's messages, we keep the report, the reason and a copy of what you reported as it was at the time: a handle, a name, an avatar, a run's numbers, or a player's page (its stage set, style, status and what it shows). A report made in a room also carries that room's last 30 chat messages, with the names of the players who wrote them, and the room's code and name. A player with a guest account can be reported from a room or a quick-play match they are in. Our team sees who made each report. The player you report is never told who reported them; you are told when someone has looked at it.
- Reports and complaints from people who do not play. You do not need to play YourBeats, or to have an account, to report a player, a chart, a room or anything else on YourBeats, or to make a complaint: write to support@yourbeats.net, or to the address in section 1. Our contact page says what to include. We keep your message, your name and contact details as you give them, what you told us about, and what we decided and did. We use them to look into your report or complaint and act on it, to tell you what we decided, and because the law requires us to deal with reports and complaints (section 3). The player concerned is not told who reported them, unless the law requires it. We may pass a report to the police or another authority when the law requires it, or to protect someone (section 5). If you report an intimate image of you, or of someone you act for, that was shared without consent, we keep your report in the same way, but not the image itself: any copy of it that came with your report is deleted once we have dealt with the report. Section 6 says how long we keep reports and complaints.
2.4 Rooms, quick play and events
- A room keeps its players' handles, avatars, levels, choices, votes, live scores and chat (its last 50 messages) only while it is open, and erases them when it closes: after 12 hours at most, or 10 minutes after the last player leaves. With an email account, your own result in each room song you were placed in (the room and the song, the difficulty, your place, medal and accuracy, whether the run was checked, whole or helped by Assist, how many players placed, how many of your friends placed with a medal, and when) is kept with your account, for achievements such as winning a song in a room with a friend, and is in your data download.
- In a room, players see the songs offered for the next round, who offered each one and who voted for it, and the difficulty each player chose for the round.
- While a room is open, the list of rooms holds its host and its name. While you wait for a quick-play or Ranked match, the matchmaker holds your account, handle, age group and the players you have blocked (and, for Ranked, your rating), until the search ends. It also keeps hourly counts of how many players are playing together, which hold no names.
- Everyone can send reactions and preset phrases. Typed messages are possible only in rooms set to friends only, only between adults, up to 120 characters, and they are filtered.
- A guest account plays in rooms under its automatic handle. A phone with no account at all gets a temporary name such as "Guest 4821", made from a number kept on the phone.
- Quick play matches you with players you do not know. Rooms, quick play, Ranked and events are not available to players under 13, or to players younger than YouTube's minimum age for their country (section 9).
- In a room, every player can play a song that one player added, and sees whose song it is.
- If you ask to be reminded about an event, we keep the reminder with your account until you switch it off. If you check in to an event, we keep your account and name with it, and your room, place, points and the songs you played there, until a day after the event.
- Ranked needs an email account. It matches you, on one song, with a player searching at the same time or with a run another player recorded. We keep your rating, your wins, losses and draws, every ranked run you play with its per-note timing log (other players can race it for 14 days, at most 5 times), each match with both players' accounts and results, and the highest venue you reached each season, which shows on your page. Under 18, or while your age is not known, other players see you as "A player" in Ranked unless "Show my name on song records" is on. If two of your runs fail our score checks in a season, Ranked pauses for your account until our team has looked at them. When you delete your account, your Ranked data goes with it; the other player's side of a match you played stays, without your account.
2.5 Charts you make
- Drafts. Each chart you make: its notes, name, description, style tags, whether others may remix it, and its version history (the newest 60 versions, the first, every version you shared, and copies kept when you settled a clash between two devices), with a short note you can write for each version (up to 120 characters) and whether each was saved on a phone or a computer. A guest's drafts are removed 30 days after they were last saved, unless the guest adds an email address.
- Carrying on at a computer. You can open a draft on a computer with a six-digit code or a QR code, which works once, for 10 minutes. While the computer is connected (12 hours at most) we keep a short description of its browser, such as "Chrome on Windows", and the computer's browser keeps the connection in its own storage until it ends. To stop people guessing codes, we keep scrambled forms of the internet (IP) addresses of the phone that made the code and of the computer for one day.
- Sharing. A chart you share shows your handle, avatar and level in the app, and its file carries your public player ID and the name shown. Its web page (yourbeats.net/ch/...) names you only if you are 18 or over, your profile is open to everyone and you show your name. Credit to anyone whose chart yours was built from is worked out automatically and cannot be removed. We keep the runs players make on your chart and their ratings (timing, musicality, difficulty and fun, and any moments they flag, with an optional note of up to 120 characters), and the ratings you give.
- Review and appeals. A chart you share is listed once you ask and it passes our automatic checks, and our team looks at any chart that is reported. We keep each decision and its reason with the chart, and if you appeal (within 14 days, up to 500 characters of your own words), we keep your appeal with it too.
- Nominating a chart. If you have finished a chart on the public lists, you can nominate it for our team's review (up to 3 a week). Your nominations are kept with your account.
- Suggesting for the official chart. In Follow, you can suggest that a song's official chart follow the melody setting your draft uses ("Suggest for the official chart"). Our server works out from your draft's notes which setting it follows, and keeps one suggestion per song and difficulty with your account, with your yes or no to being named. If our team adopts that setting, the song's page names the players who suggested it and said yes, only if their profile shows a public name, and never a player under 18.
- Deleting a shared chart takes it off the lists, but its shared versions and records stay for the players who already have it, until you delete your account.
- A chart holds a YouTube video ID and note timings. It never holds the song's audio or lyrics.
2.6 Share links
When you share a run, the app makes a link (yourbeats.net/s/...) with a picture card. We keep the link with your account, the run's details (the song, difficulty and mode, medal, accuracy, score and combo, whether Assist or "never stop the music" helped, and its place on the song records) and your choice about showing your name. Guests can make share links too. A run on a song you added can be shared like any other: its page and card then show the song's title and artist as YouTube gives them, read from our list of prepared songs each time it is shown, never kept with the link.
- Who sees what. Anyone with the link can open its page and see the song, the numbers, the run's place on the song records, and how many players took it on and beat it. Your handle, avatar and level appear on it if you are 18 or over with an email account, a profile open to everyone and your name shown on song records, unless you switch "Show my name and avatar" off when you share. Otherwise the card says "A YourBeats player".
- Counts. For each link and day we count how often it is previewed in a chat app (we keep only the app's name), opened, and taken on, without knowing who. Only you see your link's daily counts; anyone with the link sees how many took it on and beat it, and our team sees totals across all links, never who. When someone opens your link in the app and takes it on, their account is kept with the link so their result can count, and is never named to you.
- The card. Our card service draws the picture from the run's details and, when your name is shown, your handle and avatar. It keeps nothing. Cloudflare may keep the picture in its cache for up to a year (30 days for a song a player added, whose title and artist come from YouTube), but we never serve it again once you remove the link; chat apps and browsers may keep their own copies.
- Removing a link stops it working and deletes its counts. The link's own details stay with your account, unused, until you delete your account.
- Other links. The app can also share a link to a song (yourbeats.net/song/...), and your friend code, challenges, rooms and charts have link pages with picture cards of their own. A song's page names nobody, and we keep nothing about who shared it. The other pages show a person (their handle, avatar and level, and the style and status they chose for their page) only if that person is 18 or over, has an email account and a profile open to everyone, and shows their name on song records; a room's invitation shows its host by the same rule. Otherwise they name nobody, or say "A YourBeats player".
- Counts of link pages. For each day we also count how often each song's page, and each kind of link page (friend, challenge, room, chart), is opened, previewed in a chat app or leads to Google Play, and how often a free play (below) starts, with nothing that identifies anyone. These totals are kept.
- Getting the app from a link. If you open a YourBeats link on an Android phone without the app and tap to get it, the link to Google Play carries that link's own code (the share link, challenge, room, chart or song, or the friend code), so that YourBeats can open what you were sent once it is installed. Google Play receives the code with the install, under its own policies (section 5). The app reads it once, on its first start within a day of being installed, and only for a player old enough for YouTube's songs (section 9); it keeps only a note that it has looked, never the code, and then opens the link as a tap on it would.
- Play it once, free. With an email account, if you open a challenge (a share link or a friend's challenge) on a song you do not have, you can play its chart once, free. So that it stays once, our server notes with your account that you have used the free play of that song (the song's video ID and when), and your phone keeps a list of the songs whose free play you have used. The note is deleted with your account and is in your data download.
2.7 Songs you add
- Searching. When you search YouTube in Add a song, your words go to our server, which asks YouTube for matching videos (section 4). We do not store your words in our database. So that the same search is not made twice, our server keeps only a scrambled form of them, linked to no one, with the IDs of up to 20 videos YouTube found and nothing else, and gives that list to anyone who searches for the same words in the next 24 hours instead of asking YouTube to search again. It deletes the list after 2 days. Each search carries your account's sign-in so that it can be counted against your daily number of searches, under a scrambled form of your account, never your words. Your recent searches are kept on your phone. Searching Browse, which looks through YourBeats' own songs, happens on your phone.
- Importing a playlist. You can paste a link to a YouTube or YouTube Music playlist into Add a song to see which of its songs you can play. The app sends the playlist's ID to our server with your account's sign-in. Our server reads the playlist from YouTube with YourBeats' own key, up to 500 songs, checks each video as it does for a search, marks the songs that are already in YourBeats or in your library, and sends the list back. It keeps neither the link nor the list in our database. A playlist must be public or unlisted for YourBeats to read it. The list is kept on your phone (section 2.10), and "Check for new songs" reads the playlist again in the same way. If your music is in Apple Music or Spotify, the app shows you the steps of their own free transfer to YouTube Music, which Apple and YouTube Music's partners run in your browser under their own terms; YourBeats receives nothing from a transfer except the playlist you then paste or share.
- Sharing to YourBeats. Anything you share to YourBeats from another app, such as a link or a few words, is read on your phone. Only a link to a YouTube video or playlist leads to a request to our server: a video opens as if you had pasted its link, and a playlist as an import. Words open Add a song, and nothing is searched until you tap Search. YourBeats never contacts Apple Music or Spotify about a link from them: it shows the steps of their own free transfer to YouTube Music, and may suggest a search from the song title in an Apple Music link, which happens only if you tap Search.
- Lists of songs. You can paste a list of songs into YourBeats. Only the songs' details (title, artist, album, length and, where present, the ISRC, a code that identifies a recording) go to our server, which matches them with songs already on YourBeats or in the shared song list below, sends the answers back and keeps nothing. YouTube is searched for a song only when you tap "Find on YouTube", and then as a search of your own (above); "Search in the YouTube app" instead opens YouTube's own app with the song's name typed in, where YouTube handles the search under its own terms. The matches you confirm are kept with the list on your phone (section 2.10).
- Your data files from Spotify and Apple. You can also choose the file of your data that Spotify or Apple lets you download from them. It is read only on your phone and never sent anywhere: the app takes the song lists from it and handles them as a pasted list.
- Using your own music, and finding a music file's song by its sound. Your music file is read only on your phone and never copied anywhere. If the app cannot tell which song a file is from its tags, in "Use your own music" or when you choose your own copy of a song (section 2.2), it may ask you, for that file, whether to find the song by its sound, and sends nothing to Apple unless you tap "Find it". Apple's ShazamKit then receives a sound print (a one-way signature) of up to 10 seconds of the file, and at most one more if the first finds nothing (section 5). The sound itself never leaves your phone, and the original recording cannot be rebuilt from a sound print. Your answer is never remembered, so every file is asked again. A song you find or add through "Use your own music" can then be checked against your file and play from it, as your own copy (section 2.2). Finding a song by its sound is offered only to players known to be 13 or over and at least YouTube's minimum age where they live (section 9).
- The shared song list. Our server keeps one list, for every player, that links songs to YouTube videos. It learns from YourBeats' own songs, from the songs in public playlists players import (using YouTube's own credits for them), from Wikidata (a public, community-edited list of songs' official videos, which holds no player data) and from the matches players confirm, never from anything read by signing in to YouTube or Apple Music, or identified by Apple's ShazamKit. It holds songs' titles and artists in YourBeats' simplified form, recordings' ISRCs and videos' IDs, never who confirmed a match, and each video is checked with YouTube at least every 30 days. A match one player confirms is only suggested to others until a second player confirms it. So that each player's confirmation counts once, we keep a scrambled code made from your account, the song and the video for 90 days.
- Your country. Our server reads the country your internet address points to, worked out by Cloudflare, for these things only: to tell you whether a video plays there when you search, look a link up, import songs or add a song; to tell the app the minimum age YouTube sets there, and the age from which usage data can be on there, which matter for players aged 13 to 15 (section 9); and to choose which countries' Top charts to show you. We do not keep it in our database; Cloudflare's technical logs (section 2.11) may record it for 7 days.
- Adding a song. This needs an email account. We record which video you added and when, follow its preparation, and keep your allowance, so the song appears in your library. The first account that asked for a video is noted on it until that account is deleted.
- Preparing the chart. Our preparation service, which makes the chart, is told the video's ID, its YouTube title, channel and length, and never who asked. The chart is kept as part of YourBeats' catalogue, not linked to you.
- A prepared chart is shared work. If another player adds the same video, they get the same chart, and it still uses their own allowance. If you delete your account, the link between you and the song is removed, but the song and its chart stay in YourBeats.
- Songs that join our catalogue. Our team may make a song that players added part of YourBeats' public catalogue, so that every player can play it free. It then becomes one of YourBeats' own songs, and nothing we show says who added it. If you added it, it stays in your songs, and your records on it stay with it, seen only by the players who added it; the catalogue song's song records start afresh, and anyone can see them. While it is in the catalogue, adding its video opens the catalogue song and uses none of your allowance.
2.8 Purchases
You can buy Premium, a subscription, and Full-length charts, a one-off purchase, in the app, through Google Play (our terms of use say what each gives). Buying needs an email account.
- Paying. Google Play takes the payment. We never see your card or bank details or your billing address: Google handles them under its own privacy policy (section 5).
- What Google tells us. When you buy, the app sends our server the purchase's reference from Google Play (its purchase token), and our server asks Google about it. Google tells us which product you bought (for Premium, whether monthly or yearly), the purchase's order number, its state (for example active, cancelled, on hold or refunded), its dates (when it was bought, and when the period you have paid for renews or ends), whether it renews, the country or region, whether it was a test purchase, which earlier purchase it replaced if it did (for example when you move from monthly to yearly), and the scrambled code below. Google also tells our server when a purchase changes, for example when Premium renews, is cancelled, cannot be paid for or is refunded, and our server then asks Google about it again.
- The scrambled code. For each email account, our server makes a scrambled code from your account ID, which the app gives Google Play with a purchase, so that a purchase can be matched to your account without Google learning its ID.
- Why. To give you what you bought and keep it on your account, restore it on another phone, handle renewals, cancellations, payment problems and refunds, confirm each purchase to Google (Google refunds a purchase that is not confirmed within three days), stop a purchase being used by another account, and answer you if you ask us about a purchase.
- On your phone. Until our server has confirmed a purchase, the app keeps it on your phone and tries again (section 2.10).
- What we keep, and for how long. Each purchase's record (the details above, with its purchase token, which we need to ask Google about it again) is kept with your account until you delete your account. Our log of what Google tells us and of our checks names a purchase only by a short code made from it, never its token, and is kept for 120 days. To limit how often an account can ask us to check purchases (30 times an hour), we note each check with the account for 2 days (section 6).
- Our accounts. For our company's accounts and tax, we keep the sales and earnings reports Google Play gives us, which list each order's number, product, price and date, and the buyer's country and, for some countries, their state, city or postcode, for 6 years after the end of the financial year they belong to.
- Unlocks from before. If your phone has a free full-song unlock from an earlier version of the app, the app carries it into your account, with the label "YourBeats app", and we keep a note of it.
- Notifications. If you have said yes to notifications, we can tell you when Premium could not be renewed, or is about to end ("Account and safety", section 2.13).
- Google's own records. Google keeps its own records of your purchases under its own terms and privacy policy, and deleting your YourBeats account does not delete them (section 7).
The supporter mark. With Premium, you can choose to show a supporter mark beside your handle on your profile page. It is off unless you switch it on, and shows only while you have Premium, to whoever can see your page's stage set and status (section 5), so they can tell that you have Premium. It never appears on song records, boards or rooms.
2.9 Crash reports and usage data
Crash reports (every player). When something goes wrong inside the app, it sends us a report so that we can fix it:
- the error's kind and message and the technical trace of where in the app's code it happened, with anything that could say who or where you are taken out on your phone and again on our server (email addresses, handles, friend and room codes, account and draft numbers, sign-in keys and codes, the details of web addresses, long numbers, internet addresses, folder names and long quoted text), then shortened;
- which screen of the app you were on, the app's version and build, whether it runs on Android, iPhone, the web or something else, and when it happened;
- how many times the same error happened in that session.
A crash report has no account, email, name or device ID, and nothing that links it to you, your phone or another report. Each carries a random reference of its own, used only so that a report sent twice is counted once, and kept for 7 days. We group reports of the same error and count them by app version and day. A group is deleted 400 days after the error was last seen. There is no switch for crash reports: they are how we find and fix faults in the game you are playing.
Usage data (unless you switch it off). "Share anonymous usage data" in Settings starts switched on for players old enough (below), and you can switch it off at any time. While it is on, the app makes a random number for this app on your phone (it is not your phone's own ID, and it has nothing to do with your account or email) and sends short notes of what happens in the game, each with that number, the time, the app's version and build, the platform, and a running count. They cover:
- the app opening (whether for the first time, the app's language and your phone's language), the button style and the menu music;
- your first play and the tutorial: the music styles you pick, the first song you choose and its medal, and each step (how it went, tries and seconds, and whether your sound was on);
- playing: a song started, finished or left part-way (the song, the difficulty and mode, and where it was played; for a finished song the medal, accuracy to the whole percent, full combo or all perfect, whether Assist or "never stop the music" helped, the note speed, and phrases skipped, retried or failed; for a song left part-way, how far in and from where), pauses, what you tap after a song (for a guest's run, also the place its card showed on the song records and whether it was posted), note speed and practice;
- Browse (what you open, sorts, collections and filters, and how many songs a search finds, never its words), sharing (what, the format and the app you chose, how a YourBeats link was opened, whether a link came through installing the app, and, for a challenge on a song you do not have, whether you added it or played it once free), signing in, the handle sheet (whether a handle you tried was free or why not, never the handle) and opening another player's card (never whose);
- challenges, rooms, making and sharing charts on a phone or a computer, and each step of adding a song (from searching to the chart arriving, and the reason a song could not be added);
- importing songs: where you chose to bring music from, whether a list could be read and how many of its songs fell into each group, what you did with them, and checks for new songs, never a song, a list, a link or a name;
- something shared to YourBeats from another app: only its kind (a YouTube video or playlist, an Apple Music or Spotify link, or other text), never the link or the text;
- Ranked (how a search ended and how long it took, a match's result and how far your rating moved, leaving a match, your venue and the season's page), weekly events (your taps on the event's card, how many players were in your event room, and your place at the end) and ghost races (whose ghost you raced, such as your own or a friend's, how the race went, why one could not be had, and the "Ghost races" choice you set, with your age group: 18 or over, under 18, or not known), never another player or a run;
- your profile and page: opening a player's page (what kind of page, never whose), editing your page, its soundtrack, wall and crew, sending a cheer, the stage sets and handle styles you earn or choose, and sharing or reporting a page;
- your settings and suggestions: the difficulty you choose for all songs or for one, each step of a "Ready for more" suggestion, changing the app's language, your music languages (the main one, how many, and whether you mix everything) and whether a song you start is in them, and the "Heat and battery" choice;
- Follow and community charts (trying, applying or suggesting a melody setting; community charts opened, played, rated, nominated or reported), the achievements you earn, and whether Google Play Games signed you in;
- other parts of the app: sign-in prompts and how a sign-in ended (by email, "Continue with Google" or Google Play Games, with how many seconds Play Games took), the choice between two accounts, a welcome back and linking or unlinking Play Games, favourites kept in step between phones, rankings and their earlier versions opened, how covers and pictures loaded, song pages opened (and from where), your phone's storage running out, saving your data file, room invitations, the Originals' shelf and downloads, and Originals played in rooms;
- the Premium screen and purchases, offline play where the app has it, and technical problems such as the video page closing or a request failing;
- adverts at breaks (section 2.15): at each break where they are on, whether one showed, or why not (for example Premium or your age group);
- app updates: whether Google Play offered a newer version of the app or this version needed one, and what happened (Google Play's update screen shown, the update started, put off or failed, a downloaded update ready to install, the app's own notice that an update is needed, and Google Play's store page opened from that notice);
- the stores' rating card and the feedback doors: whether YourBeats asked Google Play or the App Store to show its own rating card as you left a song's results, and on Android how long the card was up (never whether you rated, your stars or your review: the store's card never tells the app), and whether you opened Rate YourBeats, Send feedback, Report a problem or a notice's Tell us (where from; never what you write: an email you send goes to us as any email does);
- "Use your own copy": the file picker's answer (where you opened it, and whether you chose a file, cancelled, or chose one that is not on your phone), the check's outcome (the song, if it is one of YourBeats' own catalogue songs; its verdict and reason, the file's format, how many seconds it took, how closely the file fits, whether parts of the song are missing from it and in how many pieces it plays), a copy you forget, and whether the file carried a cover picture; never the file, its name, its tags or where it is on your phone;
- "Use your own music": where you opened it, how many files you picked, each file's format and whether its tags named a song or why it could not be used, whether you were asked to find a song by its sound and what you answered, whether that found one (with how many tries and seconds, or why not), how the song was found and whether it was on YourBeats or in your songs, the searches you made from it and how many results they gave, the result you chose (a YourBeats song or a YouTube upload, and its place in the list), and whether Apple's "Listen on Apple Music" link was shown or tapped; never the file, its name, its tags, where it is on your phone or the song found;
- for a song that plays from the phone (the YourBeats Originals, and your own copy of a song): where the sound went, the frame rate, a timing correction, the phone's heat, a failed start and what played instead (never a timing in milliseconds), and, for your own copy, whether it played because YouTube would not play the song's video, and whether the video was blocked or removed; and, in a version of the app that includes the Originals, whether the app last ended in a crash that the phone recorded, and whether such a song was playing then;
- every song you play: the frame rate the game ran at and why, and the phone's heat as one word (such as "none" or "moderate");
- notifications (section 2.13): how you answered when asked about them, the switches and quiet hours you change (in the app or in Android's settings), which kinds of notification were shown (by the phone itself or through Google) and tapped, and whether the phone could register for notifications through Google; never what a notification said.
Usage data never carries your account, email, name or handle, anything you type, your search words, or your internet address (our server receives your address to answer, as it does for everything, and does not keep it with usage data). A song is kept only if it is one of YourBeats' own catalogue songs or Originals, never a song that is only a player's own. We use usage data, in totals, to see whether the game is fair and working: for example, how many new players finish a first song, and whether each difficulty is as hard across songs as it should be. No usage data is sent about a song whose video YouTube marks as made for children.
- Who it is on for: players from 13, or from YouTube's minimum age or the age at which they can agree to it themselves where they live, if either is higher (the app uses 16 until it knows; section 9), once they have answered the age question and agreed to the terms. Below that age it is hidden and switched off, and for a player under 13 no usage data is ever sent, whatever the setting says.
- Switching it off: sending stops at once and the notes waiting on your phone are deleted. Our server deletes everything that was sent with your random number, and the phone keeps the number only until our server confirms it has done so. If you switch it on again, a new random number is made, so nothing from before can be connected to what is sent after.
- How long: usage events are kept for 90 days. A note that your random number was active on a day is kept for 400 days after that day, and the time of each first step (first launch, first song started and finished, first sign-in) for 400 days after the number was last active.
Google Analytics for Firebase (with the same switch). While "Share anonymous usage data" is on, Google Analytics for Firebase, Google's app measurement service, which we use to understand how the app is used, is on too. While it is on, Google receives: that the app was opened, for how long, and which of the app's screens you visit; when the app is first opened, updated or removed; your phone's Android version and language, and the app's version and the store it was installed from; once purchases exist, what you buy in the app (the product and its price, never your card details); and roughly where you are (a country or region, worked out from your phone's internet address, which Google does not keep). Google files this under a random number that Google Analytics makes for this app on your phone (its "app instance ID"), never your name, email, handle, account or anything you type. YourBeats removes Android's advertising ID permission from the app, and tells Google Analytics not to collect the advertising ID, not to use the data for adverts and not to personalise anything. It never starts for a player under 13, or younger than YouTube's minimum age where they live, because the switch is not offered to them.
- Switching it off: Google Analytics stops at once, and the app clears its data on your phone and resets that random number, so nothing sent before can be connected to anything sent later. The app then sends the old number to our server, once and without your account, and we ask Google to delete everything Google Analytics holds under it: Google stops showing it within a day and deletes it within 63 days. We do not keep the number. If the request cannot be made at once (if you are offline, say), the app keeps the number and asks again later, for 60 days at most. In any case, Google deletes the detailed records it holds after 2 months (the totals in our reports, which say nothing about any one player, stay).
- Google handles this for us under the Google Analytics terms and its data processing terms; we have switched off Google's own use of the data (its "data sharing settings").
2.10 On your phone
YourBeats keeps these in the app's own private storage on your phone:
- your sign-in (your account ID, email address and sign-in key, or your guest account's secret, or the key a phone gets when Google Play Games brings a guest account back to it), and the address a sign-in code was just sent to, never the code;
- your age answer, YouTube's minimum age for your country and the age from which usage data can be on there, if the app has asked for them (only the minimum ages that apply where you are, never the country itself, though in a few countries those ages belong to that country alone), your privacy choices and your avatar;
- the version of these terms and this policy you agreed to, and when;
- your settings and language, the music languages you chose, timing adjustments, favourites, the last song you chose, the music styles you picked, your tutorial progress and the tips and invitations you have already seen;
- your bests, your progress and run history, and runs waiting to be sent, a Ranked run among them (and, for up to 24 hours, a guest's runs waiting for you to sign in and post them: section 2.2);
- your recent searches (in Browse and in Add a song) and, for 30 minutes after you leave Add a song to sign in, the search you were in;
- your chart drafts;
- the playlists you imported: each one's name, where it came from and when it was read, and for each song its video's ID or YourBeats' own song, your own name for it if it came from a list or a file, and whether you added or hid it. YouTube's details in them are read again or deleted after 30 days, and a list you have not opened for 30 days is checked again before it is shown;
- for each song you use your own copy of (section 2.2): Android's permission to read that one music file, its place on your phone, its name, size, date, length and format, a fingerprint of its contents (so that the app can tell when the file changes), how the check went and, if the file carries one, its cover picture made small; and, so that the song plays without a connection, its charts and what the check compared the file with;
- purchases waiting for our server to confirm them, and the free full-song unlock if your phone has one;
- crash reports waiting to be sent; and, only while you share usage data, the usage events waiting to be sent, the random number that goes with them and the challenges you received;
- a number for rooms, only on a phone with no account at all;
- lists kept to save time, such as this week's top songs and colours taken from song covers, and, for "Surprise me", the songs it chose for you lately, the ones you went back from, and the videos YouTube would not play on this phone, so that it does not choose them again;
- the list of YourBeats Originals on offer and any you download, and Top charts' list from your last visit (only for a country that is not yours) and a chart country you chose;
- what the game's effects last eased off for (heat, battery saver or Android's animation setting) and when, never a reading (below);
- a note that the app has looked for a link that came with installing it, never the link, and the songs whose free play you have used (section 2.6);
- for updates (section 5): the lowest version of the app our server last asked for (with the version of the app that last read it), and which newer version Google Play last offered you and when, so that it is not offered again too soon;
- for the stores' rating card (section 2.9): when YourBeats last asked the store to show it and how many times, and when you last opened Rate YourBeats, so that it is asked at most once a month and not for a year after you rate from Settings (this record never leaves your phone);
- for notifications (section 2.13): your answer to "Notifications through Google" and what our server was last told, the event reminders you asked for (each event's name and start time) and a copy of the names of the songs you added, so that a notification about one of them can name it (the reminders and names are removed when you sign out, and the names never leave your phone);
- whether Google Play Games may start on this phone, worked out from your age answer and kept for the next start (section 2.14);
- for signing in with Google Play Games (section 2.1): whether this phone is linked to it, and to which account; your Play Games name as Google shows it; a scrambled code the app makes from your Play Games player ID, so that it can tell when another profile signs in; whether its sign-in is paused on this phone; if your profile opens another account, that account's handle or masked email; and when the app last told you that Play Games did not sign you in;
- for adverts (section 2.15): an ad song waiting for Google's confirmation (its song, its ticket and when), whether Google's ads code has started on this phone, and whether Google's privacy options apply to you; and, for the adverts at breaks, a record that never leaves your phone: the times of the last day's adverts, the last time you started an ad song, opened Premium or the Full-length charts offer, or restored a purchase, when you first used YourBeats on this phone, and a random number from 0 to 99 made on this phone, which decides whether they are on for it while they are being introduced.
Your phone's heat. So that the game's effects can ease off between songs when your phone runs hot or is saving battery, the app asks Android for its heat status, its battery-saver setting and its animation setting when a song ends, when it starts and when you come back to it, never during a song. The readings stay on your phone and are never sent to us: the app keeps only the reason and the time of an ease-off. (Separately, if you share usage data, the note sent when a song starts says the phone's heat as one word: section 2.9.)
Song covers come from YouTube. So that they show quickly, and when you are offline, the app keeps each one on your phone for up to 30 days, and fetches it again from YouTube after 7 days when you are online; it deletes them all for a player under 13 or younger than YouTube's minimum age, and when you use "Remove offline data". (The cover picture from your own copy's file is kept as described above.) Settings, then About, then Reset timing and scores (under "This phone") clears this phone's timing, bests and the progress kept on it, and nothing else. Uninstalling YourBeats, or Android's "Clear storage", clears everything it keeps on your phone. Android's backup to your Google account copies nothing of YourBeats. If you set up a new phone directly from your old one (Android 9 or later), everything above is copied to the new phone, your sign-in and your guest account's secret included.
2.11 Technical information
- Our server runs on Cloudflare (section 5). Like any website, it receives your phone's internet (IP) address and the technical details your phone sends with each request, such as its Android version and model. Cloudflare keeps technical logs of each request (such as the time, the address requested and the result) for 7 days, and we use them to find faults. The address requested can include your search words, a handle you check or open, a room code, a share link, a video's ID, a playlist's ID, an ad song's ticket (and, in Google's confirmation of it, the random user ID and Google's transaction number) or the names of songs you look for on YouTube.
- To limit abuse, we count requests such as searches, song look-ups, song records, sign-in codes, sign-ins with Google Play Games or Google, crash reports and usage data under a scrambled form of your internet address or your account ID (never the address or the ID itself). Most counts last an hour; daily search counts last until YouTube's day ends.
- So that nobody can keep guessing a sign-in code, we count the wrong codes typed for an email address for a day under a scrambled form of that address.
- Some actions are counted with your account to stop spam, such as friend codes typed, rooms made and invitations sent. Each count is replaced the next time you do the same thing after 2 days, and deleted with your account.
- YourBeats does not use cookies, and nor do our web pages for players (such as friend, room, chart and share links and the account deletion page). The chart editor for computers (yourbeats.net/edit) keeps its connection in the browser's own storage while it lasts (section 2.5), and the note speed you chose for its test play. The editor and the plainer version of our home page (at yourbeats.net/home, and at yourbeats.net itself whenever our main home page is switched off) load their typefaces from Google Fonts, so Google receives your browser's internet address when you open them. The editor plays videos in YouTube's privacy-enhanced player. Three pages for our own developers, not made for players (yourbeats.net/author, /inspect and /lab), also load Google Fonts; the inspector also plays videos in YouTube's standard player and keeps unsaved chart edits in the browser's own storage.
- If you write to us from the app's Help, your email app starts the message for you, with the app's version and your Android version in the subject.
2.12 Features that are not switched on yet
These are built but not switched on in YourBeats today. Before any of them is, we will update this policy if what is collected changes.
Bringing your music into YourBeats. Section 2.7 describes the ways you can bring your music in today. We are building more, below; they are not switched on yet, and we will update this policy before each one is. None would be offered to players under 13, and those that use YouTube would stay closed, like the rest of YouTube in YourBeats, until a player reaches YouTube's minimum age for their country (section 9). They would work as follows.
Connect YouTube
Connect YouTube would let you bring in your own YouTube playlists and the videos you have liked, private ones included, without making anything public. It would always be your choice, and you could stop at any time.
- Google's own sign-in, read only. You would sign in on Google's own screen, which names YourBeats and asks whether it may "View your YouTube account": read-only access through YouTube's Data API. YourBeats would never see your Google password, would not ask Google for your email address or name, and could not change, post or delete anything on YouTube.
- What is read. The names of your playlists, the videos in them and the videos you have liked. The app on your phone would read them directly from YouTube (YouTube's answers also carry your channel's name, which the app would not keep) and send only the videos' IDs to our server, which checks them as it does for a search, sends the answers back and keeps nothing.
- Where it is kept. Only on your phone, in the app's private storage, and shown only to you. Anything read with your account would be read again from YouTube or deleted after 30 days, and never added to the shared song list (section 2.7). Google Play services on your phone would keep the access you gave and hand the app a short-lived key whenever it needs to read: the app would not store that key, and our server would never receive it. A song you choose to add from these lists is added like any other song (section 2.7).
- Removing access. You could disconnect in the app's settings at any time: the app asks Google to end its access, and deletes from your phone at once everything it read with your account (YouTube's rules allow 7 days at most). Deleting your YourBeats account would do the same. You can also remove YourBeats' access on Google's security settings page, https://myaccount.google.com/permissions: the app checks each day you open it that it still has access, and when it finds that access has gone it deletes what it read with your account straight away.
- Google's rules. What is read would never be used for advertising, sold, or shared with anyone. YourBeats' 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. For questions or complaints about how YourBeats handles it, write to support@yourbeats.net.
Apple Music
You could connect Apple Music through Apple's own sign-in (MusicKit for Android, with the Apple Music app). Apple would give the app a key for your Apple Music account, a Music User Token, which would stay in the app's private storage on your phone and never reach our server; disconnecting deletes it.
- Save to Apple Music. You could add a song, or a YourBeats playlist, to your Apple Music library. The app would send Apple the songs you chose. Your library is Apple's service, kept under Apple's own privacy policy.
- Your Apple Music playlists. The app would read your library's playlists and their songs (title, artist, album, length and ISRC) from Apple, on your phone, and send only the songs' details to our server to be matched, as for a list of songs (section 2.7). Our server would keep none of it, and nothing read from your library would go into the shared song list.
Our server would give the app a short-lived key that identifies YourBeats to Apple, and would look up which Apple Music songs match YourBeats' songs; neither sends Apple anything about you. Apple handles your account and your library under Apple's privacy policy.
Links to music services, marked "Ad"
For players who have told YourBeats they are 18 or over, YourBeats could show a few links to Apple Music and, in the UK, to Amazon (for example to wired headphones, which keep timing steady), each marked "Ad". They would never be on or over YouTube's player, on the play screen, during a song or in a pop-up, tapping one would never earn anything in the game, and you could hide them. The "Listen on Apple Music" link that Apple requires beside a song identified by its ShazamKit (section 2.7) is shown to everyone who can use that feature, but would carry YourBeats' commission code only for these players.
A link would open in your browser, or in Apple's or Amazon's own app if you have it. There, Apple (through Partnerize, which runs Apple's programme) or Amazon would see that you came from YourBeats, using cookies, your internet address and your browser's details under their own privacy policies, and would pay YourBeats a commission if you subscribe or buy. The links would carry YourBeats' own codes and nothing about you, and we would count taps without knowing who tapped.
2.13 Notifications
Notifications (only if you say yes). YourBeats can tell you when something happens while the app is closed: your song is ready (or could not be prepared), news about your songs and charts, a friend request, a challenge, an event about to start, your Ranked results, news from YourBeats, and reports and account matters. Settings, then Account, then Notifications has a switch for each group of these ("Your song is ready", "Your songs and charts", "Friends and challenges", "Events and Ranked", "News from YourBeats" and "Account and safety") and quiet hours (from 22:00 to 08:00, or 21:00 to 08:00 for players under 18, until you change them). News is off until you switch it on.
- "Your song is ready" and the event reminders you ask for can come from your phone itself: the app checks with our server, as it does today, and nothing goes through Google.
- Everything else comes through Google's Firebase Cloud Messaging, only after you say yes, and only for an email account. Your phone then gets a Firebase installation ID (a random number for this app on this phone; it does not identify you or your phone), which the app sends to our server with your phone's settings for notifications: which kinds are on, your quiet hours, your phone's time zone, Android or iPhone, and the app's version. Each notification carries only what your phone needs to word it and to open the right page when you tap it: its kind and, where it applies, a player's handle as you see it, the name of one of YourBeats' own songs or of a chart, room or event, numbers and times (such as a score, a place or when an event starts), the reason our team gave for a decision about your chart, and the IDs of what it is about (such as the song, chart, challenge, room, event or player); never your email address or account ID. The name of a song you added is never sent: it travels as its video ID, and your phone names it from its own list.
- Turning it off: "Notifications through Google" (Settings, then About, under "Your data", or on the Notifications page) removes your phone from our server and deletes the installation ID; so does signing out. Turning every switch off, or YourBeats' notifications off in Android's own settings, also removes your phone from our server (for Android's settings, the next time you open YourBeats).
- Never under 13, or younger than YouTube's minimum age where they live: Firebase never starts on their phone.
2.14 Google Play Games
On Android, Google Play Games starts with YourBeats only once you have told the app that you are 13 or older: never for a player under 13, or whose age is not known. Then, if your phone has a Play Games profile, Play Games signs you in with it when YourBeats starts, as it does in other games that use Play Games (Google may first ask which account to use, and may show a short "signed in" message). YourBeats never asks Google to make a Play Games profile for you by itself: without one, Play Games does not sign you in when YourBeats starts. If you have none and connect Play Games yourself (Connect in Settings, then Account, or Play Games where you save your progress or sign in) or tap "Continue with Google", Google may offer to make one, on its own screen. Google collects its own information about the sign-in, including its own analytics and diagnostics, under the Google Privacy Policy (what Play Games collects). YourBeats uses it to sign you in to your own YourBeats account (section 2.1): our server receives your Play Games player ID from Google and keeps it only in scrambled form, and the app reads your Play Games name on your phone to show it to you there, never sending it to us. We also start Play Games so that YourBeats' achievements appear in it: the achievements you earn are unlocked in Play Games, which Google keeps with your Play Games profile, and Google may show its own short message when one is unlocked. If you share usage data, it tells us whether Play Games signed you in, and how signing in to YourBeats with it ended, so that we can check that it works (section 2.9).
To stop it. Signing out of an email account on a phone (Sign out, in Settings, then Account; a guest account has none) stops Play Games signing you in to YourBeats there, until you sign in again or connect it yourself. Unlink, under Google Play Games in Settings, then Account, removes the link between your account and your Play Games profile, and Play Games then no longer signs you in to YourBeats on that phone until you sign in, add an email address where you save your progress, or connect it again. For an account with no email address, the app asks you first, because a new phone could then no longer bring it back. Neither Sign out nor Unlink stops Play Games itself: it still starts when YourBeats starts and, while it has signed you in, the achievements you earn are still unlocked in it. YourBeats has no switch of its own for that. To stop Play Games signing you in by itself, sign out of it in Google Play (in the Play Store app, tap your profile picture, then Settings, General, Play Games profile and Sign in account). After that, Google may show its own Play Games sheet when YourBeats starts, asking you to choose a profile: if you close it, Play Games does not sign you in, YourBeats may tell you once that it did not, and YourBeats works as before without it. Signing out in Google Play does not sign you out of YourBeats, and your account stays linked to your Play Games profile until you unlink it. Google warns that signing out of all games might lose you access to your progress and settings in other games. You can manage or delete your Play Games data in your Play Games profile or your Google Account.
2.15 Adverts
Without Premium, YourBeats may show you adverts from Google AdMob, in the two ways below. They never appear during a song, or over YouTube's player, and they are never personalised. Nobody under 13 sees one.
Adverts at breaks. If you don't have Premium, the app may show a full-screen advert at some breaks in the game, for example when you leave a song's results; never during a song, and never when the app starts or closes. Premium turns them off; other purchases, such as Full-length charts, do not. These adverts are shown only to players who have told YourBeats they are 13 or over, and never to players younger than YouTube's minimum age where they live, or younger than 15 in Denmark, or whose age is not known (section 9). To decide, our server reads whether your account has Premium and, for an email account, your age group (section 2.1), and keeps nothing new; your phone decides the rest from a record it keeps (section 2.10).
The ad song. With an email account and without Premium, once your free song is used (or while it is held by a song still being prepared), YourBeats may offer you more songs, one for each advert break you choose to watch (one or more adverts, back to back), up to the number in any 24 hours that the app shows. The app shows how many free songs and ad songs you have. The offer sits on a song's page and on a room's "Add to your own songs", and only for players who can add songs (section 9).
- What the app asks our server for. A one-time ticket for that song, with a random user ID made for that ticket alone (never your email address or account ID). Both go to Google with the request for the advert break.
- Google's confirmation. When you have watched the advert break, Google tells our server directly: the ticket, the random user ID, which of our advert slots it was, the time and Google's own transaction number, signed with Google's key. Our server checks the signature against the keys Google publishes, and then adds the song like any other song you add (section 2.7). If the song cannot be prepared, your ad song is kept for the next one.
- What we keep. Each ticket (the song, its state and times, and, until Google confirms it, the random user ID and the advert slot), Google's transaction number for it, and, for a day, a scrambled form of your internet address, which limits how many tickets one connection can ask for. A ticket that added a song is your ad song, kept with your account until you delete it, and in your data download (the song, its state and its dates). A ticket that added nothing, and Google's transaction numbers, are deleted after 30 days.
- Reporting an advert. "Report this ad" opens your own email app with the app's version, the time and Google's reference for that advert; YourBeats sends nothing itself.
For both:
- Google's ads code starts only when an advert is due: when you choose to watch an ad song's advert break, or shortly before a break at which an advert is due; never when the app starts, and never for a player who is not shown adverts. In the UK, the European Economic Area and Switzerland, Google may first show its own consent form, for the use of your information by Google and by the ad partners Google works with there, which the form lists (for the adverts at breaks, in place of the first one); if Google says no advert can be shown, no ad song is added and nothing is used. Google's ads code keeps your answers on your phone.
- What Google receives, and decides how to use. Google's ads code collects, by Google's own description, your phone's internet address (which may tell it roughly where you are), how you interact with the advert (such as taps and video views), technical information about the app and the ads code, and identifiers such as Android's app set ID, for advertising, measurement and fraud prevention (Google's data disclosure for its ads code), under the Google Privacy Policy and how Google uses information from apps that use its services (section 5). In the UK, the European Economic Area and Switzerland, Google also sends the app's advert requests to those ad partners, so they may receive some of this information from Google, and use it under their own policies (section 5).
- Never personalised, and no advertising ID. The app asks Google for adverts that are not personalised and rated suitable for teenagers at most, for every player. For players under 18, it asks Google to apply its protections for teenagers; and for players younger than YouTube's minimum age where they live, or younger than 15 in Denmark, or whose age is not known (section 9), it tells Google's consent form so and asks Google to apply its protections for children instead. YourBeats removes Android's advertising ID permission from the app, so neither YourBeats, nor Google's ads code, nor Google's ad partners can read your phone's advertising ID.
- Google's privacy options. Where Google says they apply to you, You, then Privacy and account, then Your choices for ads opens Google's own form for its adverts.
3. Why we are allowed to use it
| What we do | Our reason under data protection law |
|---|---|
| Your guest or email account (and "Continue with Google", when you choose it), syncing your runs, progress, preferences and favourites, song records and ghost races, Ranked, friends, challenges, rooms (and your results in them), events, charts (and nominations and suggestions for official charts), share links and the links that open them after installing the app, adding songs (and asking for the advert break you chose to watch to add one, and checking Google's confirmation of it), importing your music, finding your music file's song by its sound when you tap "Find it", purchases, loading YouTube's player and covers for the songs you choose, checking and playing your own copy of a song, and deleting your account when you ask | Providing YourBeats to you, as you asked (our contract with you) |
| Keeping YourBeats safe and fair: the age question and YouTube's minimum age for your country, reports and moderation (including reports and complaints from people who do not play, section 2.3), word filters, limits against spam and overuse, checking scores, scrambled internet addresses, the country check for videos, the country that chooses your Top charts, and counting each player's confirmation of a song's match once | Our legitimate interests in a safe, fair and working game, and yours |
| Crash reports, technical logs, counting what is played (in totals, with no names), getting the next song's player ready when the app starts, the typefaces of our web pages, and sharing search results between players for a day | Our legitimate interests in finding and fixing faults, a quick start, a working site and searches that go further within YouTube's limits. The law also allows the app to store and read what it needs on your phone to detect technical faults |
| Starting Google Play Games on Android for players who have told the app they are 13 or older, so that Play Games signs in a player who has a Play Games profile, as it does in other games, and signing you in to your own YourBeats account with it, which also brings that account back on another phone (sections 2.1 and 2.14) | Our legitimate interests, and yours if you use Play Games, in YourBeats working with Play Games as other games do: keeping your progress with your Play Games profile, so that it stays safe without an email address and comes back on another phone, and offering YourBeats' achievements in Play Games. Our server keeps your Play Games player ID only in scrambled form, never your Play Games name, and Google uses what it collects under its own privacy policy. The law allows a sign-in like this, to a profile you already use, without asking you first. You can stop it as section 2.14 says |
| Notifications (section 2.13) | Your consent: they start only when you say yes, and you can withdraw it at any time by switching them off, in the app or in Android's own settings. Only players old enough to give this consent themselves are asked (section 9). |
| Showing your activity to friends | Your consent: it starts switched off, and you can switch it off at any time in the app. It is offered only to players who have reached the minimum age YouTube sets in their country (13 in the UK; 13 to 16 in the European Union, depending on the country), so that only players old enough to give this consent themselves can switch it on; until the app knows the ages that apply where you live it uses 16. Below that age, it is hidden and switched off. |
| Usage data, and Google Analytics for Firebase with it (section 2.9) | Our legitimate interests in seeing, in totals, how the game is used, so that we can keep it fair and working and make it better. It is on only for players who have reached the age at which they can agree to it themselves in their country (13 in the UK; 13 to 16 in the European Union, depending on the country), and at least 13 and YouTube's minimum age there; until the app knows the ages that apply where you live it uses 16. Below that age, it is hidden and switched off. You can switch it off at any time in the app, which stops it at once and deletes what our server holds (section 2.9). |
| Adverts at breaks for players without Premium, and deciding who sees them from Premium and the age group (section 2.15) | Our legitimate interests in paying for a game that is free to play, with adverts that are never personalised and shown only to players of 13 or over, with Google's protections for teenagers for those under 18 (section 2.15). Where the law requires agreement before Google's ads code stores or reads information on your phone, Google's consent form asks you first, and Google uses what it receives under its own privacy policy (section 5). |
| Keeping or sharing information when the law requires it, including our company's accounts (section 2.8), and dealing with reports and complaints that the law requires us to handle (section 2.3) | Complying with the law |
What you must give. No law requires you to give us anything. To play, the app needs your year of birth. Without an email address you can still play as a guest, but you cannot post song records, play Ranked, add friends, add songs, share charts or buy.
Automatic decisions. Some decisions are made by our systems: the word filters refuse a name or a message, the checks refuse a chart that cannot be shared yet, the score checks can take a record off the boards, and two failed score checks in a season pause Ranked for an account until a person on our team has looked. None of them has a legal or similarly significant effect on you, and you can always ask a person on our team to look again (section 8).
You can object to anything we do on the ground of our legitimate interests (section 8).
4. YouTube
YourBeats uses YouTube API Services.
- The player. Videos play in YouTube's own embedded player, which the app loads from YourBeats' website (yourbeats.net/player/yt.html): when the app starts (with the last song you chose, or the first song on a first start, ready but not playing) and whenever a screen shows a video. It is never loaded for players under 13, or younger than YouTube's minimum age for their country (section 9). When the player loads, it collects and shares some basic information with YouTube, to show the video's picture and title, to decide whether the video can play where you are, and to fight fraud and abuse; more is collected when a video plays. YouTube may show its own adverts in the player, and may use cookies or similar technologies there. YourBeats does not control this. The app receives from the player only what it needs to stay in time with the video, such as whether it is playing and its current time.
- Covers. Song covers are YouTube's thumbnails, loaded straight from YouTube, so YouTube receives your phone's internet address and which covers are shown; the app keeps each one on your phone for up to 30 days (section 2.10). They are never loaded for players under 13, or younger than YouTube's minimum age for their country, who see YourBeats' own drawn covers instead, and on a first start they wait until the age question is answered (section 9).
- Search. When you search YouTube in Add a song, our server asks YouTube's Data API for matching videos, with YourBeats' own key. YouTube receives your search words from our server, not linked to you. If someone searched for the same words in the last 24 hours, our server may answer with the list YouTube gave then (section 2.7).
- Playlists. When you import a YouTube or YouTube Music playlist, our server reads it through YouTube's Data API with YourBeats' own key (section 2.7). YouTube receives the playlist's ID from our server, not linked to you.
- Opening YouTube. If you choose to watch a video on YouTube, it opens in your phone's browser or YouTube app, under YouTube's own terms.
- Your Google account. YourBeats never signs you in to YouTube, and never sees your YouTube account or your Google password. Signing in with Google Play Games or "Continue with Google" gives our server only what section 2.1 says. (Connect YouTube, which is not switched on yet, would let you choose to give YourBeats read-only access to your YouTube playlists and likes: section 2.12.)
- What we keep. Public details of the videos in YourBeats: title, channel, cover address, length, and whether the video may be embedded and is available, refreshed from YouTube at least every 30 days. The shared song list (section 2.7) also keeps YouTube videos' IDs beside songs' names in YourBeats' own form, and checks each video with YouTube at least every 30 days. Top charts keep YouTube's weekly music chart for the countries shown, for 14 days.
- YouTube's handling of information is covered by the Google Privacy Policy, and YouTube's own rules by the YouTube Terms of Service.
Apart from YouTube's own player, and Google AdMob's adverts with Google's own consent and privacy options forms for them (section 2.15), YourBeats does not let any other company show adverts or other content in the app. (Google Play Games may show its own sign-in message, its own message when you unlock an achievement and, when you connect it yourself or tap "Continue with Google", Google's own sign-in and consent screens: sections 2.1 and 2.14.) YourBeats' own links to music services, marked "Ad", are not switched on yet (section 2.12).
5. Who else sees or handles your information
Other players and visitors. Other players see what you let them see: your handle, avatar and level; your song records; and, depending on your privacy choices, your profile, bests and activity. Anyone who knows your handle, signed in or not, can look up its avatar and level; the rest of your profile (the month you joined, your skill, highest difficulty cleared and achievements, and, for adults, a chosen name) only as your privacy choices allow. Your handle's style shows wherever your handle does. Your page's stage set and status show to anyone if your profile is open to everyone; if it is open to friends, to your friends, and to anyone for a player known to be 18 or over; if it is set to only you, to nobody else (the supporter mark follows the same rule: section 2.8). The rest of your page (its soundtrack, wall, crew and cheers) shows to your friends unless your profile is set to only you, and to anyone else only if your profile is open to everyone and you are known to be 18 or over; places and scores on it follow your choices for song records. In rooms, players see each other's handles, avatars and levels. Other players can race your saved runs as ghosts, as your "Ghost races" choice allows (section 2.2), and other Ranked players can race your ranked runs for 14 days (section 2.4). The records of a song you added are seen only by the other players who added it (section 2.7). If our team adopts a melody setting you suggested, the song's page may name you (section 2.5). Share links, link pages and shared charts show what sections 2.5 and 2.6 describe.
Companies that run parts of YourBeats for us. They handle your information only to do this work for us:
| Company | What it does for YourBeats | What it handles |
|---|---|---|
| Cloudflare, Inc. (privacy policy) | Runs our server, database, rooms, card pictures and web pages, and passes on emails sent to support@yourbeats.net | Everything our server keeps (section 2). Our database is kept in Cloudflare's Western Europe region; rooms and technical logs may be handled in any of Cloudflare's locations. |
| LAYANET LTD (laya.net, a private limited company registered in England and Wales, company number 17430595), our email system, which acts for us as our processor under a data processing agreement and sends through Amazon Web Services, Inc. (Amazon SES, privacy notice) | Sends every email with a sign-in or deletion code | Your email address and the code. The email system keeps a record of each email (the address, which email it was, when it was sent and whether it was delivered, with the message saying why if it was not), never the code, for as long as section 6 says. The emails carry no tracking: no hidden image that reports when one is opened, and no links that report a click. For an email sent before 24 October 2026, the record may also show whether it was opened. |
| Resend, Inc. (privacy policy) | Sends our replies when you write to support@yourbeats.net (the outgoing server for our support mail) | Your email address and our replies |
| Modal Labs, Inc. (privacy policy) | Runs the preparation service that makes charts for the songs players add | The video's details (section 2.7), never anything about you |
| Google LLC (Firebase Cloud Messaging and Google Analytics for Firebase), under the Firebase Data Processing and Security Terms and Google Analytics' data processing terms | Delivers notifications, and measures app use for players who share usage data | For notifications: the installation ID, each notification's content (section 2.13) and, sent by Firebase itself, the app's version and your phone's make, model and Android version. For Google Analytics: the app instance ID and what section 2.9 lists. |
Google, under its own policies. Google decides for itself how it uses what it receives in these cases:
- YouTube (section 4).
- Gmail, which holds our support inbox: the emails you send us and our replies.
- Google Play, which installs and updates the app (when a newer version is ready for your phone, the app can open Google Play's own update screen, and Google Play does the update) and, at most once a month, shows its own card for rating the app (a rating or review you post there is public, under the store's terms, with your store name and picture; the store never tells the app whether you rated), takes the payment when you buy Premium or Full-length charts and tells our server about the purchase (section 2.8), receives the code of a YourBeats link you followed to install the app (section 2.6), and tells us about crashes and freezes that happen outside the app's own code (Android vitals, from phones whose owners share usage and diagnostics with Google, with no account of ours).
- Google Play Games, for players who have told YourBeats they are 13 or older (section 2.14), and Google's sign-in: to sign you in with Play Games (and with "Continue with Google" in earlier versions of the app), our server gives Google the one-time code Google gave the app, and Google tells it who you are; with "Continue with Google" in the current version, Google gives the app a sign-in it has signed, and our server checks it against the keys Google publishes (section 2.1).
- Google AdMob, for its adverts in the app (section 2.15).
Google's ad partners, under their own policies. In the UK, the European Economic Area and Switzerland, Google also sends the app's advert requests to the ad partners it works with there, which Google's consent form lists (section 2.15). They may receive some of what Google's ads code collects, and decide for themselves how to use it. Our server sends them nothing.
Apple, when you tap "Find it". To find the song (section 2.7), Apple's ShazamKit receives the sound prints, with your language and region settings and, as with any connection, your phone's internet address.
Our team. The few people who run YourBeats can see account information, only to run the game, answer you and moderate. Changes made through our admin panel are logged (what was done, when, from which internet address, and the account, record, chart or email address it concerned), and the log is kept for 2 years.
Otherwise, we share information only if the law requires it, to protect players or the public, or if YourBeats is sold or reorganised, in which case the new owner must keep to this policy. We do not sell your information. The only information shared for advertising is what Google's ads code collects for AdMob's adverts, which Google may also send to its ad partners (section 2.15).
6. How long we keep it
| Information | How long we keep it |
|---|---|
| Your account and what it holds (profile and page, handles, runs, progress, preferences, favourites, records, Ranked, your results in room songs, friends, challenges, drafts, charts, nominations and suggestions for official charts, share links, the free plays you used, songs you added, ad songs, purchases, event reminders, and the note of a guest account moved into it) | Until you delete your account. A guest account is deleted after 24 months without activity; an email account is not deleted for inactivity. |
| A guest's drafts | 30 days after they were last saved |
| Sign-in codes | Until used, 15 minutes at most |
| Records of sign-ins | Each sign-in lasts 120 days; its record stays until you sign out or delete your account |
| Your ways to sign in besides your email address: a scrambled form of your Play Games player ID or of your Google account's ID, when each was linked and last used, and the app's label | Until the account is deleted; a Play Games link also goes when you unlink it (Settings, then Account) |
| The keys of other phones that Google Play Games brought a guest account back to (scrambled), with the app's label and when each was made and last used | Until the account is deleted (sooner if it joins another account, or gets its email address through "Continue with Google"); at most 10 phones, the ones unused longest go first |
| A choice between two of your accounts (section 2.1): the two accounts and a scrambled form of your Play Games ID | It can be answered for 10 minutes, and is deleted the next time any player is offered such a choice |
| Records of the emails with codes, in our email system (the address, which email it was, when, and whether it was delivered; never the code) | Until they are erased, with no time limit before that. When you delete your account, we ask our email system to erase your address from them (section 7). If laya.net cannot be reached, we keep your address for up to 7 days while we try again, then delete it. If laya.net cannot be reached in all that time, your address may stay in those records: write to us (section 8) and we will erase it by hand. If a code went to an address that has no account with us, you can ask us to have them erased (section 8) |
| If an email to you bounces permanently, or you mark one as spam: your address on the lists of addresses our email system must not send to | Our email system's own list: until erased, as above. Amazon SES's list for our email system: until it is taken off, so that no more emails are sent to it. Amazon's own list for all its customers (permanent bounces only): up to 14 days |
| Resend's records of our replies to your emails (the emails themselves, their delivery events and logs) | 30 days, Resend's published retention |
| Emails you send to support@yourbeats.net or legal@yourbeats.net, and our replies | 24 months after the last message in the conversation |
| Inbox messages | 60 days, removed the next time you open your inbox |
| Your activity for friends (only while switched on) | 30 days, removed the next time your runs reach our server |
| Friend requests | They stop working after 30 days; their note is removed when either account is deleted |
| Rooms and their chat | Until the room closes: 12 hours at most (your own results in room songs stay with your account: section 2.4) |
| Event check-ins, with your room, place, points and songs | Until a day after the event |
| Codes and connections for carrying on at a computer | Codes: 10 minutes. Connections: 12 hours, removed a day after they end |
| Scrambled internet addresses | 1 day (with an ad song's ticket too: section 2.15) |
| An ad song's ticket that added nothing, and Google's transaction numbers | 30 days (a ticket that added a song is your ad song, kept with your account) |
| Counts of link pages opened, previewed or leading to Google Play (per song or kind of page and day, with nothing that identifies anyone) | Kept as totals |
| Our log of what Google Play tells us about purchases and of our checks of them (a short code for the purchase, never its token, the product, the account, when, and the outcome) | 120 days. If you delete your account sooner, the log no longer says it was yours |
| Notes of each time an account asked us to check its purchases, to limit them to 30 an hour | 2 days |
| Google Play's sales and earnings reports, kept with our company's accounts (section 2.8) | 6 years after the end of the financial year they belong to |
| Counts that limit overuse | An hour; a day for wrong sign-in codes; until YouTube's day ends for searches (section 2.11) |
| Search results shared between players (a scrambled form of the words, linked to no one, and the videos' IDs) | Used for 24 hours; deleted after 2 days |
| Counts kept with your account to stop spam | Replaced the next time you do the same thing after 2 days, and deleted with your account |
| Scrambled codes that make each player's confirmation of a song's match count once | 90 days |
| The shared song list (songs' names in YourBeats' own form, recordings' ISRCs and videos' IDs, with nothing about who confirmed them) | As part of YourBeats' catalogue; each video is checked with YouTube at least every 30 days and removed when it can no longer be played |
| A favourite you took off the list (email accounts) | A note of it for 400 days |
| Crash reports (grouped by error, with no link to you) | 400 days after the error was last seen |
| Usage data (while it is on) | Events: 90 days. Daily notes and first steps: 400 days. All of it is deleted as soon as you switch sharing off |
| Google Analytics' detailed records (only while you share usage data) | 2 months, kept by Google. Switching usage data off also asks Google to delete them (section 2.9) |
| A phone registered for notifications (its installation ID and settings) | Until you turn notifications off, sign out or delete your account; while our notifications are switched on, a phone the app has not confirmed for 270 days, or that Google says is gone, is removed |
| A notification decided for you | 30 days (its words' details are cleared once it is sent, or once it will not be) |
| Reports, chart appeals and our team's decisions | 2 years after the report or appeal is closed, or 2 years after it was made if it was never closed |
| Reports and complaints from people who do not play (their emails or letters, our replies and our decisions) | 24 months after the last message in the conversation, as for other emails to us. A copy of an intimate image is deleted once its report is dealt with (section 2.3) |
| A handle removed by our team | Kept from everyone for a year |
| Our team's action log, and failed attempts to sign in to our admin panel (by internet address) | 2 years |
| The note that an account was deleted (section 7) | 6 years |
| Cloudflare's technical logs | 7 days |
| Our database's restore history, kept automatically by Cloudflare so we can recover from a fault | 30 days |
| Backups of our email system's database, kept automatically by laya.net | 14 days |
| Copies of our email system's database that laya.net makes before updating its own software | No time limit yet |
| A search our team makes for your address in our email system's records (for example, to find out why a code did not reach you) | 30 days, in our email system's logs |
| Prepared charts and songs players added | Kept as part of YourBeats' catalogue, not linked to you |
7. Deleting your account
How. In the app: You, then Privacy and account, then Delete account, or Settings, then Account, then Delete account (for a guest account, Delete guest data in the same places). For an email account, you can also use our web page, without the app: https://yourbeats.net/api/v1/account/delete/web. You can always write to support@yourbeats.net from your account's email address instead, and we will delete it.
What happens. Your account stops working at once. Apart from what is listed under "What stays" below, everything we hold for it is removed at once; if any part fails, our server retries it automatically until it is done, within 7 days at most.
On your phone. Deleting your account signs this phone out but does not clear what the phone keeps (your bests, progress, settings and drafts). The next time you open YourBeats, it makes a new guest account and sends it this phone's run history, so that you can carry on playing. Google Play Games does not sign this phone in to YourBeats by itself again until you sign in or connect it yourself (section 2.1). If you want nothing to come back, uninstall YourBeats (or use Android's "Clear storage") after deleting your account.
Before you delete. Deleting your account does not cancel a Google Play subscription. Cancel it in Google Play first. A subscription that is still running can be restored into a new account by the Google account that bought it.
YouTube and Google. Deleting your YourBeats account does not, in any way, delete or change what YouTube or Google keep about you under their own policies (sections 4 and 5). To delete what YouTube keeps, use YouTube itself: the YouTube app or the YouTube website. You can manage what Google keeps, such as your Play Games profile (section 2.14), in your Google Account, and Google's security settings page, https://myaccount.google.com/permissions, shows which apps can use your Google account and lets you remove their access.
What stays afterwards, and why:
- a note that a deletion happened: a scrambled form of the account ID, how it was asked for, the dates and how many items were removed, so that we can show it was done (kept 6 years);
- your handle, kept from other players for 6 days with nothing linking it to you (a year, if our team had removed it), and your friend code, which is never given to anyone else;
- reports you made, with your note but without the link to you; reports about you, closed, without your name, avatar or the link to your account (the reporter's own words stay); and the messages you wrote in a room, with the name you had, inside reports other players made about that room. All of them go 2 years after the report is closed (section 6);
- a room you are in, until it closes (12 hours at most), and an event you checked in to, until a day after the event;
- a choice between two of your accounts that you had not answered, until it is deleted (section 6);
- the other player's side of a Ranked match you played, without your account;
- songs you added, as shared work no longer linked to you;
- matches you confirmed in the shared song list, which never said who confirmed them, and, for up to 90 days, the scrambled codes that counted your confirmations;
- other players' own records, runs and charts. If someone remixed a chart of yours, their chart keeps its credit line, which names you as you were shown then. If our team made your chart a song's Official chart, it stays in YourBeats, credited to you;
- our log of what Google Play told us about your purchases and of our checks of them, with your account removed from it, for up to 120 days, and, if you bought anything, Google Play's sales reports in our company's accounts (sections 2.8 and 6);
- Google's own records, of your purchases and, if Play Games signed you in, in your Play Games profile (section 2.14);
- our team's action log, which may mention your account ID or email address, for 2 years (section 5);
- the emails you sent to support and our replies, and Resend's records of those replies, for as long as section 6 says;
- our email system's records of the codes it sent you, without your address: when you delete your account, we ask laya.net to erase your address from them, and from its own list of addresses not to send to. If laya.net cannot be reached, we keep your address for up to 7 days while we try again, then delete it. If laya.net cannot be reached in all that time, your address may stay in its records: write to us (section 8) and we will erase it by hand. Its erase does not yet reach the message saying why an email to you could not be delivered, if there was one, which can quote your address; that message stays, with no time limit for now. If an email to you bounced permanently or you marked one as spam, your address also stays on Amazon SES's list of addresses our email system must not send to, until it is taken off, so that no more emails are sent to it (and, if it bounced, on Amazon's own list for all its customers, for up to 14 days). Copies stay in laya.net's backups for 14 days, and in the copies of its database it makes before updating its own software, with no time limit yet;
- copies in Cloudflare's technical logs (7 days) and in our database's restore history (30 days), after which they are gone.
Guest accounts. A guest account can be deleted only from a phone that holds it, because only such a phone can show it is yours. If you uninstall YourBeats or clear its storage first, we can no longer tell which guest account was yours, unless it is linked to your Google Play Games profile: then Play Games brings it back when you open YourBeats on an Android phone with that profile, and you can delete it there. Otherwise it stays on our server until it has gone 24 months without activity (section 6). It holds your handle, avatar, runs, achievements, preferences, drafts (for 30 days) and share links, and no email address.
8. Your rights, and how to complain
Depending on where you live, including in the UK and the EU, you can ask us to:
- give you a copy of your information. With an email account: You, then Privacy and account, then Download my data, which gives you a file, in a standard format (JSON), with what our server keeps for your account. It leaves out security keys and a few things kept in other forms: your charts' notes (the drafts themselves are in the app), the words of inbox messages, reports about you, the technical details behind our score checks (each check's result and reason are in it), purchase tokens, our log of what Google Play told us about your purchases and the technical details of Google's confirmations of ad songs (section 2.15). It also leaves out your phones' installation IDs and the notifications decided for you (section 2.13), and the scrambled forms of your Play Games and Google IDs: it lists which ways to sign in your account has, and when each was linked and last used, and the phones Play Games brought it back to (section 2.1). Write to us for any of these, or if your version of the app cannot save the file, and we will send them to your account's email address. A guest account holds no contact details, so to get a copy of a guest's data, add an email address to it first;
- correct it. You can change your handle, avatar and privacy choices in the app. To correct your age group, write to us;
- delete it (section 7);
- restrict or object to how we use it, including anything we do on the ground of our legitimate interests (for Google Play Games, section 2.14 says how to stop it);
- move it to another service, using the download above.
You can withdraw a consent at any time by changing the setting. Usage data (section 2.9) is not linked to your account, so it is not in the download: switching "Share anonymous usage data" off deletes it. We reply within one month, and may ask you to show that the account is yours, for example by writing from its email address.
Complaints. If you are unhappy with how we use your information, please tell us first, at support@yourbeats.net or by post to the address in section 1. Our contact page lists every way to reach us. We acknowledge every complaint within 30 days, look into it, and tell you the outcome. You can also complain to the UK's Information Commission (the ICO), or to the data protection authority where you live.
9. Children and teenagers
Under 13. Songs from YouTube, accounts and playing with other people are for players aged 13 and over. A younger player can still use YourBeats with those switched off, as below. When it first opens, YourBeats asks for the year of birth (section 2.1). If the answer makes the player under 13:
- YourBeats makes no account for them on our server, and deletes the guest account the phone already had, if there was one. If the phone was signed in to an email account, YourBeats signs it out; that account stays on our server until it is deleted, which a parent can do on our web page or by writing to us (section 7);
- it never loads YouTube's player, never searches YouTube and never loads YouTube's pictures: song covers show YourBeats' own drawn art instead (section 4);
- it offers no rooms, quick play, Ranked, events, friends, challenges or sharing;
- it offers none of the ways of bringing music into YourBeats that this policy describes: a link shared to YourBeats from another app only opens the app, with a short note. It never identifies their music with Apple's ShazamKit, never shows them links marked "Ad" and never offers them the ad song;
- it shows them a notice, "Some things open at 13", which says that songs from YouTube, searching for songs, accounts and playing with other people are for 13 and over, and are switched off on their phone;
- the YourBeats Originals, our own songs, stay playable without YouTube in versions of the app that include them;
- if they use their own copy of a song (section 2.2), the file is read and checked only on the phone, as for every player; what the check fetches from our server (the song's charts and timing data) carries nothing about the player;
- no usage data is sent; crash reports, which carry nothing that could identify anyone, are sent as for every player;
- no notifications from our server and no Google Analytics: Firebase never starts on their phone (the same for a teenager younger than YouTube's minimum age where they live);
- Google Play Games never starts on their phone, so it never signs them in to YourBeats (section 2.14);
- nothing made on the phone while the player is under 13 (runs, favourites, chart drafts, the avatar's look or privacy choices) is ever sent to our server, not even after they turn 13: it stays on the phone;
- the app still reads the public lists that every copy of the app reads (such as the songs in YourBeats and this week's top songs), which carry nothing about the player.
If we learn that we hold personal information about a child under 13 without a parent's consent, we delete it: a parent can write to support@yourbeats.net.
YouTube's minimum age. YouTube sets its own minimum age, and it depends on your country: it is 13 in most countries, including the UK and the US, and higher in some, for example 14 in Spain, Italy and South Korea, 15 in France, and 16 in Germany, Ireland and the Netherlands. The YouTube Terms of Service for your country give the exact age. If you are 13 or over but younger than YouTube's age for your country, you keep your YourBeats account, but everything that plays or searches YouTube videos (playing and previewing songs, searching, Add a song) stays closed until you reach it, and so do rooms, quick play, Ranked, events, friends and challenges, which are built on YouTube's songs.
To know which age applies, the app asks our server when it starts, and at most every 10 minutes when you come back to it, never while you are offline. It asks only for players aged 13, 14 or 15 (players of 16 or over need no check), except in a version of the app that includes the Originals, where the question goes with the app's usual check of its offline settings, for every player. Our server reads your country from your internet address for that answer only, and sends back YouTube's minimum age there and the age from which usage data can be on there, never the country itself. Your country is never kept in our database or on your phone: the app keeps only the minimum ages that apply where you are, though in a few countries those ages belong to that country alone. Until our server has answered, or if it cannot tell your country, YourBeats uses 16 for both.
13 to 17. Players under 18 start with safer settings: their profile is visible to friends only, their name is hidden on song records (and so in Ranked), only friends can invite them to rooms or challenge them, and only friends can race their saved runs as ghosts. Their handle, avatar and level can still be looked up by handle. Typed chat in rooms is never available to or from players under 18, they can be added as a friend only with their friend code, and share cards, our web pages and a song's credit for a suggested chart never name them.
Age not known yet. Until a player answers the age question, we use the settings for players under 18. The one exception is a name that was already shown on song records before the age question was introduced: it stays shown.
Links marked "Ad". Links to music services marked "Ad" are only ever shown to players who have told YourBeats they are 18 or over: never to players under 18, or whose age is not known.
Adverts. YourBeats' adverts from Google AdMob are never personalised, for anyone (section 2.15). The adverts at breaks are shown only to players who have told YourBeats they are 13 or over, and never to players younger than YouTube's minimum age where they live, or younger than 15 in Denmark, or whose age is not known. For players under 18, YourBeats asks Google to apply its protections for teenagers, and its protections for children for players younger than YouTube's minimum age where they live, or younger than 15 in Denmark, or whose age is not known; the ad song is never offered to players under 13 or younger than YouTube's minimum age for their country, who cannot add songs.
10. Security
- Everything between the app and our server travels encrypted (HTTPS).
- On our server, sign-in codes, sign-in keys, guest secrets (and the keys of phones a guest account was brought back to) and codes for carrying on at a computer are stored only in scrambled (hashed) form, and Play Games and Google account IDs only in a form scrambled with a secret key of our own. On your phone, your sign-in is kept in the app's private storage.
- Only the few people who run YourBeats, and the systems we run for it, can reach account information: the people through a password-protected admin panel, whose changes are logged; the systems with a secret key that only they hold.
- No system is perfectly secure. If something goes wrong that puts your information at risk, we will tell you, and the regulator, as the law requires.
11. Information that leaves the UK
Our database is kept in Cloudflare's Western Europe region. Most of the companies in section 5 are based in the United States and run services around the world, so your information may also be handled outside the UK and the European Economic Area. Where that happens, it is protected by the safeguards the law requires, such as the UK's data bridge with the United States and the EU-US Data Privacy Framework, for companies certified under them, or the standard contractual clauses (with the UK's addendum) in those companies' data processing terms. Write to us for a copy of these safeguards.
12. Changes to this policy
When we change this policy, we change the date at the top. If a change matters to you, we tell you in the app before it applies, and ask you to agree again.
13. Contact us
Unbelievable Media LTD, 29 Riverside Walk, Wickford, England, SS12 0DU
Email: support@yourbeats.net
Our contact page lists every way to reach us and to report a problem.