Privacy
Privacy
What's new: we now count totals, never who, of the gear, DJ software, genres and social sites our DJs pick, and when sets are played, to help choose where we advertise. More under Who sees what.
From 19 October 2026, Cadence Highway Ltd runs DJ back 2 back and decides how your data is used, in place of Mat, trading as Cadence Highway. Nothing about what we collect or how we use it has changed.
Who we are
DJ back 2 back (djback2back.com, and the DJ back 2 back app) is run by Cadence Highway Ltd, a company registered in England and Wales (company number 17528189). Registered office and trading address: The Old Cock, 41 London Road, Chatteris, PE16 6AS, United Kingdom. The company decides how your data is used, so it is the "controller".
Cadence Highway Ltd is registered with the Information Commissioner's Office (ICO), registration number ZC284527.
Contact: support@djback2back.com, or our privacy request form.
The short version
- We keep what we need to run your account, link you up with other DJs and keep the service safe. We don't record your sets on our servers. The app records a set on your own computer only when you both switch on Recording, with both of you in the file, and it stays there until you delete it.
- We don't sell or share your data, show ads or track you across other sites.
- DJ back 2 back is for people 18 or over.
- You can download your data, correct it, or delete your account, any time.
What we keep, why, and for how long
Each record is deleted at our daily clean-up once its time is up, so it can stay up to a day longer.
Your account
- What: your email, your DJ name, when you signed up and whether that was during the beta, that you confirmed you're 18 or over, and when, and whether you've ticked Hide my internet address. We never keep a date of birth. We don't keep your password: Clerk, which runs our log-in, keeps it. We keep the ID Clerk gives you, to link your account to it.
- We also keep which Terms you agreed to when you signed up, and when.
- Your country: to match you with DJs nearby (closer means less delay) and to count where our DJs are. It's also on our public map of where DJs play, as counts only, never who: a country shows once 3 or more of its DJs have played sets, and a line between two countries once they've played 3 or more sets together. You can change it on your account page.
- Whether you play vinyl, if you tick it on your account page. While you're on Live, logged-in DJs see you under DJs who play vinyl, and we suggest you to other DJs who play vinyl. It goes when you untick it or delete your account.
- When we sent your welcome email for the beta, so we send it only once.
- When we sent you the reminder to get the app on your computer, so we send it only once.
- If you signed up from Australia in our beta, we keep that you did, and when.
- If the beta was full when you signed up, we keep when you joined the waiting list, until your place opens. Your number on the list is worked out from that, never kept.
- Free months we give you for helping in the beta: how many, who gave them and when, kept with your account so you get them when subscriptions start. They go when you delete your account.
- A bio or kit list you added in an earlier version of the site stays in Download my data until you delete your account. It isn't shown to anyone. Your bio today is under Your socials and bio.
- If you save it to your account (on the download page, or by finishing the app's setup), or the app detects it: the gear, model and DJ software you picked under Set up your audio, on the download page, or that the app detects. It isn't shown on your public page. Your profile shows only its type, as the setup page's heading says it (such as "A USB controller"), never the model or your software. The Sessions list and your matches show only whether shared waveforms are available with your software. We keep it to show your setup and whether shared waveforms work with your software, and, in the beta, to ask DJs on gear we haven't checked to confirm its settings. It goes when you clear it or delete your account.
- Logins: each login is a random token, kept only as a hash, with when it was made and a short name for the device or browser it's on, such as "Chrome on Mac", from what your browser or our app says it is, never all of it. Your account page lists them, with Log out on each. With each login we also keep when you last signed in at Clerk, as deleting your account needs a sign-in in the last 10 minutes; for our team, also when they last gave their authenticator code. When the app logs you in through your browser, the one-use code that passes your login to the app is kept only as a hash, and works once, within 60 seconds.
- The devices you log in on: each device or browser you log in on keeps a random id, in a cookie on the web and in our app's own settings. We keep it only as a hash, with the device's short name, when you first logged in on it and when you last used it. When you log in on one we don't know, we email you its name and the time, so you can change your password if it wasn't you. We also keep that your account has logged in before, for as long as the account exists, so a log-in after every device has been forgotten still emails you.
- A card or computer on more than one account: for each account, we keep a scrambled copy of Stripe's code for the payment card it uses, never its details, and the code for each computer the app logs in on. We keep them while your account exists, and for 24 months after we close an account for breaking our rules. Only our admins see them, as a flag when the same card or computer is on another account. We never show you the other account, and the codes go to no one else.
- If you show you're 18 or over, we keep how you did it and the date. We never keep your date of birth, your ID, your selfie or your card details.
- The ID check is run by Stripe, on Stripe's own page: you give your ID and a selfie to Stripe, not to us. Stripe tells us your date of birth so we can see you're 18 or over. We don't keep it, and we then ask Stripe to delete your ID, your selfie and what it read, whether the check passed or not. Stripe can take up to four days to delete them. A check you start and don't finish is deleted at Stripe after 48 hours, or as soon as Stripe allows after that if it's still checking it. From us, Stripe gets only the ID Clerk gives you, so the check can be matched to your account. A check you start while signing up from Australia gets nothing from us.
- The credit card check is run by Stripe, on Stripe's own page: you give your card and your email to Stripe, not to us. Nothing is charged. Stripe tells us whether it's a credit card and whether your bank confirmed it's yours; we keep only that you passed, the date, and a scrambled copy of Stripe's code for the card, never its details. Stripe keeps its own record of the check. Stripe's reply also includes other details of the card and the email typed on its page; we read only whether it's a credit card, the bank's answer and Stripe's code for the card. From us, Stripe gets only the ID Clerk gives you, so the check can be matched to your account. A check you start while signing up from Australia gets nothing from us.
- You can turn free-text off at any time on your account page. Download my data shows how and when you showed you're 18 or over, and whether free-text is on. Deleting your account clears them.
- Why: to give you the account you signed up for, and to tell you when someone logs in to it.
- How long: while you have the account. If you don't confirm your email within 14 days of signing up, the account is deleted. A login lasts 30 days from when you last used it. A device is remembered for 400 days after you last use it. The app's one-use code goes at our daily clean-up once it's a day old.
Account emails
- What: when we send you one (a new log-in on a device you haven't used before, a "this email can't sign up yet", a welcome to the beta, your place in the beta opening, a genre you asked for being approved, or a security notice), we keep the kind and the time.
- Why: so it's at most 1 a minute and 5 a day of each kind.
- How long: a day. A record of a security notice, kept with our breach log, stays 3 years.
- What: for a service email, which one we sent you and when, kept against your account number only.
- Why: to show we told you.
- How long: 24 months, or until you delete your account.
- What: if you reply 'stop' to a new-version email or to the email with the link to download the app, when you did.
- Why: so we don't send you either of those emails again.
- How long: until you delete your account.
Changes our team makes to your account
- What: when we change your DJ name or page address, turn beta access or our monthly email on or off, add or take away sessions, clear your biography or socials, confirm your email for you, close your account, or send you a security notice, we keep who did it, what was done and when, never your old email. A new DJ name or page address also keeps the old one and the new one. We also keep when our team opened your account, and each search that found it, by your DJ number only.
- Why: so we can show what we did, and who did it.
- How long: 24 months. If you delete your account, the old and new names and addresses go at once, and the rest stays for its 24 months. If we close it, all of it stays with our decision for those 24 months. Sessions we add or take away are also kept with your purchase records, for as long as tax law requires.
Notes our team writes about you
- What: notes our team writes about your account, such as what we checked when you asked for help, with who wrote each and when. You see each note and when it was written in Download my data.
- Why: so whoever helps you next knows what's been done.
- How long: 24 months. Deleted with your account, unless we closed it; then they're kept with our decision until the 24 months end.
The monthly update, if you ask for it
- What: when you agreed, how (the sign-up box or your account page), the words you agreed to, and when you stopped.
- Why: to show you asked for it.
- How long: while you get it, and 24 months after you stop. Deleting your account deletes it at once.
Booking alerts for your genres, if you turn them on
- What: whether they're on, your time zone when you turned them on, so the emails show your time, and the code in the link that stops them.
- Why: to send you the alerts you asked for.
- How long: until you delete your account. The code stays after you turn them off, so the link in an old email still works.
Your library, if you add it
- What: artist names (up to 200), genre shares, and which DJ software they came from, plus when you agreed to send them. We also keep the time of each send for a week, because you can send your library at most 5 times a week. Never your track list or files. The library reader asks before it reads your library and again before it sends.
- Why: to match you with DJs who play what you play, because you chose to add it.
- How long: until you add a new one, remove it with Remove my library on your account page, or delete your account.
Your genres and public page
- What: up to 7 genres you pick, who sees your profile (Public, Friends only or Private), your public page's address, and your live link if you add one (a Mixcloud Live or Twitch channel).
- Matching: we use the genres you pick to match you with other DJs on Sessions. You can turn matching off on Your account.
- A genre you ask for: if you use Request a genre, we keep the name, when you asked and that it was you, until our team decides. Only our team sees who asked. If we add it, it goes on the list for everyone and is no longer linked to you, and we email you to say so; if not, it's deleted.
- Your profile shows your DJ name, your experience, the genres you pick, your gear's type, a verified Mixcloud link and your live link if you add one. It's Friends only until you change it on your account page: only your friends see it, logged in. With Public, every logged-in DJ sees it, and anyone can see your public page: your DJ name, genres, your experience, a verified Mixcloud link, your live link if you add one, and the sets you list. Search engines are asked not to list it. With Private, no other DJ sees your profile, and there's no public page.
- Why: matching is part of the service you signed up for. Your profile and public page are shown to the people you choose.
- How long: until you change it or delete your account. An address you leave is kept only as a one-way code, so it's never given to anyone else.
Your socials and bio
- What: the links to your own pages you add on Your account (Instagram, SoundCloud, Mixcloud, YouTube, Twitch and a website), and your bio, up to 500 characters, if you write one.
- Who sees them: your socials are on your profile, and on your public page if your profile is Public. Your bio is on your profile only, for the logged-in DJs who can see it, never on your public page. Our team can also see your bio and socials, whatever your setting, to check them against our rules and to help you when you ask. Each look is recorded.
- Checks: each link must be the address of your own page on its site, and a bio can't have a link or an email address in it. You can write a bio once you've shown you're 18 or over. Anyone who reads it can report it, and the report keeps the bio as it was then (see Reports and safety).
- Why: you chose to add them.
- How long: until you change or remove them, or delete your account.
Your sessions
- What: the sessions you make or join, when, with whom and how long they ran, the invites you send and answer, the share links you make, and who can invite you.
- Why: to link you up and run the session.
- While you're in a live session, we note which one, so you can't be in two at once; it goes when you leave.
- If you post a booking or offer to join one, we keep its time, length and genre, who offered, whether the set was played to its full length, and your time zone, so its emails show your time. We keep them for 24 months, as we keep your sessions.
- How long:
- 24 months;
- a session nobody started, a day;
- a share link, 24 hours.
- A session two DJs shared through an invite or a share link but never started is kept for 24 months, like any other session.
- A session's own working data is deleted when it ends.
- Beta feedback: after some beta sessions the app asks how it went. If you answer, we keep any ratings, what you write ("How did your set go?" and "Any issues, or ideas to improve the app or website?"), the app's version and your computer's system for 24 months, without your account unless you tick "You can email me about this" or "You can quote this" (see Quotes below). We keep which sessions you've answered with your account, also for 24 months, so we don't ask twice, and so we can give free months to the DJs who help the most. Tick 'email me' and we keep your account with your answer, so we can reply, for up to 90 days. An answer with something written or a Poor rating may be read, with the app's version and your computer's system, by the AI tools, run by Anthropic, that read our problem reports.
- Quotes: if you tick "You can quote this" after a set, we keep what you wrote with your account and may quote it on our website and social media, because you agreed: with your DJ name only if you also ticked "Use my DJ name with it". Ask us to stop at any time: we take it down and delete it. We keep it with your account for 24 months, or until you ask us to stop or delete your account.
- Recording and going live: as proof that both DJs agreed, we keep a record of when you agreed to record or go live, turned it off, asked to turn it back on, or answered yes or no. It's kept with the session for 24 months, even if you delete your account (it then shows as "Deleted DJ").
- During the beta we keep a timeline of each set, to see where DJs get stuck or wait: when each of you joined and pressed READY, your app's version and computer type, whether you were linked direct or through our relay and how long sound took between your apps, each drop and reconnect, each handover, and who ended the set and how. Your app adds how long you spent on each screen before READY, its test handovers, when you opened Settings and Mini view, whether sound was playing on each side and whose turn it was, never the sound itself, the kind of DJ gear and software your app found (only models we know; anything else just as Bluetooth, USB or built-in), and the codes of any errors it hit. Never your sound, your tracks' names or anything you type. We keep it for 90 days.
- How sessions are used: for each session, whether the link went through our relay or directly (only that, never your internet address), whether you both agreed to record or go live, how it ended (Leave, a lost connection, time up, or another way) and how long you were linked. We look at them only as totals, never by DJ, to plan fair pricing. They're kept with the session for 24 months, even if you delete your account (then without your name or email).
Your friends
- What: who you're friends with and since when, the friend requests you send and get, and a note on each friend if you write one. Only you and our team see your notes; your friends see that you're friends, never your note.
- On their Friends page, your friends see whether you're looking for a session or in a set. With Who can invite you set to Nobody, they don't see you looking for a session.
- Why: so you can find and invite each other quickly.
- How long: until you remove the friend or delete your account; a request, 30 days.
- When you first open Friends, we make your invite link and keep its code until you make a new one or delete your account.
- We also count how many people join through your link, as a number only.
- If you join or log in from a friend's invite link, we keep who invited you until you answer, or for 30 days.
Practice partner
- What: when you started and ended each practice with the Practice partner in the app, and the relay's names for it.
- Who sees it: you, in Download my data, and our team, when we open your account.
- Why: for the practice time limits, and so ending a practice early also closes its relay.
- How long: 2 days, or until you delete your account.
Your experience
- What: the experience you pick, who you'd play with, and when you set it. After a session of 10 minutes or more, your private answer about the other DJ: whether you'd b2b with them again, and when.
- Who sees it: no other DJ sees your answers, and our team can when we open your account; a "no" only stops the Sessions list suggesting the two of you to each other. The Sessions list matches you on the experience you pick. Other DJs on Sessions, and anyone on your public page if your profile is Public, see one line: your experience, how many sessions you've played and with how many different DJs.
- How long: your answers, 12 months. A "no" to b2b again keeps the two of you from being suggested to each other until either account is deleted. Your experience, until you change it or delete your account.
- Download my data has your experience, your own answers and your "no"s in full, and how many DJs said no to b2b again with you, as a count only, once 5 or more different DJs have answered about you, so it never shows who said it.
Sessions
- What: while you're switched on: when you switched on and when you were last active. The DJs you block, and the DJs you mute.
- Your live link: if you've added one, logged-in DJs see it beside your name while you're switched on.
- Why: to show you to DJs who want a b2b now, because you switched it on; and blocks, to keep you safe: a block hides you from each other on Sessions, in invites, friends, matches and Mixes, apart from sets you played together; and mutes, so their invites and friend requests don't reach you; the DJ you mute is never told.
- How long: until you switch off, start a session, log out or go quiet for 10 minutes. Blocks last until either account is deleted. Mutes last until you unmute or either account is deleted. When you're on Sessions, we keep that you were there for an hour, so a DJ who saw you can still block, mute or report you.
The app and your session page
- What: while the app is open and you're logged in, it sends us what your session page shows: the app's version and whether it's on a Mac or Windows; the sound outputs it lists, by name, and the ones and channels you've chosen; only the name of what you chose as your mix; your session code, your partner's DJ name and how the session's going; the app's latest status lines; and whether "Accept handovers automatically" is on.
- Why: so you can see and run the app from your session page. From the page you can join, hand over, accept and leave, and change your partner's output, your headphones, the partner level and "Accept handovers automatically". You can't change your mix there: it's chosen in the app. The app's window says when your session page joined or changed something.
- Who sees it: only you, on your session page while you're logged in.
- How long: only while the app is connected. It's deleted when the app disconnects, and at once if your account is suspended, closed or deleted. We keep no record of what you do from the page: the limit of 30 commands a minute is only a count while the page is in use.
Mixcloud and Mixes
- What: the Mixcloud username you link and when, the one-time code for your Mixcloud bio, and when it was checked. The sets you list: the show's address, its genre and date, the two DJs and who added it.
- Who sees it: anyone can see the sets on Mixes. To visitors who aren't logged in, a DJ is named only if their public page is on, and shows as "another DJ" otherwise; logged-in DJs see both names. On Mixes, a set by a DJ whose public page is off shows them as "another DJ", but its Listen on Mixcloud link still goes to their show on Mixcloud, where their Mixcloud username shows.
- How we check: our server looks up your public Mixcloud shows by the username you give. It doesn't send Mixcloud anything about you.
- Why: to show your b2b sets, because you chose to.
- How long: until you unlink, delete a set, or delete your account. A set hidden after a copyright complaint stays hidden until its 6 months are up, even if you delete it, so it can't go back on Mixes meanwhile. A username you never verify goes, with its bio code, after 7 days.
- Likes: which sets you like, and when. Anyone can see how many likes a set has; no other DJ or visitor sees who liked it; our team can when we open your account. Likes from a suspended or closed account don't count. We keep a like until you unlike the set, the set is deleted, or you delete your account. Your likes are in Download my data.
- Listen presses: when anyone presses Listen on a set, we add one to that set's total for the day. We never record who pressed, so it isn't in Download my data. We use the totals only to break ties in the Top 10. Each day's total is kept 13 months, and goes sooner if the set is deleted.
Claiming a name and the verified tick
- What: the name you claim, the one-time code, the links you give, what our checks found at each, the claim's status and times, and the date your account was verified.
- Why: so a reserved name goes to the DJ who uses it, and the tick only to real DJs.
- How we check: our server reads the public page at each link you give (Mixcloud, SoundCloud, Bandcamp, YouTube, Twitch or your website) for your code, a few times over about 3 hours and again each time you press Check now, and keeps only whether it was there and, for Mixcloud, the account's display name and how many sets it has. A person checks the rest by eye. We compare your confirmed email's domain with the official website on our list.
- Who sees it: you and our team. The tick is public, next to your name.
- How long: an approved claim and the tick stay with your account until you delete it. The tick comes off if you change your DJ name. A claim that's refused, taken back or never approved is deleted after 12 months.
- The reserved list: public DJ names and their official websites, from public lists and Wikidata; refreshed each October.
The message boards
- What: what you posted and replied before the boards closed, the posts you reported, and a posting ban if we set one.
- Who sees it: no other DJ. The boards have closed, and nothing on them is shown. Our team can see your own posts when we open your account.
- Why: to deal with any complaint or claim about what was posted.
- How long: until 2 October 2027, when it's deleted. A post a court case is about is kept until the case ends. If you delete your account before then, your posts become "[removed]" straight away. To have a post removed sooner, email support@djback2back.com.
Reports and safety
- What:
- reports about a DJ, a public page, a set, your place on the Sessions list or a bio: who reported, the reason, any details and when, and a bio's words as they were;
- if you report while logged out, the email you give, so we can reply;
- if we take a page down or suspend an account, the reason and when;
- while a suspension is active, a one-way fingerprint (a hash) of the account's email, so the same email can't sign up again.
- Why: to keep DJ back 2 back safe and meet the law on online safety.
- How long:
- a report, 12 months after we've dealt with it;
- a logged-out reporter's email, 90 days after;
- a page-down or suspension, 24 months after it's lifted;
- the fingerprint, until the suspension is lifted.
If you report your partner from the chat, your app sends us the chat's recent messages, yours and theirs, with your report, so we can look at them. They're kept with the report, until 12 months after we've dealt with it.
If we close an account, it can't log in and nothing of it is shown. Unless an appeal succeeds, we delete it 6 months later as if its owner had deleted it; an account that appears to belong to someone under 18 is deleted at once. Either way we keep only the record of our decision: what we did and why, and the statement we sent, for 24 months, and any copyright strikes, for 12 months after they stop counting. Reports about it stay for their 12 months, as after any deletion. We also keep a one-way fingerprint (a hash) of its email for 24 months after the close, so the same email can't sign up again. It's deleted sooner if an appeal succeeds.
Copyright notices and counter-notices
- What:
- a copyright notice: the name, email and postal address of the person who sends it, the work, their right in it, what they say infringes it and where, and when;
- a counter-notice: the DJ's name, postal address and phone number, what was taken down and where, their statement, their agreement that a court can hear the case and their signature.
- Who gets it: we pass a notice to the DJ it's about, and a counter-notice to the person who complained, as the law requires. Nobody else.
- Why: copyright law has us take these notices, pass them on and keep them for a time (US 17 USC 512 and Canada's Copyright Act).
- How long:
- a notice, 6 months after we receive it;
- a counter-notice, 6 months after what was taken down is put back or deleted, and longer while a court action about it is open;
- the complainant's email, kept with our record of the takedown, 12 months after what was taken down is put back or deleted.
Requests about your data
- What: what you ask for, what you write, the email we reply to, and when.
- Why: to answer you, and to show we did.
- How long: 24 months, even if you delete your account.
Problem reports
- What: what you tell us went wrong and where, the error code when you came from an error message, the device, system and app version you give, your gear as you leave it in Your gear and whether you ticked that it's what you were using when it happened, any app log you attach, and your email if you give it. Your gear is filled in from your account's Set up your audio and from what the app found (your DJ software, and any CDJ players), and you can change it first. Logged in, your account's email is filled in for you: clear it if you don't want a reply. The app's log holds what the app did: your DJ name, your audio devices, which apps were playing sound, the connection, and any errors. It never has your partner's name. A report isn't linked to your account, and your internet address isn't kept with it.
- Who sees it: Mat, who runs DJ back 2 back for Cadence Highway Ltd, on our admin page. AI tools, run by Anthropic, read problem reports to find the fault. They group the reports, and email Mat a daily digest with a brief for the team, plus a note straight away for a new or serious problem, instead of a copy of each report. For that, what you wrote, with any email address, phone number or internet address in it taken out, where it happened, the device, system and app version you gave, your gear and whether you ticked it, whether you were logged in when you sent it, and the error code go to Anthropic's API. Your email address and app log don't.
- Why: to find and fix the problem.
- How long: after 90 days we delete your email address and any app log, and take any email address, phone number or internet address out of what you wrote. The rest is kept for 12 months, no longer linked to you, then deleted. Our support system keeps its own copy for 90 days: the same report with any email address, phone number or internet address taken out, and without your email address or app log. Anthropic deletes what it read within 30 days, unless its safety systems flag it or the law requires it to keep it longer, and doesn't use it to train its models. The digests are kept in the team mailbox, which Apple's iCloud Mail holds for us, and deleted within 12 months, as are the reports emailed to Mat before this change.
- When an error message shows, the site sends us its code, the page and what went wrong in our script, never your name, email or account, and we keep it for 90 days.
- During the beta the app sends us each error it hits by itself: its code, where in the app it happened and the app's version. Never your sound, your tracks' names, anything you type, your name, email or account. We keep it for 90 days.
Tries we limit
- What: your internet address (an IPv6 one by its /64 block) each time you do something we limit: sign-up, log-in, on the site or for the app, confirming you're 18 or over, deleting your account, logging out a login or every login, making, checking, joining or sharing a session, invites, posting or cancelling a booking, offering to join one, accepting or cancelling an offer, the relay, matching on Sessions, adding or removing your library, editing your DJ name, claiming a DJ name or the verified tick, pressing Check now on a claim, setting your experience, saving Set up your audio or the app telling us what it found, blocking or unblocking a DJ, muting or unmuting a DJ, asking a DJ to be friends, answering a friend request, removing a friend or writing a note on one, switching I'm looking for a session on or off, staying on it and opening its live updates, turning your public page on or off, its genres and their matching, the app checking for your sessions, the app linking to your session page, the app telling us it opened for the first time, answering the questions after a session, reports, listing or deleting a set, linking or unlinking Mixcloud, liking a set, changing your live link, switching our updates emails on or off, pressing Listen on a set, Download my data, requests about your data, asking a question on the Support page, reporting a problem, sending an error report, telling us a sign-up or log-in step didn't go through, reading Sessions or the Mixes Top 10 logged in, and reading Sessions, Mixes or a DJ's page logged out. Sign-up and a logged-out request about your data also keep the email given. The others, done logged in, keep your account.
- When you sign up, link up or list a set, list a set or pay, we check which country your internet address is in, to see whether we're open there. We don't keep it.
- Why: to stop guessing and abuse.
- How long: an hour, except an age check you start, and the questions you ask and the chats you send to our team on the Support page, which count until the end of the day (UTC) and are deleted the next morning: by your account, or, for an age check when signing up from Australia, by your internet address. A refused try is counted by its kind only, with no address, for a week.
Our marketing links
- What: when you arrive by one of our marketing links, we count that a visit (and a sign-up, if you sign up) came from that link: a number per day, with nothing about you.
- How long: we keep the counts, as they say nothing about anyone.
App downloads
- When you download the app, we count that a download started, for Mac or for Windows: a number per day, with nothing about you.
- The first time the app opens on a computer, it tells us once: Mac or Windows, and the app's version. No account, name or email goes with it, and your internet address isn't kept with it. We use the totals to see how many people get from downloading to logging in.
- How long: we keep the counts, as they say nothing about anyone.
Sign-up and log-in problems
- What: when a step on our sign-up or log-in page doesn't go through (a wrong code, too many tries, a new code we couldn't send), we count which kind of problem it was: a number per day, with nothing about you.
- How long: we keep the counts, as they say nothing about anyone.
Club or Modern
- When you switch between Club and Modern, we add one to a count for that look and day. Nothing about you or your device is kept with it.
- How long: we keep the counts, as they say nothing about anyone.
Why you left, if you tell us
- What: when you delete your account, you can tick why you're leaving and add a note. We keep your answer apart from your account, which keeps no name or email once deleted. We keep it with the month only, and with no name, email or account number. Answers are shown to our team only in groups of 3 or more.
- How long: the ticks with no end date, and a note for up to 24 months.
Support emails
An email to support@djback2back.com or setup@djback2back.com goes first to our AI assistant, then to Mat, who runs DJ back 2 back for Cadence Highway Ltd. Nobody else reads it.
- Checked first: mail that fails DMARC, or fails SPF with no DKIM pass, is dropped and not read further.
- Answered only when we can check the sender: the receiving checks are there, your address has no unusual characters, the address that delivered the mail is the From address, and DMARC passes (or, for a domain with no DMARC record, SPF or DKIM passes for your own domain). Anything else, and automatic mail (auto-replies, mailing lists, bulk mail, bounces, no-reply senders and mail that asks for no automatic replies), gets no reply and isn't read by the AI; Mat gets it, up to the limits below.
- Not read by the AI either: a reply in a thread we've already answered, or more than 5 emails an hour or 20 a day from one sender. Mat gets them, up to the limits below, and no reply goes out.
- Busy hours: if more than 60 support emails arrive in an hour, or more than 300 in a day, from everyone together, the AI doesn't read the rest of that hour (or day). Each gets the reply "Thanks. A person will get back to you." and Mat gets a copy in full, up to 5 an hour and 20 a day from any one sender; beyond that, he gets just the sender's address in an hourly list. Once Mat has had 20 copies in an hour, any more reach him as just the sender's address, except mail only a person can answer, which still reaches him in full within the same limits, up to 100 more an hour; past that it isn't answered, and he gets just its sender's address in the hourly list. Mail that gets no reply (automatic mail, or mail that fails the sender check) has its own limit of 20 an hour.
- Read by a person: a reply to one of our site's own emails (a confirm or reset link, a change to your account, a security notice, a report or a decision about your account). Mat gets it, with "Thanks. A person will get back to you."
- Read by the AI: everything else is sorted by Anthropic's Claude models, which process it for us. For that, your email address, the subject and up to 12,000 characters of the text go to Anthropic's API. Spam gets no reply. Anything that needs a person gets "Thanks. A person will get back to you." A routine question gets a reply the AI writes only from this site's own FAQ, Quick guide, Back to back guide, Copyright & Mixcloud, Error codes and Download pages (and our own setup notes), and the reply says it was written by our AI assistant. A reply goes only to you. One that would link or point anywhere but djb2b.com or djback2back.com, mention passwords or payment details, or talk about money, legal matters or dates, goes to a person instead.
- Why: to answer you quickly, and send everything else to a person.
- What the log keeps: for each email, the time, your address, which of our addresses it came to (support or setup), the email's message ids and our reply's, how it was sorted and routed, the SPF, DKIM and DMARC results and your address's domain, how many AI tokens it used, whether Mat's copy went, and a short problem code (which can include the web address or email address a reply was stopped for). Never the text, the subject, attachments, names, the AI's summary or its reply. Each row is deleted after 30 days, with no other copy.
- What Anthropic keeps: Anthropic deletes it within 30 days, unless its safety systems flag it or the law requires it to keep it longer. It doesn't use your email to train its models.
- Mat's copy: every email, except one dropped by the checks, is copied to Mat's mailbox with the sender, the subject, a two-line summary by the AI, any reply we sent, the text (up to 100,000 characters) and the original email when it's 4 MiB or less. At most 5 an hour and 20 a day from one sender are copied; past that, only the log entry is kept. The copies are kept in the team mailbox, which Apple's iCloud Mail holds for us, and deleted within 12 months.
- Questions on the Support page: when you ask one, we send it, with your last few messages in that chat and our help pages, to Anthropic's API to write the answer. We don't keep what you or it wrote, only how many questions were asked each day and how many were sent to our team. If you send a chat to our team, it's kept as a support email is. Anthropic deletes what it read within 30 days, unless its safety systems flag it or the law requires it to keep it longer, and doesn't use it to train its models.
Payments
- Today: payments are off during the beta, so we take no money and keep no card details.
- When they start: Stripe takes them. We send Stripe your email, your account number and the ID Clerk gives you, and you enter your card on Stripe's own page, so we never see it. We'll keep each purchase record for as long as tax law requires, and Stripe keeps its own record.
The app on your computer
The app keeps your login and its settings (your partner level, the VirtualDJ option, your Handover button key map,
"Accept handovers automatically", whether handover tips show, "Show your partner's waveforms where their equipment allows", "Show the bar counter with waveforms", how a key is written (8A or Am), "Keep on top of your DJ software", for whichever of the app's windows you tick, whether you unticked "Open website at login", which invites you dismissed while they're still open, where you've put each of its windows, your gear and its
model, your speakers, the inputs and outputs you pick for your mix and your partner, by device ID, with their
channel pairs, the fader you learnt for your partner, with your controller's name), and a log of what it did,
including what your
session page asked it to do, one file a day. Each time the app opens, it deletes files more than
7 days old. If you stop using the app, the files stay until you delete its folder. The log never has your partner's name. It
stays on your computer unless you send it to us. On a Mac, the sound switch also keeps DJb2b's sound settings, a copy of yours
from just before each switch so it can put them back, and, while DJb2b's are on, when you switched. The settings
are your sound output and input, by name and device ID, with their sample rate, channel layout and volume. They
stay in the app's folder (~/Library/Application Support/djb2b-app/sound) until you delete them, even
if you delete the app, and they're never sent to us. On Windows, the app only notes that you've read how to set
your sound.
The app also keeps one random id for its install and sends it with each log-in, so we can tell a log-in from a
new device; we keep only its hash. An older app sends none, so each of its log-ins counts as a new device.
If an older version of the app kept a key for this computer, this version deletes it the first time it opens.
The app also notes the DJ software it last found.
During a session, while you're live and the app isn't reading VirtualDJ or
your players, it joins Ableton Link only while your DJ software, or another Ableton Link app, has it on: then
other Ableton Link apps on your computer's networks can see it's there, and your DJ software counts it as one
more. With none on, it waits for one, sending nothing. It only listens: it never sets a tempo of its own, or
starts or stops your music. It sends the DJ you link with your BPM and beat count, and nothing about it is
sent to us.
Once you press Learn, the app reads your controllers' MIDI while it's open, to
learn and follow the fader you pick: it never sends anything to them, and your computer doesn't ask.
With "USB controller" as your gear, while your
partner is playing, the app quiets your DJ software in your room, on this computer only.
If you both switch on Recording, the app records the set on this computer,
both of you joined at each handover, in Music → DJ back 2 back: about 1 GB an hour, in parts of up to 3.9 GB
(about 3¾ hours each), with a note in each part that you both consented and when, and which version of the app
recorded it. It stays there until you delete it, and it's never sent to us. If a recording falls more than a
minute behind, the app keeps some of the sound it's still to write in an encrypted temporary file on this
computer, deleted when the recording is finished or the app quits. While it's recording, the app checks the disk's free space every 30 seconds. If you both switch on Streaming, the
app plays the show at an address on this computer
(http://127.0.0.1:47474/DJBack2Back.wav) for OBS: any app on this computer can play it while it's
on, and nothing outside it can. For all of these, the log has counts and outcomes, never a folder, a file's
name or your controller's name.
What we don't keep
- Your sound goes from your app to the other DJ's when you link up with a friend. When you link up with a DJ who isn't your friend, from Sessions, by an invite or by a share link, when you've ticked Hide my internet address, or when your networks need it, it goes through Cloudflare's relay. A practice always goes through Cloudflare's relay and back to you. We don't record it.
- We don't keep your track list, your files or a date of birth.
Who sees what
- Other DJs see your DJ name.
- On Sessions they also see your genres, if you match on them. They also see your experience, as does anyone on your public page if it's on.
- If you pick Friends only or Nobody under Who can invite you, the DJs it leaves out don't see you on Sessions or in their matches, and their invites never reach you. With Nobody, their friend requests don't either.
- When you link up with a friend, the DJ you link with also gets your internet address, so the two apps can connect directly. When you link up with a DJ who isn't your friend, from Sessions, by an invite or by a share link, the link goes through Cloudflare's relay, so they don't. Tick Hide my internet address on your account page and every link goes through the relay, with friends too.
- If the app can show your track's waveform, the DJ you link with also sees the track you're playing as a waveform, with its beat grid, BPM and key, and where you are in it. Never its title, artist or file name. With Ableton Link, they see your BPM and beat count instead.
- The DJ you link with also gets any quick message you send, and, with waveforms, any mix-in point you set or suggest, and any bar counter you start or ask for. These go from your app to theirs, never through our server. When you confirm your partner is mixed out, or switch on, confirm or ask about Recording and Streaming, it goes to their app both directly and through our session room, which passes it on. For Recording and Streaming, it keeps a record of what changed and when (see Your sessions); for confirming your partner is mixed out, it keeps nothing.
- Free-text chat with your partner goes between your two apps over your link, encrypted. If the link goes through our relay, the relay passes it on without being able to read it. We don't see it or keep it.
- While you've both switched on Recording or Streaming, the DJ you link with also gets a full-quality copy of your sound, a little behind the live sound, for their recording and their show. Their recording has you in it, and it stays on their computer until they delete it.
- Anyone can see your public page, if your profile is Public.
- Mat, who runs DJ back 2 back for Cadence Highway Ltd, sees reports, problem reports, requests about your data, support emails, and the newest sign-ups' DJ names. His usage stats are counts only, never who, with the notes people leave when they delete their account. We count how many DJs pick each gear, DJ software, genre and social site, and when sets are played, as totals only, to choose what to support and where we advertise. In the beta, we also see which DJs use each model of gear, so we can ask them to confirm its settings.
- Our team can open any DJ's account, to help you or to check our rules. That shows everything in Download my data, and we record each time we open it.
Who works for us
- Cloudflare runs the site, the database, the session rooms and the relay, and sends our emails. So it handles everything the site keeps (listed above), your internet address, the emails we send you, and, when a link-up goes through the relay (with a DJ who isn't your friend, from Sessions, by an invite or by a share link, when you've ticked Hide my internet address, or when your networks need it), your session's sound, and the full-quality copy of it for the DJ you link with, as it passes through. A practice always goes through the relay and back, and isn't recorded. Sending a report, a problem report or a request about your data without logging in shows Cloudflare's Turnstile check, which tells a person from a program. Cloudflare gets your internet address and what your browser tells the check; we get only whether you passed, and keep none of it. We count visits to our pages with Cloudflare Web Analytics, which uses no cookie and keeps nothing in your browser: it gets the page, how fast it loaded, the site you came from, your country, and your browser, device type and operating system. Cloudflare also keeps our server's notes on what went wrong, for up to 7 days, so we can fix it. Each note has the web address it happened on, which for a session, an invite or share link, or the link that stops our updates email, includes that link's code. A note can also carry your account's ID, never your email, internet address or chat.
- Clerk runs our log-in and sign-up, on our site and for the app. Your password goes from your browser to Clerk, never to our server. Clerk keeps your email, your password, any Google, Apple or Facebook log-in you link, and when you sign in, with each browser's name and device type, its internet address, and the town and country that address is in. It emails you a code to confirm your email when you sign up, to set a new password, and the first time you log in with your password on a browser it doesn't know. If a sign-up looks automated, Clerk first shows Cloudflare's Turnstile check. When you log in, Clerk tells us who you are: your email, your account number with us, and when you last signed in. Download my data asks Clerk for its record of you each time, and we keep none of it. Deleting your account deletes it at Clerk too. Our team's own accounts also need a code from an authenticator app, and Clerk keeps the secret those codes are made from. Clerk works under its data processing terms, which are part of its service terms with us.
- Anthropic reads support emails and problem reports for us (see Support emails and Problem reports). It works under its data processing agreement with us.
- Stripe will take payments, when they start. It will get your email, your account number, the ID Clerk gives you and the card you enter on its page. It also runs our ID check, on its own page: it gets your ID and a selfie, and from us only the ID Clerk gives you. It also runs our credit card check, on its own page: it gets your card and email, and from us only the ID Clerk gives you.
- Apple holds the team mailbox for us (iCloud Mail): the copies of support emails, the problem-report digests, and email forwarded from support@ and hello@. They're deleted within 12 months.
- Postmark sends the monthly update for us. It gets the email address of each DJ who asked for it, and nothing else.
Cloudflare and Stripe work under their data processing terms with us.
We don't sell or share your personal information, show ads or track you across other sites. So "Do Not Track" and Global Privacy Control have nothing to switch off.
Where your data goes
- Cloudflare and Stripe are US companies, and Cloudflare's network is worldwide. Apple, which holds the team mailbox, is a US company too.
- Clerk is a US company, and it and the companies it uses can process your data wherever they work. When your data leaves the UK for Clerk, it's protected by the UK Extension to the EU-US Data Privacy Framework, which Clerk is certified under.
- Postmark is a US company.
- Anthropic may process support emails and problem reports in the US, Europe, Asia or Australia, and stores them in the US. When your data leaves the UK for Anthropic, it's protected by the EU's standard contractual clauses with the UK's addendum, in its data processing agreement.
- When your data leaves the UK for Cloudflare or Stripe, it's protected by the safeguards in their data processing terms.
How we use your data, and on what basis
- To run your account, sessions and set listings, to email you about the service, and to match you on the genres you pick: because it's the service you signed up for (contract). You can turn matching off on Your account.
- Your library, your public page, your socials and bio, whether you're looking for a session, Mixcloud, booking alerts for your genres and the monthly update: because you chose to turn them on (consent). You can turn each off any time.
- Limits, blocks, reports, bans, support emails, the record of service emails we sent, and security: to keep DJ back 2 back safe and working (legitimate interests).
- Payment records, safety duties, and answering requests about your data: because the law requires it (legal obligation).
- No automated decisions with legal or similar effects are made about you.
Your rights
- Get a copy: use Download my data on your account page for everything tied to your account, in one file. Or ask us.
- The support log (which of your emails, when, and how each was handled; never the email itself) is kept apart from your account, so it isn't in Download my data. Ask for it with the request form and we send it.
- Correct it: change your email, genres, socials and bio on your account page.
- Delete it: delete your account on your account page. To remove only your library, use Remove my library on your account page.
- Change your mind: set your profile to Private, or switch off I'm looking for a session or matching on your genres, any time.
- Object, or ask us to pause using your data: ask us.
- How to ask: use our privacy request form. Mat reads each one and replies by email, within one month.
- Complain: to us, the same way. Or to the Information Commissioner's Office (ico.org.uk). If you live in the EU or EEA, you can also complain to the data protection authority where you live.
When you delete your account, we remove:
- your email, DJ name, logins and the devices you log in on, and any bio or kit you added before;
- your record at Clerk, with your password and any Google, Apple or Facebook log-in you linked;
- your library, the genres you picked and any you asked for that our team hasn't decided yet, who can invite you, whether you ticked Hide my internet address, your invites and share links;
- your Mixcloud link and your live link, your socials and your bio, the likes you gave, and every set you added to Mixes and any whose show is on your own Mixcloud account, with their likes and Listen totals (a set a court case is about stays until the case ends, and one hidden after a copyright complaint stays hidden until its 6 months are up, so it can't go back on Mixes meanwhile);
- whether you're looking for a session and the blocks and mutes you made or that name you;
- your friends, your notes on them and your friend requests;
- your practice times;
- your board ban, the record of account emails we sent you (a security notice's record stays 3 years), and your rate-limit counts;
- your name claims and your verified tick;
- your experience, the answers you gave after sessions and the answers about you, and any "no" to b2b again, yours or another DJ's about you.
What happens to the rest:
- Your board posts and topic titles become "[removed]", except the title of a topic a court case is about, which is kept until the case ends. Any words you added to a board report are deleted; the report keeps its reason, which is a category, and when you made it.
- Reports you made stay for their 12 months, without your name or email.
- A report about your bio keeps the bio's words for 12 months after we've dealt with it, as every report does, even if you delete your account first.
- Your public page goes, and its address is retired.
- Your past sessions and purchases stay, under "Deleted DJ" with no email, and so do the records of when you agreed to record or go live, and a set your partner put on their own Mixcloud, unless you added it to Mixes.
- With them stay when you signed up and whether it was during the beta, when you confirmed you're 18 or over, and which Terms you agreed to and when.
- A request you sent us about your data stays for its 24 months.
- What our team did to your account stays for its 24 months, never your old email.
- An answer to Why are you leaving?, if you give one, stays apart from your account: see Why you left.
Age
DJ back 2 back is for people 18 or over. You confirm it when you sign up. We keep only that you did, and when. We close an account we learn belongs to someone under 18.
Cookies
We use two cookies of our own: one for your login, and one that tells us a log-in is from a device you've used before. Clerk, which runs our log-in, sets its own for it. In your browser's storage we keep up to seven things, each only if you use its button or log in to the app in your browser: that you closed the launch banner, that you paused the motion on our pages, the gear, model and DJ software you last picked on the download page, whether you picked light mode, and whether you picked Modern; if you sign up from Australia, your age check's code, in that tab only, until you've finished; and, if you log in to the app in your browser, the app's one-use log-in link, in that tab only, until Sessions opens it. The details, and how to undo each, are on our Cookies page.
Keeping your data safe
- Logins and one-use codes are kept only as one-way hashes. Your password goes only to Clerk, never to our server.
- Our own cookies can't be read by the page's scripts, and are only sent over a secure connection.
- The current app joins a session, and links to your session page, with a one-use ticket, never your login. The older beta.2 app sends your login in the session's address, over a secure connection, until it's retired.
- If a security problem puts your data at risk, we'll tell you, and the Information Commissioner's Office where the law requires.
Emails we send
We send account emails (a new log-in, security notices) and replies to your emails. Clerk, which runs our log-in, sends its own codes, for signing up, setting a new password and a new browser. Once your email is confirmed, we send you one welcome email about the beta, with a link to our Beta testers page. If you're on the beta's waiting list, we email you once when your place opens, with the welcome in it. If you ask on a phone, we email you the link to download the app. A day after you sign up, if you haven't logged in to the app yet, we email you that link once; reply 'stop' and we won't send you emails like it. We also email every account about the service itself: when a new version of the app is out, before the beta ends, before the transition after it ends, at least 30 days before a change to our Terms that affects you, and at least 30 days before we shut DJ back 2 back down. These are about your account, not marketing, so they come to every account. Reply 'stop' to a new-version email and we won't send you another. If we add a genre you asked for, we email you to say so. When you report something, we email you a receipt and then our decision. If we restrict your account or something you posted, we email you why and how to appeal. If we get a copyright notice about something of yours, we forward it to you, and tell whoever sent it that we did. If you post a booking, we email you each offer for it, and if the DJ you accepted can't make it. If you offer to join one, we email you when it's accepted, cancelled or closes. If you turn on booking alerts for your genres on your account page, we email you when a DJ who plays your genres books a set in one of them. Each has a one-click link to stop them, and you can turn them off on your account page any time.
The monthly update: if you turn it on on your account page, we'll send you one email a month about what's new. We haven't sent one yet. It goes through Postmark, an email service. Every one will have a one-click unsubscribe, and you can stop on your account page any time. We don't send any other marketing emails.
Changes to this page
When we change this page, we change the date at the bottom. If a change matters to how we use your data, we'll say so at the top of this page. If a change matters to how we use your data, we'll email you.
Contact
Email support@djback2back.com, or use our privacy request form. DJ back 2 back is run by Cadence Highway Ltd. Address: The Old Cock, 41 London Road, Chatteris, PE16 6AS, United Kingdom.
Last updated: 21 November 2026