Privacy Policy

Last updated: 1 November 2026

Jam Jam is built to respect you. The app works on your device and does not require an account. This policy explains the limited data involved when you choose to use the optional online features.

Who is responsible for your data

The controller of the personal data described below is Titouan Wattelet, sole trader, 173 rue de Courcelles, 75017 Paris, France[email protected]. Full publisher details, including the host of this website, are on the legal notice page. No data protection officer has been appointed: at this scale the GDPR does not require one, and the address above reaches a human. We answer in French or in English.

Your songs are yours

Your songbook, chords, lyrics and melodies are saved on your phone and stay usable offline. When you are signed in, they are also backed up to your private account space (including their playlists) so you can restore them on your other devices (web, Android and iOS) if you switch phones or reinstall the app, like a personal cloud drive. You choose what you import, create and publish there: Jam Jam distributes nothing of its own accord, and what other people can see is what you chose to publish.

What we store (only with an account)

• Email: used to sign you back in, to prevent fake accounts, and to write to you about your account, your content and your circle, under the rules set out in “Notifications and e-mails”. Any e-mail that is neither about your account nor required by law can be turned off in Settings or in one click from the e-mail itself. No e-mails about new features or offers without your consent, with a single exception: if you have paid for Premium, news about Jam Jam, which you can object to at any time.
• Profile: your chosen username and, optionally, an avatar (moderated for safety). Others can see those two things and any songs you make public, never your email. You can change your username or clear your avatar at any time, and stay anonymous.
• Activity: a “last active” date for optional newsletter preferences, and a device identifier to enforce one active session per environment (web and mobile can be signed in at once).

Signing in with Google or Discord

If you wish, you can sign in with your Discord account (provided by Discord Inc.), just as with Google or Apple. This is optional: the email code always remains available. If you choose it, Discord sends us only your identifier with that service, your display name, your email address and, if you have one, your profile picture. We use this data to authenticate you and to create or find your Jam Jam account: your name may at most appear as an example in the username field, and is never saved or shown to anyone without your confirmation; your profile picture may be offered to you as your Jam Jam picture, and is only copied to our servers if you accept it (see below). Legal basis: performance of the contract (Art. 6(1)(b) GDPR), namely the sign-in you request. This data is kept with your account and deleted with it. Jam Jam posts nothing on Discord, reads neither your friends nor your messages, and asks for no other permission. Discord handles your sign-in under its own privacy policy, as a separate controller: it is not our processor, and we send it none of your Jam Jam data. You can revoke Jam Jam’s access at any time from your Discord account settings; this does not delete your Jam Jam account, which you delete from the app or the account deletion page.

In the same way, you can sign in with your Google account. This is optional: the email code always remains available. If you choose it, Google sends us only your identifier with that service, your display name, your email address and, if you have one, your profile picture. We use this data to authenticate you and to create or find your Jam Jam account; your profile picture may also be offered to you as your Jam Jam picture, and is only copied to our servers if you accept it (see below). Legal basis: performance of the contract (Art. 6(1)(b) GDPR), namely the sign-in you request. This data is kept with your account and deleted with it. Jam Jam posts nothing on Google and asks for access to no other data in your Google account. Google handles your sign-in under its own privacy policy, as a separate controller: for this sign-in it is not our processor, and we send it none of your Jam Jam data. You can revoke Jam Jam’s access at any time from your Google account settings; this does not delete your Jam Jam account.

Suggested profile picture. When you sign in with Google or Discord and that service provides a profile picture, Jam Jam offers it to you as your Jam Jam profile picture. To show you the preview, your device downloads it directly from Google’s or Discord’s servers, before you have even decided: that service therefore receives your IP address, as with any image loaded from its servers. Until you confirm, nothing is copied to Jam Jam: if you decline or ignore the suggestion, the picture is neither saved nor used. If you accept it, a reduced copy (256 pixels, JPEG format) is saved in our storage hosted in the European Union and becomes your profile picture, exactly like a picture you had chosen yourself: it goes through the same moderation (Google Vision SafeSearch), it is visible to others like your username, even to a visitor without an account, unless you restrict it to your followers in the settings, and you can change or remove it at any time. Legal basis: performance of the contract (Art. 6(1)(b) GDPR), namely the profile picture you choose to use. Signing in with Apple provides no picture: nothing is offered to you in that case.

Ads

The mobile app (Android and iOS) shows no advertising: no banner, no full-screen ad, and no ad to watch in exchange for extra usage. It no longer shows Google’s ad consent form (UMP/TCF) or Apple’s tracking prompt (App Tracking Transparency), and it sends no data to Google AdMob or to any advertising network for advertising purposes. The Google Mobile Ads (AdMob) software library is still bundled in the app so that advertising could be switched back on one day, but it is switched off: it is not initialised, sends no request, and no advertising identifier is collected or shared. If advertising were ever switched back on in the app, this policy would be updated first and the consent form would be shown again before any ad request. This website and the web app show no advertising either. This website uses no third-party tracker or analytics tool, and loads no third-party script unless you explicitly ask for one (see “What your browser stores”). To show it in your language, the site detects your approximate country from your IP address via a self-hosted offline database: no third-party service is contacted and your IP is never stored. IP geolocation by DB-IP (CC-BY 4.0).

The official YouTube player is a separate optional service: its own ads may appear in the web and mobile apps, including for Premium accounts.

What your browser stores

This website stores a handful of values in your browser, all of them strictly necessary except one (the random session identifier of the audience measurement, described in the section “Audience measurement on this website” below) and none of them used for tracking or advertising: your chosen language and your light/dark theme, so the site opens the way you left it; a marker recording that we already redirected you once to your language, so we do not do it again; and, only if you sign in, your session, so you stay signed in. There is no advertising or analytics cookie on this website, and no third-party script is loaded by default. The content security policy allows an optional service on the public website, only after you ask for it: the Trustpilot review form, on the home page. It stays dormant behind a button; before you press it, nothing at all is requested from Trustpilot. It sets no cookie and writes nothing to your browser. We measured this, but once loaded it does tell Trustpilot your IP address, the page you are on and your browser’s language, which Trustpilot uses for its own audience statistics. Trustpilot A/S is established in Denmark, inside the European Union: this is not a transfer outside the EU, Trustpilot is not one of our processors, it acts as its own controller, and its own privacy policy governs what you write there. The plain link to Trustpilot, next to that button, loads no script whatsoever. The strictly necessary items are exempt from prior consent; the measurement identifier is covered by the section mentioned above. Clearing your browser data removes them all.

Jam Run without an account. If you play Jam Run without signing in, your progress (levels, scores, mascot items and outfit, game preferences) stays in your browser; if you sign in later, your account takes it over and it is then erased from the browser. The game also keeps in your browser a log of your last 100 attempts judged through the microphone (measurements derived from the sound around each strum, such as level and recognised notes, the verdict and the reason for a refusal, the instrument, the date), without any audio recording: it is never sent, and only leaves your device if you export it yourself from the game options. Clearing your browser data removes both.

Audience measurement on this website

