Who is responsible for your information
Wedding Jukebox is responsible for the personal information described in this policy. For privacy questions, rights requests or complaints, contact hello@weddingjukebox.app.
Wedding Jukebox
How Wedding Jukebox handles app, event and guest request information.
Last updated 6 September 2026Wedding Jukebox is responsible for the personal information described in this policy. For privacy questions, rights requests or complaints, contact hello@weddingjukebox.app.
Wedding Jukebox helps a host plan wedding music, securely synchronise event plans, control Apple Music playback and create a private guest request page for an event.
Hosts can enter wedding details such as couple names, event date, music moments, playlists, request settings and guest website options.
Guests can enter a display name or nickname, an optional note and a song request. Guests may make a separate, unticked choice to keep their name with that activity in the host's private Soundtrack keepsake. Without that choice, the name is used only to operate the event and the later keepsake says ‘Guest’. Where a table QR code is used, its verified table is associated with the temporary guest session so table context, duplicate voting and request limits can work.
If you join the launch list or contact support, Wedding Jukebox stores the details you submit so we can reply or send product availability updates.
When a host signs in with Apple, Wedding Jukebox stores Apple's stable account identifier and the email Apple first returns, which may be a private-relay address. Short-lived access credentials, rotating refresh credentials, device-verification challenges and privacy-minimised security events protect the account.
Signed-in hosts can synchronise event metadata, moments, playlists, cue references, settings, moderation state, played history, website configuration and Soundtrack keepsakes across devices. Imported audio files and device output settings are not uploaded; imported tracks must be relinked on each device. Wi-Fi poster credentials are encrypted separately.
The account portal provides device/session review, data exports, anonymisation and deletion. It does not provide browser-based editing of event plans.
The iPhone, iPad and Mac apps can connect to Apple Music so hosts can search playlists, select music and control playback. Apple Music account details are handled by Apple and are not stored by Wedding Jukebox.
The guest request website uses the event's host-selected Apple Music country or region to return song titles, artists, album names, artwork and content rating information. Each request records the country or region used to validate song availability.
Wedding Jukebox shares information only where needed to provide the service, deliver guest requests and Apple Music features, send support messages, maintain security or comply with law. Service providers that process personal information must protect it consistently with this policy.
Wedding Jukebox uses event, guest request and purchase information to provide the service requested by hosts and guests and to perform its agreement with a host.
It uses limited service, security, support and aggregate information where necessary for legitimate interests in operating, protecting and improving Wedding Jukebox. It uses information where needed to meet legal obligations. Launch-list and optional marketing messages are sent with consent, which can be withdrawn at any time.
Guest request pages store event settings, request history, votes, guest display names, opaque event-scoped session records and now-playing details needed to run the event. Table attribution is derived only from the table-specific QR link; guests cannot supply it themselves.
Guest access uses one secure browser cookie containing a random secret. The server stores only a keyed digest and keeps separate, expiring access state for each event. Raw IP addresses and full browser user-agent strings are not stored.
Wedding Jukebox may use existing event, request, vote and playback records to create aggregate operational statistics, such as active portal counts, request totals, vote totals, provider/theme breakdowns and top requested songs.
These admin statistics are used to monitor and improve the service. They do not show guest names, requester names, couple names, event titles, emails, IP addresses, user agents, host tokens, access codes, guest session IDs, purchase IDs, table labels or event slugs.
Wedding Jukebox may record first-party website events such as page views, button clicks and form submissions to understand product interest and improve the site.
Wedding Jukebox does not sell personal information, does not use third-party advertising SDKs and does not track users across other companies' apps or websites.
Some providers, including Apple and technical service providers, may process information outside the United Kingdom. Where data-protection law requires it, Wedding Jukebox uses an approved transfer mechanism or another lawful safeguard.
Wedding Jukebox uses Sign in with Apple, rotating sessions, Keychain storage, encrypted connections, protected local account data, time-limited live access, data minimisation, backups and operational monitoring to protect information. No internet service can guarantee absolute security.
Operational guest and session data—including guest/session identifiers, table links, device and moderation records, routing tokens, temporary logs and raw request rows—is deleted or irreversibly tombstoned 30 days after a portal has closed or expired, after the private Soundtrack keepsake has been materialised.
A Soundtrack keepsake may retain the requested song, votes, played attribution, minimal event timing and an optional note. Notes are retained independently of the guest's name choice. A guest name is retained only where that guest chose to keep it; otherwise the keepsake says ‘Guest’. Keepsakes remain private to the host account until the host removes the name or note, or deletes the guest, Soundtrack, event or account. They are never returned by public guest endpoints.
First-party marketing and launch-list records do not store raw IP addresses or full user agents. Short-lived anti-abuse network buckets use keyed, opaque identifiers. Deleted server data may remain in encrypted operational backups for up to 30 additional days before those backups age out.
Cloud event plans and keepsakes remain until the account owner deletes them. Account deletion removes cloud content and sign-in credentials, while retaining only a one-way Apple identity binding and the minimum pseudonymous App Store purchase ledger needed for billing, refunds and prevention of silent purchase transfer. A deleted account is not automatically reactivated. Local app data remains until the host uses Remove from Device, deletes the event, or deletes the app. Deleted server data may remain beyond use only until encrypted backups age out after 30 days.
Wedding Jukebox is designed for wedding hosts and is not directed to children. A guest page may nevertheless be opened by a guest under 18. Guest pages use high-privacy defaults, collect no age, location, raw IP address or advertising profile, and ask only for the limited information needed to request and vote on music. A parent, guardian or guest can ask for information to be removed by contacting hello@weddingjukebox.app.
Depending on where you live, you may have rights to ask for access to, correction of, deletion of or a copy of your personal information, and to object to or restrict certain uses. You may withdraw consent at any time without affecting earlier lawful use.
Contact hello@weddingjukebox.app to make a request. If you are in the United Kingdom, you may also complain to the Information Commissioner's Office at ico.org.uk.
Use the contact form or email hello@weddingjukebox.app and include Wedding Jukebox in the subject line.