Raw Kutzz Radio
Privacy Policy
Version 10
13 November 2026
Version history
| Version | What changed |
|---|---|
| Version 10 13 November 2026 | DJs on the Raw Roster can now send us a flyer for their shows (optionally with their application, or later to the station), and the station posts it automatically on our Facebook page and on X on the days they play, with their DJ name and show time. We keep the flyer pictures on our server. See sections 6.1 and 6.2. |
| Version 9 9 November 2026 | The chat now shows a small ball with three dots under a person’s name in the Users list while they are typing a message, so others can see that a reply is coming. Only the people in the same room (or the same private chat) can see it, and only for a few seconds: it is not saved and not logged anywhere, and an admin can switch it off for any room (see 1.2, Who is online). |
| Version 8 8 November 2026 | A DJ can now pay the Raw Roster fee by card in the DJ Area, once the station has switched that on. The card, Google Pay or Apple Pay is taken by Stripe in its own secure box, so we never see or keep the card number. For each card payment we keep Stripe’s payment reference, the months it was for, the amount, the date, whether it went through and the DJ’s name, and the months are then ticked in the Roster fee record automatically. We email a receipt to the address we hold for the DJ (their recovery email, or the address an admin saved with their DJ account). Changes to sections 6.3, 8, 9, 10 and 12.1. |
| Version 7 8 November 2026 | We now keep a month-by-month record of the Raw Roster fee. The fee is still arranged with and collected by the station, not through this website, but the station’s admins now tick off each month a DJ has paid on the website, so we can see who has paid and who is behind. For each month we keep whether it has been paid, the date and amount, how it was paid (for example bank transfer or cash), a short note such as a payment reference and which admin recorded it, together with the month a DJ started and any months their fees were stopped. Only admins can see it and every change is written to the activity log. We do not keep your bank or card details for this. Changes to section 6.3, section 10 and section 12.1. |
| Version 6 8 November 2026 | We now keep the details of our merch suppliers (the businesses that make and post our merch): the business name, the name of our contact there, a work email address, the company address and a phone number, and, for a supplier we pay by bank transfer, the account name, sort code and account number they give us. The account number is stored encrypted, only the people who run the station’s admin can see these details, and every time an account number is shown it is written to the activity log. A supplier we pay through Stripe gives its bank details to Stripe, not to us. Changes to sections 9, 10 and 11. |
| Version 5 7 November 2026 | You can now ask to return an order, or tell us a parcel has not arrived, on your order page or the new Return an order and Where is my order? pages. We keep what you tell us (the reason, anything you write, what is being returned) and how we dealt with it, with the order record. The Where is my order? page only shows an order when the order number and email address you type both match. Change to section 10. |
| Version 4 6 November 2026 | Chat members and artists can now add an optional recovery email so they can reset a forgotten password themselves instead of asking an admin. It is only used for that, and you can remove it at any time. New section 2.12, and changes to the table in section 1, to 2.1 and to section 10. Also 6 November 2026: the station now counts where its listeners are, and how many are new or returning (by country, region and town, as counts only: never an address; the one-way marks used for this are kept for up to 90 days) so the admins can see the audience, and a Studio's error report can say which DJ it came from. Changes to 1.1, to the error reports paragraph and to section 10. |
| Version 3 4 November 2026 | The chat now records where messages were sent from, so that serious problems can be reported to the police or another authority with real information: the IP address, the approximate place and the network name are kept with each message for 90 days (up to a year if the message is reported or its sender is banned). New section 2.11, and changes to 2.1, 2.3, 2.7, 10, 11 and 12.2. |
| Version 2 11 October 2026 | Updated 2 November 2026: new section 2.10 and a line in section 10 for the Bugs and ideas page, where DJs, moderators and admins report a bug or suggest a feature. Updated 1 November 2026: section 1.3 now says that a DJ’s Studio also tells us the name of the DJ software it is reading (for example Serato 3), which only admins see. Updated 30 October 2026: section 6.1 now says that the DJ software you give is also used to set up your Studio program so that it reads your track names from the right software. Now matches the Android app’s Google Play listing: the station, apps and website are for people aged 18 and over (section 13); a plain list of the information the apps collect (section 1.2); how to ask us to delete your account or some of your data (section 12.1); how to report a chat message and what we keep about a report (section 2.7); chat polls, listening streaks and read receipts (section 2.8); how long we keep Contact page messages and copies of emails (section 10); the email addresses of DJs who were set up before the site went live (section 6.2); and the extra phone permissions, notifications at log-in and encryption are described. Updated 11 October 2026: payments by Stripe, including Google Pay and Apple Pay (4.3 and the list of services), and the music categories in the chat’s GIF picker (2.2). Updated 16 October 2026 (later): backups: we keep an encrypted second copy of our database and files on a separate computer, and how long it is kept (sections 10 and 11). Updated 16 October 2026: merch is made up and posted for us by a supplier, so we share your name, delivery address and phone number with them (4.2, 4.4 and the list of services). Section 2.7 (reporting a chat message and what we keep about a report) is back in its place, and the cookies list now includes the supplier sign-in cookie (section 8). New: chat safety rules for new accounts and banned members (2.3); a section on DJs using the Studio program (1.4), the safeguards that apply when information goes to services outside the UK (section 9) and our supplier’s staff in the list of services (section 9). Updated 28 October 2026: section 3 now says that shout-outs (studio messages) appear on the ticker straight away, with links removed and swearing starred out, and that an administrator can hide or delete any message afterwards. Updated 29 October 2026: a new section 2.9 on The Wall (pictures and videos posted by members), and how long Wall posts are kept (section 10); the opening paragraph now names who we are (the station is run by Mark Rossiter, trading as Raw Kutzz Radio). |
| Version 1 7 October 2026 | First numbered version. |
This policy explains what information Mark Rossiter, trading as Raw Kutzz Radio (“we”, “us”), collects when you listen to the station, use our mobile apps or website, chat, buy merch or tickets, or apply to join the Raw Roster — what we do with it, who else sees it, how long we keep it, and what your rights are. We have tried to keep it plain. Questions? Email Support@RawKutzzRadio.co.uk.
- We do not sell your information, and there is no advertising or tracking on the station, the apps or the website.
- We never see or store your card or bank details — our payment provider (Stripe) handles all payments.
- We collect only what each activity needs (a chat account, an order, a ticket, an application) and keep it only as long as we need it. Everything sent between you and us uses an encrypted (https) connection.
- The station, apps and website are for people aged 18 and over.
- To keep the chat safe, it records the IP address and approximate place each message was sent from, for 90 days. Only a few named admins can see this (see 2.11).
- You can ask to see, correct or delete your information (see Your rights). A few limits apply — for example, we keep a hidden record of deleted chat messages so we can deal with complaints and reports of abuse.
1. Listening to the station
1.1 The radio stream
The stream is delivered by our streaming provider (mixstream.net). As with any server you connect to, it receives your IP address and basic connection details so it can send you the audio. We do not link this to your name or account.
The site also keeps a count of how many people are listening (one number a minute, with the name of the show on air, taken from the stream’s own figures) so the station’s admins can see listener statistics. It is not linked to any person. Admins can also look at the stream’s live list of connections (the kind of device or player and the connection’s IP address) to see how people are listening. That list is read live from the stream server, is shown only to admins and is not saved by us.
Where listeners are (counts only). About once a minute, while the station is on air and someone has the website open, the site reads that same live list and works out the approximate place of each connection (country, region and town) from its IP address, using a place lookup kept on our server (the same one the chat records use). We keep only counts: how many listeners there were, in which place, in which hour, during which show, and how many different listeners there were in a place on a day. We do not keep the IP address or the device. To count each listener once a day, and to tell new listeners from returning ones, we keep a one-way scrambled mark of each listener (it cannot be turned back into an address or a device) for up to 90 days and then erase it. Only the daily totals of new and returning listeners are shown. A town with fewer than three different listeners is shown only as part of a wider area. The counts are shown only to admins (never to DJs), describe the station’s audience as a whole, are not linked to any person or account, and are kept for up to 14 months. This starts on 6 November 2026; nothing from before is available. Our legal basis: our legitimate interest in understanding where the station's audience is, so we can run and improve it (see 12.2).
1.2 The mobile and desktop apps (Android, iPhone, Windows, Mac and Linux)
What the apps collect. The apps have no advertising and no analytics tools, and we do not collect your location or contacts through them. You can listen without giving us anything. If you choose to log in to chat, buy or keep tickets, or switch on notifications, the apps (whose Chat and Events tabs show pages of this website) collect the information in the table below, and it is covered by sections 2, 4 and 5. Nothing is shared with other companies for advertising or marketing; the services that help us run the station (section 9) handle only what they need.
| Information | When | What we use it for |
|---|---|---|
| Name | When you buy or receive tickets or merch, or apply to the Raw Roster | Your order, your ticket, your application |
| Email address | When you buy or receive tickets or merch, apply to the Raw Roster, join the newsletter or use the contact form, or (optionally) add a recovery email to your chat account | Sending your order, ticket or reply, or emailing you a link to confirm that address or to reset your chat password |
| User ID (your chat username) | When you create a chat account or log in | Your account, and showing who posted a message |
| Messages | When you post in the chat or send a private message | Showing your messages in the chat (see section 2) |
| Photos | If you add a profile picture or send a picture in the chat | Showing it in the chat (see section 2.2) |
| Purchase history | When you buy tickets or merch | Your orders and tickets, receipts and our accounts. Card details are never stored by us |
| Device or other IDs (a push address) | If you switch on notifications on an Android phone | Delivering notifications to that phone |
What stays on your phone. The apps save a few small settings on your device only: whether the radio was playing when you last left the app, whether it has already asked for battery settings, and the chat name you can optionally enter for mention alerts. These are not sent to us or to anyone else.
Notifications. If you allow notifications, the apps show playback controls and, if you set a chat name, an alert when someone mentions you in the chat. These are created on your device. (If you are a logged-in member on an Android phone and allow notifications, messages can also be delivered to your phone by push; see “Notifications in the phone apps” below.)
Permissions the apps ask for:
- Internet – to stream the radio and load the chat.
- Foreground service and wake lock – to keep playing while the screen is locked or the app is in the background.
- Notifications – for playback controls and mention alerts.
- Battery optimisation exemption (Android) – so Android does not stop the radio when the screen locks. The app asks once, and you can say no.
- Camera – only to read the barcode in a ticket email so the ticket can be kept on your account. No picture is kept.
- Fingerprint or face unlock – only if you choose the biometric log-in described below.
- Start-up and exact alarms – so reminders for the DJs you follow can still go off after the phone restarts.
What is on air. While an app is open or playing, it asks our website every few seconds which show and track are on air. As with any request to a server, our website receives your IP address and basic connection details; nothing else about you is sent.
Face ID / fingerprint log-in (phone apps). If you choose to turn this on, the phone’s own Face ID, face unlock or fingerprint check unlocks a random log-in token that the app keeps in the phone’s secure storage. Your face and fingerprint never leave the phone and are never seen by the app or by us: the phone only tells the app “yes” or “no”. Our website keeps a one-way fingerprint of the token (so it cannot be turned back into the token), the name you gave the phone, when it was set up and when it was last used. The token stops working when you change or reset your password, when you turn the feature off in the app, or if your account is banned, and a member keeps at most five phones. Guests and door scanner logins cannot use it.
Newsletter. If you sign up to our newsletter we keep your email address, the wording you agreed to, when you agreed and confirmed, and where you signed up. We use it only to email you about the station’s shows, events and tickets. Every email has an unsubscribe link; unsubscribing stops the emails at once, and you can ask us to delete your address completely by emailing Support@RawKutzzRadio.co.uk. An address that is never confirmed is deleted after 14 days.
Notifications in the phone apps. When a member logs in on the phone app, the app asks to switch notifications on (Android asks you to allow them); the bell in the chat turns them off and on again. Once on, the website gives that phone a random notification token (only a one-way fingerprint of it is kept, with the time it was last used). While the app is running the app uses it to ask whether there are new @mentions, replies or private messages for that member, and shows them as notifications on the phone. Chat guests cannot use it. It is switched off by the bell, by logging out in the app, or by changing the password.
Who is online. The chat shows a list of the members who are in it. You appear in that list while you have the chat page open, and, if you are logged in on the phone app with notifications on, also while the radio is playing in the app (it shows "listening on the app"). Only your chat name is shown. You stop appearing a minute or two after you leave or stop the radio. While you are typing a message, the other people in the same room (or private chat) also see a small ball under your name for a few seconds. We do not save or log this: it is a note that disappears a few seconds after you stop typing.
Duo shows (DJs only). When an admin sets up a show for two DJs, the two Studio programs connect directly to each other so one can hear and mix the other. To do that, each computer learns the other’s internet (IP) address, and a public connection-helper server (Google’s by default, which can be changed by the admin) sees the connection addresses. We keep who took part, and when, as part of the show’s record. No sound from a duo show passes through or is stored on this website.
Push messages (Android). On an Android phone, switching notifications on (when you log in, or with the bell) also registers the phone’s push address (a random code that Google’s Firebase Cloud Messaging gives the app) with your member account. When someone @mentions you, replies to you or sends you a private message, our server sends Google a short notification (the sender’s name and the start of the message) so that Google can deliver it to your phone while the app is closed or the screen is locked. We do not send push messages to guests, to people who are looking at the chat at that moment, or if you have blocked the sender. We keep up to five push addresses per member. The bell, logging out in the app, or changing your password switches it off and removes the address; we also remove an address when Google tells us the phone no longer exists. iPhone push is not used yet. If you follow DJs in the app, the app also tells our server which DJs you follow (so it can push “is on air now” when one of them goes live); this list is kept with your member account, replaced each time you change it, and used for nothing else.
Tickets on your account. If you buy tickets while logged in to your member account, or add a ticket to it by scanning the barcode in your ticket email (the app uses the camera only to read the barcode; no picture is kept), we record which tickets belong to which account so they show on every phone you log in on. Only member accounts can do this (not guests). If a ticket is sent on to someone else it is removed from your account.
Tickets saved on your phone. After you buy or receive a ticket, your phone or the app keeps a copy of it (event, time, the name on the ticket and its barcode) so it still shows with no signal at the venue. This stays on your own device. A ticket that has been used, cancelled or sent on is removed from your phone the next time it is online. Clearing the site’s data in your browser, or turning off the feature in the app, removes it.
Staff activity log. When an administrator or moderator changes something on the site (for example editing a product, deleting a chat message or banning an account), we record who did it, what, when and from which connection, so that mistakes and misuse can be traced. Passwords and keys are never recorded. These records are kept for two years.
Error reports. If the phone app, the desktop app or the Studio crashes or meets a serious error, it sends our website a short technical report so we can fix the problem. It contains the name and version of the app, the type of device and system (for example “Windows 11”), the time, and the error message with the place in the program where it happened. File paths that contain a user name, e-mail addresses, keys, IP addresses and web addresses with details are removed before and after sending. It never includes your chat messages, the tracks you play, your name or your account details, and the phone app and desktop app reports cannot be used to tell who sent them. From version 2.1.4, Studio sends the DJ’s private key with its report, which lets our admins see which DJ it came from (the key itself is not stored in the report), so they can ask that DJ for more detail. The desktop app and the Studio have a setting to switch error reports off. Reports are kept for up to 12 months.
The desktop app is the website in its own window, so this policy applies to it exactly as it does to the website. It has no accounts, advertising or analytics of its own. It keeps only the window size on your computer, and the website’s cookies and storage (section 8) are kept in the app just as they would be in a browser. Closing its window leaves it playing in the system tray until you choose Quit.
1.3 Track names and what is on air
The Listen page, the apps and the Alexa skill show which show is on air and the track playing. The show comes from the title the DJ’s broadcasting software sends. Track names come from the DJ’s own public Serato Live Playlist (a public web page the DJ chooses to publish) and, if the station switches it on, from a music-recognition service (AudD) that listens to the same public stream as any listener and names songs. No information about listeners is involved. Some DJs also send us the artist and title of the track they are playing from their own computer, using a private key that an admin can cancel. While a DJ is live, their Studio also sends how loud the broadcast is (a few numbers every 10 seconds, never any sound) so the admins can see the level; only the last 15 minutes are kept. Studio also tells us the name of the DJ software it is reading (for example “Serato DJ Pro 5”, “Serato 3” or “rekordbox 7.2.19”), so the admins can see what each DJ uses and help if track names do not appear; it is kept with the DJ’s key and shown only to admins. Nothing else is sent.
1.4 DJs using the Studio program
The Studio is for DJs on the Raw Roster. It connects to our website using the DJ’s private key, which identifies the DJ. While a DJ is live, Studio sends us the show title, the names of the tracks being played, that the DJ is live, and how loud the broadcast is (numbers only, no sound) every 10 seconds so admins can check the levels. In a duo show it also sends connection-quality numbers (delay, jitter and lost sound) so admins can help if the link is poor. The broadcast sound goes to the station’s streaming provider (section 1.1). If a DJ chooses to send video, the camera picture and show sound go to the station’s own pages on YouTube, Facebook, Mixcloud and hearthis.at, which are public and are covered by those services’ own policies; the camera is used only when the DJ presses Show camera or goes live. The Check my upload button sends a few megabytes of meaningless data to our website to time it; nothing is kept. Studio also asks our website whether a newer version exists. Studio keeps its settings (the key is encrypted by the computer) and any recordings only on the DJ’s own computer. Crash reports are described in section 1.2. We keep a DJ’s key, when it was last used and the last track it sent for as long as the DJ is on the Roster, and then switch the key off.
2. Chat on our website
The chat on the Listen page is run by us. You can read the public chat without an account; to post you can sign up, or join as a guest.
2.1 Accounts and guests
- Members choose a username and password. We store the username, a scrambled (hashed) version of the password — we cannot read it — the date you joined, when you were last active, and the messages you post. We also keep the connection (IP) address you last used while you are active and for 24 hours afterwards, or for 30 days if your account is banned, so that a banned person cannot simply create a new account from the same connection (see 2.3). The IP address, approximate place and network are also kept with each message you send (see 2.11). We do not need an email address for a chat account. You may add one as a recovery email if you want to be able to reset a forgotten password yourself (see 2.12); if you do not, we store none.
- Guests join with just a name, no password or email. We keep the name together with your IP address (so that banned people cannot simply return) until you leave or have been away for about 15 minutes — or for 30 days if a moderator bans the guest. The IP address, approximate place and network are also kept with each message a guest sends (see 2.11). Guests, like brand-new members, cannot send links, private messages or pictures during their first hour (see 2.3). Messages a guest posted stay in the chat history under the name they used.
- Artists and staff accounts are made by us for DJs on the Raw Roster and for moderators and admins.
2.2 What you post, and who can see it
- Public chat messages are visible to everyone. A separate private room is visible only to the station’s artists and admins, and other rooms can be restricted by us.
- Private messages between registered members are stored on our server and shown only to the two people in the conversation. Moderators cannot read them in the chat, although someone with access to the server itself could technically do so. If one of the two people reports a private message (section 2.7), an admin can read the reported message.
- Replies, reactions and deleting. Everyone in the chat, including guests, can reply, add emoji reactions (others can see who reacted by hovering over a reaction) and delete their own messages. Deleting a message removes it from view for everyone, but we keep a hidden copy — see 2.4.
- Who has read a message (staff and artist rooms). In the rooms that alert people when someone posts (the admins’ and moderators’ room and the artists’ private chat), the people who can open the room can see who else has read each message. We only remember how far each person has read in the room, not when, and this cannot be switched off. It is not shown in the public chat or in private messages (where a person can turn their own read receipts off).
- Pictures and avatars. Registered members can add a profile picture and share pictures. Every picture is re-saved on our server, which strips hidden data such as the location a photo was taken. Anyone in the chat can see your avatar and pictures. If you delete a picture message, the picture file is deleted from our server; your avatar is deleted when you remove it or ask us to.
- GIFs. Your GIF search words (or the music category you tap, such as Music or DJ) are sent to GIPHY through our server (not directly from your device). When a GIF is shown, your browser loads it from GIPHY, which can then see your internet address (see GIPHY’s privacy policy).
2.3 Keeping the chat safe
Moderators can delete messages and mute or ban accounts. Anyone can block another member, which hides that member’s messages from them and stops them sending private messages. Offensive words are replaced automatically. To protect the chat from abuse we keep, for up to 24 hours, a record of your IP address against sign-ups and failed log-in attempts. For registered members the connection address is also kept while you are active and for 24 hours afterwards, and, if an account is banned, for 30 days after that member was last seen, so that a banned person cannot simply create a new account from the same connection. A brand-new account (a new member or guest, but never a DJ, moderator or admin) cannot send links, private messages or pictures for its first hour; this protects the chat from spam. Where each message was sent from is recorded as described in 2.11.
2.4 Deleted messages: records we keep for safety
When a message is deleted, by you or by a moderator, it disappears from the chat. We keep a hidden copy that only we can see.
Edited messages. You can change one of your own text messages for 15 minutes after you send it. The chat then shows “(edited)”. We keep what the message said before each edit, for the same reasons and the same six years as a deleted message, and an admin looking into a report can see it.
Why we keep it:
- to deal with reports and complaints;
- to protect other users;
- to give information to the police or another authority if they lawfully ask for it.
If we deleted messages for good we would have nothing to go on when something serious was reported.
How long: six years from the day the message was deleted, and then we erase it permanently.
Also covered:
- Private messages are treated the same way.
- Pictures are different: a deleted picture file is removed from our server.
2.5 Staying logged in
A cookie keeps you logged in for up to 30 days (see section 8).
2.6 Closing your account
To close your account, email Support@RawKutzzRadio.co.uk. We will delete your account and profile details (such as your username login, password and avatar). Messages you have already posted may stay in the chat history, and we may keep copies, including hidden ones, where we need them for the reasons in 2.4. If that applies we will tell you.
2.7 Reporting a message
Anyone in the chat can report a message to the station’s admins using the report button on it. You must choose a reason and may add a note. We keep the report with the message it is about, your chat name, the reason and note, the time, and what an admin decided and when. The person who wrote the message is not told who reported it. Admins use reports to deal with abuse and complaints, and we may pass them to the police or another authority if they lawfully ask. If you report a private message, an admin can read that message (see 2.2). We keep a report for six years from the day it was made, then erase it (see section 10). When a message is reported, the records of where it was sent from (see 2.11) are kept for up to a year instead of 90 days.
2.8 Polls, listening streaks and read receipts
Polls. DJs and admins can ask a quick question in the chat. If you vote, we keep which answer you chose against your account while the poll is running and for a year afterwards, so one person gets one vote. Other members see only the totals, never who voted for what.
Listening streaks and badges. If you are logged in and listening on the website or in the app, we count the minutes you listen each day against your account, so we can show your streak and award badges. Your current streak (a flame and the number of days) and your best badge are shown next to your name in the chat, to everyone who can see the chat. You can switch this off in your profile menu (Show my streak); your streak is then not shown to anyone else, though we still count it for you. We keep the daily totals for about 13 months. We do not record what you listened to, only that you were listening and for how long.
Read receipts. In a private message conversation, the other person sees two ticks beside a message once you have had the conversation open on your screen, and the time. We keep only the newest message you have seen in each conversation and when. You can switch this off in your profile menu (Read receipts); then nobody sees when you have read their messages, you do not see when they read yours, and what we recorded is cleared.
Answering a private message. The people list only shows who is in the chat now, and you can start a private message only with someone who is there. But you can always answer a private message you were sent in the last 14 days, even if the person has since left. If they have the phone app with notifications switched on, they get a notification that you replied; otherwise they see it next time they open the chat.
2.9 The Wall (pictures and videos)
What we collect. When a signed-in member sends a picture or video to The Wall we keep the file, the caption they typed, their username, the date and time, and the file’s size and type. We remove the location and camera details from pictures when they are uploaded. Videos are kept exactly as they were sent, so if you do not want a video to carry location details, check your phone’s camera settings before you send it. We do not read or keep anything else from the file.
Why, and our legal basis. To run The Wall for the radio community, with an admin checking each post before it is shown (our legitimate interests, and providing the service you asked for by posting).
Who sees it. While a post is waiting, only the member who sent it and the station’s admins can see it. After an admin approves it, anyone who visits the website can see the picture or video, the caption and the member’s username.
How long we keep it. A post stays on The Wall until the member deletes it or an admin removes it. A post that is turned down or removed has its files deleted at once, and a short record (the reason and the date) is kept for 7 days so the member can see why, and is then deleted. If a member’s account is deleted, their Wall posts are deleted within an hour. Copies of the station’s files are included in the station’s encrypted backups, which are kept for the periods in section 10.
Your choices. Members can delete their own posts at any time. To ask for a post to be removed, including a post of you that someone else put up, contact us.
Who it is shared with. Approved posts are public on the website, and we may also show them on the station’s own social media pages (see the Wall rules). We do not sell them. The files are stored on our hosting provider’s servers (section 9).
2.10 Bugs and ideas (DJs, moderators and admins)
What we collect. Signed-in DJs, moderators and admins can report a bug or suggest a feature on the Bugs and ideas page. We keep what they type (a title, what happened or the idea, what they expected, how serious it is, and the version of the program or phone if they give it), up to three pictures they add, their username (taken from their log-in, not typed), the date and time, and the progress we record (a status, and a private note that only admins see). We remove the location and camera details from pictures when they are uploaded.
Why, and our legal basis. To find and fix faults and to plan improvements to the website, the apps and the Studio program (our legitimate interests).
Who sees it. Only the person who sent the report and the station’s admins. Each new report is also emailed to the station’s admin and support mailboxes and to the Raw Kutzz mailboxes of the support team; the email contains the text and the username but not the pictures. Nothing on this page is public.
How long we keep it. A report and its pictures are erased 12 months after the last change to the report. Copies of the station’s files are included in the station’s encrypted backups, which are kept for the periods in section 10.
Your choices. To ask for a report of yours to be corrected or deleted sooner, contact us.
2.11 Where your messages were sent from (chat records)
What we collect. So that we can report serious problems (threats, harassment, illegal content, or someone coming back after a ban) to the police or another authority with real information, the chat records, with every message you send — text, pictures, GIFs and private messages — your IP address (the internet address your connection uses), the approximate place that address belongs to (usually a town or region), and the name of your internet provider’s network. The place is worked out on our own server from a free database, so your address is not sent to anyone for this. It is only an estimate and can be wrong, especially on mobile networks or with a VPN.
How long we keep it. 90 days. After that the address, place and network are erased from the message (the message itself stays in the chat history as described in 2.4). If a message is reported (2.7), or its sender is banned, the records of that message, or of that person’s recent messages, are kept for up to one year. Copies of our database made for safety (backups) can still hold the records for a limited time after they are erased, as set out in section 10.
Who can see it. Only a small number of named admins. Ordinary admins and moderators cannot, and nor can other chat users. Every time the records are looked at, searched or downloaded, it is written to our activity log. A private message appears to those admins only once it has been reported.
Who we may give it to. The police or another authority that lawfully asks, or where it is needed to protect someone from serious harm. We do not sell it or use it for advertising.
Our legal basis. Our legitimate interest in keeping the chat safe and being able to deal with serious abuse (see 12.2).
Place data: IP Geolocation by DB-IP.
2.12 Recovery email (optional)
Member and artist accounts can add one recovery email address in their profile (Recovery email), after typing their current password. You do not have to.
- What we store. The address, and whether you have confirmed it. We also keep, for a short time, a scrambled (hashed) copy of each one-time link we email you; we cannot read it back.
- What we use it for. Only to email you a link to confirm the address (it works for 24 hours), a link to choose a new password if you press Forgot password? (it works for 1 hour, and once), and a short notice after your password has been changed. We never use it for newsletters, adverts or anything else, we do not show it to other members, and the text of these emails is not kept in our email log.
- Who can see it. It is not shown to other members or in the admin pages. It is held in the website’s database like the rest of your account.
- Removing it. You can remove it yourself at any time from your profile. It is erased when your account is closed (see 12.1).
- Admins and moderators do not use this: another admin resets their passwords.
- Our legal basis. It is optional and you choose to give it, so that we can do what you asked: help you get back into your account.
3. The WhatsApp and Alexa shout-outs (the ticker)
You can send a text message to the station’s WhatsApp number and it may scroll across the Listen page.
- What is shown: your message and the name on your WhatsApp profile.
- What we keep: the message, the name, and a scrambled code made from your phone number so that we can block someone who abuses the service. We do not show or keep your phone number. Only plain text is used; links are removed.
- How long: messages stay on the ticker for about a day, and we delete them from our records after 30 days. We may hide or delete any message sooner.
- WhatsApp (Meta) handles your message in transit under its own privacy policy. Please do not send personal information.
If you use the Raw Kutzz Radio Alexa skill, you can also say a shout-out (now called a “studio message”) to the station, or type one on the screen of an Echo Show, and it may scroll across the same ticker.
- What we receive: only the words of your shout-out, as text, and a scrambled code made from your Alexa account so that we can limit how many one person sends and block someone who abuses the service. We do not receive your name, address, voice recording, or Alexa account details. Links are removed and swearing is starred out. A message appears on the ticker straight away; an administrator can hide or delete any message afterwards.
- How long: the same as WhatsApp messages: on the ticker for about a day, deleted from our records after 30 days.
- Amazon processes your voice to turn it into text and runs the skill under Amazon’s own privacy notice. Please do not say personal information in a shout-out. The skill also asks our site what is playing, which does not involve any information about you.
4. The merch shop
4.1 What we collect
When you buy merch we collect your name, email address, delivery address (and state or region where needed), an optional phone number, and what you ordered.
4.2 What we use it for
Only to take payment, have your order made up and posted, send you a receipt and a posting update, and deal with any problem.
4.3 Payment
Payment is taken by Stripe (cards, Google Pay and Apple Pay), which handles your card details and wallet on its own secure fields. We never see or store your card number. Card payments are verified with your bank (3-D Secure), which may ask you to approve the payment in your banking app. Stripe and your bank may also check the payment for fraud under Stripe’s privacy policy. When you pay with Google Pay or Apple Pay, Google or Apple passes an encrypted payment to Stripe; they handle that under their own privacy policies. From Stripe we receive only a payment reference, the amount, and how you paid (card, Google Pay or Apple Pay). Stripe is separately responsible for the payment information it holds, including for fraud checks and their own legal duties.
4.4 Delivery, including abroad
Our merch is made up and posted for us by a supplier. When you buy merch we share your name, delivery address, phone number (if you gave one) and what you ordered with the supplier, so they can pack and post it. We do not give the supplier your email address. They may use your details only to fulfil your order, under a written agreement with us that requires them to keep the details secure, not to use or share them for anything else, and to delete them once they are no longer needed (they do not keep them for more than 90 days after delivery unless the law requires). If you return an item, the supplier takes it back.
The supplier hands your parcel to the postal service or courier, who needs your name and address to deliver it. We post worldwide, so your details may be sent to, and handled by carriers and customs authorities in, the country you ask us to post to.
4.5 Your basket and unfinished checkouts
Your basket is kept in a session linked to a cookie on your device. If you start checkout but do not pay, we keep that unpaid order for up to 3 days and then delete it.
5. Event tickets
If you buy tickets we keep your name, email address and the tickets you bought (each with its own code). If you send a ticket to someone else we keep a record of who sent it to whom (names and email addresses, and when) and give the ticket a new code. Door staff see your name and the event when your ticket is scanned, and we record when it was checked in and by which member of staff, so a ticket cannot be used twice. We keep this for six years after the event, to deal with queries, refunds and our accounts, and then erase it. Payment works as in section 4.3. Tickets need no postal address.
Free tickets. Some tickets are free. We collect the same details and apply the same rules, and we limit how many free tickets one email address can take for an event.
Sending a ticket on, and wallets. When you send a ticket to someone else we email them a private link to it and send you a confirmation; anyone who has that link can use the ticket, so keep it private. If you choose Add to Apple Wallet or Add to Google Wallet, the ticket details (the event, date and venue, the holder’s name and the ticket code) go into a pass that Apple or Google then holds under its own privacy policy.
On your device. The ticket pages remember the links to the orders and tickets you have opened, in your browser’s storage on that device only, so that the Events page can list “Your tickets”. Clearing your browser data removes the list; your tickets can still be opened from your emails.
6. Joining the Raw Roster
6.1 When you apply
The application form asks for your name, DJ name, email address, contact phone number, genre, DJ software, the time slot you want, your bio, and (optionally) a photo and a flyer advertising your show. If you add a flyer, you are happy for us to post it (see 6.2). We also record that you ticked the box at the end confirming your details are correct and that you understand the Roster fee, and when. We use this only to consider your application and to contact you. If you are approved, we also use your DJ software answer (and the software an admin notes for you) to set up your Studio program, so that it reads your track names from the right software.
6.2 If you are approved
- Your DJ name, bio, genre and photo are shown publicly on the Artists page, and your show on the schedule.
- Your flyer. A flyer you send us (with your application, or later) is kept on our server and may be posted, with your DJ name and show time, on our Facebook page and on X on the days you play: once in the morning and once shortly before your show. An admin approves each week before anything is posted. Once posted, the picture is also held by Facebook and X under their own policies. Tell us if you do not want your shows posted and we will stop, and we delete your flyers if you leave the Raw Roster.
- We create a chat account for you (and add you to the artists’ chat room) and email you a temporary password.
- Your phone number. We keep the contact phone number you gave on your application against your DJ account, and an admin may add or change it, so the station’s admins can reach you about your shows. Only admins can see it. It is deleted if your account is deleted, or when you ask an admin to remove it.
- Welcome packs for DJs set up before the site went live. An admin may type your email address next to your DJ account so we can email you your welcome pack: your username, a new temporary password, your Studio key and settings file, a Studio download link and the DJ Guide. We keep that email address, with the date the pack was sent, in a contact list linked to your DJ account. We also use it to send messages to DJs (schedule changes, rules and news). It is deleted if your account is deleted, or when you ask an admin to remove it.
- If you applied through our temporary DJ sign-up page, or an admin sends you a welcome pack (see the previous point), we also make a private download link for the Raw Kutzz Studio program. To build the download we keep your Studio settings file (it holds your private Studio key) in encrypted form for up to 30 days, then delete it. The link works only for the people who have it, for a limited number of downloads.
6.3 Fees
Being on the Raw Roster costs £10 per month. The fee is arranged with and collected by the station directly (for example by bank transfer or cash), or, when the station has switched it on, a DJ can pay it by card in the DJ Area (see “Paying by card” below). We do not keep any bank, card or account numbers for it, and no subscription is set up: nothing is ever taken automatically.
Our record of the fee. So that the station can see who has paid and who is behind, the station’s admins keep a month-by-month record of the fee on this website. For each month we keep whether it has been paid, the date and amount received, how it was paid (for example bank transfer or cash), a short note the admin may add (such as a payment reference) and which admin recorded it. We also keep the month you started, whether your membership is free, and any months in which your fees were stopped. Only the station’s admins can see this record. Every change to it is written to the staff activity log, and a spreadsheet of it may be downloaded for the station’s accounts (each download is logged too). We use it only to run the Raw Roster and the station’s accounts. How long we keep it is in section 10.
Paying by card. When the station has switched it on, a DJ can pay this fee in the DJ Area by choosing this month, 3, 6 or 12 months. The payment is taken by Stripe (card, Google Pay or Apple Pay) in Stripe’s own secure box inside the page: we never see or store the card number, and your bank may ask you to approve the payment in your banking app. We work out the price here, never in your browser, and we ask Stripe to confirm the payment before anything is ticked. For each card payment we keep Stripe’s payment reference, the months it was for, the amount, the date, whether it went through, and the DJ it was for, together with any short note Stripe gives us if it failed. When it has gone through, the months are ticked in the record above automatically (marked as paid by card), and we email a receipt to the address we hold for you: the recovery email on your account, or the address an admin saved with your DJ account. If we hold no address, no receipt is sent. A payment that was started but never completed is erased after 90 days. Only the station’s admins can see these records. Stripe is separately responsible for the payment information it holds (see sections 4.3 and 9).
6.4 If you are not approved
If we turn your application down, we email you to say so and then delete everything you sent us on the application (your name, DJ name, email address, phone number, bio, flyer, genres, software, time slot and photo) straight away. We keep only a blank record that one application was turned down, so we can count them, and the log that shows a reply email was sent (the address it went to and when, not what it said).
7. Contacting us
If you use the contact form we receive the name, email address, phone number (optional) and message you enter, and use them only to reply to you. The message is emailed to our support mailbox and kept in the admins’ inbox on the site for 12 months, and then erased. When we email you (replies, receipts, order and ticket emails, application results), we use the email address you gave us for that purpose only.
8. Cookies and similar storage
We do not use advertising or tracking cookies, and we do not run analytics. We use:
- Our session cookie (“rkr_chat”) – keeps you logged in to the chat (up to 30 days), holds your merch basket and protects our forms from abuse. It is needed for those features to work.
- The supplier sign-in cookie (“rkr_sup”) – used only by people who work for our merch supplier, in the private supplier area. It is not set for visitors, and it ends when the browser is closed.
- Small settings in your browser’s storage – for example, remembering that you have already seen the welcome sign-in box, and (for door staff) which event you were scanning, and the tickets and orders you have opened (so the Events page can show “Your tickets”). These stay on your device.
- Cookies from services we use. The Stripe payment form on the checkout page (and in the DJ Area when a DJ pays the Roster fee by card) is loaded from Stripe and may set its own cookies for security and fraud prevention; GIFs are loaded from GIPHY. We do not control these; see their privacy policies.
9. Who else handles your information
We do not sell your information. We use these services to run the station, and they handle some information on our behalf or for their own purposes under their own policies. Some of them are based outside the UK, so your information can be transferred abroad.
Where one of these services is outside the UK, it handles your information under safeguards that UK law allows for such transfers, such as the UK government’s adequacy regulations, the UK’s standard contract terms or the provider’s certified data-transfer schemes. Each provider explains its own arrangements in its privacy policy, and you can ask us for more detail.
People who work for our merch supplier have a sign-in to a private area of the website where they deal with orders. We keep their name, work email address, a record of when they sign in, and what they do with each order (accepting, rejecting, posting, tracking numbers), to run the orders and keep customers’ details secure. Sign-in and order records are kept for as long as the supplier works with us, and the staff activity records for two years (see the staff activity log in section 1.2).
Our merch suppliers themselves. For each supplier we keep the business name, the name of our contact there, a work email address, the company address, a phone number and any notes we make, to run the orders and to pay them. If we pay a supplier by bank transfer we also keep the account name, sort code and account number they give us, only to make those payments. The account number is stored encrypted, only the people who run the station’s admin can see these details, and every time an account number is shown it is written to the activity log. If a supplier is paid through Stripe instead, it gives its bank details to Stripe on Stripe’s own secure form and we never see them. A supplier can be a sole trader or a partnership, so some of this can be personal information about the people behind it.
| Who | What for | What they see |
|---|---|---|
| Streaming provider (mixstream.net) | Delivering the radio stream | Your IP address and connection details |
| GIPHY | GIFs in the website chat | Your search words (via our server); your IP address when GIFs load |
| WhatsApp / Meta | The WhatsApp ticker | Your message and phone number, as with any WhatsApp message |
| Amazon (Alexa) | The Alexa skill and its spoken shout-outs | Your voice, which Amazon turns into text; we receive only the text and a scrambled code |
| Stripe | Card, Google Pay and Apple Pay payments for the shop and tickets, and for a DJ paying the Roster fee | Your payment details, order amount, name, email and delivery details (for a Roster fee: the amount, the months and a reference that names the DJ) |
| Google (Firebase Cloud Messaging) | Delivering push notifications to Android phones (only if a member switches notifications on) | The phone’s push address and the notification text: the sender’s name and the start of the message |
| Google and Apple (Google Pay, Apple Pay) | Only if you choose to pay with your phone’s wallet | Your wallet passes an encrypted payment to Stripe; we never receive your card number |
| Apple and Google (Wallet) | Only if you choose to add a ticket to your phone’s wallet | The ticket details in the pass: event, date, venue, holder’s name and ticket code |
| AudD | Naming songs from the public stream (if switched on) | The stream audio, as any listener hears it; no information about you |
| Our merch supplier’s staff | Dealing with orders in the private supplier area | Their name, work email address, sign-in records and what they do with each order |
| Our merch supplier | Making up and posting merch orders, and taking returns | Your name, delivery address, phone number (if you gave one) and what you ordered; not your email address |
| Postal services and carriers | Delivering merch | Your name and delivery address |
| Our web host and email services | Running this website and sending our emails | The information stored on or sent from the site |
We may also share information, including chat messages and account details, with the police or other authorities where they lawfully ask for it or the law requires it, and where it is needed to protect our users and the station from abuse, harm or fraud.
10. How long we keep information
| Information | How long |
|---|---|
| Member accounts | Until you ask us to close them |
| Counts of where listeners are (by country, region, town and hour; no addresses) | Up to 14 months, then erased |
| The scrambled marks used to count a listener once a day and to tell new from returning listeners | Up to 90 days, then erased |
| Recovery email (optional) | Until you remove it or ask us to close your account. The one-time links we email you stop working after 24 hours (confirmation) or 1 hour (password reset), and are erased soon after |
| Chat messages (including private messages) | Shown in the chat until deleted. Once deleted, a hidden copy is kept for six years from the day of deletion (for safety, complaints and legal requests), then erased permanently |
| Pictures you post in the chat | Until you delete them (then the file is removed from our server) |
| Pictures, videos and captions posted on The Wall | Until deleted by the member or removed by an admin. For a post that is turned down or removed, the files are deleted at once and the reason is kept for 7 days |
| Guest names and IP addresses | Until the guest leaves or has been away for about 15 minutes (30 days if banned). Messages a guest posted stay in the chat history |
| IP records for sign-ups and failed log-ins | Up to 24 hours. A member’s connection address is kept while they are active and for 24 hours after (30 days if the account is banned) |
| The IP address, approximate place and network a chat message was sent from (chat records) | 90 days, then erased from the message. Up to a year for a message that is reported, or for the recent messages of someone who is banned. Backup copies can hold them for a little longer, as for database backups below |
| WhatsApp and Alexa ticker messages | On the ticker for about a day; deleted from our records after 30 days |
| Unfinished (unpaid) checkouts | Up to 3 days |
| Merch orders and payment records, including any return or “parcel not received” request (your reason, anything you wrote, and how we dealt with it) | Six years (the usual period for accounts and tax records), then erased |
| Our merch suppliers’ business details, and the bank details of a supplier we pay by bank transfer | For as long as the supplier works with us. When we stop paying a supplier by bank transfer (or they stop working with us) we erase their bank details; the records of what we paid them are kept with our accounts, as above |
| Tickets, ticket transfers and check-in records | Six years after the event, then erased |
| Raw Roster applications | While your application or membership continues, then until you ask us to delete it (everything about an unsuccessful application is deleted straight away) |
| Raw Roster fee records (which months a DJ has paid, the date, the amount, how it was paid and any note), and the record of each card payment of the fee (Stripe’s payment reference, the months, the amount, the date and whether it went through) | While you are a DJ on the Raw Roster. If you leave the Roster, the records are kept until they are six years old (the usual period for accounts and tax records), then erased. A card payment that was started but never completed is erased after 90 days |
| Database backups | 30 days on our server (backups are made daily and the oldest are deleted automatically). A second, encrypted copy is kept on a separate computer that we control: daily copies for about 60 days and database snapshots for about 30 days, and then the oldest are deleted automatically |
| Backup copies of files (pictures, emails we sent, logs) | Kept in the same encrypted second copy; a file that is deleted from our server is deleted from that copy within about 30 days |
| Poll votes | A year from the poll, then erased |
| Daily listening totals (for streaks and badges) | About 13 months, then erased, or sooner if you ask us to close your account |
| Contact page messages (and our replies) | 12 months from the day they were sent, then erased |
| Bug and idea reports from DJs, moderators and admins (and their pictures) | 12 months from the last change to the report, then erased |
| Reports of chat messages | Six years from the report, then erased |
| A record of the emails the site sends (tickets, receipts, welcome and reply emails), with a copy so one can be sent again | 30 days, then erased |
| Other emails you send us | As long as needed to deal with your enquiry |
11. Keeping your information safe
What we do to protect it:
- Passwords are stored scrambled, so even we cannot read them. Anyone given a temporary password must choose their own before they can use their account.
- Our database is kept outside the public part of the website and is backed up daily.
- Backups on a second computer. We keep an extra copy of our database and files on a separate computer, so we can rebuild the station if our server fails. That copy holds personal information, so it is encrypted (AES-256) and can only be opened by our own backup program with a password that only we know. It is sent to that computer over an encrypted connection and is encrypted a second time before it leaves our server, so it cannot be read on the way.
- Keys that connect us to other services are stored encrypted.
- A supplier’s bank account number (only for a supplier we pay by bank transfer) is stored encrypted, shown only to the admins, and every look is written to the activity log.
- Staff log-ins expire after 12 hours.
- Chat records (2.11) can only be seen by a few named admins, and every look is written to the activity log.
- Pictures are re-saved to remove hidden data.
- Forms and admin tools are protected against misuse, and access to administration and private areas is limited to people who need it.
- Encryption in transit: the website and the apps talk to our server over https, so what you send us cannot be read on the way.
- Card and wallet payments are handled entirely by Stripe.
No system is perfectly secure, so please use a strong password for your account and tell us straight away if you think your account has been misused.
12. Your rights and how to complain
12.1 Deleting your account or some of your data
This applies to the Raw Kutzz Radio apps and website. You can ask us to delete your whole account, or just some of your information without closing your account.
- Email Support@RawKutzzRadio.co.uk from the address on your account, or tell us your chat username. Put “Delete my account” or “Delete some of my data” in the subject line.
- If you want only some information deleted, say which (for example your profile picture, your pictures in the chat, your follow list, your notification registrations, your newsletter address or a ticket order).
- We reply to confirm it is you, and carry the request out within one month.
What we delete: your account and profile details (username login, password, avatar), your chat pictures, your follow list, your push notification registrations and signed-in phones, and your newsletter address.
What we may keep, and for how long: messages you posted may stay in the chat history; hidden copies of deleted chat messages are kept for six years from deletion; merch orders and payment records for six years; the Raw Roster fee records, and the records of card payments of the fee, of a DJ who has left, until they are six years old; tickets, ticket transfers and check-in records for six years after the event. We then erase them. Section 10 lists every period. If we have to keep something, we tell you what and why.
12.2 Why we are allowed to use your information
We use your information:
- to do what you have asked, such as a chat account, an order, a ticket, an application or a subscription;
- for our legitimate interests in running the station and keeping the chat and website safe and free from abuse (including recording where chat messages were sent from, section 2.11);
- to meet legal duties, such as keeping accounting and tax records;
- to keep the records we need to deal with complaints, reports of abuse and requests from the police or other authorities;
- with your consent, where we ask for it.
12.3 Your rights
Under UK data protection law you can ask us to:
- tell you what we hold about you and give you a copy;
- correct anything that is wrong;
- delete your information (unless we need to keep it by law);
- restrict or object to how we use it;
- give you your information in a portable form.
Where we rely on your consent you can withdraw it at any time. To do any of these, email Support@RawKutzzRadio.co.uk — we will reply within one month.
Some of these rights have limits. For example, we may keep information we need to keep by law, or to deal with a complaint, protect other people or make or defend a legal claim, such as the hidden copies of deleted chat messages described in 2.4. If we cannot do everything you ask, we will explain why.
12.4 Complaints
If you are unhappy with how we have handled your information, please tell us first so we can put it right. You can also complain to the Information Commissioner’s Office (ICO) at ico.org.uk.
13. Children
The station, apps and website are for people aged 18 and over. They are not directed at children or anyone under 18, and we do not knowingly collect information from anyone under 18. If you think someone under 18 has given us information, please email Support@RawKutzzRadio.co.uk and we will delete it.
14. Changes to this policy
We may update this policy as the station changes. The date at the top shows when it was last changed, and we will make clear any significant change on the website.
Contact: questions about this policy go to Support@RawKutzzRadio.co.uk.