This website measures its own audience, to know which pages are read and how many visitors leave a page without opening the app or clicking through to an app store. We do it ourselves, on our own server, with no cookie and no third-party service. When a page is displayed, and when you click a link to the app, Google Play, the App Store or TestFlight, your browser sends a short message to jam-jam.org: the page (without anything after the question mark in its address), the page language, the website you came from (its domain name only), the source, the placement type and the campaign of the link you arrived through, when it carries them (for example alternativeto, listing, evergreen; never the rest of its address), the button you clicked and a random session identifier. That identifier stays in your tab’s memory (sessionStorage), disappears when you close the tab, is not derived from any data about you or your device and does not link two visits. When the site redirects you to your language, the domain name of the website you came from and the source, placement type and campaign of the link (nothing else) are also kept in your tab’s memory for that single redirect, then erased as soon as they have been used. If you open the web app from this site, the source of the link you arrived through is also kept in your tab’s memory (sessionStorage) until you close the tab, and added to the links to the app so that the app can credit your arrival. Our server log also keeps your country (inferred from your IP address by our network provider) and your browser type, but never your IP address, which is removed from this log. The log is erased after 14 days. Each hour it is reduced to daily statistics (per page, language, origin, source, placement type, campaign, country and device type) that contain no identifier and are kept for 25 months in our database hosted in the European Union (Supabase). Nothing is matched with your account or passed to a third party. Legal basis: our legitimate interest in knowing how the site is used (Article 6(1)(f) GDPR); this measurement, limited to anonymous statistics, is exempt from prior consent. You can object at any time, without giving a reason: turn on “Do Not Track” or Global Privacy Control in your browser, or turn off Usage statistics in the web app settings on this browser, and the site sends nothing at all. You can also write to [email protected].

Purchases

Optional Premium subscriptions and the lifetime purchase are processed by our payment providers: Google Play Billing (in-app on Android) and Stripe (for direct purchases on jam-jam.org). Your card details are handled by these processors and never stored by Jam Jam.

So that a free trial is granted only once per person, we check with Stripe whether your e-mail address has already had a Premium subscription. Legal basis: our legitimate interest in preventing trial abuse (Article 6(1)(f) GDPR). This check uses the billing data that Stripe keeps for 10 years; no other data is created.

Where data is stored

Account data is hosted on Supabase (EU region) with row-level security, so you can only ever reach your own data. The website itself is served from a machine rented in France from OVH. Beyond those two, exactly five processors act on our instructions, and no other: Resend sends your sign-in codes and account e-mails (it therefore receives your e-mail address); RevenueCat reconciles your subscription across stores (an account identifier and a purchase status); Stripe and Google Play Billing take the payment; and Google Vision SafeSearch moderates avatars, on the uploaded image only; finally, Expo routes push notifications: it receives your device’s push token and the content of each notification, and hands them to your phone’s notification service, Apple Push Notification service on iPhone or Google Firebase Cloud Messaging on Android, which use them only for that delivery. None of them is allowed to use your data for its own purposes. One exception, for the optional AI music detection feature only: an external analysis provider receives the audio or the link you submit; it is presented, with its terms, in the section “AI-generated music detection (external provider)”.

Transfers outside the European Union

Your songbook, your profile and your account stay in the European Union. Five of the processors above are established in the United States, so a transfer does take place when they are used, and only what each one needs: your e-mail address to Resend, an account identifier and a purchase status to RevenueCat, your billing data to Stripe, the avatar image to Google Vision, the push token and notification content to Expo and, through it, to Apple or Google, which deliver them to your phone. Those transfers rely on the European Commission’s standard contractual clauses and, where the provider is certified, on the EU–US Data Privacy Framework. The web lookups described under “Online correction” are not transfers of personal data: nothing that identifies you accompanies them. The AI music detection provider is not part of this count: its policy does not say in which country it processes audio, so we cannot announce a transfer mechanism to you; this sending is optional and takes place only if you submit a track to that tool.

Voice dictation and following lyrics by voice (web app)

Two optional features of the web app use the speech recognition built into your browser (Web Speech): dictating lyrics in the song editor, and following the lyrics by voice in the reader, which scrolls the song along with what you sing. They only start when you press their microphone button, and stop when you turn them off or leave the page. In Google Chrome and Microsoft Edge, the only browsers where they are offered, recognition generally runs on the servers of the browser’s publisher (Google or Microsoft): while listening, your browser sends them the sound from your microphone and receives the recognised text. That service belongs to your browser’s publisher and is governed by its own privacy policy; it may process this sound outside the European Union. Jam Jam never receives this sound and has no agreement with that service: the web app only receives the text, which becomes your lyrics as if you had typed them (dictation), or is only used to find the line being sung and is not kept (following by voice). To avoid it, simply do not use these two features: type your lyrics, and scroll the song by hand or with auto-scroll. In Safari and Firefox, they are not offered. The tuner, live detection and the microphone in Jam Run analyse sound only on your device and do not use this service.

Analysing an audio file on our server

Analysing an audio file (chords, rhythm, lyrics) runs either on your device or on our server. This is true of the mobile app as well as the web app, and you are the one who decides. The setting lives in Settings → Listen & detect → “Where audio analysis runs”, and it has three positions. On my phone: nothing is ever sent. Online: the analysis is handed to our server. Depending on my connection, the default: in the mobile app, the analysis goes online when you are on Wi-Fi or a wired link and the connection answers properly, and stays on your phone in every other case (no connection, mobile data, slow link, server unreachable, saturated, or unable to perform the requested analysis); in the web app, the analysis goes to our server only when it is free (nobody is waiting), your file is under its size limit and you still have server analyses left (Premium subscribers go ahead of the queue), and otherwise it stays in your browser, which sends nothing. The app always shows where the computation is happening, and you can switch from one side to the other while it runs.

When the analysis runs on our server, what is sent is the audio file itself, dropped into a queue shared by the mobile app, the web app and our API: only one of your uploads is processed at a time, up to 50 pending uploads per account, and the processing keeps running even if you close the app or your browser. The result is there when you come back.

The file is received in a private work area hosted in the European Union (Supabase, EU region), before being converted and analysed by our own machine rented in France from OVH (100 MB and 12 minutes of music at most). It is deleted as soon as the processing ends, and at most after 72 hours, whether the processing succeeded, failed, was cancelled, or was never picked up: those 72 hours bound how long the work can wait, never a retention of the audio itself.

The result of the analysis (chords, tempo, sections, synced lyrics) is, by contrast, saved in a separate table hosted in the European Union, readable by you alone: unlike the audio file, it is no longer erased after a few minutes, it is kept for as long as the song and your account exist, so you can find it again without running the analysis a second time. A “Your analysis is ready” notification tells you when it is available; it is on by default and can be switched off in Settings → Notifications. Lyric syncing runs automatically right after the analysis when the song has lyrics; the sync button then only serves to retry after a failure, for free.

Separation of vocals and instrumental. When an audio file is added to a song in your songbook, Jam Jam automatically separates the vocals from the instrumental. This processing runs on our own machine rented in France from OVH, starting from the audio already stored in your private space hosted in the European Union (Supabase, EU region); no processor is involved and no data is sent to any third party. The working file of the separation service is erased a few minutes after processing ends. The two resulting tracks (vocals and accompaniment) are derived copies of your file, stored in your private space: they are treated like the audio of the song they come from (readable by you alone, and by mutually-following accounts only if you publish the song), kept for as long as the song and your account exist, and deleted along with them. This separation is a processing of your own audio necessary for the app to work (Article 6(1)(b) GDPR); it costs you no quota. The “Separate vocals” button remains available in the player for a separation made on demand. To delete these tracks, delete the song, or write to [email protected].

