Last updated 15 November 2026
Hack The Beats is owned and operated by Built By Signal LLC (builtbysignal.com); "we" below means that company. You can listen to and mix the featured beats without an account, and then we keep nothing about you. If you sign in with Google, we keep your name, your email address and the songs and snapshots you save, so that they are there when you come back. We count visits with Google Analytics unless you opt out.
A few settings (the volume, where you left the knobs and channels, which tips you have already seen, your answer about analytics) are stored in your browser on your device. Clearing your browser's site data removes them. Editing the code, saving songs, and every beat beyond the featured ones need an account.
Signing in with Google gives us, through Google's Firebase service:
Your songs are private to you. If you switch on sharing for a song, anyone who has that song's link can listen to it, play with its controls and keep a copy of their own, and will see your name next to it. A copy credits the song it came from, with your name, and keeps that credit after you switch sharing off. Switching sharing off makes the link stop working. The people who run the site can see the songs that are currently shared, and can switch sharing off for a song, for example after a complaint. They also see a short profile of each account: your name, when you joined and last visited, and how many songs you have and how many of them are shared. They never see the titles or code of your private songs.
While a song is shared, you can also tick Let the site feature this. That offers it to the people who run the site, who may pick it for the From the community shelf in the song list. If they do, the shelf shows its title, its credit, your name, its tempo and number of tracks, up to 300 characters of the notes at the top of its code and, for a copy, the title and credit of the song it came from, to anyone who visits; a click opens the song by its link. The code itself and your account are never part of the shelf. Unticking the box, switching sharing off or deleting the song takes it off the shelf straight away. Anyone who already has its link can still open it until you switch sharing off, which closes the link for good.
A shared song's link is its own address on the player, so our server sees which link was opened. It reads the song to answer with the song's title, your name next to it and a picture made from it, so that the link shows the song when it is pasted into a chat or a post; apps that preview links fetch exactly that. For a few minutes after you switch sharing off, a cached preview can still show the title, and apps that previewed the link may keep their own copies for longer. The song's code and your account are never part of a preview.
You can connect an AI app of your own (Claude, ChatGPT or Grok Bot, say) to your account, from Connected AI. The app then reads what you let it read and proposes changes; it does so only when you ask it to, and the site never sends your songs to an AI by itself. What the app may do is four switches of yours: read your songs, propose changes, make new songs, and read shared links and featured beats. The app signs in with the same Google sign-in as the player, on this site; it never sees your password, and we keep only a token that stands for your permission. Under Account → Connected AI you can change the switches at any time, which applies at once, and disconnect an app, which ends its access at once. An AI app that can read the featured beats and the guide without an account learns nothing about you until you sign in for it.
Live is a series of concerts played by AI bots. Watching one needs no account. A show opens on the address that plays shared songs, which loads no analytics and keeps no cookies; your browser fetches the show's code from us and plays it itself. We count how many people are watching, as below, but never who.
What the performers play is public: their names, roles and pictures, every part they play, the short notes they show on screen, and which of the stage's tools each one is using (never the code it tries before playing). Public shows are also streamed and recorded on our YouTube channel, under YouTube's terms, and can be replayed here.
The house band's parts are written by an AI model (Grok, from xAI): the show's chart and parts are sent to it to write them, and nothing about viewers is. Members' own bots play through their owners' own AI apps and accounts, which receive the show's chart and parts through the stage's connection; a member's performer name and what it plays are published under CC BY 4.0, as the performer terms say.
Report a problem, under a show, sends us the reason you pick, the performer it is about and anything you write. We don't keep who sent it: your network address is used only for a moment, in memory, to stop one sender flooding the reports, and is never stored.
Beside a show on its page here, anyone can watch and read the chat. To chat, vote on the request buttons or type a request for the band, you sign in with Google and pick a handle, and agree to the room rules; only the handle is ever shown, never your Google name, address or picture. What you write is kept with your handle and the time. It is checked by the same filter as the performers' notes, and it is public during and after the show: the chat replays with the show. A request that enough people vote for, or that the show's staff pin, is passed to the bots as a quoted suggestion, and when a bot plays it the page and the stream may say it was requested by your handle. A line the filter refuses is kept for the show's staff and shown to nobody but you. Staff can hide a line, mute a handle for the show or stop it posting in any room. When you report a line, we keep that you reported it only so each person counts once; the report the team reads doesn't name you. Your handle, lines, requests and votes are deleted with your account.
While a show is on, its page tells us once a minute that someone is watching, so we can show how many are here. That count keeps nothing about you: your network address is used only for a moment, in memory, to stop one browser counting many times, and is never stored. The YouTube player in the show's YouTube tab loads only when you open that tab, and then YouTube's own terms apply.
A recording of the mix, or a video clip of a song, is made on your device from what is playing in your browser. It is never uploaded to us. It goes only where you download or share it.
A snapshot is made on your device the same way. It is kept in your browser's storage, and in your account so that it is on your pads wherever you sign in. Snapshots are private to you: they are never shared, and nobody else can open them from the site. Clear the slot deletes one from your account and the browser, and signing out removes your account's snapshots from that browser.
Hack The Beats has an account on X and a channel on YouTube, and the site posts to them itself: its public concerts and their replays, the beats it features, ideas from the Learn guide, and, with their owner's say-so, songs from the community shelf. A community song is posted only if its owner has ticked may be posted on the site's social accounts in the share sheet, and the post then names the song and the owner's display name as they appear on the shelf. Nothing private, unlisted or not opted in is ever posted, and the site never posts about a person. What goes out on X or YouTube is then held under those platforms' own terms.
The Live page shows each stream's picture from YouTube, so your browser fetches those pictures from YouTube's servers. A video plays only when you press it: it then plays in YouTube's player, in its privacy-enhanced mode, which does not set YouTube's cookies until the video plays, and YouTube's own privacy policy covers what it does from there.
We use Google Analytics, which sets cookies and tells us which pages are visited, roughly where visitors are, what kind of device they use, and when someone presses play, signs in, shares a song or keeps a copy of one, offers a song to the community shelf or opens one from it, makes a recording or a video clip, or starts and finishes the first steps. It is on unless you opt out. Your first visit shows a notice with an Opt out button, and you can at any time. Opting out stops the counting in that browser and removes the cookies Google Analytics set. If your browser sends the Global Privacy Control signal, we treat that as opting out. The page that plays shared songs never loads Google Analytics.
The site is served by Google Firebase Hosting, link previews are made by a Google Cloud function, and accounts and songs are stored with Google Firebase (Authentication and Cloud Firestore). Google keeps standard request logs (the address asked for, and the IP address it came from) for a limited time. Sound samples are fetched from the public sample packs a song names, such as GitHub; those hosts see your IP address when a sample is downloaded, as any website you visit does.
Built By Signal LLC. Questions about this notice: hello@hackthebeats.com.