We collect very little, we use it only to run SoundPour, and we do not sell it to anyone. This page sets out exactly what we hold, why, how long for, and the rights you have over it. Last updated 15 October 2026.
SoundPour is a trading name of Andy Wilson, of Darlington, United Kingdom. We are the data controller for the information described on this page, which means we are the ones responsible for it. Our full postal address is available on request by emailing hello@soundpour.co.uk.
You can contact us about anything on this page at privacy@soundpour.co.uk.
There are two places on this site where you can give us personal information, and neither of them is optional reading.
The form at start.html asks for your name, your business name, your email address, the type of venue and the venue's postcode. It also offers two optional fields: phone number, and town or area, which the form fills in from the postcode for you to change if you like. You can leave both blank and still sign up.
We use these to set up your player, to email you your link, and to contact you about the beta. We also use the postcode and business name to check the venue, because the music is licensed to the premises you sign up for: how, and who that involves, is under "Who else sees it" below. Those are the only things we use them for. We also record the date, the version of the beta terms you accepted, and the IP address the form was submitted from, because that is what turns a ticked box into a record worth keeping.
Our lawful basis for setting up and running your player is Article 6(1)(b) of the UK GDPR: the processing is necessary in order to take steps at your request before entering into a contract, and then to perform that contract. We are not relying on consent, so there is no consent for you to withdraw, but you can end the agreement and ask us to delete your details at any time.
For the venue check our lawful basis is Article 6(1)(f) of the UK GDPR, our legitimate interest in making sure each player goes to a real venue at the premises named before we license music to it. We use only the postcode and the business name for it, and we keep nothing from it beyond the area the postcode belongs to and a note that the venue was confirmed. You have the right to object; if you do, tell us and we will agree another way to confirm the premises with you.
If you do not give us the required fields we cannot set up a player for you, because we would have nowhere to send it, no premises for the licence to cover, and no way to check the venue or set the player up for the kind of place it is.
The Feedback button inside a venue player sends us your venue name, the player's reference, a rating if you give one, whatever you write in the message, and an email address if you choose to add one. The email address is optional and is only there so we can reply.
Our lawful basis is Article 6(1)(f), our legitimate interest in understanding whether the product works and fixing it when it does not. You are under no obligation to send feedback at all.
Every web server in the world keeps a record of what has been asked of it, and ours is no different. When your player asks for the next piece of music, or checks whether the library has been updated, or when you open a page on this website, our server writes down what was requested, when, and the internet address it came from. That happens automatically. It is how the web works, and it would happen whether we looked at it or not.
We do look at it, and we would rather tell you that than let you assume otherwise.
Why. Without these records we would be guessing about the things that decide whether this is any good: whether a player is being opened each day, which parts of the music library are reaching real rooms and which are not worth making more of, and whether a venue has quietly stopped using it because something is wrong. A venue that has gone quiet is one of the most useful things we can know, because it usually means we have got something wrong and can put it right. Guessing instead produces a worse service for you, and a duller library.
What we look at. Which player was opened, on which days, and roughly for how long. Which tracks a player has downloaded to your device. Which pages of this website were visited. We look at this at the level of "this venue opened the player on eleven days last fortnight", not at the level of individual moments.
What we genuinely cannot see. We cannot tell what is playing at any given moment, or how many times anything has been played. The player downloads each track to your device once and then plays it from there, so a track played fifty times looks exactly the same to us as one played once. We have no microphone and no way to hear your room. We know nothing whatsoever about your customers.
One thing worth being straight about. Because a player tends to be opened when you open and closed when you close, these records give a rough impression of your trading hours. We are aware that is information about your business, not just about our software. We use it to understand whether the product is working, never to draw conclusions about how you run your venue, and we do not pass it to anyone.
Our lawful basis is Article 6(1)(f) of the UK GDPR, our legitimate interest in knowing whether the thing we have built actually works. Because we rely on legitimate interests, you have the right to object. Tell us and we will exclude your player from anything we look at, and it will not affect your subscription or the music you receive in any way.
We keep these records for twelve months and then delete them. Our hosting provider may hold its own copies for a shorter operational period.
These marketing pages set no cookies and store nothing on your device.
The customer player does use your browser's local storage, for three things: the setup answers you gave it, whether it has been started before, and what it has played recently so it does not repeat itself. It also stores the music itself so it keeps playing if your internet drops. All of that is necessary for the thing you asked the player to do. Under regulation 6(4) of the Privacy and Electronic Communications Regulations, storage that is strictly necessary for a service the user has requested does not require consent, which is why you are not asked for any. That applies to what the player keeps on the device. What it sends to us is covered in the next two paragraphs.
The music you have downloaded, and the record of what has been played recently, stay on that device and are never sent to us.
Your answers to the setup questions are also saved on our server, against your venue, so that every device you use plays the same thing. Change them on the laptop and the tablet behind the counter follows, instead of the two drifting apart. If you would rather they stayed on the device, email us at privacy@soundpour.co.uk and we will switch it off for your venue and delete the copy we hold.
What is saved is the venue name you typed, your opening hours, the handful of playback preferences the setup screen asks for, the date and time it was last changed, and whether the change came from a computer, a tablet or a phone. Your name and your email address are not part of it, and nothing about your customers is. We keep it for as long as your player exists and delete it when the player is removed, or sooner if you ask.
Mostly this is information about your venue rather than about a person. Where it does identify someone, for instance if you trade under your own name, our lawful basis is Article 6(1)(f) of the UK GDPR, our legitimate interest in the player behaving the same way on every device a venue uses. Because we rely on legitimate interests you have the right to object, and the email address above is how.
You can clear what is stored on the device at any time through your browser. If your setup is saved with us, the player will pick it up again next time it is opened, which is the point of it. If you have asked us to switch that off, it will simply ask you the setup questions again.
Our website and email are hosted by our hosting provider on servers in the United Kingdom, and your information sits there. They act on our instructions and do not use it for their own purposes. We also keep a copy on our own equipment here in Darlington, so that we have a working record. Both copies stay in the United Kingdom.
We do not store your information outside the United Kingdom.
Checking a venue. When you sign up we check the venue before setting up a player. We send the postcode, and nothing else, to postcodes.io, a free postcode lookup service, to confirm it is a real postcode and see roughly where it is. The form also does this as you type the postcode, through our own server, so it can show you the area it belongs to before you send anything; we do not keep the postcode you type unless you go on to sign up. We may also search for the business name and postcode on the Food Standards Agency's food hygiene ratings website and on an online map, the same way anyone looking for your venue would, so those searches are seen by whoever runs those sites. A map search, or the postcode lookup, may be handled outside the United Kingdom. We never send your own name, email address or phone number to any of them.
Apart from those checks, we would only ever hand information to anyone else if the law required us to.
Under the UK GDPR you have the right to:
Email privacy@soundpour.co.uk and we will answer within one month. There is no charge, and you do not need to give a reason.
If you are unhappy with how we have handled your information, please tell us first and we will try to put it right. You also have the right to complain to the Information Commissioner's Office, which is the UK regulator for data protection. Their guidance and complaints process are at ico.org.uk, and their helpline is 0303 123 1113.
If we change this notice we will update the date at the top of the page. If a change materially affects anyone who has signed up, we will email them rather than rely on them checking.
This notice covers soundpour.co.uk and the SoundPour customer players. The beta terms you accept at sign-up are separate, and are set out in full on our beta terms page.