Privacy Policy

Last updated: October 24, 2026

DekkR is a DJ mixing application that runs entirely in your browser. This page describes exactly what data is processed, why, and who it is shared with.

Publisher and contact: Raphaël Morlec — contact@dekk-r.com

1. What never leaves your browser

Your audio files are never uploaded. Not to DekkR, not to any third party. Playback and analysis (tempo, beat grid, key) are computed locally, by your browser, offline included.

Also staying on your device: the analysis cache, your playlists, your MIDI controller mappings and your display preferences.

2. No analytics

DekkR uses no tracking or analytics tool: no Google Analytics, no Sentry, no advertising cookie. No advertising profile is built, and no data is sold or passed to an advertiser or a data broker.

3. User account

Creating an account is optional: DekkR works without one. It exists so you can find your analyzed collection again on several machines.

If you create an account, the following is stored: your email address, an account identifier, and the list of your devices (name, type, last connection date) in order to sync your settings. Authentication and synchronization are handled by Supabase.

4. What is synced if you have an account

• The analysis results for your tracks: file name, size, title, artist, duration, tempo, key, cue points, beat grid
• The metadata retrieved for your tracks: genre, style, year, label, country, cover artwork address
• Your playlists, your favorite transitions, the inventory of your USB drives, your MIDI mappings and your settings
• Your set log: the tracks that stayed at least 30 seconds in the mix, with the time, the deck, its tempo and key settings, the previous track, and who picked them (you, the automix, the Dig or the remote). Nothing is logged without a signed-in account.

No audio file is involved.

5. Track recognition and shared transitions

If you have an account, DekkR matches your tracks against a public record catalog (built from Discogs public data) to show their details and suggest the tracks often mixed with them. This matching is done by a computer operated by the publisher, which reads, for each of your tracks, the file name, size, title and artist — nothing else, and never your audio files. The result (the record found, or "not recognized") is stored at Supabase and is visible to you only. It is deleted with your account.

Shared transitions — only if you agree. Sharing is off by default. The first time you like a transition, DekkR asks whether you want to share your favorite transitions; nothing is shared unless you answer yes. If you do, they contribute, anonymously, to the suggestions shown to other users: only a count is kept ("liked by N DJs"), never your identity or the rest of your collection. A transition in which one of the tracks is not recognized is never shared. You can change your answer at any time in the app (Settings › Compte › Partager mes transitions aimées — share my liked transitions), or by writing to contact@dekk-r.com. Your choice applies at the next run, within the hour; your liked transitions keep serving your own suggestions either way.

Catalog access. To prevent bulk copying, browsing the catalog and the suggestions is limited per account; unusual use is reported to the publisher and may temporarily suspend access.

6. Google Drive

If — and only if — you connect your Google account, DekkR requests the drive.file scope. It does not give access to your whole Drive: DekkR only sees the files you choose in the Google file picker and the files DekkR itself created at your request.

What DekkR does with that access: list and read those files to play and analyze them; and, only when you click Copier sur mon Drive (copy to my Drive), upload copies of your local tracks into a DekkR folder of your Drive. DekkR never modifies or deletes any other file in your Drive.

What is retained: the Google access token stays in memory only and is never written to disk nor sent to a server. If you have an account, the file names of the tracks analyzed are stored with Supabase, like those of your local tracks, so you can find your analyzed collection again on another machine.

Limited Use: DekkR's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. This data is used solely to provide the user-facing features described here, is never sold, is never used for advertising purposes, and is not read by any human.

Revoking access: at any time from your Google account.

7. Third-party services

If you use DekkR's companion applications, they run on your own machine and send nothing to DekkR.

8. Retention and deletion

Account data is retained for as long as the account exists. Data stored on your device can be erased at any time by clearing the site's data in your browser.

From the app: the “Delete all my data” button, in the settings, erases your data immediately from our servers and from this device — analyses and beatgrids, playlists, settings, Drive folders, media, liked transitions, set log, MIDI profiles, registered devices and profile. Your audio files are not touched. Your account itself remains, holding nothing but your email address.

The set log can also be erased on its own, from the Sets screen: one set at a time, or the whole log — in the cloud and on this device.

By email: to access, correct or delete the account itself — or if part of the data resisted deletion — write to contact@dekk-r.com. Deletion is permanent and takes place within 30 days.

9. Changes

Any change to this policy will be published on this page, with the date at the top updated.