Datenschutzerklärung · Information under Art. 13 and 14 GDPR
The controller responsible for processing your personal data on this service is:
For any privacy question, or to exercise the rights in section 9, write to .
We have not appointed a Data Protection Officer. As a one-person business we are not required to under Art. 37 GDPR / § 38 BDSG.
| Data | Purpose | Legal basis |
|---|---|---|
| Email address, password (stored only as a hash), or your Google account identifier if you sign in with Google | Creating and securing your account | Art. 6(1)(b) — performance of a contract |
| Learning progress: which lessons and topics you completed, your checkboxes, your position in the curriculum | Saving your progress and syncing it across your devices — the thing an account is for | Art. 6(1)(b) |
| Questions you type into Ask AI and AI Guide, and conversations with the AI Architect, including any files you attach | Producing the answer, the guidance or the blueprint you asked for | Art. 6(1)(b) |
| Payment records: amount, currency, product, billing country, and a VAT ID if you supply one. Card details never reach us — see section 4. | Fulfilling the purchase, and meeting German tax and accounting obligations | Art. 6(1)(b) and Art. 6(1)(c) — legal obligation |
| Company workspace membership, role, and an audit log of administrative actions (business customers only) | Running team accounts and showing an administrator who did what | Art. 6(1)(b) and Art. 6(1)(f) — legitimate interest in accountability |
| Technical logs from our hosting and API layers, including IP address | Security, abuse prevention, and diagnosing faults | Art. 6(1)(f) — legitimate interest in a secure service |
You can read the map and the curriculum without registering. In that case your progress and a counter of how much you have explored are kept in your own browser only (localStorage); clearing your browser data erases them, and they are never used for advertising or tracking across sites.
Usage events — which lesson was opened, which question was answered — are sent to our own servers even while you are signed out, with no account attached. See “Usage data” below.
We record what happens in the app so we can tell which lessons work and which do not: a lesson opened or completed, a question answered and whether it was right, a node or tab opened, a module visited, and the two steps of starting a purchase. Each record holds what happened, when, and a random identifier for that browser session.
We do this because we cannot otherwise tell the difference between a lesson nobody needs and a lesson nobody can follow. A question almost everyone gets wrong usually means we explained something badly — that is the kind of thing this is for, and it is the only thing we use it for.
This is first-party only: the records go to our own database in Frankfurt and nowhere else. No third-party analytics service, no tracking pixels, no advertising network, no cross-site tracking, no cookies for this. We do not build profiles of you, we do not sell or share this, and it never influences what you are charged.
Where you are signed in, these records are linked to your account, so in principle we can see what an individual did. In practice we read it in aggregate, and we do not use it to judge or rank anyone. If your employer bought your seat, they never see it. Your company's administrator sees whether learning is happening across the team — never an individual's clicks, timings, answers or scores.
The legal basis is our legitimate interest in making the product work (Art. 6(1)(f) GDPR). You can object at any time under Art. 21 GDPR — write to and we will stop recording yours and delete what exists. Deleting your account removes the link to you.
One correction to be straight about: earlier versions of this page said that nothing reaches our servers while you are signed out. That is no longer true — we record the same usage events for signed-out visitors, with no account attached, because the point at which people give up is usually before they register.
We run no advertising, no third-party analytics, no tracking pixels and no cross-site tracking. The usage data described above stays on our own servers and is never combined with anything from another site. We do not sell or share personal data with data brokers. There is no automated decision-making producing legal effects concerning you (Art. 22 GDPR).
We use only what is strictly necessary to operate the service:
Because these are strictly necessary for a service you have requested, they do not require consent under § 25 Abs. 2 TTDSG. We set no analytics or advertising cookies, which is why you are not asked to accept any.
Payments are processed by Stripe (Stripe Payments Europe, Ltd., Dublin, Ireland). When you pay, you enter your card details on Stripe's own payment page. We never see, receive or store your card number.
Stripe passes back to us: the amount, currency, product, your billing country, and a VAT ID if you entered one. We keep those because German tax law requires us to document what was sold, to whom, and where they were located — the billing country determines which country's VAT rules apply to a digital service (§ 3a Abs. 5 UStG).
Stripe acts as an independent controller for its own payment and fraud-prevention purposes. See stripe.com/privacy.
This is the section worth reading carefully, because it is the one where your words leave our systems.
When you use Ask AI, AI Guide or the AI Architect, the text you write — and any file you attach — is sent to Anthropic (Anthropic PBC, USA) to generate the response. Relevant excerpts of our own curriculum are sent alongside it as context.
Please do not enter personal data about other people, confidential business information, or anything you are not free to share. The Architect is designed to work from a description of your use case; it does not need real names, customer records or credentials to do its job.
To find the right curriculum excerpts, the text of your question is also sent to Voyage AI (USA) to be converted into a numerical representation.
Your conversations are stored in our database so you can return to a session. You can delete a session at any time from the Sessions menu.
We keep the text of every question you type into AI Guide, together with the date, whether an answer was found, and how many results it produced. We do this to see where the guidance sends people to the wrong place, which is the only way to make it better.
Keep this in mind when you write: a question can describe your business. Please do not put customer names, confidential figures or anything you are not free to share into it — AI Guide only needs the subject you want to understand.
These questions are not shown to other users, not linked to your name anywhere in the product, and not used to train any AI model. If you would rather we did not keep yours, and we will delete them and exclude you.
We read Architect conversations ourselves in order to improve how the Architect asks questions and where it gets things wrong. This is done manually, by a person, on a small number of sessions — we do not use your conversations to train any AI model, ours or anyone else's, and they are never sent to a third party for that purpose.
The legal basis is our legitimate interest in making the product work properly (Art. 6(1)(f) GDPR). If you would rather we did not read yours, — say so and we will exclude your sessions. You can also object at any time under Art. 21 GDPR, and deleting a session removes it from this entirely.
If your employer bought your seat, this changes nothing: what you write to the Architect is never shown to your company's administrator. They see whether learning is happening, never what anyone wrote.
You can search and read the free part of the map from Claude, ChatGPT or another AI assistant, through our connector. You do not need an account for this.
When you do, the assistant sends us only what is needed to answer: your search words, or the id of the topic or lesson you asked for. We send back the same free text you would see on the website. We never receive your conversation with the assistant.
We keep a record of these requests for 90 days — the search words, the topic asked for, the time, and a one-way scrambled form of your network address that lets us recognise repeated use without storing the address itself. It is used to stop abuse of an open endpoint and to see what people look for. The legal basis is our legitimate interest in keeping the service available and useful (Art. 6(1)(f) GDPR).
The assistant itself — Anthropic, OpenAI, Google or whoever provides it — is chosen by you and handles your conversation under its own privacy policy. We are not a party to that, and they are not acting for us.
We use the following providers. Each is bound by a data processing agreement under Art. 28 GDPR where it acts as our processor.
| Provider | Purpose | Location |
|---|---|---|
| Supabase | Database, authentication, server functions | EU — Frankfurt, Germany |
| Cloudflare | Website hosting and delivery | Global CDN; EU edge for EU visitors |
| Stripe | Payments | EU — Ireland |
| Anthropic | AI responses (Ask AI, Architect, content updates) | USA |
| Voyage AI | Text embeddings for finding relevant curriculum | USA |
| Resend | Transactional email (invitations, account mail) | EU — Ireland |
| "Sign in with Google", if you choose it | USA |
Your account data, learning progress and payment records are stored in the EU. Transfers to providers in the USA occur only for the purposes above, and are based either on the European Commission's adequacy decision for the EU–U.S. Data Privacy Framework where the recipient is certified under it, or otherwise on the European Commission's Standard Contractual Clauses together with supplementary measures.
| Data | Retention |
|---|---|
| Account and learning progress | Until you delete your account |
| AI conversations and blueprints | Until you delete the session, or the account |
| Invoices and payment records | 10 years — required by § 147 AO and § 257 HGB. These survive account deletion because we are not permitted to delete them. |
| Usage data (section 2) | Kept for 24 months, then deleted. Long enough to compare one curriculum revision with the next; not a permanent record of anyone's clicks. Deleting your account removes the link to you immediately. |
| Connector requests (section 5) | 90 days, then deleted automatically. Search words and topic ids only, with a scrambled network address — never your conversation. |
| Technical logs | Short-term, for security and diagnostics |
You can delete your account from the Account panel. That removes your profile, learning progress and AI sessions. Payment records are retained for the statutory period described above, reduced to what tax law requires.
Under the GDPR you have the right to:
Write to and we will respond within one month.
You also have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR) — in Germany, the data protection authority of the federal state in which the controller is established.
Data is transmitted over TLS. Passwords are stored only as salted hashes and are never visible to us. Access to the production database is restricted, and paid content and customer records are readable only by server-side components holding privileged credentials — not by the browser.
We will update this policy when the service changes. The version in force is always the one published here.