Legal basis: your consent (Article 6(1)(a) GDPR), given through the setting above. This upload is optional and never silent: the screen states where the analysis is running before and during the processing. You can refuse: choose “On my phone”, and no audio file will leave for an analysis again. The feature still works, it is only slower and your device warms up more. You can also refuse upload by upload, by cancelling it while it waits or while it runs. Withdrawing your consent stops any new upload; the result already obtained, though, stays kept for the durations described above, until the song or your account is deleted, or on request to [email protected].

Exporting your karaoke as a video (optional)

From the mobile app as well as the web app, you can ask for a video of your karaoke. The editing is done by our server, in France, on our own machine: your soundtrack is therefore sent to jam-jam.org for the time it takes to make the video. Along with the optional server analysis described above, it is one of the two features that send an audio file off your phone, it never leaves on its own, and the screen says so before the first byte goes out.

Legal basis: your consent (Article 6(1)(a) GDPR). Nothing is sent unless you started the export, export by export; not starting one has no consequence anywhere else in the app. What goes up: the song’s audio file, the time-stamped lyrics and the chords that make up the picture, and your display settings. What does not go up: your songbook, your email address, your username. An export requires an account (that is what carries your export quota); the server then receives a derived, non-reversible identifier, used only so that two people are never served each other’s video.

Retention, and three rules decide it, whichever comes first: the finished video is deleted 24 hours after you asked for it, one hour after you first download it, or as soon as a fourth export replaces your oldest: we keep at most three exports per account. The audio file you sent is erased as soon as the editing ends, whatever happens (success, failure or cancellation), and cancelling an export erases the video straight away. That video contains a copy of the sound track: that is why these limits exist, and why they are short. Rendering happens on our own server in France; no processor is involved, nothing is logged, and nothing is ever used to train a model.

Detection error reports (opt-in audio)

This is the only case in which we keep one of your audio files beyond your own songbook, on our own initiative and to improve our model: the optional server-side analysis described above keeps only its results (chords, tempo, lyrics) and, for the separation of vocals, the two derived tracks described above. If you report a detection error and explicitly tick the consent box, the analysed audio and its detection results are uploaded to your private space on our EU-hosted infrastructure (Supabase, EU region) and kept for up to 90 days to improve our detection model, then deleted. That box is never pre-ticked; without your consent, no audio of yours is ever stored by us.

Online lyric and chord search (optional)

Chord detection and lyric transcription run on your device or on our server, according to the setting described above. Whichever you pick, the option below is a separate matter: it never sends audio. If online lyric and chord search is enabled (on by default. It is presented during onboarding and can be turned off there, or at any time in the settings), Jam Jam can query a search engine and lyrics sites to find or complete the lyrics and chords of your songs, both during an audio analysis and from your songbook. In that case only anonymous text metadata is sent. The song title, the file name and short lyric excerpts. To third-party services (MusicBrainz, a web search engine and Wikipedia). Your audio is never sent, and no user identity or account information is attached. You can turn this option off at any time; when it is off, no online lookup ever happens. The web search goes through DuckDuckGo, and the lyric or tab pages it points to are then read, a handful at most per analysis. In the web app those requests first go through our own relay on jam-jam.org (browsers cannot call those sites directly): we therefore see your session at that moment, but nothing about you is passed on to DuckDuckGo or to the sites consulted. Legal basis: our legitimate interest in finding and completing the lyrics and chords you ask us to look up. Which is precisely why the option can be switched off in one tap, at any time, without losing anything else in the app. Because none of your identifiers travels with these lookups, MusicBrainz, DuckDuckGo and Wikipedia cannot attach them to you.

Converting a file

Some formats cannot be read on your phone or in your browser: a photo or PDF of sheet music, a scanned songbook, a video, or any format that needs one of our own conversion engines. In those cases, on mobile, on the web and through our API, the file itself is sent to our own conversion service at jam-jam.org, running on our machine in France. It is never sent to a third party. The source file is deleted the moment the conversion ends; the result is kept for at most 24 hours, so you can still collect it if you closed the app, then it is erased too. Nothing is attached to your account unless you choose to import the result, and it is never used to train a model. If you would rather nothing left your device at all, import the melody another way: MIDI, MusicXML, plain text, or by playing it. For stem separation, the source audio is temporarily stored in private Supabase storage in the EU while it waits and is processed. The separated tracks and ZIP remain available there for up to 24 hours after processing. For signed-in users, the history retains the file name, duration, model, processing time and status until account deletion; it does not retain the audio itself.

Every conversion, whether started from an account, anonymously or through the API, adds one line to a technical usage log: the pair of formats involved, the size of the file, how long the computation took, the platform and, if you are signed in, an account reference. Never the file name, its content, an online address you submitted, or your IP address. This log lets us know which conversions are used and where they fail; it is kept 90 days.

This conversion tool is also available on our website without an account, within a limit of 3 conversions per rolling 24 hours. To enforce that limit without creating an account for you, our server computes an irreversible, salted hash of your IP address (salted with a key that changes every day), a technical fingerprint of your browser and a token stored in your browser, keeps only the most restrictive of the three, and deletes it after 48 hours. Your IP address, your fingerprint and that token are never stored in clear and never linked to an account. Legal basis: our legitimate interest in preventing abuse of a feature open without an account. Past that limit, a one-off Cloudflare Turnstile challenge may be shown before you can try again; it runs in your browser and is not used to profile you.

Usage counter of your API keys. For each API key of your account, we keep a counter per day: the number of calls, the number of errors, the number of jobs submitted and the time of the last call. No IP address, no online address and no content you send is kept. This counter is visible only to you, as the account holder, in your API key settings, and it lets you see how your keys are used. It sets no limit of its own. The rows are deleted after 90 days, including for a revoked key, and together with your account if you delete it.

If you use this conversion service through our public API, you authenticate with a personal API key that we never store in clear: only its irreversible hash and the date it was last used are kept, so you can tell whether it is still active and revoke it at any time from your account.

Separating a track into stems (on-demand tools)

Two tools separate a track into stems, only when you start them: “Remove vocals” (page /app/vocal-remover, vocals and instrumental) and the stem splitter (page /app/stem-splitter, two or four stems). The first sends your audio to the separation service on jam-jam.org, the second to our conversion service. In both cases the computation runs on our own machine rented in France from OVH and no analysis provider receives your audio (the stem splitter only places its working file with Supabase, our European Union host, as explained below). Both also open without an account, with lower limits.

“Remove vocals”. What is sent: the audio file (exactly as you chose it, under the neutral name “audio”), never your file name. If you are signed in, your session token accompanies the request so that the service can check your account with Supabase; it is neither kept nor logged. From your account identifier (or, without an account, your IP address) the service derives an irreversible fingerprint, kept for the duration of the task, used only to allow one separation at a time per person. The service’s technical log contains no IP address, no token and no file name.

