Privacy Policy

Last updated: 03 August 2026

This site (https://dj.stott.pro) is run by DJ Mark Stott to take music requests at Ceroc / Modern Jive events. We aim to collect only the information needed to deliver the service, and to delete it as soon as it is no longer useful.

What we collect when you submit a request

When you request a track, we do not ask for or store any other data than that which is listed specifically below:

• The display name you enter on the request form.
• The track you ask for — either a song name or a link, stored exactly as you pasted it.
• The event you are requesting it for.
• An anonymous browser identifier (see Cookies below) that links your requests together for the same event.

Please note that anything that is sent using the request form that is not a music request will be deleted.

The DJ Assistant (AI chat)

On each event page you can choose to chat to the DJ Assistant instead of filling in the request form. If you do:

• What you type is sent to Azure OpenAI, Microsoft's hosted AI service, so it can suggest tracks and reply to you.
• The name of the event goes with it, and — if you have requested a track before — the display name held against your browser identifier, so that you are not asked for it twice.
• The conversation is not stored on this site. It lives in your browser tab and is sent back with each new message. Close or reload the page and it is gone.
• To check that a track really exists, the assistant may send a short search phrase to Tavily, a web search service. Your name and your cookie identifier are never included in it.
• Only the request you actually confirm is saved, exactly as if you had used the form — and it is deleted on the same timetable.

You never have to use the assistant. The standard request form does the same job without sending anything to an AI service.

What we collect when you submit the contact form

• The name you enter into the form.
• The email address you enter into the form, so that a reply can be sent to you.
• The subject and message you write.

The form is sent to DJ Mark as an ordinary email and is not saved in the site's own storage. It is never used for marketing and you will not be added to any mailing list. Because it arrives as an email, it stays in DJ Mark's mailbox until it is deleted, so it is not covered by the 48-hour deletion described below — ask at any time and it will be removed.

The form also carries a hidden field that acts as a honeypot trap for automated bots to fill in, and a measurement of how long the form was open before you sent it. Both are used solely to filter out spam, and neither is kept.

Cookies

We use a single essential cookie called cydjr.requestor. It contains a randomly-generated identifier (a GUID) that is unique to your browser and device. It is used only to:

• Show you the requests you have made for an event under your own identity (shown to you as "You").
• Associate any further requests you make with the same person.

The cookie expires after 365 days. It is not used for advertising, profiling, or analytics. You can clear it at any time from your browser's settings; doing so means subsequent requests will be recorded under a fresh identifier.

Who can see your name

• The DJ can see the display name you enter, alongside your request.
• The DJ can also log a request on your behalf if you ask him in person, and may note your name against it as a reminder to check you are still on the floor when it comes up.
• Other dancers browsing the request list will see your request, but your name is never shown to other users. Here is a list of replacement names they will see:
  • Ballroom Ghost
  • Dancefloor Poet
  • Dancing Queen
  • Disco Voyager
  • Groove Bandit
  • Harmony Rebel
  • Moonlight Mover
  • Midnight Rider
  • Rhythm Renegade
  • Son of a Preacher Man
  • Spin Me Slowly
  • Sweet Caroline
  • Sweet Child of Mine
  • The One & Only
  • Tiny Dancer

How long we keep your data

All data held on https://dj.stott.pro for an event — including the event information itself and every music request made for it — is permanently deleted within 48 hours after the event has ended. This deletion is a manually triggered process and is non-recoverable.

Two things sit outside that: emails sent through the contact form, which stay in DJ Mark's mailbox until deleted, and DJ Assistant conversations, which are never stored in the first place.

Where your data is held

Events, music requests and the DJ's track catalogue are stored in Microsoft Azure AI Search in the United Kingdom. DJ Assistant conversations are processed by Azure OpenAI in the United Kingdom. Neither is copied to a region outside the UK by us.

The one lookup the site makes to another company is the exception: if the assistant needs it, a Tavily web search. Tavily operates internationally and may handle the request outside the UK — which is why it is never sent your name or your cookie identifier. See Third parties below.

Third parties

• If you submit a link, the site stores it and shows it to the DJ. It does not visit the link or send anything to the site the link points at. If the DJ chooses to open it, the destination site's own privacy policy applies from that point.
• Azure OpenAI (Microsoft) handles DJ Assistant conversations. Microsoft states that prompts and replies are not used to train its own or OpenAI's models, and are held for up to 30 days only to check for misuse of the service. See Microsoft's data, privacy and security notice.
• Tavily runs the web searches the assistant makes. Tavily states that it does not retain the queries sent to it, though a query may be passed on to its own upstream search providers when it cannot answer from its own index. See the Tavily privacy policy.
• The site uses Microsoft Application Insights for diagnostics — page requests, response times and errors. It is not linked to your cydjr.requestor identifier, and it does not record what you type into the track search box or the DJ Assistant.

Who is responsible for your data

The data controller is Mark Stott (DJ Mark), based in the United Kingdom. The quickest way to reach us about anything on this page is the contact form.

Why we are allowed to use it

We rely on legitimate interests under the UK GDPR. To run a request list at a dance event we need to know what was asked for, who asked for it, and that one person is not quietly filling the whole list. What we collect is no more than you would give a DJ walking up to the booth, and it is deleted shortly after the event.

The cydjr.requestor cookie is strictly necessary to provide the service you asked for, so it does not need separate consent. We set no advertising, tracking or profiling cookies.

Your rights

Under the UK GDPR you can ask us to:

• Tell you what we hold about you, and give you a copy of it;
• Correct it if it is wrong — a mistyped display name, for instance;
• Delete it, which for requests happens anyway within 48 hours of the event ending;
• Stop using it, or restrict what we do with it.

In practice these rights only apply while an event is upcoming or in progress. Once the 48-hour deletion has run there is nothing left to show you, correct or erase — so if you want us to act on a request, please get in touch before or during the event. Contact form emails are the exception: they stay in the mailbox until deleted, so you can ask about those at any time.

Ask through the contact form and we will reply within one month, and sooner where an event has not yet passed. Requests are only identified by a random browser identifier and the display name you chose, so tell us which event it is and the name you used — without both we cannot pick your requests out from anyone else's.

Complaints

If you are unhappy with how your information has been handled, please tell us first through the contact form — mark it as a privacy complaint and we will look into it and reply within one month. Most things are a misunderstanding or a mistake we can simply put right.

You do not have to come to us first, and doing so does not affect your rights. You can complain to the Information Commissioner's Office at any time, at ico.org.uk/make-a-complaint.