Cookies and local storage
JukeDJ uses no advertising or analytics cookies and does not track you across websites. We store on your device only what the service needs to work. Such storage does not require your consent under the EU ePrivacy rules, so we do not ask for it.
Guest website – app.jukedj.com
The website sets a single cookie, jd (technical, no advertising or tracking; see the table below). It also uses the browser's local storage (localStorage, sessionStorage and IndexedDB):
| Name | Purpose | Kept |
|---|---|---|
jukedj.listener.v1 | The event you joined, your guest sign-in token and your requests, so you don't have to rejoin after reloading the page | Until you leave the event or clear browser data |
jukedj.device.v1 | A random browser identifier. The server stores only its one-way hashed fingerprint (for 48 hours), so the limit of free requests per guest and night also applies after rejoining from the same browser | Until you clear browser data. In case the browser deletes part of its data, we keep it in two places, localStorage and a tiny IndexedDB database (jukedj-device); the third copy is the jd cookie |
jd (cookie, set by our API at api.jukedj.com) | The same random browser identifier, only for the case that the stored copies disappear from the browser. It contains nothing but this random identifier, no name or other data. It is a first-party cookie (same jukedj.com domain), HttpOnly (the web page cannot read it), Secure, SameSite=Lax, and is sent only when you join an event | 7 days from the last join |
jukedj.listener-name.v1 | Your nickname for the next request | Until you clear browser data |
jukedj.language | Chosen language | Until you clear browser data |
jukedj.checkout.v1 (sessionStorage) | A payment in progress when you return from the payment page | Until you close the browser tab |
To pay, we send you to the Stripe payment page (checkout.stripe.com), which uses its own cookies under the Stripe Cookie Policy.
DJ web app – dj.jukedj.com
- Sign-in (Google Firebase): keeps the DJ signed in using browser storage (IndexedDB) until they sign out.
- Bot protection (Google reCAPTCHA Enterprise): checks that a real browser is using the app and may set Google's own cookies for this. See the Google Privacy Policy.
- App settings: language, email for the next sign-in and similar preferences.
Mobile app
The app stores on your phone a device identifier, your nickname, the last event code, the chosen mode and the DJ's email for the next sign-in. It does not store passwords. Uninstalling the app removes this data.
How to delete the data
Clear the site data in your browser settings or uninstall the app. The website and app will keep working; you will just need to rejoin the event or sign in again.
For more on data processing, see the Privacy Policy.