Privacy Notice

Goo Holdings Ltd, trading as JukeLoop, is the data controller for the personal information described here. We are registered in England and Wales, with company number 17141115 and a registered office at 79 Shawclough Way, Rochdale, England, OL12 6DS.

Our ICO registration number is to be confirmed before publication.

Contact us about your data: privacy@lineman.io Anything else: support@jukeloop.fm

The address above is not at a domain that matches our name, and it must be before this notice is final: a person exercising their rights should not be writing to a different company. It reaches us today, which is why it is still printed rather than replaced with a blank.

Whether we have a data protection officer is to be confirmed before publication.

One notice, not three: the marketing site, the patron app and the venue dashboard. Venue staff and venue operators are covered by section 12.

You can look at what is playing, search the catalogue and see the queue without giving us anything.

To do that, your phone is given an anonymous session — a random identifier so that the app knows which requests on screen are yours. It is not tied to your name, your email or your phone number. It is stored on your device and we hold a matching record.

If you never buy anything, that session and the anonymous account behind it are deleted after 30 days and nothing of you remains.

To buy credits you need an account. We ask for:

Your credits are held against your account, so they follow you to a new phone.

If you register and never buy anything, we keep your account — it is your account, and deleting it because you had a quiet month would be its own kind of wrong. You can delete it at any time (section 8). Whether a dormant account is deleted in the end, and after how long, is to be confirmed before publication.

Your card details go straight to Stripe and never reach us. We cannot see your card number and we do not store it.

We keep a record of the amount, the pack, the venue you were in, the date, and Stripe’s reference for the payment. We keep those because we have to — see section 7.

The card code. Stripe gives us an opaque code that is the same for the same card, so that one person cannot fill a venue’s queue by making a second account. It is not your card number, it cannot be turned back into one, and it is only ever compared with itself. It is also what makes a venue’s suspension cover a second account you set up (section 9).

Being honest about the payment record. Stripe’s reference for the payment carries your account identifier with it, so that a payment can be matched to the person who made it. That means a payment record is not fully anonymous, even after you ask us to delete your account. Section 8 explains exactly what survives an erasure and what does not.

"Lawful basis" is the Article 6 UK GDPR ground we rely on. Where it says consent, you can withdraw it at any time and we stop.

Where we rely on legitimate interests, we have weighed our interest against your rights, and you can ask us for that assessment.

The periods in section 6 are what the system actually does, not aspirations:

• 30 days for a session that never bought or queued anything, and for the anonymous account behind it.
• Two years for a pub’s enquiry from our home page.
• 90 days is not a retention period but the life of a credit — see the terms of sale.

When a period ends we delete the record. Where we cannot delete it because we have to keep the money or the licence report, we strip out what identifies you instead, which is what section 8 describes.

Payment records and play logs are the two we keep for seven years, with the accounting record — nothing deletes them automatically, so that is a period we hold ourselves to rather than one the code enforces. Everything else in the table above is deleted by a job that runs nightly.

Email privacy@lineman.io and we will do it within one month, as the law requires.

What goes completely:

• your profile — name, email, mobile, postcode, your 18+ confirmation;
• your sign-in;
• your marketing choices; and
• the opaque card code.

What stays, and in what state:

• payment records and the record of credits spent, because HMRC requires us to keep them;
• what was played, where and when, because PPL and PRS are owed a report of it and that is what pays the artists.

Those records are detached from you: your account identifier, the card code and your session token are removed from them.

One thing to be straight about. Stripe holds its own record of your payment, under its own retention rules, and the reference we keep carries an account identifier inside Stripe’s copy. So "nothing anywhere connects the payment to you" would not be true, and we do not claim it. What is true is that nothing in our systems connects the remaining records to you after an erasure, and you can ask Stripe to deal with its copy separately.

Unspent credits are cancelled when you delete your account. If you would rather have your money back first, ask us before you ask for deletion — see clause 18 and clause 19 of the terms of sale.

Whether your suspension records, and the record of the marketing questions you were asked, should survive an erasure is still being decided. Today they go with the account.

Bar staff have to be able to run the room. So, at the pub you are in:

The pub can see

• the name you registered with, next to each request;
• what you have asked for at that pub — playing, waiting, played, and songs that were pulled or skipped — with the times;
• when you were first and last seen at that pub;
• whether you have been suspended at that pub before;
• whether an account that paid with the same card has been suspended at that pub before — but never anything that identifies that other account.

The pub cannot see

• your email address, your mobile number, your postcode or your card details — unless you separately asked to hear from that pub, and then only what section 10 describes;
• anything you have done at any other venue; or
• what you paid, if the person looking is bar staff rather than the owner or manager.

Why we allow this. One song is not enough to justify stopping someone requesting. Staff need to see the pattern before they act, so the history is on the same screen as the decision. We think that is a fair balance between the venue’s interest in a safe room, your interest in not being barred over a misunderstanding, and everyone else’s interest in a jukebox that is not being used to harass them. If you disagree, section 11 is how to object.

Suspension notes. Staff can write a note when they suspend an account. The note is about you, so you can ask us for a copy (section 11) — and staff are told to write it on that basis.