Retention. The file you send is kept only while it is being processed and, in every case, never more than 30 minutes after the upload; it is also erased if the separation fails or is cancelled. The two resulting tracks remain retrievable for 15 minutes after the computation ends (and 30 minutes at most since the upload): your browser downloads them and then asks for their immediate deletion. So as not to compute the same track twice, the service also keeps a copy of the two tracks for 7 days at most (10 GB in total at most; beyond that, the oldest go first). This copy is attached to no account and no address: it is identified only by the fingerprint of the original file and is returned only to a new upload of the exact same file.

Legal basis: performance of the service you request (Article 6(1)(b) GDPR) for the separation itself; our legitimate interest (Article 6(1)(f) GDPR) for the fingerprint that limits you to one separation at a time and for the 7-day computation copy. Not using these tools has no other consequence. For any request on this subject, write to [email protected].

Stem splitter. Processing is done in one-minute slices, which may wait their turn: your file is therefore placed, while it waits and while it is computed, in a private Supabase storage space hosted in the European Union (no public access; download addresses are signed and valid for 1 minute at most). It is deleted from there as soon as processing succeeds, fails or is cancelled. The tracks (MP3), the ZIP archive and the description file remain downloadable for 24 hours after processing ends, then are deleted. Without an account, your limits (1 separation per day, 3 per month, 5 minutes of audio at most) rely on a random token kept in your browser (local storage and a functional cookie lasting one year) and on irreversible fingerprints of your IP address and, if your browser provides it, of its technical fingerprint, never the plain address. With an account, a history entry (file name, model, number of stems, state, dates, duration, computing time), without the audio, is kept in your private space until your account is deleted. Without an account, this entry, which holds only fingerprints and never your connection in the clear, is deleted 90 days after processing ends (90 days after creation if the task never ended). Legal basis: performance of the service requested (Article 6(1)(b) GDPR); our legitimate interest (Article 6(1)(f) GDPR) for the usage limits without an account.

Separation on your device. The stem splitter (page /app/stem-splitter) and Advanced Mastering (when you separate a finished song into stems there) first run the separation in your browser, on your device’s graphics processor (WebGPU). In that case your audio file stays in your browser and nothing is sent: neither the file, nor its name, nor its content. The separation model (htdemucs) is downloaded from our own site (jam-jam.org) the first time and then kept by your browser: that download contains none of your data. Only if your device cannot run the computation, or cannot complete it, and you are signed in to an account, is the separation relayed to our server; the description of the stem splitter above then applies, and only in that case. Without an account, nothing is relayed: the tool tells you that your device is not supported or that the computation failed. In Advanced Mastering, separating a finished song requires a free account: without one, nothing is sent and the tool invites you to create an account or to drop your own stems.

Counting separations run on your device. So that the daily and monthly limits are the same whether the computation runs on your device or on our server, your browser tells our service, without any audio, that a separation is starting. With an account, the service records against your account a counter per day and per month, together with a random request key generated by your browser for that separation and the duration of the track. Without an account, the count relies on the anonymous signed token kept in your browser, of which the service keeps only an irreversible fingerprint (not that of your IP address). This record holds no file name and no content. For a visitor it is deleted 90 days after the separation; for an account it is kept as long as the account exists and is deleted with it. Advanced Mastering applies the same count, but separating a finished song there requires an account: the anonymous token therefore concerns only the stem splitter.

Device diagnostic. Only if a separation (in the stem splitter or in Advanced Mastering) fails, if your device is not supported, or if the separation is relayed to our server, a minimal summary of your device is added to the corresponding usage event (see “Usage measurement and crash reports” below): browser and major version, operating-system family, device class (computer, phone or tablet), WebGPU available or not, software graphics adapter or not, and memory in brackets, never the exact amount. Never a file name, never any content, and nothing of the kind when the separation succeeds. These events follow the rules of the usage events described below, including the Usage statistics switch, and are kept 90 days.

Legal basis: our legitimate interest (Article 6(1)(f) GDPR) in keeping the service reliable (understanding why a separation fails or cannot run on a given kind of device) and in protecting it against abuse (the limits above). You can object to the device diagnostic by switching off Usage statistics; for any request on this subject, write to [email protected].

AI-generated music detection (external provider)

AI music detection (page /app/ai-music-detection, mobile app and API) analyses a track to look for signs of AI generation. What you submit: an audio file (dropped in, or, from the mobile app, recorded with the microphone after a gesture of yours and erased from the device once sent) or a link (a Spotify link or identifier, an ISRC code, the direct address of an audio file; YouTube is not supported). Nothing is analysed unless you have submitted it.

The file first arrives on our server in France (OVH). It is then analysed by our provider, SH Labs (detection service shlabs.music), an external recipient: for a file, we make it available to the provider at a random, temporary address (valid for 3 minutes at most, closed as soon as the call ends), under the generic name “audio”; for a link, the link or identifier is passed on as it is and the provider fetches the track itself. The title written in the file’s tags, however, stays in the bytes sent.

SH Labs states in its own policy (shlabs.music/privacy, version of 30 June 2026) that audio is processed in memory and then discarded, that it is neither kept, sold nor used to train a model, and that no person listens to it; that it may keep a result (the scores, not the audio) for up to 24 hours to answer an identical request quickly; and that its request logs are deleted after about one month. These are its commitments, not ours: we report them without being able to verify them. It relies on cloud computing providers and, for a Spotify link or an ISRC code, on music resolution services; its policy does not say in which country its servers are located.

On our side, the file is kept only for the time of the analysis: it is erased when processing ends, whether it succeeds, fails or is cancelled. If the provider is unavailable, a file (not a link) may be analysed on our own machine, with no sending to a third party, when that fallback is enabled. With an account, a history entry stays readable by you alone for 90 days: the file name (or the title read from its tags) or the submitted link, the date, the state and the result, never the audio; you can delete it, and it disappears with your account. Without an account, the result is readable for only 24 hours. Usage limits (visitor: 2 per day and 5 per month; free account: 5 per day and 50 per month; Premium: 30 per day and 300 per month) are counted per account or, without an account, with a random token kept in your browser’s local storage and an irreversible fingerprint of your IP address, renewed every month, never the plain address; these counters are erased at the end of the month.

Legal basis: performance of the service you request (Article 6(1)(b) GDPR); our legitimate interest (Article 6(1)(f) GDPR) for the usage limits and their fingerprints. Sending is optional: no audio goes to this provider if you do not use this tool, and no other Jam Jam feature sends it any. Because its policy does not say where it processes audio, we have no guarantee of location and no transfer mechanism to announce to you at this time: if that matters to you, do not use this tool. For any request, write to [email protected].

Import improvement statistics

When you import a song or a melody, Jam Jam records one anonymous line to find out where imports break: the kind of source (link, PDF, photo, file, paste…), whether it succeeded or the reason it failed, the bare host of the online source (for example ultimate-guitar.com, never the full address), the number of songs produced, the app version and your interface language. Nothing else: no account, device or session identifier, no file, no lyrics, no chords, no file name. These lines are not linked to any user and are deleted after 180 days. Legal basis: legitimate interest in keeping the import engine working. You can switch this off at any time, for free and with no effect on the app, in Settings → Songbook, or in the app’s Privacy screen.

