Privacy notice
Version: 5 November 2026 · privacy-2026-11-05-review-11
1. Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) is Timo Schnabel, Potsdamer Allee 74, 14532 Stahnsdorf, Germany, kontakt@mdmdojo.com. Further details are in the legal notice.
No data protection officer has been appointed. The conditions of Art. 37 GDPR and Sec. 38 German BDSG are not met: fewer than twenty people are permanently engaged in the automated processing of personal data, and there is neither large-scale processing of special categories of data nor large-scale regular and systematic monitoring. Please address data protection enquiries to the address above.
2. What data we process and why
We process personal data for personal invitations, user accounts, providing the training offering, its secure operation and the further purposes described below. In detail:
2.1 User account + credentials
- Email address, hashed password (bcrypt-equivalent, no plaintext).
- Display name (optional), language (de/en), role (user/admin), sign-in timestamps.
- We send service and security emails about your account, such as confirming your address, a welcome message and notices about changes to your password, email address or second sign-in factor.
- Restoring access without a second factor: if you have neither your authenticator app nor a recovery code, you can request, after signing in with your password, that two-step sign-in be turned off. This only happens three days after you confirm by email. During that time you receive a daily email with which you can cancel. For this we store the times, the status of the process, hashes of the links and a rough device description (operating system and browser, without further identifiers). Owners, organisation administrators and admin accounts are excluded. So that access to your mailbox alone is not enough, we store the time of your last password change. This recovery is locked for seven days after a change. Legal basis: Art. 6 (1) (b) GDPR; for the lock Art. 6 (1) (f) GDPR, our legitimate interest is protecting your account against takeover. Retention: we delete finished processes after 90 days and unconfirmed ones when the link expires. We store the time of the password change for as long as the account exists.
- Copy of your data: in the settings you can request a copy of the data about you. We store the time and send a link by email; the copy is available for 14 days and is created when you download it. A full access request under Art. 15 GDPR remains possible through the contact route.
- Legal basis: Art. 6 (1) (b) GDPR (contract performance).
- Retention: for the lifetime of the account. You can delete your account yourself at any time in the settings. We send you a link by email that is valid for 24 hours. Only confirming through this link deletes the account. Until then we store a hash of the link and its expiry. Your account data is then deleted without undue delay unless a statutory retention obligation applies (see 2.2).
2.1a Invitation to the closed testing phase
- The operator selects people for the closed testing phase. They can bind an invitation code to an email address in advance and send it by email, or personally pass on a code that has not yet been assigned. We store a hash of the code shown once, its validity, activation and revocation, and any link to the registered account. We store the email address in advance for a personally assigned code; otherwise we store it when the code is first used for registration. We do not store the plain-text code. The invitation links to this notice.
- When the beta registration is submitted, we record the time and versions of the accepted beta participation terms and acknowledged privacy notice. After account creation and email confirmation, the preview course is available without another code; this does not create a membership.
- The legal basis for invitations and restricted access is Art. 6 (1) (f) GDPR (legitimate interest in a limited, secure testing phase); after registration, processing serves performance of the participation terms under Art. 6 (1) (b) GDPR. Accepting the terms is not blanket consent to data processing.
- Unused invitations are deleted 30 days after expiry or revocation. A used invitation remains linked to the account as a record of registration and is removed when the account is deleted, unless an overriding retention obligation applies.
2.2 Payment and subscription data
- Stripe customer ID, Stripe subscription ID, status, end of term, plan (monthly/annual).
- For cancellation or resumption: technical receipt ID, contract reference, request timestamp, intended period end and confirmation-delivery status.
- For the public cancellation entry, we retain an account and contract reference, the hash of a one-time confirmation token, locale, timestamps and processing status for no more than 30 days after the link expires. The token itself and the entered email address are not stored there. The resulting cancellation receipt follows the retention period stated below.
- We never see card or bank details - these are exchanged directly between you and Stripe (see section 3.1).
- Legal basis: Art. 6 (1) (b) GDPR.
- Retention: 10 years under German commercial and tax retention obligations (Sec. 257 HGB, Sec. 147 AO).
2.3 Access codes + redemptions
- When you redeem an access code we store: code reference, your account, redemption timestamp, expiry date of the granted access.
- Legal basis: Art. 6 (1) (b) GDPR.
- Retention: redemption and granted access remain stored until the account is deleted. Records for any invoice are handled separately under the applicable retention obligations.
2.4 Course progress
- Per task: status (open/in progress/done) + ticked success criteria.
- If you repeat a finished module in a second pass, we store the ticks of that pass separately until you end it.
- If a previously invited free learner later obtains general course access, we copy the self-marked progress of the five identical foundation tasks once into the regular fundamentals course. Existing work there remains unchanged.
- Legal basis: Art. 6 (1) (b) GDPR.
- Retention: for the lifetime of your account.
2.4a Private notes, saved items and setup
- Private notes: you can write notes of up to 4,000 characters, either on a task or freely, without a task. We store the text, the time of the last change and either the task or, for a free note, a random identifier. The application shows notes only to you: organisations, team leads and the admin area have no view of them. Please do not enter passwords or other people’s data there.
- Saved items: when you save tasks, modules, paths or reference entries, we store the entry and the time. Organisations cannot see this. The operator only sees in aggregate how often tasks and modules were saved, without any link to a person.
- Setup: we store which steps of setting up your test environment you marked as done, and when. We do not collect details of the test environment itself.
- Legal basis: Art. 6 (1) (b) GDPR.
- Retention: until you delete the entry or clear the tick yourself, at the latest for the lifetime of your account. This data is included in any access request under Art. 15 GDPR.
2.5 Knowledge checks
- Your personal review data is stored in your browser. This browser’s local storage records which questions you last answered correctly or incorrectly, when you answered them and how many attempts you made. It is used to suggest reviews. You can delete this data in your browser settings (“clear site data”). This storage belongs to the browser, rather than to an individual account. Signing out or deleting your account does not automatically remove this local data. On shared devices, other people using the same browser may therefore encounter existing review data.
- To check question quality, when an answer is confirmed the browser sends the course, module, task, question, selected option, attempt number and language to our server. The server checks sign-in and course access and determines whether the answer is correct. The statistics record contains, without an account ID: course, module, versioned question ID, correct/incorrect, which attempt at this question it was in your browser, and the day (no time of day). The selected option, answer text and sign-in data are not stored in that statistics record. Processing the authenticated submission is a separate step.
- The purpose is to detect ambiguous or overly easy/difficult questions through aggregated metrics. The quality view evaluates questions, not individuals; organisations and employers receive no individual test results from it.
- Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in the quality of the practice questions). Where the data has no personal reference, the GDPR does not apply to it.
- Retention: 24 months, then deletion; the quality view considers only the most recent 180 days. Attempts from before this change that are still linked to an account are likewise deleted after 24 months and when you delete your account.
2.6 Contact form
- Name, email, company (optional), subject, message body, inquiry type, language, and any files you choose to attach (file name, type and contents).
- Attachments are kept in private storage on our server at IONOS (see 3.2). Only the operator can retrieve them, after signing in with a second factor. The email notification contains the file names only, not the files. They are deleted together with the message.
- If we answer your request from the admin area, we store the reply and the time together with the request. Both are deleted with it.
- IP hash: a cryptographic hash of your IP address (no plaintext, not reversible without significant effort) used only for spam detection and rate limiting; the hash is stored with the message and deleted after processing.
- Legal basis: Art. 6 (1) (b) GDPR (for pre-contractual contact) or Art. 6 (1) (f) GDPR (legitimate interest in answering inquiries and protecting against spam).
- Retention: at most 6 months after final processing, then deletion.
2.6a Reports on tasks
- If you report a problem with a task, we store your message, the type of report, the task, the page, the language and your account. If we reply, we also store the reply and the time.
- Legal basis: Art. 6 (1) (b) GDPR; for improving the content Art. 6 (1) (f) GDPR.
- Retention: 24 months. If your account is deleted, we remove the link to your account.
2.8 Certificates of participation
- On issuance we store your name and the course title as a snapshot taken at the time of issuance, together with course, language and issue date. The snapshot keeps an already issued certificate accurate even if you later change your display name.
- A certificate is issued solely on the basis of the tasks you marked as done yourself (self-report). We do not check or assess any learning results.
- We generate the PDF file from this data. The public verification page does not show a name, but it does show the validity status, course title, issue date, documented course version and verification ID.
- Legal basis: Art. 6 (1) (b) GDPR.
- Retention: for the lifetime of your account.
2.9 Use through an organisation (employees)
- If you use the offering through access provided by your employer or another organisation, that organisation can assign you courses, its own tasks and its own paths, also with a due date. We store the assignment and who made it. For its own tasks and paths we also store who created them and who last changed them. Your status in such tasks is stored per task, including the ticks you set.
- The organisation’s insight into your task status requires your explicit consent. This consent is split in two and can be given separately: once for the tasks you marked as done, including certificates of participation, and once for the day-level indication of when you were last active. Without consent the organisation sees neither.
- The activity indication is deliberately coarse: only a date is stored, no times and no duration of use. Even this indication may allow inferences about usage behaviour; it is not evidence of learning success or work performance.
- You may withdraw consent at any time with effect for the future, separately per area. After withdrawal the organisation’s insight ceases immediately.
- An organisation can also determine which learning aids (success criteria, hints, solutions, knowledge checks) are visible to the members it manages, and whether tasks are worked on in guided mode or challenge mode, for everyone, per team or for individual people. We store these rules and who last changed them. This concerns how the course is presented, not any assessment of you as a person.
- For a team the organisation can store a separate test environment with a name. This concerns the team, not you as a person.
- Coverage: owners, administrators and team leads see aggregated figures per module and path. They are based only on people who consented to this view and appear only from five such people upwards, with no values for individuals.
- Legal basis: Art. 6 (1) (b) GDPR for delivering the training, Art. 6 (1) (a) GDPR (consent) for the organisation’s insight. Where employee data is concerned, Section 26 BDSG applies in addition; co-determination rights of employee representatives remain unaffected.
- Retention: for as long as your membership in the organisation and your account exist.
2.10 Spam protection in forms
- In the contact form and the public cancellation form we use Cloudflare Turnstile to prevent automated submissions. A verification component from Cloudflare is embedded in the page; for this Cloudflare processes connection data including the IP address as well as technical characteristics of your browser.
- Turnstile works without image puzzles and, according to the provider, sets no cookies for advertising purposes. For details about the provider and transfers to the USA see section 3.4.
- Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in protecting our forms against abuse).
2.11 Organisations: joining, domains, company sign-in, change of owner
- Join requests: If you send a request through an organisation’s address or through the hint about your company domain, we store the request, an optional message from you and its status. The organisation’s owner and administrators see your name and email address and are notified by email. You only become a member once someone there accepts the request.
- Domains: An organisation can register domains and prove that it owns them, either through the owner’s address or through a DNS record that our server checks daily. If the domain of your email address is verified for an organisation, we show you a hint about that organisation after you sign in. For this we only compare the part of your address after the @. Nothing about you is disclosed to the organisation, and you never join automatically.
- Sign-in with your company account (SSO): If your organisation has set up sign-in through its own identity provider, that provider sends us your email address, your name and an identifier of your company account when you sign in. We use this only to sign you in and link the sign-in to your account. For the set-up we store the technical details of the identity provider submitted by the owner and who submitted and reviewed them. Signing in with your company account does not make you a member of the organisation.
- Emergency change of owner: If the owner of an organisation can no longer be reached, we can transfer ownership on request. For this we store the request, a note on the evidence presented and who made and decided it. The owner and administrators are emailed beforehand and can object within 30 days.
- Invitations and codes: an invitation is valid for 14 days. Four days before it expires we remind the invited person by email; after it expires the person who sent it learns that it was not accepted. Redeeming an organisation’s code can assign you directly to a team. When inviting people, an organisation can mark them as external and state their company. Both then appear with the invitation and the membership and are visible to owners and administrators.
- Legal basis: Art. 6 (1) (b) GDPR where you use these functions yourself; otherwise Art. 6 (1) (f) GDPR. Our legitimate interest, and that of the organisation, is that only authorised people join and manage an organisation.
- Retention: for as long as the organisation exists. If your account is deleted, we delete your own requests; in records you decided or submitted for others, we remove the reference to you.
2.7 Server logs
- When you visit the site, the upstream service Cloudflare (see 3.4) processes the connection data of your request, including IP address, timestamp, requested URL, status code, referrer, user-agent. This serves delivery of the site and protection against attacks.
- Operational logs of the application arise on our server (see 3.3). We do not keep a persistent access log containing IP addresses there.
- Legal basis: Art. 6 (1) (f) GDPR (security and operational stability).
- Retention: at Cloudflare per their default, typically a few days; operational logs on our server are rotated continuously.
3. Service providers and data protection roles
We use external service providers for the activities described below. Their data protection role depends on the processing involved. Processing on our behalf under Art. 28 GDPR is distinct from processing for a provider’s own purposes as a controller.
3.1 Stripe - payment processing
Stripe Payments Europe Ltd., 1 Grand Canal Street Lower, Dublin 2, Ireland; Depending on the processing, Stripe entities act as processors or as controllers for their own purposes. Payment data for the selected payment method + tax determination. Transfers to the USA rely on the EU Standard Contractual Clauses (SCC) plus supplementary measures. DPA: stripe.com/legal/dpa.
3.2 IONOS - database server
IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, Germany. Operation of the server that runs our database, sign-in management and the private storage for contact attachments. We operate the software used for this (Supabase) ourselves on that server; the software vendor has no access to your data. The database itself is not publicly accessible. The application and browsers reach sign-in and data only in encrypted form through our interface api.mdmdojo.com, browsers doing so via Cloudflare (see 3.4). The contractually assured place of processing is the European Union; the server’s network block is registered to the IONOS site in Frankfurt am Main. A data processing agreement under Art. 28 GDPR is in place.
3.3 Hetzner - server hosting
Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany. Operation of the server the application runs on and where the latest encrypted backup is kept (see 6). The server location used is Helsinki, Finland. This does not establish the location of every support or subprocessor access. DPA: hetzner.com/rechtliches/auftragsverarbeitung.
3.4 Cloudflare - network, DNS, attack mitigation + Turnstile
Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Domain name resolution, delivery of the site via a global network, TLS encryption and attack mitigation. Connection data including the IP address is processed; Cloudflare also derives the country code from the IP address, which we use for the language default (see section 4). We also use Cloudflare to operate the Turnstile spam protection in our forms (see section 2.11). Transfers to the USA rely on the EU Standard Contractual Clauses. DPA: cloudflare.com/cloudflare-customer-dpa.
3.5 netcup - email mailboxes
netcup GmbH, Emmy-Noether-Strasse 10, 76131 Karlsruhe, Germany. Operation of the mailboxes through which you can contact us. Sender, recipient, subject, message, attachments and technical delivery data are processed. The specific product location and mailbox domains are being checked against the agreement. A data processing agreement under Art. 28 GDPR is in place.
3.6 Resend - transactional email
Plus Five Five, Inc. (Resend), 2261 Market Street #5039, San Francisco, CA 94114, USA. Delivery of confirmation and notification emails. The selected Ireland sending region (eu-west-1) controls routing, not storage: Resend stores message content and delivery logs, among other data, in the United States. For transfers there, the provider identifies the EU Standard Contractual Clauses in its DPA. DPA: resend.com/legal/dpa.
3.7 Sentry - error monitoring
Functional Software, Inc. d/b/a Sentry, 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA. Captures stack traces and context data for application errors; pseudonymous user IDs, no plaintext emails; session replay is disabled. Your IP address is not stored. When an error report arrives, a coarse location at city level is derived from it and attached to the report so that regional faults can be narrowed down. Storage and processing take place in the EU region Frankfurt am Main. Access from the USA, for example for support purposes, cannot be ruled out and relies on the EU Standard Contractual Clauses. DPA: sentry.io/legal/dpa.
Transfers to third countries: the providers above may process data or access it from outside the European Economic Area. In particular, Resend stores messages and logs in the United States. The applicable transfer mechanisms and supplementary measures must be checked against the actual agreements and configuration. We do not make a blanket promise of exclusively European processing.
4. Cookies
We only use strictly necessary cookies (in particular session cookies from our own sign-in management to keep you signed in). These do not require consent under Sec. 25 (2) no. 2 German TDDDG.
Language preference: on your first visit we use the country code derived by Cloudflare (see 3.4) from the request’s public IP address. Germany defaults to German; every other recognized country defaults to English. The application receives only the country code and stores neither the IP address nor city, region, or coordinates. Only the resolved language is stored in the functional cookie (“NEXT_LOCALE”). Once signed in, your account language takes precedence. This cookie is also strictly necessary and therefore consent-free under Sec. 25 (2) no. 2 German TDDDG.
Further cookies: if you choose challenge mode, the level of help or the view for tasks, we remember this in the functional cookies “ia-challenge”, “mdm-help-depth” and “mdm-task-view” for one year. We remember the route you chose through a course in a functional cookie “mdm-route-…” per course, also for one year. When you accept an invitation or reset your password we set time-limited cookies (“ia-org-invitation”, up to 14 days, and “ia-password-recovery”, 10 minutes).
Protection against automated access: Cloudflare (see 3.4) checks requests for automated access and runs a short check script in the browser for this. Cloudflare stores the result in the cookie “cf_clearance” for up to one year. It serves only the security of the website, is strictly necessary and therefore consent-free under Sec. 25 (2) no. 2 German TDDDG.
Browser storage: in your browser’s local storage (localStorage) we keep your display settings (colour scheme, contrast, text size, motion), the state of the sidebar, introductions and notices you have seen, and task states until they are transferred. This data stays in the browser. You can delete it through your browser settings.
We currently use no analytics or tracking cookies. Should that change, we will update this notice and, where required, obtain fresh consent.
5. Your rights
You have the following rights at any time:
- Access (Art. 15 GDPR)
- Rectification (Art. 16 GDPR)
- Erasure (Art. 17 GDPR)
- Restriction of processing (Art. 18 GDPR)
- Data portability (Art. 20 GDPR)
- Objection (Art. 21 GDPR) to processing based on legitimate interests
- Withdrawal of given consents (Art. 7 (3) GDPR) with effect for the future
To exercise your rights please use the email address listed in the legal notice.
You also have the right to lodge a complaint with a data protection supervisory authority. The authority competent for us is the Landesbeauftragte für den Datenschutz und für das Recht auf Akteneinsicht Brandenburg, Stahnsdorfer Damm 77, 14532 Kleinmachnow, Germany. You may also contact the authority of your habitual residence or place of work.
Provision of your data: an email address and a password are required in order to enter into and perform the usage contract; without them we cannot maintain an account or provide access. Payment and invoicing data are required by law and by contract. All other details, in particular display name and the consents in the organisation area, are voluntary; not providing them has no consequences for the contract.
No automated decision-making: there is no automated decision in individual cases, including profiling, within the meaning of Art. 22 GDPR. The placement assessment and the review suggestions in the course only control the order in which learning content is shown; they produce no legal effect and do not similarly significantly affect you.
6. Data security
The connection to this site is encrypted via TLS/HTTPS. Passwords are only stored as hashes. Sensitive API keys are held exclusively server-side and managed via environment variables. Access to production systems is restricted to the controller.
We back up the database and contact attachments daily in encrypted form. Backups are kept for up to 14 days on our server at IONOS (see 3.2), and the latest version additionally on our server at Hetzner (see 3.3). Deleted data may therefore remain in backups until this period ends.
7. Changes
We update this notice when data processing changes or when legally required. The current version is always available here; the date at the top of the document shows the effective date.