Privacy Policy
Effective from: 22 October 2026
1. What we collect
Hosts: name (shown publicly, and may be a stage name), email, password (hashed), country, profile information (bio, host type, avatar, cover image, accent colour, pinned message, thank-you message for Guests, public page slug, social media handles, and links to tracks, mixes or videos they feature, with the title and artwork the music platform gives us for each), which version of the Terms they accepted and when, confirmation that they are 18 or over, notification preferences, whether they asked for tips and product news (with the wording they agreed to and when), push notification subscription token, and an account activity log (see section 12). Hosts paid through Stripe: Stripe collects their identity details, date of birth, address and bank details directly. We receive only their Stripe account ID, whether Stripe has enabled payments and payouts, what Stripe still needs from them, and the amount and date of each payout. We never see or store their bank details. Hosts paid by withdrawal (before moving to Stripe payouts): legal name (private, used to check that payouts go to a bank account in the Host's own name) and bank details, encrypted at rest. The exact bank fields depend on payout currency: UK (GBP) sort code, account number, and account holder name; US (USD) routing number, account number, and account holder name; Canada (CAD) transit number, institution number, account number, and account holder name; or EU (EUR) IBAN, BIC/SWIFT (optional), and account holder name. If we ask one of these Hosts to verify their identity, we also collect the documents we request, such as photo ID, a selfie holding that ID, proof of address, a bank statement or a business registration document (see section 14). These details are deleted once the Host has moved to Stripe payouts and their earlier balance has been paid out. Guests: name, email (used to send your receipt and updates about your request), request content and dedication, and payment method details (processed by Stripe; we never see or store card numbers). If you tick "Remember my name and email on this device", they are kept in your browser, not on our servers. Guests who leave a tip: the amount, their email for the receipt, and optionally their name and a message. People who send a Host a booking enquiry: name, email, event date, type and location, and their message, which we pass to the Host. Hosts' song lists: song titles and artists a Host uploads for Guests to choose from. Fans who ask to hear when a Host goes live: email address and a record of when they asked. Performers on our waitlist: email, country and anything they choose to tell us. Everyone: IP address (logged temporarily for security and bot protection) and browser user agent, and anything you type in live chat if you open it. To count visits, we record which page was opened and when, with an anonymous code made from your IP address and browser that changes every day, so we can count you once a day but can't follow you from one day to the next. We don't store the IP address with it or set a cookie for it. For Hosts, the IP address and browser are also recorded with account activity, as described in section 12.
2. How we use it, and why we are allowed to
To provide the Platform and take and pay out payments, because that is our contract with you. To keep financial records and report to tax authorities, including HM Revenue & Customs under the Platform Operators (Due Diligence and Reporting Requirements) Regulations 2023, because the law requires it; Hosts receive a copy of what we report about them. To keep accounts secure, prevent fraud, investigate disputes, provide support and improve the Platform, because we have a legitimate interest in doing so. To send tips and product news, alerts when a Host goes live, and push notifications, and to remember a Guest's details on their device, only with consent, which you can withdraw at any time.
3. Payments and payouts
Guest payments are processed by Stripe. OnCuePay stores only the Stripe payment ID, the amount in the currency's smallest unit, and its status. We never see or store card numbers, CVCs, or full card details. For Hosts paid through Stripe, Stripe verifies their identity and holds their bank details as an independent controller, under Stripe's privacy policy. For Hosts still paid by withdrawal, bank details are stored encrypted using AES-256, used only to make their withdrawals, and never shared with third parties.
4. Email
We send service emails about requests, payments, payouts, disputes and your account; Hosts can choose some of these in My account. Anything else, such as tips and product news, or an alert that a Host you follow has gone live, is only sent if you asked for it, and every one has an unsubscribe link. When you unsubscribe, we add a scrambled (hashed) copy of your email address to a suppression list so we never send you that kind of email again; we keep that list indefinitely, because deleting it would mean we could email you by mistake. We never message people on a Host's or Guest's behalf to promote OnCuePay.
5. Retention
We keep each kind of data only as long as we need it. Profile data (name, bio, host type, avatar, cover image, pinned and thank-you messages, slug, social handles and featured music links) is deleted within 30 days of account closure; when a Host closes their account with money still to be paid out, their name, email and payout details are kept only until it has been paid. Bank details are deleted once nothing more is owed to the Host. Authentication data (password hash, session tokens) is deleted on account closure or session expiry. Email and transactional records (notification preferences, support correspondence) are retained for up to 2 years post-closure for support continuity, then deleted. Records of marketing consent are kept while you are subscribed and for 2 years after you unsubscribe, as evidence of what you agreed to. Financial transaction records (request amounts, fees, payout references, but not bank details) are retained for 7 years from the date of the transaction in anonymised form (no personal identifiers attached), as required by HMRC for UK tax records. Guest request content is retained for 2 years from completion, then deleted. A fan's alert sign-up is deleted when they unsubscribe. Waitlist entries are deleted 90 days after they are made. Booking enquiries are deleted 90 days after they are sent. Tips are kept as financial transaction records, like requests. IP logs (bot protection, security analysis) are retained for 30 days, then deleted. Visit counts (the page opened, when, and the day's anonymous code) are deleted after 400 days. Host account activity logs (section 12) are retained as follows: records of pages visited are deleted after 90 days; all other activity records, including the IP address and device recorded with them, are kept while the account is open and deleted 2 years after it is closed. Identity documents (section 14) are deleted 90 days after we make our decision on them, and straight away if the account is closed. Where local law sets a shorter retention period than the above for a given data category, the shorter period applies.
6. Who we share it with
We use these providers to run the Platform. Stripe (stripe.com) processes payments and payouts and verifies Hosts' identity. Mailgun (mailgun.com, EU region) delivers our emails. DigitalOcean (digitalocean.com) hosts the application and database. Cloudflare R2 (cloudflare.com) stores uploaded profile and cover images. Sentry (sentry.io) monitors errors and may receive error details, including partial request data but never card data. tawk.to (tawk.to) runs our live chat, and only receives anything if you open the chat: what you type, your browser details and IP address. Anthropic (anthropic.com) powers the optional "Write with AI" button on some Host and admin forms, and only receives anything when you press it: the text in that field and the details needed to write it (for example your name and the kind of performer you are, or the request or support conversation it is about). Anthropic doesn't use this data to train its models. Google reCAPTCHA protects our sign-up, sign-in and request forms and loads only when you submit one of them; Google's privacy policy applies (policies.google.com/privacy). Plausible (plausible.io, EU) counts page visits without cookies or personal identifiers. Music players: a Host can feature tracks, mixes or videos from Spotify, YouTube, SoundCloud or Mixcloud on their profile. When they add one, we ask that platform for its title and artwork, sending only the link. On the profile, the artwork is shown from the platform's image servers, which therefore receive your IP address and browser details. The player itself only loads when you press play; that platform then receives your IP address and browser details, may set cookies, and handles your data as an independent controller under its own privacy policy. We also use a geolocation database from DB-IP (db-ip.com) that runs on our own server to show the right currency; your IP address is never sent to DB-IP. We do not sell personal data, we do not use advertising networks, and we do not share data for marketing purposes.
7. International data transfers
Some of the providers above process personal data outside the United Kingdom, for example in the United States (Stripe, Google, tawk.to, Anthropic and, depending on its region, Sentry) and the European Union (Mailgun EU, Plausible). Music platforms whose players you choose to play (section 6) handle your data under their own policies and may do so outside the UK. When personal data leaves the UK, we make sure a transfer mechanism recognised by UK data protection law is in place. You can ask us for details of the safeguards that apply.
9. Your rights
Your rights depend on your country of residence. If you are resident in the United Kingdom, you have the rights granted by the UK GDPR: to access, correct, delete, restrict, port, and object to processing of your personal data, and to withdraw consent at any time, and you can complain to the Information Commissioner's Office (ico.org.uk). If you are resident in the European Union or European Economic Area, the EU GDPR grants you equivalent rights, and you may also lodge a complaint with your national data-protection authority. If you are resident in Canada, the federal Personal Information Protection and Electronic Documents Act (PIPEDA), plus where applicable provincial legislation including Alberta and BC's PIPA and Quebec's Law 25, grants you the rights to access your personal information, correct inaccuracies, withdraw consent, and lodge a complaint with the Office of the Privacy Commissioner of Canada or the relevant provincial commissioner. In all cases, to exercise any right, contact us via live chat. We will respond within 30 days. To delete your account and personal data, use My account → Delete account; financial transaction records will be retained as described in section 5 (Retention) but in anonymised form. To export your earnings data, use Earnings → Export CSV. To stop marketing email, use the unsubscribe link in any of those emails, or My account → Notifications.
10. Security
All data is transmitted over HTTPS. Passwords are hashed using bcrypt. Bank details are encrypted at rest using Laravel's AES-256 encryption. We do not store payment card details. Access to production systems is restricted to authorised personnel only. If you believe your account has been compromised, contact us via live chat immediately.
11. Bot protection and IP logging
To protect against automated abuse, OnCuePay logs IP addresses and browser user agents when bot protection measures are triggered. These logs are retained for 30 days and used only for security analysis. Google reCAPTCHA v3 checks submissions of our sign-up, sign-in and request forms (see section 6). We also consult a locally hosted DB-IP geolocation database (db-ip.com) to detect a visitor's country code at page render time, used solely to display the appropriate currency on landing and onboarding pages. The IP address is processed entirely on our server, and no IP data is transmitted to DB-IP or any other third party for this purpose. The database is refreshed monthly.
12. Account activity logs
For Hosts, OnCuePay keeps a log of activity on your account so we can keep it secure, help when you contact support, and investigate disputes or suspected fraud. The log records sign-ins, sign-outs and failed sign-in attempts; changes you make (for example to events, request types, settings and payout details, where we record that a change happened but never account numbers themselves); requests you accept, decline or complete; payouts and withdrawals; and the pages of your dashboard you visit. Each entry records the time, and for actions you take yourself, the IP address and the browser and device you used. The log also records what happens to requests sent to you (for example when a guest sends, confirms or cancels a request, or a payment is released or refunded), including the guest's name and request; we do not record guests' IP addresses or devices in this log. Only authorised OnCuePay staff can see the log, and when our support staff view your dashboard to help you, that is recorded too. Retention is described in section 5.
13. What Hosts can see about Guests
When you send a request, the Host sees your name, your request and any dedication, the amount you paid, and the request's progress. To help Hosts recognise regulars and supporters, a Host's dashboard also shows how many requests a returning Guest has sent them and the total they have paid that Host. The Host sees only a partly hidden version of your email address (for example j•••••@example.com), and never your full address. Hosts cannot see your card details. If a Host uses a big screen at their event, your first name and your request or message can appear on it, but only after the Host approves it; you're told this before you pay. Your full name and email are never shown.
14. Identity verification
This applies to Hosts still paid by withdrawal; for Hosts paid through Stripe, Stripe carries out identity checks (section 3). Most Hosts are never asked for documents. If we need to confirm who a Host is, for example to prevent fraud, to make sure payouts reach the right person, or to meet a legal obligation, we ask for specific documents from the list in section 1 and explain why. We rely on our legitimate interest in preventing fraud and protecting Guests and Hosts, and on legal obligation where the law requires checks. Documents are uploaded through your account and kept in private storage that is never publicly accessible. Only authorised OnCuePay staff can open them, and every time a document is opened it is recorded. We never show them to Guests or other Hosts, and we do not share them with anyone except our hosting and storage providers, or where the law requires it. If we can't approve a document, you can upload a new one, which replaces the earlier one, and the earlier file is deleted. Documents are deleted 90 days after we make our decision, and straight away if you close your account. We keep a record of the outcome (what was requested, when, and whether it was approved) with your account activity log (section 12). You can ask us to delete your documents sooner, but if we still need to verify your account we may have to pause payouts or suspend it until you do.
15. Waitlist
If you join the waitlist because OnCuePay isn't open in your country yet, we use your email only to tell you when it opens there, and we delete your entry 90 days after you join.
16. Contact
Data controller: Interstack Ltd, registered in England and Wales, company number 16321411. Registered office: Newport Avenue, London. Trading as OnCuePay. contact us via live chat.