When importing by a link that fails, we additionally keep, in a separate technical table, the minimised address of the failed link (identifying or tracking parameters removed before it is sent), together with its host, the kind of source, the platform and the failure code. As with the line above, this entry is never linked to any account, device or session: no such column exists. It exists only so we can replay a specific case and fix the adapter that fails on a given site. Kept 90 days, then deleted automatically. Same opt-out as above.

Reports and anomaly reports

When you report a problem from the app or the web app (always a voluntary action, and one that requires being signed in) a diagnostic context is automatically attached to your report so that it can actually be acted on. None of it is collected outside a report you trigger yourself.

• What you tell us: the kind of problem, the boxes you ticked and, if you write one, your free-text message. That message is sent exactly as you wrote it, so please do not paste sensitive information into it.
• The build you are running: the app version, the platform and its system version, the brand and model of the device (never the name you gave it) or, on the web, your browser and its major version plus the screen format, where the install came from (the name of the site you arrive from, for example a search engine or an assistant, never the full page address), the interface language, the light/dark theme and the interface scale.
• Where the problem is: the screen or page you are reporting from, the element you pointed at (a chord, a diagram, a sound, at most a single line of lyrics) and the settings of the feature involved (instrument, capo, transposition, style… and, on the web, the size of the browser window).
• The state of the app: whether you were online or offline (and, on the web, the connection type reported by your browser), the date of the last successful songbook sync, how many uploads were still pending, how long the app had been open, and your account tier (standard, premium, beta, admin).
• A technical trace: the list of the last screens you visited, the error message if there was one, and the last 80 lines of the app’s technical log.
• Triage markers: the send date, how many taps it took you, and a technical fingerprint used to group identical reports together.

Screenshots. On mobile, the quick report (long-press an element, then pick a symptom) sends no image at all. Only the detailed form attaches a picture of the screen as it was at the moment of your gesture: it is shown to you as a thumbnail and can be removed with one tap before you send. No image ever leaves your device without having been shown to you, and the capture is refused outright on sign-in, verification-code and payment screens, or whenever a password field is on screen. In the web app nothing is captured automatically: only an image you attach yourself is sent.

The technical log is filtered on your device before it is sent: session tokens, API keys, authorisation headers, passwords, email addresses and phone numbers are replaced by a marker. Including when they are split across two lines. The same filter is applied to the settings attached to the report. It deliberately errs on the safe side: better to erase something useful than to let something leak. Your free-text message, by contrast, is transmitted as written.

The following is never sent with a report: audio from your microphone (the one exception being the detection error report described above, with your explicit consent), the full lyrics of a song (at most one bounded line, the one exception being the detection error report described above, with your explicit consent), the list of your songs or your songbook, your email address, username or avatar (we reach you through your account), your location, an advertising identifier, your contacts, the content of your conversations with other accounts, and (on the web) your browser’s full identification string, your extensions, your installed fonts or the content of your input fields.

Retention. The diagnostic context is erased 90 days after the report is sent, or 30 days after the report is processed if that comes sooner. Concretely, what is erased on that clock is the technical trace, the app state, the device model, the system version, where the install came from and your interface language: everything that describes your phone rather than the problem. Attachments (screenshots and images) are deleted 30 days after the report is processed. What survives is the report itself and only the report: your description, its category, the screen concerned, the platform, the app version, and the follow-up. Kept for as long as your account exists so you can read the answer, and deleted together with your account. Legal basis: your consent, given by voluntarily sending the report, and our legitimate interest in fixing defects in the app. To have a report deleted sooner, write to [email protected].

Beta programme: measurement bench

If you are a beta tester, you can start a measurement bench from the app settings: a short series of automated tests, 5 to 10 minutes, run only on audio and text files we supply ourselves. Never on your songbook. Its purpose is narrow and it is the only one: detecting defects specific to each phone model (which chord engine actually loads, what transcription really costs on an older device, how the screen behaves). A bench that only ever runs on the developer’s handset only ever measures the best case. It never starts without your explicit consent, it is never proposed to anyone outside the beta programme, and no box is ever pre-ticked.

When the run ends, a report is sent through the ordinary reporting channel, so it is attached to your account and hosted on Supabase (EU region). Its content is a closed list, built field by field, not “the whole report minus what we thought to remove”. Exactly these twelve items leave your phone:

• the commercial model of the phone (e.g. “Google Pixel 6a”);
• the Android version;
• the processor architecture (e.g. “arm64-v8a”);
• the screen dimensions and its density;
• the version of Jam Jam installed;
• a random campaign identifier, its duration and its verdict;
• which test ran, on which file from our own corpus;
• the outcome of each test: completed, failed, timed out, not run;
• the durations measured, stage by stage;
• the thermal state of the phone and the processor throttling;
• the numeric quantities measured (real-time ratios, recognition rates…);
• on failure, an error category: never the message itself.

And here is what, explicitly, never leaves your phone with a bench report:

• the app’s internal log;
• the titles, lyrics or chords of your songs;
• not a single screenshot: the screen-capture scenario is banned by name from the beta bench, because no whitelist of fields protects an image;
• your username, your email address, your avatar;
• your location, your address book, your files;
• any advertising identifier or device identifier.

Legal basis: your consent (Article 6(1)(a) GDPR). Deliberately not legitimate interest: this measurement is in no way necessary to provide the Service, and refusing it changes nothing about what Jam Jam does for you. Purpose: detecting defects specific to each phone model, and nothing else. Retention: a bench report is kept at most 180 days, then deleted. Withdrawal: you can withdraw your consent at any time from the app settings. The effect is immediate. Consent is re-read from storage just before any upload, so a withdrawal made during a run also cancels the upload of that run, and nothing more leaves your phone until you grant it again. To have reports already sent deleted sooner, write to [email protected].

Usage measurement and crash reports

To know which tools actually get used and where the app breaks, Jam Jam records usage events: the mobile app and the web app send them to our own infrastructure, hosted in the European Union (Supabase, EU region). No third-party measurement tool is involved, nothing is sold or shared, and none of it is used to target advertising at you. The only things derived from it are a basic usage profile, which chooses the timing and topic of your notifications, and a count of the days you opened the app, which sets the timing of an invitation to leave a review: both are described under “Notifications and e-mails”, together with how to object to them.

What gets recorded fits into three closed categories, picked in advance from a list written into the code: the screens you open and the time you spend on them, the actions you trigger (opening a song, starting an analysis, creating an account…), and the technical errors you run into. Each event carries a name taken from that list, the platform, the app version, the interface language, a session identifier and, on the web, the device type (phone, tablet or computer) and the operating-system family (Windows, macOS, Linux, ChromeOS, Android, iOS or other), worked out locally by your browser: the User-Agent itself is never sent. Never any free text: no song title, no lyrics, no chords, no file name, no full address, no search term. The values attached to an event are themselves picked from closed lists or rounded into brackets.

