Privacy Policy – Juqed Go (iPhone & iPad)
As of: 1 November 2026 · This policy applies to the iOS and iPadOS app Juqed Go. It is intentionally written separately because the technical processing differs from Juqed (Mac).
Download as PDF (includes Legal Notice)1. Controller
The controller within the meaning of the GDPR for the processing of personal data within Juqed Go is the operator named in the Legal Notice.
2. Principle: hosted service, no local library
Juqed Go is an iOS / iPadOS application that uses Apple Music via Apple's official MusicKit framework. Unlike Juqed (Mac), Juqed Go does not process a local music library; playback streams directly from the Apple Music catalog. To allow host and guests to share an event across different networks (Wi-Fi, mobile data, mixed), the relay runs through a server in Germany operated by the developer (Hetzner Online GmbH, see Section 4).
3. What data is processed?
On the host device (iPhone / iPad) — by the app itself:
- Apple Music song identifiers (MusicItemID) of tracks suggested by the host or guests
- Cover, title, artist, album, and duration metadata returned by Apple's MusicKit API
- Vote counts of queue entries
- Playback history of the current session
- Blacklist terms and fair-use settings (stored locally)
- a random installation identifier in the device's keychain (see Section 6a)
From the guest device (smartphone / browser):
- A freely chosen display name (e.g. "Anna", "DJ Tom") — no real names required
- Search queries within the Apple Music catalog
- Song suggestions (MusicItemIDs) and voting actions
- An anonymous browser token used for fair-use logic (no personal reference)
No email addresses, phone numbers, location data, advertising IDs or Apple device identifiers are collected. Apple ID data stays with Apple. For the app's pseudonymous installation identifier see Section 6a; for the server logs see Section 4a.
Legal basis: processing is necessary to provide the service (Art. 6(1)(b) GDPR). For persistent configuration data (blacklist, fair-use settings), the operator's legitimate interest in providing a usable application also applies (Art. 6(1)(f) GDPR).
4. Relay server (Hetzner, Germany)
To allow host and guests to share an event across different networks, voting and queue data is relayed through the operator's server. This server is hosted at Hetzner Online GmbH (Industriestr. 25, 91710 Gunzenhausen, Germany); a data processing agreement under Art. 28 GDPR is in place. Transmission between app, server, and guest browsers is encrypted via HTTPS.
Stored on the server: only the data required to operate the event: event ID, the name and occasion of the event (if the host provides them), queue and history entries (MusicItemID plus the song's title, artist and genre — required to display the guest view), the suggesting guest's display name, vote counts, and event settings (e.g. blacklist terms). When the host ends an event, all event data is deleted immediately and completely. The figures of the usage statistics (Section 6a) and the event summary (Section 6c) remain. Events that are not explicitly ended are deleted automatically once the event validity expires (normally 7 days).
4a. Server log data when guests visit the event page
Unlike Juqed (Mac), where the guest interface is served only on the local Wi-Fi, the Juqed Go guest interface contacts the relay server over the public internet. When loading the guest URL and on every interaction (search, suggest, vote), server log data is generated by the Hetzner server, as is technically standard for any web service:
- IP address of the requesting device
- Date and time of the request
- Requested URL or API endpoint
- HTTP status code and amount of data transferred
- User agent (browser and operating system identifier)
- Referrer (previously requested page), if available
Purpose and legal basis: this processing is required to ensure technical operation, prevent abuse (e.g. DDoS, automated attacks), and analyze errors. Legal basis is Art. 6(1)(f) GDPR (legitimate interest in a stable, secure service). No further analysis (e.g. profiling, personalized advertising) takes place.
Retention period: server logs are kept for a maximum of 14 days and then automatically deleted or anonymized. They are not combined with other data sources. IP addresses are not used for marketing and not shared with third parties.
Cookies and similar technologies: the guest interface sets no cookies. It uses only the browser's Local Storage for UI preferences (display name, theme) and an anonymous session token for fair-use detection. No tracking pixels, no advertising IDs, no cross-device recognition is used.
Event URLs are not guessable: every event URL contains a cryptographically random event ID. Without the specific URL (via QR code or shared by the host), an event cannot be discovered. There is no public list of running events.
5. Apple Music — processing by Apple
Playback uses Apple's official MusicKit framework. Accordingly, Apple Inc. (One Apple Park Way, Cupertino, CA 95014, USA) processes data — in particular search queries, playback actions, and the host's Apple ID linkage — as an independent controller within the meaning of the GDPR. The operator of Juqed Go has no influence over this processing. Apple's privacy policy applies and is available at apple.com/legal/privacy.
Juqed Go transmits to the relay server only the catalog data of suggested songs required to display the queue (MusicItemID, title, artist, genre — see Section 4). The host's Apple ID, listening history and other Apple Music account data are not transmitted to the relay server and not shared with third parties.
6. Guest browser: no cookies, no tracking
The guest web interface uses no cookies and no tracking. It uses only the browser's Local Storage for UI preferences (display name, theme) and an anonymous session token for fair-use detection. This data does not leave the guest device (other than the token, used solely to limit duplicate submissions) and can be deleted by the guest at any time via the browser's settings. The server-side usage statistics are described in Section 6a.
6a. Usage statistics (server-side)
So that the operator can see how and for what Juqed Go is used, the relay server keeps a number of figures beyond the end of an event. They are derived from the event data (Section 4) while the event exists, and they remain when the event is deleted. This applies to events from the app as well as to events from Juqed Web.
Per event, stored under its random event ID:
- whether it ran in the app or in the browser (Juqed Web), and whether it was a Gold event
- the country of the music catalogue (Apple Music storefront, e.g. "DE")
- the occasion, if the host chose one (e.g. "Birthday")
- the Auto-DJ source that was set
- the number of songs played, broken down by who chose them (guest, Auto-DJ, host) and where they came from (Apple Music or own music files)
- the number of song requests from guests and of votes cast
- the number of guests who joined and the number of guests who requested at least one song
- the times at which the event was created and the last song was played
Across all events: the total number of events and countries, and the totals of votes, guest requests and songs added by Auto-DJ, carried forward per day.
Not in the statistics: guests' display names, the name of the event, search queries, song titles and artists, IP addresses, cookies and account data from Juqed Web.
Installation identifier (pseudonymous): When the app is first launched, it stores a random identifier in the device's keychain. It survives deleting and reinstalling the app and is not synchronised with other devices via iCloud. The server does not store this identifier, only a hash value derived from it with a secret key (HMAC-SHA256), together with: when the installation was first and last seen, how many events it has created, the first and latest app version, the system version reported by the operating system, and a yes/no flag indicating whether a request ever came from Apple's network (this identifies App Store review devices; the IP address itself is not stored for this). The purpose is to count how many devices use Juqed Go and how many events each one accounts for. No advertising ID and no Apple device identifier is used.
Gold events: For Gold events, the pseudonymous subscription transaction ID (Section 6b) is kept permanently together with the event ID and the time the event was created. This makes it possible to count how many subscribers hold several events.
Publication: Aggregated values from these statistics are published, among other places on juqed.com, for example the total number of song requests, votes and countries, breakdowns by occasion or country, and typical values per event (e.g. the median number of requests and guests per event). Individual events, event IDs and identifiers are not published.
Retention and legal basis: The data described in this section is kept permanently and evaluated only in aggregate, not per person. It contains no name, no email address and no Apple ID. To the extent it constitutes personal data – in particular the installation identifier and the subscription transaction ID – the processing is based on Art. 6 (1) (f) GDPR (legitimate interest in measuring the use of the service and reporting on it). (The server logs described in Section 4a are separate and are deleted after 14 days at the latest.)
6b. Juqed Gold (subscription) — subscription verification
For the optional "Juqed Gold" subscription, Apple handles the entire purchase (Merchant of Record); payment and account data remain with Apple. To link a Gold extension to an event and to prevent abuse, the app transmits the pseudonymous subscription transaction number (originalTransactionId) to the relay server. It is stored there together with the event; together with the event ID and the time of creation, it is kept permanently for the usage statistics (Section 6a). In addition, the server processes Apple-signed subscription status notifications (App Store Server Notifications) to detect expired or revoked subscriptions. The operator cannot derive the host's name, Apple ID or payment data from this. Legal basis: Art. 6 (1) (b) GDPR (performance of a contract).
6c. Event summary and recommendation question
During an event, the host receives in the app (or in Juqed Web) the address of an event summary that they can pass on to their guests. A summary is created per evening – a new evening starts after at least six hours without a song – and contains:
- the name of the event and the occasion, if the host provided them
- all songs played, with title, artist, time and origin (guest request, Auto-DJ, host)
- highlights of the evening, such as the song with the most votes
- the number of guests and songs and the length of the evening
- a counter of how often the page was viewed, without identifying visitors
Guests' display names and other guest identifiers are not included. Anyone who knows the address can open the page; the address is randomly generated, cannot be guessed and does not contain the event code. The page sets no cookies and includes no analytics. The summary is deleted automatically 30 days after the end of the evening; in Juqed Web the host can delete it earlier.
Recommendation question: At the end of the summary, guests and the host can voluntarily state how likely they are to recommend Juqed (0 to 10) and write a comment. Stored are the answer, the comment, whether it came from a guest or the host, the language of the page, the time, and the country, occasion and date of the event. No guest identifier or display name is stored with it. The answers are kept permanently, even after the summary expires; if the host deletes the summary in Juqed Web, the answers are deleted with it. Please do not write names or other personal details in the comment.
Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in offering the host and their guests a memento of the evening and in improving the service based on the feedback).
7. App Store — Apple as distributor
Juqed Go is distributed via the Apple App Store for iOS and iPadOS. Apple Inc. acts as Merchant of Record and processes payment, Apple ID, and update data as an independent controller. Anonymized crash reports (if the user has enabled "Diagnostics & Usage") are made available via App Store Connect for the sole purpose of bug fixing.
8. App Store — data categories (Privacy Nutrition Labels)
In accordance with Apple's App Store Connect requirements, the collected data categories are declared as follows:
- Data collected by the developer: only the event data required for operation on the relay server (Section 4; deleted when the host ends the event, at the latest when the event validity expires), technical server logs (Section 4a; 14 days), the figures of the usage statistics and the pseudonymous installation identifier (Section 6a), the event summary including answers to the recommendation question (Section 6c) and, with an active Gold subscription, the pseudonymous subscription transaction number (Section 6b).
- Data used to track you: none. The app contains no tracking, no advertising IDs, no cookies and no cross-device recognition.
- Data linked to you: none. The operator cannot link any of the processed data to a natural person; Apple ID and payment data remain entirely with Apple.
- Data not linked to you: the figures of the usage statistics and the installation identifier (Section 6a), the event summary including answers (Section 6c) and the operational event data (Section 4).
9. User rights
Since Juqed Go — apart from the data described in Sections 4a (server logs), 6a (installation identifier, subscription transaction ID), 6b and 6c (event summary) — does not collect personal data and the operator at no point receives data that he can link to a natural person, the typical data subject rights under Art. 15–21 GDPR cannot, in practice, be exercised against the operator. The host can uninstall the app at any time or remove app data via "Settings → General → iPhone Storage → Juqed Go". Guests can delete their browser's Local Storage at any time. For data protection inquiries, contact the email address listed in the Legal Notice.
10. Changes
This privacy policy may be adjusted in case of changes to the app or the form of distribution. The current version is available at juqed.com/en/legal/privacy-juqed-go.