Effective Date: February 26, 2026 — Last Updated: September 17, 2026
This Privacy Policy explains how OCDJ ("we," "us," or "our"), operated by Plan Bakery B.V., a company registered in the Netherlands, collects, uses, stores, and protects your personal data when you use the OCDJ application, website, and related services (the "Service").
We are committed to protecting your privacy and complying with the General Data Protection Regulation (GDPR) and other applicable data protection laws.
The data controller for the processing of your personal data is:
OCDJ (operated by Plan Bakery B.V.)
KvK: 70878986
Molenkade 18, 2645 AX Vinkeveen
The Netherlands
Email: [email protected]
| Data Type | Purpose | Legal Basis |
|---|---|---|
| Email address | Account identification, communication | Contract performance |
| Authentication credentials | Account security (WebAuthn/passkeys) | Contract performance |
| IP address | Security, fraud prevention, rate limiting | Legitimate interest |
| Session identifiers | Maintaining authenticated state | Contract performance |
| Data Type | Purpose | Legal Basis |
|---|---|---|
| Track titles, artists, BPM, key | Library analysis and processing | Contract performance |
| Playlist names and structure | Library organization features | Contract performance |
| Cue points and DJ settings | Backup and restoration | Contract performance |
| File names and full file paths | File mapping, deduplication, and DEBUSSY (see 2.8) | Contract performance |
When you use the Cloud Backup Service, we additionally process:
| Data Type | Purpose | Legal Basis |
|---|---|---|
| Music files (audio content) | Cloud backup storage and restoration | Consent / Contract performance |
| File SHA-256 hashes | Deduplication and integrity verification | Contract performance |
| File sizes | Storage quota tracking | Contract performance |
| Upload/download timestamps | Backup history and audit trail | Legitimate interest |
Payment processing is handled by Stripe, Inc. We do not store credit card numbers, CVVs, or full bank account details. Stripe's handling of your payment data is governed by Stripe's Privacy Policy.
The OCDJ desktop application processes your DJ software database locally on your computer. The following describes what data stays local versus what is transmitted to our servers:
| Data Type | Local Only | Sent to Server |
|---|---|---|
| Music audio files | Yes (unless using Cloud Backup) | Only if you enable Cloud Backup |
| DJ database (Rekordbox/Traktor) | Yes — read and modified locally | Never sent as a file. The app maintains a separate working library database, a copy of which is uploaded — see 2.8 |
| File paths on your computer | No — the working library database records the full path of each track, and a copy of that database is uploaded (see 2.8) | Yes, inside the library database described in 2.8 |
| Application logs and diagnostics | Stored locally | Error reports sent to Sentry (see 3.7) |
| Application settings and preferences | Yes — stored in local config file | Yes — a copy is included in the account-recovery backup described in 2.9 |
To enrich your music library metadata (BPM, key, genre, artist names, artwork), we match your tracks against our own proprietary music catalog on our servers. When we do this:
DEBUSSY is the assistant inside the desktop app that answers questions about your collection and can carry out library tasks for you. To do that, it needs a copy of your library on our servers.
What is uploaded, and when. The desktop app keeps its own working database of your library, separate from your DJ software's database. A compressed copy of that working database is uploaded to our servers:
This upload happens for every signed-in desktop account, whether or not you use or subscribe to DEBUSSY. It is not tied to the Cloud Backup Service, which is a separate, opt-in feature covered by 2.3.
What that database contains. One row per track in your library, holding the information the app has read or derived from your DJ software and your files, including:
It does not contain your audio files — no audio is uploaded by DEBUSSY.
Where it is stored. The uploaded copy is held on our application servers (as a working cache of the most recently used libraries) and in our Backblaze B2 storage (see 3.1) under a key specific to your account. Each new upload replaces the previous one. From that copy we also derive a summary of your collection — track counts, genre, BPM and key distributions, top artists, most-played tracks, playlist and folder names — which we store in our application database and in Cloudflare R2 (see 3.11) so the assistant does not have to recompute it on every question. Transfers use HTTPS/TLS.
What is sent to the AI provider. When you send a message to DEBUSSY, we send to Anthropic (see 3.8): your message, the conversation so far, the summary of your collection described above, any standing preferences or instructions you have given the assistant, and the results of the read-only queries the assistant runs against your uploaded library database. Those results can include track titles, artists, albums, genres, BPM, keys, ratings, comments, play counts and playlist names; file names; and, for Rekordbox libraries, the folder names your tracks are organised into. Full file paths are shortened to the file name before they are sent. Your audio files, your email address and your IP address are never sent.
Conversations. Your DEBUSSY conversations — the messages you send, the assistant's replies, the actions it takes on your behalf, and any feedback or complaint you submit about a reply (including the free text you write and the reply it refers to) — are stored on our servers so the assistant can remember them and so we can investigate problems you report. They are retained for the life of your account (see 5).
Human review. We do not read your DEBUSSY conversations for product-improvement purposes unless you have separately opted in to conversation review; the app asks you for that choice explicitly during setup (the answer defaults to no, and you can change it at any time in Settings), and no review takes place before you opt in. Independently of that choice, a small number of authorised staff may access conversation records where it is strictly necessary to investigate a fault or a support request you have raised, to detect and prevent abuse of the service, or where we are legally required to.
Training. We do not use your library, your conversations or your music to train AI models, and our AI providers do not train their models on the data we send them (see 3.8 and 3.9). If you opt in to conversation review (see Human review), staff may read the conversations you share to improve our software, but those conversations are never used to train an AI model.
Deleting it. When you ask us to delete your account (see 6.1), we delete your uploaded library database (including the cached copy and the derived summary) and your DEBUSSY conversations within the same 30-day period. You can also ask us to delete the uploaded library database on its own, at [email protected], without closing your account — but note that the app will upload a fresh copy the next time one of the triggers above occurs, for as long as you remain signed in to the desktop app.
Separately from Cloud Backup (2.3) and from the working library database described in 2.8, the desktop app also backs up a small set of local files that a config wipe or a lost machine would otherwise destroy: your device identity (client name, platform, paired-device details), your saved settings and preferences, your manual fix decisions, and your taste profile.
A copy of each is uploaded to our servers after every successful FIX & ENRICH run, when the app starts, and when you re-pair a device — for every signed-in account, with no separate toggle to turn it off.
These files are meant to never include your account credentials — API keys and session tokens are stripped before upload and are meant to live only in your device's Keychain — and never include your audio files. They are encrypted at rest and stored with Backblaze B2 (see 3.1), under a key specific to your account, and replaced by each new upload.
Your data may be processed by the following third-party service providers, each acting as a data processor on our behalf.
Purpose: Storage of your music files when you use the Cloud Backup Service, storage of the library database copy that powers DEBUSSY (see 2.8), and storage of the account-recovery backup of local app state (see 2.9), for every desktop account.
Data stored: Your music files (encrypted at rest with AES-256), file metadata (keys, sizes); the compressed copy of your library database described in 2.8; and the settings/identity/decisions/taste-profile backup described in 2.9.
Location: EU Central data center (European Union).
Privacy policy: backblaze.com/company/policy/privacy
Backblaze acts as a sub-processor. We have entered into a Data Processing Agreement (DPA) with Backblaze to ensure GDPR-compliant handling of your data. Files are stored in Backblaze's EU data center to keep your data within the European Economic Area (EEA).
Purpose: Hosting our web application and API servers.
Data processed: Request metadata, IP addresses, session data.
Privacy policy: railway.app/legal/privacy
Purpose: Processing payments for paid features.
Data processed: Payment card details, billing information, transaction records.
Privacy policy: stripe.com/privacy
Purpose: Website traffic analysis and user journey optimization (via Google Tag Manager and Google Analytics 4).
Data processed: Page views, referral source, device/browser info, approximate location (country/city level).
Privacy policy: policies.google.com/privacy
Purpose: Product analytics, session replay, conversion funnel analysis.
Data processed: Page views, click events, scroll depth, anonymized session recordings (form inputs masked).
Location: EU data center (when using eu.posthog.com).
Privacy policy: posthog.com/privacy
Purpose: Sending verification codes and service notifications.
Data processed: Email addresses, email content.
Privacy policy: resend.com/legal/privacy-policy
Purpose: Monitoring application errors and crashes in both the web application and desktop app.
Data processed: Error stack traces, browser/OS type, anonymized user identifiers, request URLs. No music files or library content is included in error reports.
Privacy policy: sentry.io/privacy
Purpose: Anthropic's Claude API is the AI model behind DEBUSSY (see 2.8) and behind AI-generated smart playlists. It is used for all users of those features, free and paid.
Data processed:
We do not send your audio files, your email address or your IP address to Anthropic.
Location / transfer safeguard: Data may be processed outside the EU/EEA, including in the United States. Transfers of EU/EEA and UK personal data are governed by the Standard Contractual Clauses (Module Two or Module Three) incorporated in Anthropic's Data Processing Addendum (effective February 24, 2025).
Training & retention: Under Anthropic's Commercial Terms of Service (effective June 17, 2025), Anthropic may not train models on data sent through its API. Anthropic automatically deletes API inputs and outputs within 30 days, except where a request is flagged by its trust and safety systems (kept for up to 2 years) or where retention is required by law.
Privacy policy: anthropic.com/legal/privacy
Purpose: The GroqCloud API is used in two limited places: (1) on our public website demo chat, only as a last resort to pick which of our pre-written help answers best matches a question our standard matching could not place — Groq chooses an answer from our list and never writes the text you see; and (2) where enabled, in the cleaning pipeline, to double-check an ambiguous artist or title correction, or to suggest better search terms for a track our catalog could not identify. It is not used by DEBUSSY.
Data processed: For the website demo, the question you type into the demo chat. For the pipeline helpers, the artist and title values involved (original and corrected) and, when identifying an unmatched track, its file name and existing tags. We do not send audio files, email addresses, or IP addresses to Groq.
Location / transfer safeguard: United States (data retained in Google Cloud Platform buckets in the US). Transfers of EU/EEA personal data are governed by EU Standard Contractual Clauses (SCCs) incorporated in Groq's Data Processing Addendum (Commission Implementing Decision 2021/914, Module 2).
Training & retention: Groq does not use your inputs or outputs to train or fine-tune any AI model without your explicit permission. By default, inference requests are not retained; where temporary logs are created for system reliability or abuse monitoring, they are deleted within 30 days. Zero Data Retention is available.
Privacy policy: groq.com/privacy-policy · DPA: console.groq.com/docs/legal/customer-data-processing-addendum · Sub-processors: trust.groq.com/subprocessors
Purpose: Running audio analysis models (tempo, key, genre, embeddings) on serverless GPUs when you opt into cloud analysis.
Data processed: Short audio features derived from your files. Raw audio is deleted after analysis.
Privacy policy: modal.com/legal/privacy
Purpose: Serving album artwork, waveforms, and onboarding screenshots to the mobile and desktop apps via a public CDN; and storing the collection summary DEBUSSY derives from your library (see 2.8).
Data processed: HTTP request metadata (IP address, User-Agent) handled by Cloudflare's edge network; and, for DEBUSSY, the collection summary described in 2.8 (track counts, distributions, top artists, most-played tracks, playlist and folder names).
Privacy policy: cloudflare.com/privacypolicy
Purpose: In-browser live chat so we can answer support questions on the marketing pages.
Data processed: Messages you send, page URL, browser/OS type, chat-session cookie.
Privacy policy: crisp.chat/privacy
Status: Discontinued. We no longer send any backup data to AWS, and it is no longer part of how your cloud backup works. Your cloud backup is stored with Backblaze (3.1).
Data processed (historically): Music files previously archived from the cloud backup.
Location / transfer safeguard: Held in an EU AWS region (eu-north-1); EU data residency applied. Files were encrypted (AES-256) before transfer.
Privacy policy: aws.amazon.com/privacy
Purpose: Optional account sign-in using your Google account (separate from the analytics use in 3.4).
Data processed: The identity token Google returns (your email address and name).
Location / transfer safeguard: United States; transfers are covered by Google LLC's certification under the EU-US Data Privacy Framework.
Privacy policy: policies.google.com/privacy
Purpose: Optional account sign-in using your Apple ID.
Data processed: The identity token Apple returns; you may choose to hide your email (Apple relay).
Location / transfer safeguard: United States; transfers are governed by EU Standard Contractual Clauses (SCCs).
Privacy policy: apple.com/legal/privacy
We process your personal data for the following purposes:
| Data Type | Retention Period |
|---|---|
| Account data | Duration of account + 30 days after deletion request |
| Music library metadata | Duration of account + 30 days after deletion request |
| Cloud backup files (Backblaze) | Duration of account + 30 days after deletion request |
| Uploaded library database for DEBUSSY, and its derived summary (2.8) | Replaced by each new upload; kept for the duration of account + 30 days after deletion request |
| Account-recovery backup of local app state (2.9) | Replaced by each new upload; kept for the duration of account + 30 days after deletion request |
| DEBUSSY conversations and feedback on replies (2.8) | Duration of account + 30 days after deletion request |
| Payment records | As required by Dutch tax law (7 years) |
| Security logs (IP, auth attempts) | 90 days |
| Anonymized analytics | Indefinite (non-personal) |
As a data subject under the GDPR, you have the following rights:
To exercise any of these rights, contact us at [email protected]. We will respond within 30 days as required by the GDPR.
You may request complete deletion of your account and all associated data at any time. Upon receiving a valid deletion request:
We implement appropriate technical and organizational measures to protect your personal data, including:
If we become aware of a personal data breach that is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority — the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) — without undue delay and, where feasible, within 72 hours of becoming aware of it, in accordance with Article 33 GDPR. Where the breach is likely to result in a high risk to you, we will also notify you directly without undue delay (Article 34 GDPR), describing the nature of the breach, its likely consequences, and the measures we have taken or propose to take.
We store and process your data within the European Economic Area (EEA):
Where data is transferred outside the EEA (e.g., to certain sub-processors), we ensure appropriate safeguards are in place, such as Standard Contractual Clauses (SCCs) approved by the European Commission.
These cookies are required for the Service to function and cannot be disabled:
With your consent, we may load the following client-side (in-browser) analytics tools. These set cookies or local storage on your device, so they run only after you choose “Accept All” in the consent banner — never if you choose “Essential Only”:
| Tool | Purpose | Data Collected | Privacy Policy |
|---|---|---|---|
| Google Analytics 4 (via Google Tag Manager) | Website traffic analysis, acquisition channels, user journeys | Pages visited, time on site, referral source, device/browser type, approximate location (country/city level) | Google Privacy Policy |
| PostHog | Product analytics, session replay, conversion funnels | Page views, clicks, scroll depth, session recordings (with form inputs masked), feature usage | PostHog Privacy Policy |
When you first visit our website, a cookie-consent banner lets you choose:
You can change your choice at any time by clearing your browser's local storage for our domain and refreshing the page.
We do not use advertising cookies or tracking pixels. We do not participate in any advertising networks. We do not sell, rent, or share analytics data with third parties for marketing purposes.
Separately from the cookie-based tools in 9.2, we record a limited set of server-side product events (for example: an account was created, a payment completed, a page was served) via PostHog (EU). These events set no cookie and store nothing on your device, and they contain no directly-identifying data — only a pseudonymous session or account identifier, never your email address or IP address. Because they place nothing on your device, they fall outside the cookie-consent choice above and are processed under our legitimate interest (Art. 6(1)(f) GDPR) in understanding and improving the Service. You may object to this processing at any time (Art. 21) by contacting us.
The Service is not directed at children under the age of 16. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us and we will promptly delete it.
We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy on our website and, where appropriate, by email. Your continued use of the Service after such changes constitutes acceptance of the updated policy.
If you believe your data protection rights have been violated, you have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens):
Autoriteit Persoonsgegevens
Bezuidenhoutseweg 30, 2594 AV Den Haag, The Netherlands
Website: www.autoriteitpersoonsgegevens.nl
Phone: +31 70 888 8500
For any privacy-related questions, requests, or concerns, please contact us at:
OCDJ (operated by Plan Bakery B.V.) — Data Protection
KvK: 70878986
Molenkade 18, 2645 AX Vinkeveen, The Netherlands
Email: [email protected]
Website: ocdj.ai
See also: Terms of Service
HOME