Jam Jam works without an account, so the measurement exists before there is one. It then relies on a random install identifier, generated locally on your device or in your browser, which contains nothing about you. We would rather write this plainly than let you find out later: if you then create an account, the history carried by that identifier is attached to that account. That is what lets us understand the path that leads to a sign-up, and it is also why this data leaves with your account when you delete it.

Once you are signed in, these events are attached to your account. They are therefore part of your data export (Profile → Export my data) and are deleted with your account, including the ones recorded before it existed, for the installs linked to it.

Two pieces of information come from your connection and deserve a precise description. We derive a two-letter country code from your IP address (for example FR), to know where the app is used from: the IP address itself is neither kept nor attached to the events, only the country code is. And because a sending channel open without an account can be flooded, an anti-abuse quota relies on an irreversible fingerprint of the IP address, short-lived, used only to count submissions and never matched against the events.

Retention: the event detail is deleted after 90 days; sessions are kept for 400 days, because it takes a full year to know whether people come back. Aggregated usage statistics are kept with no time limit; beyond 24 months, they no longer contain any identifier. Until then, the daily activity summary stays tied to the random install identifier (and is deleted with your account if you create one), while the anonymous daily totals (numbers, screen names, platforms and versions: no identifier, no account, no install) survive the deletion of your account, because they no longer describe anyone.

Legal basis: our legitimate interest (Article 6(1)(f) GDPR) in knowing what is used and what breaks in our own app. That is why the measurement is on by default, and why opting out has to be simple: the Usage statistics switch sits in the mobile app (Privacy screen) and in the web app (Settings → About, help and privacy). It is free, tied to no subscription, available without an account on both sides, and takes effect immediately: nothing further is sent from that moment on, within the current session. Rows already recorded expire on their own schedule; to have them deleted sooner, write to [email protected].

Jam Run. The game adds its own events to that closed list: opening the game, first jump, start and end of a level (outcome, level, difficulty, instrument, input and the share of chords hit, rounded), missed chords (the chord, the reason and a count rounded into brackets), mascot items unlocked or worn, opening the feedback form and time spent on a game screen. No named score, no leaderboard and no sound: no audio and no signal from the microphone or the MIDI keyboard is included. Same retention and same switch as above.

Reviewing Mastering and track-separation use. In the administration area, the Jam Jam team looks at the use of the mastering and track-separation tools account by account: the number of simple masterings, the number of advanced mastering projects, the number of separations run on our servers, the number of separations run on your device (completed, failed or cancelled), and the dates of first and last use. The team also looks at a funnel with no names at all: how many distinct people opened the mastering page, started a mastering, downloaded a separated track or the final file. Purpose: to understand how Mastering is used so we can steer the product, and nothing else. These are counters and dates: never the content of your files, their titles or file names, or your IP address.

Who sees this list, and how to leave it. Only Jam Jam administrators can read it, in the administration area. It does not include accounts that have switched off the Usage statistics switch (the same switch as above), administrator accounts, or visitors without an account, who are never listed individually. Simple masterings and separations run on our servers are counted from the ledger that enforces their limits, kept for 40 days; everything else comes from the usage events described above (detail kept for 90 days). That ledger was created to enforce the limit and is reused here for this second purpose, with no extra data. Legal basis: our legitimate interest (Article 6(1)(f) GDPR) in understanding how Mastering is used so we can steer the product. You can object: by switching off Usage statistics (your choice is saved on your account and you no longer appear in the list) or by writing to [email protected].

Automatic crash reporting, on the other hand, remains switched off: the app ships without any crash-reporting key, and no crash is ever reported behind your back. The only detailed technical information that reaches us is what you send yourself when you report an anomaly, as described in the section above. This website itself uses no third-party tracker or analytics.

Your public profile

As long as your profile is private, only the people whose request you accepted see what you publish on it. If you make it public, your username, your display name, your picture, your bio and the songs you chose to publish there, with their comments and their number of likes, become visible to any Jam Jam account. Your profile picture stays visible even to a visitor without an account; you can reserve it to your followers in settings. Your profile page also becomes readable on the web without an account, but a visitor who is not signed in does not see the lyrics. Legal basis: your consent (Article 6(1)(a) GDPR), given by the 15 or older box you tick to make your profile public. You can withdraw it at any time by switching back to private, without losing anything else in the app. Those pages carry a header that forbids indexing: they do not appear in search engines.

What you do on the social surfaces is visible within the same limits: who you follow and who follows you, the comments you write under someone else’s song, and your likes. The number of times one of your songs was imported stays private: you are the only one who sees it.

Your declarations and your reports

Two records concern you specifically. Your rights declarations: before a song goes beyond the circle of accounts you accepted, we record the date, the version of the accepted text and the song concerned. They serve to establish our diligence as a host and to handle a takedown request, nothing else; you can read them again, our administrators can too, and they are deleted with your account. Your reports: what you report is read by our administrators in order to decide, and the record of the decision stays 24 months in our moderation log, without the removed content and without the name of the person who reported. We never disclose your identity to the person targeted.

Answering a report

When you report content, you can leave an email address: it is used only to send you the acknowledgement of receipt and the reasoned decision that the European regulation on digital services requires from us (art. 16(4) and (5) of Regulation (EU) 2022/2065). Legal basis: our legal obligation. It is never shown to the person targeted, never used for anything else, and it is erased 6 months after the report. Without an address, the report is handled in exactly the same way, but we cannot answer you.

Diligence log of website reports

The report form on this website records, when you send it, the timestamp, the reason you chose, the address you reported and the language of the page. Neither your name, nor your text, nor your IP address is recorded. That record serves only to prove that we handle reports within a reasonable time, and it is erased after 12 months.

Your rights (GDPR)

You can access, export and delete your data at any time from the app (Profile → Export my data / Delete my account). The export is machine-readable JSON: it is how you exercise your right to data portability (Article 20 GDPR), and (like backing up your whole songbook) it is free, unlimited and outside every usage quota. You also have the right to rectification, restriction and to object, and wherever a processing rests on your consent you may withdraw it at any time, without affecting what was lawfully done before. Deletion is permanent and removes your profile, avatar and account. Requests: [email protected]. If you think we are mishandling your data, you may lodge a complaint with your national supervisory authority: in France, the CNIL. We would rather you told us first, but that right does not depend on us.

Retention

We keep account data while your account exists. When you delete your account, the associated server-side data is removed: songbook backup, profile, avatar, shared songs, reports and settings. Three things outlive the deletion, and we would rather write them down than let you discover them: entries in our administrative action log (which support or moderation action was taken, and on which account identifier) are kept 24 months so that a decision can still be audited, then purged automatically; a message you wrote inside someone else’s report thread stays in that thread so the other person keeps their answer, but it is detached from your account and can no longer be traced back to you; and accounting records of a purchase are kept for 10 years as French commercial law requires. Those are held by Stripe or by the store, not inside the app. Deleting your account also carries away what you had published: public profile, published songs, comments and likes go with it. The audio files in your vault are removed by a clean-up task: their actual erasure takes a few days, not a few seconds, and we would rather write it down. The history of AI music detection and that of the stem splitter are removed with your account.

Children

