Legal

Privacy Policy

GermanForLife does not collect personal data. Your learning progress stays in your browser. Here is exactly how it works.

Last updated: 2025

No accounts, no login

GermanForLife does not have user accounts. You do not create a profile, provide an email address, or log in to use this website. No personal information is required or requested.

No personal data collected

GermanForLife does not collect, store, or process any personal data on its servers. There is no backend database. There is no user tracking system. We do not know who you are, where you are from, or what you have studied on this website.

localStorage, how progress is stored

Your learning progress, including vocabulary known/weak word lists, article quiz mistakes, sentence builder mistakes, daily plan completions, and mock exam scores, is stored using your browser's built-in localStorage feature. This is a client-side storage mechanism that keeps data on your own device, in your own browser. This data is:

  • Local only, stored on your device, not on any server
  • Never transmitted, not sent to GermanForLife or any third party
  • Not accessible by us, we have no way to read your localStorage data
  • Tied to your browser, switching browsers or devices will show a fresh start

The localStorage keys used

GermanForLife stores data under the following localStorage keys:

KeyWhat is stored
ad_known_wordsIDs of vocabulary words marked as known
ad_weak_wordsIDs of vocabulary words marked as weak
ad_article_mistakesNouns where the wrong article was chosen
ad_sentence_mistakesSentence exercises answered incorrectly
ad_daily_planWhich days of the 30-day plan are marked complete
ad_mock_exam_scoresScores from mock exam sessions (last 5)
ad_last_visitedLast page path and time (used for "continue" feature)

How to delete your progress data

Because data is stored in your browser's localStorage, you control it completely. To delete your GermanForLife progress:

  • Chrome / Edge: Settings → Privacy and security → Clear browsing data → Local storage and site data
  • Firefox: Settings → Privacy & Security → Cookies and Site Data → Clear Data
  • Safari: Preferences → Privacy → Manage Website Data
  • Or: Use your browser's developer tools (F12) → Application → Local Storage → delete the ad_ keys individually

Clearing browser data or browsing in private/incognito mode will also prevent localStorage from saving or retaining progress.

Cookies

GermanForLife does not set any cookies by default. The website does not use tracking cookies, advertising cookies, or analytics cookies in its core operation. If third-party advertising is added in the future, this policy will be updated and a cookie notice will be shown.

Third-party services

GermanForLife is a static website. It does not currently use any third-party analytics (such as Google Analytics), advertising networks, social media widgets, or external tracking services. All resources (CSS, JavaScript, data files) are served from the same domain.

External links

GermanForLife may link to external websites (such as the Goethe-Institut, Deutsche Welle, or official German government websites). These external sites have their own privacy policies, which we do not control. We are not responsible for the content or privacy practices of external sites.

Children

GermanForLife is a general educational resource. It is not specifically directed at children under 13. Since we collect no personal data from any users, there are no special provisions related to children's data.

Changes to this policy

If this privacy policy changes in a material way, for example, if advertising or analytics are added, the policy will be updated and the "last updated" date at the top will reflect this. Continued use of the website after any such changes constitutes acceptance of the updated policy.

Contact

If you have questions about this privacy policy or about how your data is handled, you can contact us through the website. Since no personal data is collected, most questions related to data access or deletion can be resolved simply by clearing your browser's localStorage as described above.