Privacy

30daysGerman stores the least it can get away with: who you are, how far through the course you got, and whether you have paid. There is no advertising, no tracking pixels, no profile built about you, and nothing is sold or shared with anyone for marketing.

You can use the entire course without an account at all. Signing in exists so your progress survives a new phone, not so we can learn things about you.

Nothing reaches our servers. Your progress lives in your own browser's local storage on that one device, and clearing your browser data erases it permanently. We cannot see it, restore it, or move it for you.

Google tells us three things about you, and we store them so the app can greet you and keep your account attached to your progress:

• Your name, as it appears on your Google account.
• Your email address, which identifies the account.
• Your Google profile picture — we store the link to it, not the image.
• A Google account identifier and the sign-in tokens Auth.js needs to keep you signed in.

Once you have an account, the same progress document your browser already keeps is copied to our database so it follows you between devices. It contains only:

• Which topics you have reached and how far into each one.
• How many exercises you completed on each calendar date, for the day grid and the streak.
• The date you started, so the DAY n / 30 counter is right.
• A display name, if you set one.

Payments are processed by Stripe. Card numbers, expiry dates and security codes are entered inside Stripe's own secure frame and never reach our servers, our logs, or our database — we could not see them if we wanted to.

What we do store is whether you have paid, when, and the Stripe customer reference for that purchase, so that support and refunds are possible. Stripe's own handling of your payment data is governed by their privacy policy.

One cookie, and only after you sign in: the session cookie that keeps you signed in. There are no advertising or tracking cookies, no third-party cookies are set by us, and the page-view counting above sets none either. Signing out deletes it.

We count page views, and that is the whole of it. Our host, Vercel, records that a page was requested along with the country, the rough device type, and the site you arrived from — figures that are aggregated on the way in and never assembled into a record of a person.

No cookie is set for this, no identifier is stored on your device, and nothing follows you to another website. It cannot be linked to your account, and it exists to answer one question: is anybody reading this.

Four processors, each doing one job and nothing else: Google handles sign-in, Supabase hosts the database, Stripe processes payments, and Vercel serves the site and counts the page views described above. Your data is not sold, rented, or shared for advertising, and there is no fifth party.

Your account and progress are kept for as long as the account exists. Delete the account and the progress row goes with it automatically — the database enforces that, so there is no copy left behind. Records of a payment are kept as long as tax and accounting rules require, which is a legal obligation rather than a choice.

You can ask for a copy of everything stored about you, ask for it to be corrected, or ask for the account and its data to be deleted outright. Email info@30daysgerman.com and it will be done.

If you are in the UK or EU, the GDPR gives you these rights explicitly, along with the right to complain to your national data protection authority.

The course is not aimed at children under 13, and accounts are not knowingly created for them. If you believe a child has signed up, email us and the account will be removed.

If this policy changes in a way that affects what is collected or why, the date at the top changes with it.