The Service is not directed to children under 13 (or the minimum age in your country). Do not create an account if you are under that age. Making a profile public requires being 15 or over: below that, French law asks for the agreement of those holding parental authority before an open publication. We ask you to confirm it with a tick box at the moment you make the profile public, and we never ask you for your date of birth.

Soundtracks shared with accounts that follow each other

When you attach an audio file to a song, Jam Jam converts it to a lightweight format (Opus mono, 24 kbps, roughly 0.7 MB for four minutes) and stores it in a private bucket hosted in the EU, so that the song works the same on your phone and in your browser. As long as the song stays in your own songbook, you are the only person who can hear that file. It becomes available to the accounts you follow and who follow you back when you publish the song to your profile, and to nobody else: neither a mere follower nor a visitor without an account can reach it, and no download link is ever generated. A file is capped at 2.5 MB, and each account may store 50 MB in total.

Your rights declaration. Before one of your soundtracks becomes audible to anyone else (when you publish the song, or when you suggest that soundtrack to another account), we ask you to declare that you have the right to share the recording. We keep the date, the version of the text you accepted and the song concerned: without those three, a declaration proves nothing later on. Its purpose is to establish our diligence as a host and to handle takedown requests, nothing else. You can read your own declarations, our administrators can read them, and they are deleted with your account.

Someone who imported one of your songs may suggest a soundtrack for it. Nothing is published until you accept it. Every shared soundtrack can be reported from the app, and we can withdraw it. If you delete your account, a suggestion that was never accepted is deleted with its file; a soundtrack that people already depend on stays in place, but the link to you is severed (it is then shown as coming from “a user”). We warn you before you confirm the deletion. If you want the content itself removed rather than merely unattributed, write to [email protected] and we will handle it through the withdrawal procedure.

Voice and instrumental tracks, separated automatically (stems)

When you attach an audio file to a song, Jam Jam automatically separates it into two tracks, voice and instrumental, using the same engine that feeds the player’s speaker menu and the karaoke export. Both tracks are converted to the same lightweight format as the original soundtrack (Opus mono, 24 kbps), roughly 1.4 MB for the pair, and count against the same 50 MB cap per account. They are kept like the original file, for as long as the song exists in your songbook, even if you never publish it.

They follow exactly the same access rules as the soundtrack they come from (see the section above): you alone can hear them while the song stays in your private songbook; an account you follow and who follows you back can hear them only once you have published the song and accepted the rights declaration that goes with it. Neither a mere follower nor a visitor without an account can reach them.

Both tracks are deleted with the audio file they come from, with the song, or with your account. You can also remove them explicitly from the app, without touching the rest of the song.

Sending a song or a playlist to an account

The Share menu lets you send directly a song, a playlist or your profile to an account you follow and who follows you back. The recipient gets a notification carrying your identity and a reference to what was sent; nothing is deposited into an inbox, and opening the notification applies the same visibility rules as if the recipient had found it themselves.

To limit abuse, every send is counted in a separate log (20 sends per hour, 3 sends per day to the same account for the same object); that log serves no other purpose, is read by no human, and is deleted after 7 days.

Jam Run game progress (with an account)

If you play Jam Run while signed in, your game progress is saved to your account so you find it again on your other devices: levels completed, scores and best runs, game counters, the mascot items you own or have seen, your mascot’s outfit and your game preferences. No audio and nothing from your microphone is ever sent: the game listens on your device only. This data is hosted in the European Union, used only to restore your progress, readable only by you, and deleted with your account. Legal basis: performance of the contract (Article 6.1.b GDPR), because you asked for this feature by playing while signed in. You can download a copy at any time from the game (Options, Advanced, “Export my game data”) or with your account data export; you can also write to [email protected].

The microphone in Jam Run. With or without an account, the sound from your microphone is analysed only on your device, during the game, to recognise the chord you play: it is neither recorded nor sent. If you play with a MIDI keyboard, the microphone is not opened at all.

Jam Run records and leaderboard

When you play Jam Run while signed in, your best score on each level of the game is saved with the difficulty, the instrument and the date, to show you your record and tell you when you beat it. Only the game’s own levels have records: never a song from your songbook. Legal basis: performance of the contract (Article 6.1.b GDPR). Each level also shows the top 3 players, visible to signed-in Jam Jam accounts: only public accounts appear there, with nothing but their username, score and instrument (no display name, no picture). That display rests on your consent (Article 6.1.a GDPR), the same one as your public profile: the “15 or older” box you tick to make your profile public. A private account keeps its record to itself; switching back to private removes you from the leaderboard straight away, without losing anything else. Your records are hosted in the European Union, included in your data export and deleted with your account.

Notifications and e-mails

With an account, Jam Jam can let you know in three ways: the bell in the app, a push notification on your phone (only if you have allowed it in your phone’s settings), and e-mail. Every message belongs to one of the five categories below, and its category decides what is on by default. Everything is set in Settings → Notifications, on mobile and on the web, and the Notifications page explains how.

• Account and legal obligations: your sign-in code, the welcome message, a security alert, notice that one of your items has been removed, updates on a report you made. On by default. Notice of a removal cannot be turned off: the law requires us to give it to you, together with your means of redress. Legal basis: performance of the contract (Article 6(1)(b) GDPR) and our legal obligation (Article 6(1)(‌c) GDPR, Regulation (EU) 2022/2065).
• My content: what follows from something you did or a service you use, for example “Your analysis is ready”, a karaoke video ready to download, a reply to your feedback, free days of Premium, or a required app update. On by default, on your phone and by e-mail, and can be turned off. Legal basis: performance of the contract.
• My circle: another account does something involving you or your songs (follow request, new follower, a song liked, commented on, imported or sent to you). On by default on your phone. By e-mail, a summary of these facts: at most one every 14 days, only when there is at least one fact about you that you have not seen for 72 hours, with no suggestion and no promotion; it is on by default when you do not receive push notifications, and can be turned off. Legal basis: our legitimate interest in keeping you informed of what happens to your content (Article 6(1)(f) GDPR), with a simple right to object in Settings or in one click from the e-mail.
• Reminders: if you have not been back for a while (the delay depends on your usual rhythm), a reminder that carries only a real fact about you, such as a song published by an account you follow or one of your songs being imported, never a bare “we miss you”. On by default on your phone; by e-mail only if you have accepted news. Reminders and news together: at most one per 7 days and 3 per 30 days, through a single channel. After two reminders with no response, 30 days of silence; after three, 90 days; after four, none at all. Legal basis: our legitimate interest, with the right to object in Settings.
• Jam Jam news: new features in the tools you use, an important new version (never a mere bug-fix release), Premium offers. Only if you have agreed, by push or by e-mail, and only from the age of 15; at most two per 30 days, within the cap shared with reminders. Legal basis: your consent (Article 6(1)(a) GDPR and Article L34-5 of the French Post and Electronic Communications Code), which you can withdraw at any time. The only exception, described below: paid Premium.

Your choice about news. Right after you create your account, a “Stay in touch” screen offers you two buttons of equal weight: “Yes, with the news” and “Just the essentials”. Nothing is pre-selected, and choosing the essentials, or “Later”, changes nothing else in the app. In the mobile app, your answer covers both notifications and e-mails; on the web, e-mails only. Each channel can then be set separately in Settings → Notifications, or in one click from any news e-mail. News is reserved for people aged 15 or over: if you have not confirmed this yet, the button asks you, and we never ask for your date of birth.

