← Back

Privacy policy

Note on this translation: The legally binding version of this document is the German one. This English translation is provided to help you understand it; in case of any discrepancy, the German wording applies.

1. Controller

Samuel Liba

Samuel Liba Digital Solutions

Geranienweg 7, 85586 Poing, Germany

Email: hallo@framepath.de

2. Data collected

When you use this platform, the following data are processed:

  • —Email address (for registration and login)
  • —If you sign in to the app with Apple or Google: your account identifier with that provider and the email address it passes to us (with Apple optionally a relay address), with Google also the name and profile picture address from your Google profile. We never learn your password there. Plus the time you confirmed “at least 16” and agreed to the terms
  • —Display name, username, profile data (avatar choice, genre preferences, equipment, software, experience level, city) — your profile is publicly accessible under your username
  • —Your answers from the onboarding survey (goal, time budget, prior experience)
  • —Learning progress data: lessons opened (when first opened and how far you got), completed skills and phases, quiz attempts and results, XP collected, streak, chosen daily goal, practice days logged and DJ logbook entries (type, duration, date, optional note), reviews due and daily tasks redeemed. For the badges we also keep counts only: how often you listened to listening examples in full, answered questions and used tools (which tools, how many phrases, Camelot pairs and minutes on the simulator), whether you hit 128 BPM, at how many gigs the ear-break reminder was on, and how often other signed-in users opened your profile — we never store who looked
  • —My Studio: for your studio, we store the room, the light mood and which item stands on which spot — at the latest once you furnish it for the first time, and after that the way you furnish it. Until then we show you the starting studio without storing anything. When you buy something with Gage, we store the item, the price and the time — your Gage balance is calculated from that. On top of that, the code of your DJ character is stored on your profile so the studio can draw your figure itself. Gage is an in-game currency you only earn through activity; no real money is ever involved. If your profile is public, other signed-in users can view your studio: the room, light mood, furnishing, style including the neon sign, your figure and the number of lessons you have completed (which is shown on your public profile anyway). Purchases, prices and your Gage balance are visible only to you. If you set your profile to private, nobody but you can see your studio. Once your studio is stored with us, we also note on it whether your studio and your figure should be shown while you learn (one switch each, on by default) — so your choice applies on every device. If you had switched one of them off on a device before, we take that over from there once, the next time you visit your learning path. So that another account in the same browser doesn’t inherit your setting, the browser also keeps a short tag derived from your account ID (not the ID itself); it never leaves the device. If another account signs in there, the browser resets both switches: if that account has its own setting stored with us, that applies from then on; otherwise both are on. A choice that was only kept in the browser because your studio had not been stored with us yet is lost in the process — when you come back to this device afterwards, both switches are on there again. Only you can see the switches. If you delete your account, both go with it.
  • —Studio career: when you complete a career task in your studio, we store which task it was, when you completed it and whether it was already fulfilled when you first opened the career (this only applies to accounts that had used their studio before: their already fulfilled tasks are taken over at that point without you completing them yourself). Whether a task is fulfilled is checked against data that exists anyway: your purchases with Gage, your furnishing, your light mood and which learning phases you have completed. On top of that, we note on your studio when you saw or skipped the first-time introduction, since when your career has been running, and whether the task note should be shown in the room. If you have no saved furnishing yet, we create the row for your starting studio for this when your career first loads (the bedroom with the items every studio starts with) — or already at the switchover if by then you had only bought something. If you used your studio before the introduction existed (saved it or bought something), you never see it; in that case the time stored is the time of the switchover rather than a time you saw it. Anyone who gets the introduction receives their first speakers as a gift, even if they skip it; this appears among your purchases like a purchase at price 0 and does not change your Gage balance. We do not hand them out afterwards. A task never earns Gage, XP or real money, and nothing in learning depends on it. Only you can see which tasks you have completed. If you delete your account, all of it goes with it.
  • —Your DJ character's wardrobe: when you store a look in the wardrobe, we save its character code in one of six fixed slots on your profile (no free text). Whether a look contains parts that only come with a pass, with Gage or with a learning badge is checked when you store it, against data that exists anyway: your passes, purchases, badges and completed phases. Unlike your profile, the wardrobe is not public — only you can see it. If you clear a slot, the look is gone; if you delete your account, the whole wardrobe goes with it.
  • —Supporters (applies only once the supporter programme starts): when you support DJLearn, we store your pass (Guest List, Backstage, Booth or Opening Night), since when and until when it is valid, the amount, whether it was paid once, monthly or yearly, for Opening Night your spot number and, if the operator adds one, an internal note about it (never public). On top of that, three separate consents that are off by default: your DJ name on the public supporter wall (in the app together with your figure, the DJ character, in the Supporter House on the floor of your pass), your name in the thank-you reel on Instagram (for this our video workshop only receives your DJ name, and for Booth the code of your DJ character), and your supporter badge on your public profile. The Supporter House adds a fourth switch, also off by default: “Show my studio” — other signed-in users who tap your figure then see your studio, but only if your profile is public; we only store the yes or no, never who looks at it. If you took part in the former monthly supporter vote (discontinued on 20 November 2026), which of the three options you chose and when stays stored until you delete your account; nobody sees it individually, the operator included, and you receive it with the export of your data. Only what you agreed to becomes publicly accessible — and never an amount; the page only shows the total of all contributions. Learning stays free for everyone; none of it depends on a pass. You can withdraw any consent at any time; if you delete your account, your pass, consents and votes go with it.
  • —Supporter purchases in the app (applies only once the app sells them): if you buy a supporter pass in the iPhone app, you pay Apple — only Apple sees your name, Apple Account and payment details, never us. So that the pass reaches your DJLearn account, the app gives Apple your account identifier with the purchase, and Apple sends us a confirmation signed by Apple. From it we store: the identifiers of the purchase at Apple, which product, whether it was a test or a real purchase, purchase and expiry date, the price and currency as Apple reports them, whether a subscription renews or has been cancelled, and whether Apple refunded the purchase. Apple also tells us about renewals, cancellations, expiry and refunds when you do not open the app. For Opening Night, we note for 15 minutes before the purchase that a spot is reserved for you. If a paid purchase cannot be booked (for example because all 25 spots were taken), we store it as a case to resolve so the operator can help you. None of this becomes public; if you delete your account, purchases, reservation and open cases go with it. The legal basis is performing the purchase (Art. 6(1)(b) GDPR); Apple's own processing is governed by Apple's privacy policy.
  • —Have your say: when you vote on feature proposals, we store against your account which proposal you gave one of your three votes to and when. Only you can see your votes; everyone else — the operator included — only sees the totals per proposal (votes overall and how many people voted). If you currently have an active supporter pass (Backstage, Booth or Opening Night), your vote counts double; for this the count checks whether your pass is active, and none of it is shown individually. If an idea you sent while logged in via “Help & feedback” becomes a proposal, we remember that link so you can see in the app what became of it. Voting earns no XP and no advantage. You can take back a vote at any time; if you delete your account, your votes go with it.
  • —Shared links: when you share your learning progress or a DJ spot, an address is created under which the shared content is accessible to ANYONE who knows the link — even without an account. You can withdraw a link at any time; after that it leads nowhere.
  • —Reports: when you report a profile, a DJ spot or a post in the community feed, we store WHAT you reported, the reason you picked and your optional note — together with your identifier. Without it, misuse of the reporting function could not be detected. Whoever was reported does NOT learn who reported them; only the operator can read the report, reviews it and, if necessary, takes the content out of public view. You can see your own reports in your data export. If you delete your account, your reports go with it; the same happens if the reported content is deleted.
  • —Blocks: when you block a user, we store WHOM you blocked and when. After that, the two of you no longer see each other — neither profile nor spots nor leaderboard —, any friendship between you ends, and neither of you can send the other a request. Only you can see your list of blocks; the blocked person is not notified. You can lift a block at any time; if you delete your account, your blocks go with it.
  • —DJ spots with location data (only if you place them yourself — you choose the coordinates) along with photos, videos, voice notes and the names of any companions you enter; for planned gigs also the date, set time and occasion, which are as visible as the spot itself, and your prep list with ticks and your own items, which only you can see. In the iOS app, when you drop a spot, Apple’s place search looks up the city for the pin position (the position goes to Apple for this; we only store the city name on the spot); “My location” asks for your location only when you tap it, only while the app is open, and does not store it
  • —Mix recordings you upload and the feedback you write on other people's mixes
  • —Friend requests and friendships (only with mutual consent)
  • —Notifications (receipt, read status, timestamp)
  • —Push subscriptions: when you enable push notifications on a device, we store the delivery address issued by your browser and its encryption keys. If you disable push, the entry is deleted. The app’s reminders (learning, streak, gigs) are scheduled by your device itself; we store nothing for them and nothing is sent to our server.
  • —Wishlist: when you save a product in the equipment catalogue, we store the product's identifier, whether you have ticked it off as bought, and the time. Only you can see the list; it is deleted with your account.
  • —Use of the equipment catalogue: we count anonymously which filters are chosen, which products are saved and which links are clicked — only event type, product, language and day. No link to an account, no IP address; two events cannot be attributed to the same person.
  • —App usage statistics (iOS and Android): we store against your account on which days you open the app and which areas you use — as fixed, named events (app opened, onboarding step, quiz passed, review finished, studio, tool, supporter page and purchase, supporter wall, help, music in the studio, DJ logbook entry with its type, gig added with or without a time, look back after a gig saved, whether you allowed reminders, whether the app asked for a rating, “Have your say” opened, vote given), plus app version, platform (iOS/Android), language and time. No content, no device identifier, no advertising ID, no IP address. No third party is involved: the data goes only to our own server. We use it to see how many people come back and where onboarding breaks off, in order to improve the app. You can switch the statistics off in the app under Settings → “Usage statistics”; nothing is recorded or sent after that. We keep the entries for 13 months at most; they are deleted together with your account.
  • —Technical access data (IP address, browser, timestamp) — in server logs
  • —Error diagnostic data when an error occurs in the app (error message, stack trace, page called up, browser identifier) — see section 8
  • —Error reports and feedback from the iPhone app: if an error occurs in the app, it automatically sends an error report to our own server (not to Sentry). It contains the error message, a shortened stack trace, the page of the app where it happened (without identifiers), the app's version and code revision, the operating system and its version, and the app's language. The app removes email addresses, sign-in tokens and URL parameters beforehand; your name, your email address and your account identifier are not attached to the report. So that a faulty device cannot report without limit, we only count the NUMBER of reports per account and day — under a daily key from which your account cannot be read — and delete that number after seven days. Without an internet connection, a report waits on your device for at most two weeks. If you write to us via “Help & feedback”, we store your text, the type you chose (bug, idea or praise), the same technical details, the page of the app you came from and — if you are signed in — your account identifier, so that we can attribute the feedback. Only the operator can read either; they are kept like the other entries of the error board (section 10). The legal basis is our legitimate interest in a stable, secure app (Art. 6(1)(f) GDPR).
  • —Anonymous page-view statistics (Vercel Web Analytics and, since 2026-09-18, Ahrefs Web Analytics): page visited, referrer, country, device type and browser — without cookies, without a persistent identifier and without profiling; the numbers are only visible in aggregate and cannot be traced back to a person