Your requests at one pub are that pub’s business and nobody else’s. We do not give one venue a view of what you did at another, and the venue agreement forbids a venue from trying to identify you from anything else it holds.

When you register there are two boxes, both unticked: one to hear from JukeLoop, one to hear from the pub you are in. Each is its own choice. Neither is a condition of buying anything, and buying does not sign you up to either.

If you tick the pub’s box, that pub is given your name and contact details so it can tell you about its events and offers. It is not told what you played or what you spent.

Changing your mind. You can withdraw either at any time, from the account menu in the app. It lists JukeLoop and every pub you have ever answered for, not only the one you are standing in, and each is a switch. Withdrawing is the end of it — we do not ask why and we do not ask again.

We keep a record of what you were asked, what you answered and when — including a "no" — because we have to be able to show it.

You can:

• ask what we hold about you, and get a copy — free, within one month;
• have mistakes corrected;
• have your data deleted (section 8), where we are not obliged to keep it;
• get your data in a portable form, for the things you gave us and the things we hold to perform our contract with you — we will send you a machine-readable file;
• object to anything we do on the basis of legitimate interests, including what a venue can see (section 9). Tell us why and we will stop unless we have compelling grounds not to;
• ask us to restrict what we do with your data while a dispute is sorted out; and
• withdraw consent at any time, for marketing (section 10) or for your phone’s location (section 13). Withdrawing does not undo what we did before.

Email privacy@lineman.io. We may ask you to confirm who you are, but no more than we need to.

If you are not happy with our answer, you can complain to the Information Commissioner’s Office: ico.org.uk/make-a-complaint, or 0303 123 1113, or Information Commissioner’s Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF. We would rather you told us first, but you do not have to.

If you run or work at a JukeLoop pub, we hold your name, email, your role, and a record of what you did in the dashboard — pulling a song, closing the night, suspending a patron. We hold it to run the service, to work out what the venue is owed, and so there is a record of who did what. The lawful basis is contract (with the venue) and legitimate interests. How long we keep it after the venue leaves the network is to be confirmed before publication.

The venue’s bank details. If you are the owner of a JukeLoop pub, we also hold the bank details your share is paid into: the name on the account, the sort code and the account number. We hold them to pay you, and for nothing else. The lawful basis is contract.

The sort code and account number are encrypted before they reach our database, with a key the database has never been given, so a copy of the database on its own is no use to anybody. Only the last four digits are kept in a form anyone can read.

There is no screen, no export and no support tool that shows the number back — not to you, not to the pub’s staff, and not to us. Your dashboard shows the name on the account and the last four digits, so you can check at a glance that the money is going where you think. If it is wrong you replace it; we cannot read it out to you. Every change is recorded in the venue’s audit log with who made it and when.

We keep them while the venue is on the network and its payments are outstanding, and for seven years after the last payment, with the rest of the accounting record. You can ask us to stop holding them at any time — we will, and we cannot pay the venue afterwards until you tell us where to send it.

Two different things, and they are worth keeping apart.

Finding a pub. When you use "find your pub", your phone works out which venues are nearest on the phone. The sorting happens there and your location is not sent to us.

Requesting a song. JukeLoop only takes requests from inside the venue, so when you make a request your phone sends us where it is, with the request. We compare it with the pub’s location, allow for the reading’s accuracy, and accept or refuse the request. We do not store it. It is not written to any table, it is not in your history, and it is not in a log.

Your phone asks your permission before either of these, and you can take that permission back in your browser at any time. Without it we cannot accept a request, and no credits are taken.

We do not use advertising cookies and we do not track you across other websites.

Our database is in the United Kingdom (London), and so is the audio.

Some of the companies we use process data outside the UK — most importantly Stripe, which processes payments in the United States as well as in Ireland. The safeguard we rely on where that happens is to be confirmed before publication, and you can ask us for a copy of it.

Who we share with, and why:

We do not sell your data to anyone, ever.

An email provider and an error-reporting provider are decided but not yet set up on any project, so they are not named here. Naming a processor we do not use would be a statement about processing that is not happening.

We and the venue are joint controllers for some of the personal data that passes through the service, so here is the essence of the arrangement between us, which Article 26(2) UK GDPR requires us to publish.

You can exercise your rights against either of us, whatever that split says, and JukeLoop is the contact point. It is quicker to come to us.

The table above is the same allocation as clause 11.2 of the venue agreement, word for word, because two documents describing one arrangement differently would be worse than one describing it badly. If one moves, both move. The amendment that replaces the agreement’s old "non-identifying information" promise is drafted and has still to be reviewed.

We do not make decisions about you by automated means that have a legal or similarly significant effect. A suspension (section 9) is decided by a person at the venue looking at the history, not by an algorithm, and you can ask us to review it.

JukeLoop is for people aged 18 or over, and you confirm your age when you register. We do not knowingly hold data about anyone under 18. If you think we have, tell us at privacy@lineman.io and we will delete it.

We will update this notice when what we do changes. The version and date are at the top. Where a change matters to you — new processing, a new recipient, a longer retention — we will tell you before it takes effect rather than quietly republishing.