Skip to content

Privacy Policy

This policy explains what DJ Coach collects, why, who else handles it, where it is kept, for how long, and what you can do about it. It describes the product as it actually works today, checked against its code and against the settings of the services it uses. When the product changes, this page changes with it.

Version 1.13 · Last updated:

What changed: Tab storage now also keeps which account last signed in in that tab, so that a different person signing in there starts a new visit and does not inherit the previous person's unsent reflection draft. Nothing else changed.

DJ Coach is a set-planning and coaching tool for DJs. The operator of the service is DJ Coach, which decides how your data is used and is responsible for it — the controller of the database, in the language of data-protection law.

For anything on this page — a question, a request to see, correct, export or delete your data, or a complaint — write to us at support@djcoachpro.com.

  • You can use DJ Coach without an account. A guest plan stays in your own browser.
  • If you create an account, we keep your email address, a hash of your password and the sets you save, until you delete them. Deleting your account removes all of it from the live database at once; copies inside the encrypted backups expire within 30 days. If you never confirm your email address, the account is deleted automatically after 7 days, and at the latest 30 days after you signed up if we sent you a link. If our email could not be sent, it is deleted after 30 days, or kept while our email sending is switched off.
  • If you leave a review after downloading a plan, we keep it with your account. It is published on the website only if you tick the box that allows it and we have read and approved it, and you can delete it at any time.
  • Audio analysis is optional. If you use it, your music files are analysed in your browser, on your device: the audio, the file names and the fingerprints that identify the files never leave it. Only a few numbers per track, at most 512 bytes, are sent with a plan request.
  • There is no advertising, no third-party cookie and no cross-site tracking, and we do not sell data.
  • Without your consent, usage analytics uses no cookies and is not tied to your account. You can switch it off on this page, and a browser privacy signal switches it off for you. Usage events are kept for six months.
  • Cookies for analytics (Google Analytics, PostHog) and for product research (PostHog heatmaps and A/B tests) are used only if you accept them in the cookie banner. Until you choose, nothing optional runs, and you can withdraw at any time under "Cookie settings" at the bottom of every page.
  • When Pro is on sale, it is sold by Paddle, our reseller and Merchant of Record. Paddle handles your payment details; we never see your card number.
  • The product's database and our servers are in the European Union, in Frankfurt; the site's pages are delivered through Vercel's worldwide network. Two things go to the United States automatically: an encrypted daily backup kept by GitHub for 30 days, and Vercel's page-view counts. If you accept Analytics cookies, Google may also process Google Analytics data in the United States. The email that confirms your address when you sign up, and a password-reset email you ask for, go through Resend, in the United States. Email you send us and our replies are kept by Hostinger, a company in Cyprus that does not publish where it stores mailboxes.
  • We send two kinds of automated email: when you sign up, a link that confirms your email address (again only if you ask), and a password-reset link, only when you ask for one. Otherwise we email you only to answer a message you sent us, or — if you asked — once, to tell you that Pro has opened.

What is stored depends on how you use the product. This is the complete list.