3. Purpose of processing

The data are used exclusively to provide the platform's functions: authentication, storing your learning progress and personalising the learning experience. They are not passed on to third parties for advertising purposes. We process reports and blocks to protect users from offensive, objectionable or unlawful content; the legal basis is our legitimate interest in a safe community (Art. 6(1)(f) GDPR). Texts that others can see (DJ name, username, bio, location, spot names and notes) are checked by an automatic word filter when saved; it stores nothing additional in the process.

4. Legal basis

Your data are processed on the basis of Art. 6 (1) (b) GDPR (performance of a contract) and Art. 6 (1) (f) GDPR (legitimate interest in operating the platform).

5. Third-party provider — Supabase

This platform uses Supabase (Supabase Inc., 970 Toa Payoh North, Singapore) as its backend infrastructure for authentication and database services. Supabase processes data in accordance with its own privacy policy. The data are stored in EU data centres.

6. Hosting — Vercel

This platform is hosted by Vercel Inc. (440 N Barranca Ave #4133, Covina, CA 91723, USA). When the website is accessed, technical data (including IP address, browser, timestamp) are automatically recorded in server logs. Vercel processes these data in accordance with its privacy policy. The transfer of data to the USA takes place on the basis of the EU standard contractual clauses (Art. 46 GDPR).

7. Map service — Mapbox

The DJ spot map uses Mapbox (Mapbox Inc., 740 15th Street NW, 5th Floor, Washington DC 20005, USA) to display map tiles. As soon as you load a page containing a map (for example /karte), your IP address is transmitted to Mapbox so that the map data can be delivered. Mapbox processes the data in accordance with its privacy policy.

The transfer takes place on the basis of our legitimate interest (Art. 6 (1) (f) GDPR) in offering you the map functions. The transfer of data to the USA is safeguarded by EU standard contractual clauses.

8. Error analysis — Sentry

So that we can notice and fix crashes and errors in the app, we use Sentry (Functional Software, Inc. d/b/a Sentry, 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA). When an error occurs, the following are transmitted: the error message and stack trace, the page called up, details of the browser, operating system and device, and your IP address. In addition, performance data are recorded for a sample of around 10% of page views.

We deliberately transmit no user identity to Sentry — neither your email address nor your user ID nor your name. Session recordings (“session replay”), meaning the capture of your screen contents and input, are completely disabled.

The legal basis is our legitimate interest in the stable, secure operation of the platform (Art. 6 (1) (f) GDPR). The transfer of data to the USA is safeguarded by EU standard contractual clauses (Art. 46 GDPR). Details in Sentry's privacy policy.

Independently of this, we also log errors in our own database (Supabase, see section 5) in order to evaluate them on our internal error board. What is stored is the error message, the stack trace, the page called up, a browser identifier and — if you are logged in — your user ID. These data do not leave our own infrastructure.

9. Email notifications — Resend

To send reminder emails we use Resend (Plus Five Five, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA). What is transmitted is your email address and the contents of the message (for example your DJ name and the state of your learning streak).

There are exactly two kinds of such mail: a reminder when your learning streak is about to lapse, and a weekly summary of your progress. They go only to active users. We do not send third-party advertising, and your address is not passed on or sold.

Every one of these emails contains an unsubscribe link. One click stops all reminder emails permanently; your account is unaffected. The legal basis is our legitimate interest in communicating with our users about their own learning progress (Art. 6 (1) (f) GDPR); you may object to this processing at any time (Art. 21 GDPR).

The transfer of data to the USA is safeguarded by EU standard contractual clauses (Art. 46 GDPR). Details in Resend's privacy policy.

System-critical emails — for example to reset your password or confirm your address — are triggered by Supabase (see section 5) and likewise delivered via Resend. The information in this section applies to those messages too. They are necessary for the operation of your account and cannot be unsubscribed from.

10. Retention period

Your data are stored for as long as your account is active. You can permanently delete your account and all associated data at any time via your profile settings — deletion takes place without delay.

Supabase and Vercel may keep short-term technical backups (up to 30 days). After that these too are overwritten automatically. Server access logs (IP, timestamp) are kept for a maximum of 14 days and then anonymised or deleted.

Error reports at Sentry (section 8) are deleted automatically after 90 days. Delivery data at Resend (section 9) are deleted no later than on termination of the service. Entries on our internal error board are cleared once the error in question has been fixed.

11. Your rights

Under the GDPR you have the following rights:

  • —access to the data stored about you (Art. 15 GDPR)
  • —rectification of inaccurate data (Art. 16 GDPR)
  • —erasure of your data (Art. 17 GDPR)
  • —restriction of processing (Art. 18 GDPR)
  • —data portability (Art. 20 GDPR)
  • —objection to processing (Art. 21 GDPR)

To exercise your rights, contact us by email at hallo@framepath.de. You also have the right to lodge a complaint with a data protection supervisory authority.

12. Cookies & local storage

This platform uses only technically necessary cookies for authentication (session tokens from Supabase Auth). No tracking or advertising cookies are used. Consent is not required for technically necessary cookies (§ 25 (2) TDDDG, Art. 6 (1) (f) GDPR).

In addition we store small amounts of data in your browser's local storage in order to remember UI settings (for example your chosen map style or your onboarding position). These data do not leave your device.

13. Minors

Our service is aimed at people aged 16 and over. If you are younger, you need the consent of a parent or guardian before creating an account. We do not knowingly collect data from children under 16. If we become aware of such data, we delete them immediately.

14. Push notifications

If you enable push notifications on a device (streak reminder and weekly recap), your browser creates a delivery address with your browser vendor’s push service (e.g. Google, Mozilla or Apple). We store this address and its encryption keys so we can send you messages. The content of the messages is end-to-end encrypted — your browser vendor’s push service cannot read it.

The legal basis is your consent (Art. 6(1)(a) GDPR): nothing is stored and nothing is sent without your explicit “Enable” on the device and your browser’s permission. You can withdraw your consent at any time — via “Disable” under notifications or in your browser settings; the stored entry is then deleted. If you delete your account, all push entries are deleted along with it.

15. Audience measurement (Vercel Web Analytics, Ahrefs Web Analytics)

To understand which pages are read, we use Vercel Web Analytics — audience measurement without cookies and without a cross-device identifier. It records the page visited, the referrer, country, device type and browser; evaluation is exclusively aggregate, no conclusions about individual persons are possible and no profiling takes place. The provider is Vercel Inc., which also provides the hosting (section 7).

The legal basis is our legitimate interest in analysing and improving the free offering (Art. 6(1)(f) GDPR). As no cookies are set and no information is stored on your device, no consent is required (§ 25 TDDDG does not apply).

Since September 2026 we additionally use Ahrefs Web Analytics by Ahrefs Pte. Ltd. (Singapore). For this your browser loads a script from analytics.ahrefs.com that counts the page view — according to the provider without cookies and without storing anything on your device; it records the page visited, the referrer, country, device type and browser, evaluated only in aggregate. When the script loads, Ahrefs technically receives your IP address. The transfer to Singapore relies on the EU standard contractual clauses (Art. 46 GDPR). The legal basis is, as above, our legitimate interest (Art. 6(1)(f) GDPR).

16. Affiliate links and places to buy

The equipment catalogue, the gear box of some buying guides and the wishlist carry links to retailers. The links labelled as ads earn us a commission — for example as a participant in the Amazon Associates programme. Links without that label earn us nothing. Which programmes exist and how we handle them is set out at https://djlearn.de/partner.

When you click one of these links, we count it anonymously: we store only the type of event, the product identifier, the retailer, the place the link sat (such as “catalogue card” or “wishlist”), the page address without language and query (such as “/dj-controller-vergleich”), the language and the date — no IP address, no user identifier, no session. Two clicks by the same person cannot be linked to each other. The legal basis is our legitimate interest in knowing which parts of the catalogue are used (Art. 6(1)(f) GDPR).

Only the click takes you to the retailer. From there the retailer's own privacy policy applies; in Amazon's case, Amazon also sets its own cookies in order to attribute a later purchase to us. We transmit no data about you in the process — neither your name nor your email address nor your setup. If you would rather not have that, open the retailer's site directly instead of using our link.

17. No data shared with AI services

Large parts of DJLearn's texts, translations and program code are produced with the help of AI language models (Claude by Anthropic), directed and approved by the operator. That work happens in development — on source code and content, not on your account.

The running site transmits no data to AI services: not your email address, your learning progress, your wishlist, your location permission or anything you enter into forms. The application contains no interface to such a service. Should that change, we will announce it here beforehand and state the legal basis.

How we make sure AI-assisted content is still backed by evidence — every factual claim with a source we have read, checked before every release — is set out at https://djlearn.de/quellen.

18. In-app purchases — Apple

Once supporter passes are sold in the DJLearn app, the following applies: you buy them in the app for iPhone and iPad as an in-app purchase. Apple handles the sale and the payment (Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Republic of Ireland). Apple processes your name, your Apple Account and your payment details under its own responsibility and privacy policy — we do not receive them.

So that the pass reaches your DJLearn account, the app gives Apple your account identifier with the purchase — a random string, not a name and not an email address. Apple then sends us a confirmation of the purchase signed by Apple and later tells us about renewals, cancellations, expiry and refunds. What we store from this is listed in section 2 under “Supporter purchases in the app”.

The legal basis is performing the purchase (Art. 6(1)(b) GDPR). We store the purchase data for as long as your account exists; if you delete it, the data goes with it. Learning stays free — no purchase is needed for it.

As of: 2026