Privacy Policy

Last updated: August 10, 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

No audio file is involved.

5. Google Drive

If — and only if — you connect your Google account, DekkR requests the drive.readonly scope, which allows reading the files in your Drive.

Why this scope, and not a narrower one. DekkR needs to walk the entire contents of a music folder, and to walk it again each session to pick up new tracks. The narrower drive.file scope only grants access to files selected one by one and does not allow listing a folder's contents: it would force you to manually reselect every track, and to start over on every addition.

What DekkR does with that access: list the audio files in the folders you explicitly added, and read them to play and analyze them. DekkR never modifies or deletes any 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 names and identifiers of the folders you added, along with the file names analyzed, are stored with Supabase so you can find your 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.

6. Third-party services

ServiceWhat it receivesWhy
SupabaseAccount, devices, analysis results, settingsAuthentication and synchronization
GoogleAuthentication and Drive read requests, IP addressSign-in and access to your Drive
OctavTitle and artist of the current track, when suggestions are requestedSuggesting tracks to mix next
DiscogsYour IP address, when a cover is displayedCovers are loaded from Discogs servers
VercelTechnical access logs (IP address, page requested)Website hosting

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

7. 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, MIDI profiles, registered devices and profile. Your audio files are not touched. Your account itself remains, holding nothing but your email address.

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.

8. Changes

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