Your account
If you sign up: your email address, your password as a bcrypt hash (never the password itself), an optional display name, your interface language and the day the account was created. Signing in creates a session record that holds only a SHA-256 hash of your session token and the day it expires — never the token itself. If you ask to reset your password, we also keep a record of the link we email you: a SHA-256 hash of its secret (the secret itself is only in the email), the day you asked, when the link expires (rounded up to the next five minutes) and the day it was used. When you sign up we also keep a record of confirming your email address: whether and on which day you confirmed it, the day the account was created, the day we last sent you a confirmation link, and a SHA-256 hash of that link's secret until you use it (the secret itself is only in the email). Accounts that existed before email confirmation was introduced are recorded as confirmed.
Your saved sets
For a signed-in user, the sets you save: the set name, whether you play on 2 or 4 decks, the format you imported, and for each track its title, artist, BPM, musical key, energy, length and the file reference your DJ software exported — from a rekordbox or Traktor file also the track's cue points (their names, positions and colours) and its beat grid, as the file lists them, so an export can write them back — plus the plan we computed (order, transition points, techniques and explanations) and the "Worked / Rough / Skipped" marks and notes you add after a gig. If you used audio analysis, the BPM and Key values you accepted are saved as the track's own, and the saved plan keeps what was computed from the analysis, such as a start point at an estimated outro, a cue for the incoming track, a transition score or a note that an energy was measured from your audio. The full analysis stays on your device.
"Notify me when Pro opens"
If you press it while signed in: a record that your account asked, with the day you asked (not the time). It is deleted with your account. It needs a confirmed email address, because the note goes to it.
Your review
If you leave one (only an account with a confirmed email address can): the rating from 1 to 5, the text if you wrote any, the language of the page you wrote it on, whether you allowed us to publish it, the first name you typed (kept only if you allowed publishing), the day you wrote it, whether it is waiting, published or rejected, the day we decided, and whether our automatic filter for profanity, links and contact details marked it. It is tied to your account and is never shown with your email address. We collect none of this unless you send the review form.
Using it without an account
Nothing about your set is saved on our servers. The file name, the track data and the generated plan stay in your own browser (localStorage) for 7 days. To compute a plan, the track data is sent to our server, used for that one answer and not written to our database.
Audio analysis on your device (optional)
Where DJ Coach offers it, you can choose audio files on your own device so it can read the BPM, key and energy rating stored in their tags and measure each track's tempo, beat grid, key, loudness, energy and sections. The files are read, decoded and analysed entirely in your browser, on your device, and nothing is analysed until you choose them. The audio, the file names and folder paths, and the content hashes (fingerprints your browser computes from each file's bytes, so it can recognise the same file later) never leave your device. With a request to compute or save a plan, only a few numbers per track are sent, at most 512 bytes: the measured energy (overall, at the start and at the end), how confident the tempo, key, beat-grid and energy measurements are, the estimated mix-in and mix-out windows and up to 4 drops and 2 breakdowns (each a start time, a length and a confidence), the analyser and format versions, the length of audio analysed, and which of the track's values you accepted from the audio. Where the files' tags hold a BPM, a key or an energy rating (your DJ software or Mixed In Key writes them there) and the playlist has no value, that value fills the track, and it is sent and saved like the track's other values, as if your playlist file had carried it; nothing else from the tags, such as comments or artwork, is kept or sent. The analysed BPM, Key and beat grid are suggestions until you accept them; a value you accept becomes the track's own value, as if you had typed it in. What stays on your device is listed under "Cookies and browser storage".
Analysed cue points in a downloaded file (optional)
If you used audio analysis and choose to add analysed cue points when you download a rekordbox or Traktor playlist, your browser sends our server only the kind of each point (such as a drop or a mix-out point) and its time in the track. The server writes them into the playlist file as memory cues labelled "DJC …", at most 8 on each track and never as hot cues, sends the file back to you and keeps nothing of it. They are added only to tracks whose own cues from your file go into the download unchanged, so the file keeps your cues alongside them, and your music files are never changed.
How the product is used
We record usage events: an event name from a fixed list, such as "plan generated", with small values such as the mode, the file format or the number of tracks. Each visit carries a random identifier created in your browser, kept only for the life of the tab and not derived from you, your account, your device or your address. The events are stored without your IP address, your email or your track titles, and the events written at the moment of an account action — signing up, saving a set, adding a reflection — carry no visit identifier at all.
Product analytics (PostHog)
The same events, and one page-view event per page, are also sent to PostHog's European service. Each event carries the page address without its query string (and with the identifier of a saved set replaced by a placeholder), the referring site's domain only, your browser and its version, your operating system, the device type, and your screen and window size, plus random identifiers: our visit identifier, which lasts as long as the tab, and PostHog's own, which last only as long as the page. Without your consent, PostHog is set to use no cookies and no browser storage; automatic click capture, heatmaps, session recording and exception capture are all off; campaign and click identifiers and your time zone are removed before anything leaves the page, and the full browser identification string is not recorded as an event property (your browser still sends it with each request, as it does to every website). PostHog is instructed not to derive a location from your connection, and is set to discard IP addresses. What changes if you accept cookies is described under "Cookies and your consent".
Page-view counts (Vercel Web Analytics)
Vercel, our hosting provider, counts page views without cookies. For each view it records the page address (we remove the query string), the referring page, the country — which Vercel works out from your IP address — and the type of device, browser and operating system. It is not loaded at all when analytics is switched off.
Google Analytics (only with your consent)
If you accept Analytics cookies, Google Analytics receives one page-view event per page: the page address in the same form PostHog gets it, used as the page title too (never the page's own title, which can name a saved set), the referring site's address without its path for the first page of a visit, your browser, operating system, device type, screen size and language, and the identifiers in its cookies. Google receives your IP address with each request; for visitors in the European Union, Switzerland and the United Kingdom, Google states that it uses the address only to work out a coarse location and does not log or store it. Before you accept, no request goes to Google at all.
Error reports (Sentry)
When something breaks unexpectedly, an error report goes to Sentry: the type of error, its message and code location, the page or route it happened on, and technical details such as the browser or server runtime. It does not include your cookies, request headers, request body, query string or account details, and there is no session replay and no performance tracing. Reports from our server carry the location of our server (Frankfurt), not yours; reports from your browser are sent with an instruction not to record your IP address, so no location is derived from it. Expected errors — a wrong password, a file that is too large, a rate limit — are not reported.
Abuse protection
To keep sign-in, password resets, plan generation and exports from being abused, we count requests per network address, per email address and per account. Each counter stores a keyed hash of that subject, never the address, email or account in readable form, and its timestamps are rounded to the length of its window. Signing in, signing up, asking for a password reset, asking for a new confirmation link and sending a review are also checked by Vercel BotID, the bot check of our hosting provider: a script Vercel serves from our own address runs in your browser and sends its result with that request, and Vercel tells us only whether the request looks automated. We do not receive or store what the check looks at.
Hosting logs
Like every website, our hosting provider handles the technical details of each request to deliver it — the IP address it came from, the page requested, the time, the status and the browser type. Its request logs are kept for one hour on our plan.
Backups
Every day the whole product database is copied to a machine run by GitHub in the United States. There it is encrypted with AES-256 and test-restored into a temporary database to prove the copy works, and the machine is then discarded. GitHub keeps the encrypted copy for 30 days, so the service can be restored after a failure. The encryption passphrase is stored as a secret in our GitHub account.
Explanations rephrased by an AI model
The explanation beside each transition is written by the product itself from templates. There is an optional mode in which a language model from Anthropic rephrases it. It is switched off: no key is configured, so no request is ever made. If it is switched on, what is sent is the computed transition data — the two track titles, the musical keys, the BPMs, the energy and the suggested technique, plus the language to write in. Your email, your account and everything else about you stay with us, and this policy will be updated before it happens.
Email you send us
If you write to support@djcoachpro.com: your message, your email address and our reply, kept in our support mailbox, which runs on Hostinger.
Password-reset email
If you ask for a reset link on the "Forgot your password?" page and an account uses that address, we send the link to it through Resend, our email delivery provider, which receives the address and the message. If no account uses the address, no link is created and no email is sent. The message holds only the link and short instructions — no tracking pixel and no marketing.
Confirmation email
When you sign up, and again only if you ask for it, we send a link that confirms your address through Resend, which receives the address and the message. The message holds only the link and short instructions — no tracking pixel and no marketing. Opening the link changes nothing until you press the button on the page it opens.
What we do not collect
No card or bank details (when Pro is on sale, Paddle collects those, not us — see "Payments"), no audio and no music files (audio analysis, if you use it, runs on your device — see "Audio analysis on your device"), no precise location, no contacts, and nothing from other websites.

Pro is not on sale until checkout opens on the pricing page; until then nothing is bought and no payment data exists. This section describes what happens once it is on sale.

Orders are processed by Paddle.com, our online reseller and the Merchant of Record for all our orders. You buy Pro from Paddle, in Paddle's own checkout window, and Paddle collects the details its checkout asks for — such as your email address, your country and your payment details — and processes them as an independent controller under Paddle's privacy notice. We never see or store your card number.

To open the checkout, we pass Paddle the email address of your DJ Coach account (so the form is pre-filled) and an internal account identifier, so the payment can be matched to your account.

What we store
From Paddle's notifications we store, with your account: your Paddle customer ID, your subscription ID, its status, the price you are on (monthly or yearly), when the current billing period ends, any scheduled change such as a cancellation, when a renewal payment started failing (if one has), and the time of the latest change.
Webhook bookkeeping
We also keep the ID and type of each notification Paddle sends, so none is applied twice, and for each subscription the ID and time of the latest notification, so an older one never overwrites a newer one. These records hold Paddle IDs only — no email, name or payment details — and are not deleted with your account; they are deleted automatically after 180 days.
What we do not store
Card numbers, bank details, billing addresses, receipts or invoices. Those stay with Paddle, which also sends your receipts.
Managing your subscription
"Manage subscription" opens Paddle's customer portal, where you can update your payment method or cancel. We create the link for your own account only.
Deleting your account
If you delete your account while a subscription is active, we first cancel it at Paddle so it does not renew, then delete the subscription record together with the rest of your account. If we cannot confirm with Paddle at that moment that no subscription is still active, the deletion is refused and nothing is deleted: you are asked to cancel from "Manage subscription" first, or to contact us. Paddle keeps its own transaction records, as the law requires of a seller.

No law requires you to give us any of it. Everything you provide, you provide by choice.

An account needs an email address and a password; without them we cannot create one, but you can still plan sets as a guest. The display name is optional. A plan needs track data, because that is what it is computed from. Usage analytics can be switched off at any time without losing anything. Audio analysis is optional: without it, a plan is computed from your playlist's own data.

We use the data only for the purposes below. We do not use it for advertising, we do not build advertising profiles of you, we make no automated decisions that have legal or similar effects on you, and we never sell it.

To provide the service you asked for
Creating and running your account (including the link that confirms your email address and the password-reset link you ask for), saving your sets, computing plans and explanations (with the measurements from audio analysis, if you chose to run it), producing export files, answering your messages and — when Pro is on sale — linking your Pro subscription to your account. Basis: performing our agreement with you (the Terms of Use).
To read your review and, if you allow it, publish it
Keeping the review you send so that we can read it and, only if you ticked the box that allows publishing and only after we approved it, showing its rating, text and the first name you gave on the DJ Coach website. Basis for keeping and reading it: you sent it to us on purpose. Basis for publishing it: your consent, which you can withdraw at any time by deleting the review. We use reviews for nothing else.
To keep the service secure and available
Rate limiting, bot checks, protection against abuse, error monitoring and hosting logs, so that one abusive client cannot take the product down and a broken page gets fixed, and deleting accounts whose address was never confirmed, so that nobody keeps an account on someone else's address. Basis: our legitimate interest in running a secure, working service; each of these is stripped down to what that purpose needs.
To understand how the product is used
Pseudonymous usage counts that show which steps people finish and where they give up. Basis: our legitimate interest in improving the product, balanced by the design above — no cookies, no link to your account — and by your right to switch it off at any time on this page.
To measure visits over time and research the design, if you allow it
Recognising your browser on later visits (Google Analytics and PostHog cookies), heatmaps, and A/B tests that compare two versions of a page. Basis: your consent, given in the cookie banner, which you can withdraw at any time under "Cookie settings". See "Cookies and your consent".
To be able to recover from failure
The encrypted daily backup. Basis: our legitimate interest, and yours, in not losing your saved sets.
To meet legal obligations
Answering requests you make under data-protection law, and responding to a lawful demand from an authority. Basis: legal obligation.

These service providers host or receive data on our behalf, only to do the job listed next to them and under their data-processing terms. The exception is Paddle, which sells Pro as our reseller and handles payment data as its own controller. Nobody else receives it.

  • Vercel

    What it does
    Hosts and serves the website and the API; keeps request logs for one hour; checks sign-in, sign-up, email requests and reviews for bots (Vercel BotID).
    Where
    Servers in Frankfurt, Germany — region fra1; pages delivered through Vercel's worldwide network
  • Vercel Web Analytics

    What it does
    Cookieless page-view counts: page, referring page, country, device type, browser and operating system.
    Where
    Vercel Inc., United States — storage location not confirmed; see "International transfers"
  • Supabase

    What it does
    The product database: accounts, saved sets, usage events and abuse counters.
    Where
    Frankfurt, Germany — region eu‑central‑1
  • PostHog

    What it does
    Product analytics, configured as described above; with your consent also its cookie, heatmaps and A/B tests.
    Where
    European Union — EU cloud
  • Google Analytics

    What it does
    Measures visits and pages with cookies, only if you accept Analytics cookies, and is loaded only then. Google processes the data on our behalf under the Google Ads Data Processing Terms, which list Google Analytics as a service Google provides as a processor.
    Where
    Google Ireland Limited (Ireland); the data can be processed in the United States — see "International transfers"
  • Sentry

    What it does
    Error monitoring, configured as described above.
    Where
    European Union — Sentry's EU region
  • GitHub

    What it does
    Runs the daily backup job on a machine it hosts, which copies the database, encrypts and test-restores it; keeps the encrypted copy for 30 days.
    Where
    United States — see "International transfers"
  • Paddle

    What it does
    Reseller and Merchant of Record for Pro: runs the checkout, takes payment, adds tax, sends receipts and handles refunds and billing support. Receives payment data as its own controller.
    Where
    Paddle.com Market Ltd, United Kingdom — see "International transfers"
  • Resend

    What it does
    Our email delivery provider: sends the email that confirms your address when you sign up and the password-reset email you ask for, so it receives your account's email address and the message with the link.
    Where
    Plus Five Five, Inc., United States — see "International transfers"
  • Hostinger

    What it does
    Hosts our support mailbox, which receives and stores the messages you send to support@djcoachpro.com and our replies.
    Where
    Hostinger International Ltd, Cyprus — see "International transfers"
  • Anthropic

    What it does
    Would rephrase transition explanations. Switched off: nothing is sent.
    Where
    United States — only if switched on

We may disclose data if the law requires it, for example under a court order, and only to the extent required.

If the service is ever transferred to another operator, your data moves with it under this policy, and we will say so on this page before it happens.

The product's database and the servers that run it are in the European Union, in Frankfurt; the pages themselves are delivered through Vercel's worldwide network, like most websites. The European Union recognises Israel as providing adequate protection for personal data, and Israel's regulations on transferring data abroad permit transfers to countries that are party to the Council of Europe's data-protection convention, which every EU country is.

Some data leaves the European Union. The first is the daily backup: the database is copied to a GitHub-hosted machine in the United States, encrypted and test-restored there, and the machine is then discarded; GitHub keeps the encrypted copy for 30 days. While the job runs the copy is unencrypted on that machine, and the encryption passphrase is a secret stored in our GitHub account, so GitHub's systems do handle this data. GitHub is certified under the EU–US Data Privacy Framework and also relies on the EU Standard Contractual Clauses.

The second is Vercel Web Analytics. Vercel Inc. is a US company, and we have not been able to verify where it stores these page-view counts, so treat them as processed in the United States. Switching analytics off stops them.

Only if you accept Analytics cookies: Google Analytics data can be processed in the United States by Google LLC, which is certified under the EU–US Data Privacy Framework, the UK Extension to it and the Swiss–US Data Privacy Framework. Rejecting Analytics cookies, or withdrawing your consent, stops it.

The third is the email we send you, the link that confirms your address when you sign up and a reset link when you ask for one: your account's email address and the message go through Resend (Plus Five Five, Inc.), in the United States. Resend is certified under the EU–US Data Privacy Framework and also relies on the EU Standard Contractual Clauses.

The fourth may be email you send us: our support mailbox is at Hostinger (Hostinger International Ltd, Cyprus), which stores the messages you send us and our replies. Hostinger does not publish where it stores mailboxes. Our mail reaches it through its servers in Germany and France, but its privacy policy says it may store personal data in the United Kingdom and that some of its servers are outside the European Union. Hostinger's data-processing terms apply the EU Standard Contractual Clauses to any transfer outside the European Economic Area.

When Pro is on sale, Paddle processes payment data under its own privacy notice; its contracting company is in the United Kingdom, which the European Union recognises as providing adequate protection and which is party to the same Council of Europe convention.

The AI rephrasing mode would send transition data to Anthropic in the United States. It is off. If it is ever switched on, the transfer will be covered by that provider's data-processing terms, and this policy will be updated first.

A guest plan
7 days in your own browser; after that it is discarded on your next visit. Clearing your browser's site data removes it at once.
Audio analyses and corrections on your device
In your browser only, until you delete them; we never receive them. "Clear saved analyses" in the "Audio analysis" panel deletes the saved analyses, and clearing this site's data in your browser deletes the analyses, your corrections and the review marks. The analysis store keeps at most 2,000 files, removing the least recently used first, and the corrections store at most 5,000, removing the oldest first.
Your account, sets and reflections
Until you delete them, or until your account is deleted.
A "notify me" request
Until your account is deleted.
Your subscription record
While your account exists; it is deleted with your account. Paddle keeps its transaction records under its own policy.
Paddle notification records
180 days after the notification (or, per subscription, after its latest notification), then deleted automatically. They hold Paddle IDs only and outlive account deletion until then.
Sign-in sessions
A session lasts up to 30 days and is extended while you keep using it, but never beyond 90 days after you signed in. Signing out deletes it immediately; an expired session is deleted within a day.
Password-reset links
A link works once, for 30 minutes. Our record of it is deleted by the daily clean-up once a day has passed since the link expired or was used; asking for a new link or setting a new password deletes your other unused links, and deleting your account deletes them all.
Unconfirmed accounts
If your email address is not confirmed, the account and everything in it are deleted automatically by the daily clean-up after the last day for confirming it, which the site shows you. If we sent you a confirmation link, that day is 7 days after the day we sent the latest one, and never later than 30 days after you signed up, however many links were sent. If no link could be sent, it is 30 days after you signed up, except while our email sending is switched off: then an account that never got a link is kept. An account with a subscription is never deleted this way, and accounts that existed before email confirmation was introduced count as confirmed.
The email confirmation record
While your account exists; it is deleted with your account. The hash of a link's secret is deleted as soon as you confirm, and replaced when you ask for a new link.
Reviews
A review stays until you delete it or you delete your account. If we reject it, the daily clean-up deletes it 30 days after the day we rejected it. A review you did not allow us to publish, or that has no text, stays private and is shown to nobody, until you delete it or delete your account. When you delete a published review it leaves the website at once, but a copy held by the website's delivery network or another shared cache can still show it for up to five minutes.
Abuse counters
Only for the window they measure — between one minute and one day — and then they are deleted.
Usage events in our database
Six months (180 days). Older events are deleted automatically every day.
Usage events in PostHog
For the retention period of PostHog's plan, which is one year on the plan we use. PostHog applies that limit on its side.
Your cookie choice
12 months in this browser; then we ask again. We also ask again when what a category covers changes.
Google Analytics (only with your consent)
Its cookies last up to 12 months after your last visit, and are deleted from this browser at once when you withdraw your consent or it expires. Google keeps event-level data for 2 months, the shortest setting it offers; that setting does not apply to Google's standard reports, which show only totals.
PostHog cookie and browser storage (only with your consent)
Up to 12 months, and deleted from this browser at once when you withdraw your consent. The events themselves are kept as described under "Usage events in PostHog".
Error reports in Sentry
Deleted automatically by Sentry after the retention period of our plan — no more than 90 days.
Hosting request logs
One hour.
Backups
30 days. This means that data you delete can remain inside an encrypted backup for up to 30 days before that backup expires. Backups are used only to restore the service after a failure.
Email you send us
As long as we need it to answer you and to keep a record of what we agreed (for example, a refund), and then deleted. Hostinger keeps its own records under its data-processing terms.
Password-reset and confirmation emails
We keep no copy of the email. Resend keeps its records of the messages it delivers under its data-processing terms.

Every connection to DJ Coach is encrypted (HTTPS), and the database is reached over an encrypted connection. Passwords are stored only as bcrypt hashes, session tokens only as SHA-256 hashes, and abuse counters only as keyed hashes. Backups are encrypted with AES-256 on the machine that makes them, before they are stored, and the passphrase is kept as a secret in our GitHub account. Access to production systems is restricted to the people who operate DJ Coach. A password-reset link works once and for 30 minutes; its secret travels in the part of the link your browser never sends to a server, it is stored only as a SHA-256 hash, and setting a new password signs you out on every device. A link that confirms your email address is kept the same way, and it confirms nothing until you press the button on the page it opens. Deleting your account asks for your password. Audio analysis runs entirely inside your browser and sends your audio to no one.

No system is perfectly secure. If a security incident affects your data, we will notify the authorities and you as the law requires.

You have the right to see the data we hold about you, and to ask us to correct it or delete it. If you are in the European Union or the European Economic Area, you also have the right to receive your data in a portable format, to restrict or object to processing based on our legitimate interest, and not to be subject to decisions made solely by automated means (we make none).

Delete your account yourself
Sign in, open "Your sets", open "Account management" and choose "Delete account". It takes effect immediately and removes your account, your sessions, your review, every saved set and every track, plan item, transition and reflection in it from the live database. It cannot be undone. Copies inside the encrypted backups expire within 30 days. Usage events are not stored with your account, and we keep no record that ties a visit identifier to an account, so they cannot be picked out and deleted with it; they are deleted on the six-month schedule above. If you have had a Pro subscription and we cannot confirm with Paddle at that moment that none is still active, the deletion is refused and nothing is deleted: you are asked to cancel from "Manage subscription" first, or to contact us.
Delete your review
Open "Your sets": if you left a review, it is shown there with a "Delete my review" button, and the same button is in the download dialog. Deleting is immediate and withdraws your consent to publish it. You can also write to us.
See and correct it in the product
Your sets, their plans and your reflections are all visible in the product. Track details can be corrected in the review step before a plan is generated, and any plan can be exported back to a playlist file for your DJ software.
Data kept on your device
Audio analyses, your corrections and a plan in progress are kept only in your browser, so we cannot see, copy or delete them for you, and a request to us does not cover them. You can delete them yourself: "Clear saved analyses" in the "Audio analysis" panel deletes the saved analyses, and clearing this site's data in your browser deletes everything DJ Coach keeps there.
Ask us
For access, correction, deletion, a copy of your data (we send it as a JSON file), restriction or objection, write to support@djcoachpro.com from the email address on your account, so we know the request is yours. It is free. We answer within 30 days, and within one month for requests under EU law.
Object to analytics, or withdraw consent
Switch usage analytics off below, or turn on Global Privacy Control or Do Not Track in your browser. See "Turning analytics off". Consent to cookies can be withdrawn at any time under "Cookie settings" at the bottom of every page, as easily as it was given; withdrawing does not affect what was collected before.

Analytics is on by default because it is cookieless and not tied to your account. You can switch it off here at any time. When it is off, this browser loads no analytics code, records no usage events on our side or in PostHog, keeps and sends no visit identifier, and Vercel Web Analytics counts no page views. Switching it off also stops anything already waiting to be sent.

Your choice is saved in this browser only (in localStorage), so it applies to this browser and device. A browser that sends a Global Privacy Control or Do Not Track signal is treated as switched off automatically, with no need to use this switch. The analytics code is only loaded after the page has checked your choice, so there is a brief moment at first load when nothing runs yet.

Switching it off here also refuses the optional cookies described under "Cookies and your consent", and accepting one of those categories switches it back on, so the two choices can never disagree.

Error reports are not affected: they exist to keep the service working and contain no account or request data, as described above.

Usage analytics

Checking this browser's setting…

On your first visit a banner asks whether you allow optional cookies. "Accept all" and "Reject all" are equally easy, and "Choose" lets you decide per category. Until you choose, nothing optional runs, and nothing optional is ever switched on in advance.

Necessary storage is always on, because the site cannot work without it: signing in, the bot check, the guest plan and your cookie choice. It is listed under "Cookies and browser storage".

Analytics (optional)
Google Analytics counts visits and pages. It is loaded only after you accept: before that no request goes to Google at all. It runs without Google signals and without ad personalisation, every advertising consent stays refused, and it receives the page address described under "Google Analytics (only with your consent)". PostHog also keeps its own random identifier in a cookie and in browser storage, so it recognises this browser when you return; it stays the pseudonymous identifier it was, never linked to your account.
Product research (optional)
PostHog records heatmaps: where on a page you click (including repeated clicks and clicks that do nothing), where the pointer moves and how far you scroll, as positions on the page, without the text of anything you click or type. It may also place you in an A/B test, which shows some visitors a different version of a page: PostHog then receives which version you saw, and your browser's time zone setting with the request that decides it. Session recording and automatic capture of what you click or type stay off. Without Analytics cookies, the version can change from one visit to the next.

The basis for both categories is your consent (Article 6(1)(a) GDPR, and the consent that storing or reading cookies needs under the EU's ePrivacy rules). You can withdraw it at any time under "Cookie settings" at the bottom of every page. Withdrawing applies at once, without reloading the page: Google Analytics stops and its cookies are deleted from this browser, and PostHog goes back to working without cookies, with heatmaps and A/B tests off. It does not affect what was collected before.

Your choice is kept in this browser for 12 months. After that, or when what a category covers changes, we ask again.

A browser that sends a Global Privacy Control or Do Not Track signal is treated as refusing both optional categories, and no banner is shown. To change that, change the setting in your browser.

Analytics
…
Product research
…

Checking this browser's choice…

DJ Coach sets no advertising cookie and no third-party cookie, and does no cross-site tracking. Without your consent it sets no analytics cookie either. This is everything it keeps in your browser; the table after the list gives each item's provider, purpose, duration and category:

Session cookie — __Host-djcoach_session
Keeps you signed in. Set only when you sign in; readable by the server only (HttpOnly), SameSite=Lax, sent over HTTPS only and only to this exact site (that is what the __Host- prefix requires), valid for up to 30 days, deleted when you sign out. If you signed in before the cookie was renamed, your browser holds it as djcoach_session until your next visit renames it.
Sign-in hint cookie — djcoach_auth
Always the value 1. It only tells the page that it is worth asking the server who you are, so signed-out visitors are spared that request. It carries no identity, the server never reads it, and it is set and cleared together with the session cookie.
Bot check — Vercel BotID
When you sign in, sign up, ask us for an email or send a review, the bot check of our hosting provider runs a script served from our own address. It may keep technical values in your browser, only to tell a person from an automated program. We do not read them, and they are not used for advertising or tracking.
Guest plan — localStorage
Your plan in progress, so closing a tab does not lose it. If you used audio analysis, it also holds the review marks for each track: the values you accepted, kept or corrected, which values came from the audio files' tags, and a reference to the file's analysis on this device (its content hash). Kept for 7 days.
Analytics choice — localStorage
Present only if you switch usage analytics off on this page. It records that choice and nothing else.
Cookie choice — localStorage djcoach.consent.v1
Your answer to the cookie banner: whether you allowed Analytics and Product research, and when. Kept for 12 months.
Layout hint — localStorage
The height your "Your sets" list had on this screen size last time, so the page does not jump while it loads. Only numbers — nothing about the sets themselves.
Saved analyses — IndexedDB djcoach-audio
Present only if you used audio analysis. The result for each analysed file — tempo, beat grid, key, loudness, energy, sections, estimated cue points and a small waveform for display — stored under the file's content hash, so the same file is not analysed twice. No audio and no file name. At most 2,000 files, the least recently used removed first. "Clear saved analyses" in the "Audio analysis" panel deletes them.
Your corrections — IndexedDB djcoach-corrections
Present only if you corrected an analysed value by hand — for example halved a BPM or moved the first beat — or locked a value against the analysis. Each correction is stored under the file's content hash, so it comes back with the same file in another playlist. At most 5,000 files, the oldest removed first. "Clear saved analyses" does not delete them; clearing this site's data in your browser does.
Tab storage — sessionStorage
The random visit identifier, markers that stop the same usage event being counted twice in one visit, your scroll position on a plan, a note that you asked to save a plan or to hear when Pro opens while signing in, a one-time note that your account was just deleted, an unsent reflection draft, which account last signed in in this tab (so that a different person signing in here starts a new visit and does not inherit the previous person's draft), and, if part of the home page fails to load, that page's address, so it is reloaded only once. All of it disappears when the tab is closed.
Google Analytics cookies — _ga, _ga_…
Only if you accept Analytics cookies. Set by Google Analytics on this site: a random identifier for your browser (_ga) and the state of your visit (_ga_ followed by our property ID). Deleted when you withdraw your consent.
PostHog — ph_…_posthog
Only if you accept Analytics cookies. PostHog's random identifier for this browser and its current visit (the name holds our PostHog project key), as a cookie and in localStorage, plus visit and window markers in tab storage. In localStorage PostHog also keeps, for its own record of the visit, the address you arrived on (without anything after #) and the referring page; neither is in the cookie, and we remove both from everything sent. With Product research also allowed, it holds which version of an A/B test you were given. Deleted when you withdraw your consent.
  • __Host-djcoach_session (cookie)

    Provider
    DJ Coach
    Purpose
    Keeps you signed in
    Duration
    Up to 30 days; deleted when you sign out
    Category
    Necessary
  • djcoach_auth (cookie)

    Provider
    DJ Coach
    Purpose
    Tells the page it is worth asking who you are
    Duration
    As long as the session cookie
    Category
    Necessary
  • Vercel BotID values

    Provider
    Vercel
    Purpose
    Tells a person from an automated program when you sign in, sign up, ask for an email or send a review
    Duration
    As Vercel sets them; not published by Vercel
    Category
    Necessary
  • Guest plan (localStorage)

    Provider
    DJ Coach
    Purpose
    Your plan in progress
    Duration
    7 days
    Category
    Necessary
  • djcoach.consent.v1 (localStorage)

    Provider
    DJ Coach
    Purpose
    Your cookie choice
    Duration
    12 months
    Category
    Necessary
  • djcoach.analytics.optout.v1 (localStorage)

    Provider
    DJ Coach
    Purpose
    Your choice to switch usage analytics off
    Duration
    Until you switch it back on
    Category
    Necessary
  • Layout hint (localStorage)

    Provider
    DJ Coach
    Purpose
    Keeps "Your sets" from jumping while it loads
    Duration
    Until you clear this site's data
    Category
    Necessary
  • djcoach-audio, djcoach-corrections (IndexedDB)

    Provider
    DJ Coach
    Purpose
    Audio analyses and your corrections, only if you use audio analysis
    Duration
    Until you delete them; capped as described above
    Category
    Necessary
  • djcoach.analytics.sid.v1 (sessionStorage)

    Provider
    DJ Coach
    Purpose
    The random visit identifier for cookieless usage analytics
    Duration
    Until the tab is closed
    Category
    Usage analytics without cookies (on unless you switch it off)
  • Other tab storage (sessionStorage)

    Provider
    DJ Coach
    Purpose
    Once-per-visit markers, scroll position, sign-in notes, a reflection draft, which account last signed in in this tab (so someone else signing in here starts a new visit, without the previous draft), the home page's address if part of it fails to load (it is reloaded only once)
    Duration
    Until the tab is closed
    Category
    Necessary
  • _ga (cookie)

    Provider
    Google
    Purpose
    Distinguishes browsers for Google Analytics
    Duration
    Up to 12 months after your last visit
    Category
    Analytics (consent)
  • _ga_… (cookie; the name ends in our property ID)

    Provider
    Google
    Purpose
    Keeps the state of your visit for Google Analytics
    Duration
    Up to 12 months after your last visit
    Category
    Analytics (consent)
  • ph_…_posthog (cookie and localStorage; the name holds our project key)

    Provider
    PostHog
    Purpose
    PostHog's random identifier for this browser and its visit
    Duration
    Up to 12 months
    Category
    Analytics (consent)
  • ph_… (sessionStorage)

    Provider
    PostHog
    Purpose
    The current visit and window
    Duration
    Until the tab is closed
    Category
    Analytics (consent)
  • A/B test version (inside PostHog's storage)

    Provider
    PostHog
    Purpose
    Which version of an A/B test you were given
    Duration
    As PostHog's storage above
    Category
    Product research (consent)

Without your consent, PostHog keeps nothing in your browser; Vercel Web Analytics never does. Google Analytics is not loaded at all without your consent.

Paddle's checkout loads only when you choose to buy Pro, in Paddle's own window, under Paddle's own cookie and privacy terms. Nothing from Paddle is loaded before that.

To remove all of the above, the audio analyses and corrections included, sign out and clear this site's data in your browser's settings. Closing the tab clears the tab storage on its own.

You must be at least 13 years old to use DJ Coach — with or without an account. If you are under 18, you may use it only with the agreement of a parent or guardian, who accepts these documents with you. In the European Union and the European Economic Area, a user under 16 likewise confirms that a parent or guardian has agreed.

If we learn that someone under 13 has created an account, we delete the account. A parent or guardian who believes this has happened can write to us at support@djcoachpro.com.

Younger users get the same small footprint as everyone else: no advertising and no advertising profiles, no sale of data and no cross-site tracking. The account and the service rest on our agreement, and cookieless analytics and error monitoring on legitimate interest, with analytics open to opt-out. The only processing that relies on consent is the optional cookies (Analytics and Product research), which stay off unless accepted: in the European Union and the European Economic Area, a user under 16 should accept them only with a parent's or guardian's agreement, and "Reject all" is always available.

DJ Coach sends two kinds of automated email. When you sign up, one link that confirms your email address; it is sent again only if you ask for it, and an account whose address is not confirmed is deleted after 7 days (30 if the email could not be sent; while our email sending is switched off, such an account is kept). And a password-reset link, only when you ask for one with "Forgot your password?" on the sign-in page, and only to the email address of an account; it works once, for 30 minutes. Nothing is sent for marketing. If you cannot reset your password that way, write to us at support@djcoachpro.com.

Apart from that, we email you in two cases only: to answer a message you sent us, and — if you pressed "Notify me when Pro opens", which needs a confirmed address — once, to tell you that Pro is available. Our support mailbox runs on Hostinger, and the confirmation and reset links are sent through Resend. When Pro is on sale, Paddle sends the receipts and billing emails for your purchase.

If we ever start sending other email, this policy will say what and why before we do, and we will send marketing messages only to people who have agreed to receive them, as Israeli law requires.

If you are unhappy with how we handle your data, please write to us at support@djcoachpro.com first — we will try to put it right.

You also have the right to complain to a supervisory authority: in Israel, the Privacy Protection Authority at the Ministry of Justice; in the European Union or the European Economic Area, the data-protection authority of the country where you live or work, or where you believe the problem happened.

When what the product does changes, this page changes with it: the version and the "Last updated" date at the top move, and a line says what changed.

A significant change — a new service provider, a new kind of data, a new purpose, a longer retention period — is announced on the site before it takes effect, not quietly edited in.

Write to us at support@djcoachpro.com. How quickly we answer, and where to go for payment questions, is on our Contact page.