Proof of your choice. Every consent and every withdrawal is written to an append-only register: the purpose (news), the channels concerned (push, e-mail), granted or withdrawn, the version and fingerprint of the text you were shown, its language, the screen, the platform, the app version and the date. A withdrawal is a new line, never an erasure. This register serves only to prove that we respect your choice; it is kept for as long as your account exists and deleted with it. Legal basis: our obligation to be able to demonstrate your consent (Article 7(1) GDPR).

Paid Premium. If you have paid for Premium (a current subscription or a lifetime purchase), we may send you news about Jam Jam and Premium by e-mail even if you have not accepted news, as the law allows towards customers for similar services (Article L34-5 of the French Post and Electronic Communications Code). This requires that the notice was shown to you at the time of purchase, with a “Don’t send me these e-mails” link: we keep a record of that display (date, text version, language) in the register described above, and it is deleted with your account. You can object right then, and afterwards at any time and free of charge, in Settings or in one click from any of these e-mails. These e-mails are never about a third party’s products, never reach you by push without your consent, and are never sent to anyone who has not confirmed being 15 or over. Free trials and free days of Premium do not count as a purchase.

Unsubscribe in one click. Every e-mail that is neither about your account nor required by law carries an “Unsubscribe from these emails” link, which opens a confirmation page without asking you to sign in, as well as the standard unsubscribe header that mail apps show as a button: either one stops that kind of e-mail immediately. Account and legal e-mails (security, removal of an item, updates on a report) carry a link to your settings instead.

Suppression list. If an e-mail permanently cannot be delivered to your address, or if you mark it as spam in your mail app, our sending provider Resend tells us through an authenticated message, and your address joins a suppression list, with only the reason (bounce or complaint) and the date: Jam Jam then sends it no notification e-mail at all. This list is tied to the address, not to the account: it is kept even after your account is deleted, precisely so that we never write to you again. To be removed from it, write to [email protected]. Other delivery events are kept only as daily totals, with no personal data. Legal basis: our legitimate interest in respecting your refusal and in keeping our e-mails deliverable.

Push token and time zone. When you allow notifications on your phone, the app stores the push token your phone assigns to it, along with the platform (Android or iOS). It is used only to send you your notifications, and it is removed when you sign out, when you turn push notifications off, when your phone’s service reports it as invalid, and with your account. To write to you at a reasonable hour and respect your quiet hours, the mobile app and the web app also store your device’s time zone (for example “Europe/Paris”), never your location; it is kept for as long as your account exists. Legal basis: performance of the contract.

Fitting notifications to your use. To choose the timing and topic of a reminder or a news item, we compute a usage profile every night from the usage measurement described above, over the last 56 days: how you use Jam Jam (exploring, mostly alone, in a group, jamming, both), the tool you use most, whether you mostly publish or read, your main platform, your rhythm (days, time slot, share of weekends, usual gap between two active days), the date of your last activity and a few capped counters (minutes, sessions, days). It never contains the content of your songs: no titles, lyrics, chords or song identifiers. If the computation cannot decide, the app may ask you once the optional question “Do you mostly play alone, with others, or both?”; your answer, or the fact that you skipped it, is kept for as long as your account exists. This is profiling (Article 4(4) GDPR), with no legal effect and no significant decision about you. Legal basis: our legitimate interest in sending you only useful messages, at the right time (Article 6(1)(f) GDPR). You can object: if you refuse usage statistics, your refusal is saved to your account, no profile is computed any more and yours is erased the following night, even if older measurements still exist; the same applies if you turn off reminders or all notifications; you can also write to [email protected]. The profile and your answer are included in your data export and deleted with your account.

Invitation to leave a review. If you have accepted the “Invitation to review” e-mail (off by default, in Settings → Notifications), we may write to you once, no earlier than 21 days after your account was created, to suggest that you share your experience on Trustpilot; this e-mail is blind-copied to Trustpilot, which receives your e-mail address and sends you the invitation itself. So that the invitation arrives right after a real experience, not months after your last visit, we only trigger it if you have opened the app within the last 14 days, on at least 3 different days out of 30. This count reads only the days on which the app was opened, taken from the usage measurement described above (which therefore also serves, in a limited way, this purpose) and from two technical dates of the service (your last activity and the last connection of each platform). It never looks at what you did or whether you are satisfied, and it applies to every account in the same way. Legal basis: our legitimate interest in asking for a review at the right time (Article 6(1)(f) GDPR), in addition to your agreement to receive this e-mail. You can object by turning this e-mail off, or by refusing usage statistics: no more measurement data is then collected for this count.

Measuring what our notifications achieve. Every reminder, news item or summary is recorded in a measurement table, separate from the log described below: category, type, template and subject of the message (an identifier, never a title), channel, platform, app version, account type, your usage profile at the time of sending, dates of sending, delivery, opening and click. We also note whether, within 72 hours of sending, you turned off that kind of message, all notifications or e-mails, withdrew your agreement to news, lost push permission or unsubscribed in one click, and whether you came back to the app within 24 hours and within 7 days. A click in one of these e-mails goes through a signed redirect link on jam-jam.org, which records the time of the first click before taking you to the intended page; we use no pixel to find out whether you opened an e-mail. To know the real effect of reminders, 10% of accounts, assigned once and for all by a fixed draw on the account identifier, never receive reminders or news: this is the control group, and a line is still recorded for them. This table is kept for 13 months, then reduced to anonymous totals; it is included in your data export and deleted with your account. Administrators only ever see totals, never an individual line. Legal basis: our legitimate interest in checking that our messages are useful, and in sending fewer when they are not (Article 6(1)(f) GDPR). You can object to this measurement, clicks included, by writing to [email protected]; turning these messages off stops it too.

Notification log (administrators)

Every notification the Service sends is recorded: sender, recipient, type, channel (push, email, in-app), outcome, and the body of the message. Purpose: diagnosing “I never got it” and detecting abuse: nothing else. Retention: 30 days, then automatic deletion by a scheduled job. It is readable by administrators only, and it is erased in both directions (as sender and as recipient) when an account is deleted.

YouTube addresses

Jam Jam uses YouTube API Services for optional playback in the official embedded player. No YouTube script, thumbnail or metadata request is loaded before your agreement. Loading sends Google your IP address, browser/device information, the source page address (which may contain a song identifier), video identifier and playback activity. Google processes these under its own privacy policy, including cookies or similar technologies and possible transfers outside the EU. The youtube-nocookie mode does not mean no data collection. The optional loading relies on your consent (Article 6(1)(a) GDPR). You can stop the player and withdraw your agreement at any time; this stops future player loading, without erasing data already received by Google. Jam Jam stores the link and any timing marks in your songbook, without downloading the video or audio. YouTube may show its own ads, including for Premium accounts. Google privacy.

Audio transformations require an audio file you provide. A copy is stored in your private space for access on your devices. Sharing follows the mutual-follow rules described above. A YouTube link is never converted into such a file.

Changes & contact

We may update this policy; changes appear here with a new date. Questions or requests: [email protected].