Cookies and browser storage at www.teachpie.de and app.teachpie.de
As of: November 9, 2026
This overview fully describes the information TeachPie currently stores on or reads from devices using cookies, Local Storage, Session Storage, IndexedDB and Cache Storage. The responsible entity is Astep Ahead UG (haftungsbeschränkt). Privacy inquiries can be sent to datenschutz@teachpie.de be directed.
The essentials at a glance
- No analytics or marketing tracking: TeachPie currently does not use web analytics, advertising pixels, retargeting technologies, or embedded social media trackers.
- No selection required in the cookie banner: TeachPie uses only technically necessary storage or storage triggered by a feature you explicitly request. That’s why no consent banner is shown when you visit the site.
- Marketing page: Simply visiting www.teachpie.de currently does not set cookies or create entries in Local Storage or Session Storage.
- Web app: Cookies and browser storage are created on app.teachpie.de depending on the feature used, especially when signing in, during “Learn with class” rounds, security checks and when saving local work or display states.
1. Technically necessary web app cookies
Merely opening the login page creates only the diagnostic identifier tp_error_browser (1.5); opening the legal pages additionally creates the protection cookie csrf_token (1.2). The other cookies are created only when the respective feature is used. Retention periods are maximum periods; logging out, completing a process, or earlier technical deletion may shorten storage.
1.1 Sign-in and session
tp_session– signed session metadata for server-side verification of a sign-in. Provider: app.teachpie.de. Protection: HttpOnly, Secure in production, SameSite=Lax. Maximum duration: 90 days.tp_access_token,tp_id_token,tp_refresh_token– Sign-in and renewal tokens for the authenticated session. Provider: app.teachpie.de. Protection: HttpOnly, Secure in production, SameSite=Lax. Maximum duration: 90 days;tp_refresh_tokenis set only if a renewal token is present.TeachPieAuth.<Client-ID>.<Nutzerkennung>.accessToken,.idToken,.refreshTokenandTeachPieAuth.<Client-ID>.LastAuthUser– temporary compatibility storage for the existing client-side sign-in flow. Provider: app.teachpie.de. Secure and SameSite=Lax in production; readable by the web app for technical reasons. Maximum duration: 90 days. This transitional storage is intended to be removed once the auth migration is complete.
1.2 Security and external sign-in
csrf_token– Protection against unwanted cross-session requests. Provider: app.teachpie.de. Protection: HttpOnly, Secure in production, SameSite=Strict. Duration: 5 minutes for session-bound use, otherwise no more than 1 hour.oauth_state,oauth_verifier,oauth_redirect,oauth_origin,oauth_callback,oauth_providerand depending on the processoauth_popup,oauth_account_typeandoauth_nonce– Protection, association and secure return during a login explicitly initiated via Google, Microsoft or Eduplaces. Provider: app.teachpie.de. Protection: HttpOnly, Secure in production, SameSite=Lax. Duration: no more than 10 minutes; normally deleted when the process is completed.tp_email_verification_state– app-signed state, nonce, and PKCE binding for a registration, resend verification email, or email sign-in explicitly initiated by the user; during the subsequent verification process, also bound to the expected Keycloak identity. Provider: app.teachpie.de. Protection: host-only, HttpOnly, Secure in production, SameSite=Lax, Path/api/auth. Duration: no more than 15 minutes per phase; deleted earlier upon successful completion or explicit cleanup.tp_trusted_mfa– hands over the signed request for the second sign-in factor to the login page when a sign-in via Google, Microsoft, Eduplaces or a test access requires a second factor. Provider: app.teachpie.de. Protection: host-only, HttpOnly, Secure in production, SameSite=Lax. Duration: no more than 5 minutes; deleted once the sign-in is completed.tp_user_cache_bypass– short-lived marker after redeeming a pilot access so that the web app reloads the changed access immediately. It does not unlock anything. Provider: app.teachpie.de. Protection: HttpOnly, Secure in production, SameSite=Lax. Duration: 35 seconds.tp_school_first_login_completed– short-term marker so the completion of school-related initial registration can be recognized immediately. Provider: app.teachpie.de. In production: Secure, SameSite=Lax. Duration: 60 seconds.
1.3 Learning with the class
tp_room– A session for a child without an account in a “Learn with your class” round opened by a teacher. Contains only a random identifier; only its hash is stored on the server. Provider: app.teachpie.de. Protection: HttpOnly, Secure in production, SameSite=Lax. Duration: up to twelve hours after the round ends; deleted immediately when leaving the round.
1.4 Language settings
teachpie-locale– records an explicitly selected language for the marketing website and its public tools. Provider: www.teachpie.de. Browser-readable, host-only, HTTPS Secure, SameSite=Lax, path/. Duration: no more than 365 days or until the website data is deleted. The first language is selected from the browser's language settings without storing anything; no IP geolocation takes place.NEXT_LOCALE– remembers a specifically selected interface language. Provider: app.teachpie.de. Browser-readable, host-only, Secure over HTTPS, SameSite=Lax, Path/. Duration: no more than 365 days or until the website data is deleted.
1.5 Error diagnostics
tp_error_browser– random, signed identifier of a browser without sign-in, under which TeachPie accepts technical error reports from this browser so that they can be viewed and withdrawn there. It does not sign anyone in; only a pseudonym is stored on the server. It is set on the pages of the web app without sign-in as soon as error capture starts, including the login page. Provider: app.teachpie.de. Protection: host-only, HttpOnly, Secure in production, SameSite=Strict. Duration: until the browser is closed; associated error reports for no more than 90 days. This storage serves the secure and error-free operation of the web app (§ 25(2)(2) TDDDG).
1.6 Notifications on the device
tp_meldeweg_geraet– random identifier of the device, set only when a teacher switches on “Notifications on this device” in the settings. It allows TeachPie to recognize the device after a new sign-in so that notifications that were switched on return for the same person; only a hash is stored server-side. Provider: app.teachpie.de. Protection: HttpOnly, Secure in production, SameSite=Lax, path/api. Maximum duration: 400 days; it remains when signing out and is removed when the browser’s website data is deleted.
2. Local Storage, Session Storage and other browser storage
§ 25 TDDDG covers more than just cookies. That's why other browser storage is also listed transparently.
2.1 Local storage
Local Storage generally remains until the application removes the entry or the browser storage is cleared. TeachPie uses it for specific functions, including:
- Account limits and local work-in-progress: user-specific keys following the pattern
tp:v1:user:<Nutzer-ID>:…as well astp:v1:auth:lastUserId. They prevent local state from getting mixed up between accounts and, for example, store work, tasks, whiteboard, learning path or lecture states. Account-related entries are removed when switching accounts or during scheduled cleanup. - Display and interaction preferences: for example, the state of the sidebar in the classroom area, recently used learning areas, and dismissed notices, tours, and welcome messages. The sole purpose is to locally remember display or interaction choices made explicitly by the user.
- Microphone and audio choice:
audioConsent_<Nutzer-ID>locally records the consent granted or withdrawn by the user for an audio feature they started, including the time and version. The entry is removed when consent is withdrawn. - Gifts:
teachpie.geschenke.geraetcontains a random identifier. It is set and read only when a gift is created and when it is redeemed, so that no one can give a gift to themselves with their own code (Privacy Policy, section 3.13). The entry remains until the browser storage is deleted.
2.2 Session Storage
Session storage is limited to the respective browser tab and is usually deleted when the tab is closed. TeachPie uses it for:
- Sign-in security: PKCE and status values such as
auth_pkce_verifier,auth_oauth_state_…andoauth_user_id, which are removed after use. - Temporary workflows: ongoing chat, task, whiteboard, and workspace states, a pending marketplace action, brief usage tips, and controlled retries of failed dynamic loads.
2.3 IndexedDB
IndexedDB is a browser data store for larger amounts of data. TeachPie uses it only in the web app and only for:
teachpie-error-reporting– technical error reports that could not yet be sent to TeachPie, for example without a network connection; error capture creates the initially empty database as soon as the web app is first opened, for example on the login page. The reports are deleted after transmission; TeachPie no longer accepts reports older than seven days, and they are then removed as well.teachpie-material-author-recovery– local backup of unsaved changes in the material editor so that nothing is lost after a crash or reload. It is assigned to the account, is never read for another account and is removed once saving has been confirmed.teachpie-exam-drafts– local interim state of the answers in an ongoing exam until the submission is confirmed. It is deleted after the confirmed submission, on sign-out and after 14 days at the latest.
2.4 Service worker and Cache Storage
In the signed-in area of the web app and in the installed app, TeachPie sets up a service worker. It stores in Cache Storage under teachpie-grundschale-… the page that appears instead of the browser’s error page when there is no network connection, together with the interface files it needs (styles, scripts, fonts, icons). It contains no content and no personal data. It is kept until the next version of the web app or until sign-out; when signing out in the browser, the service worker is removed as well. Nothing of this is created on the sign-in page or the other public pages in the browser. In addition, the offline page remembers in the tab’s Session Storage for at most one minute that a retry has just taken place. This storage is technically necessary (§ 25(2)(2) TDDDG); it can be deleted via the browser’s website data.
If a teacher switches on “Notifications on this device” and the browser allows notifications, the browser additionally creates a push subscription with its push service for this service worker (Section 3). It contains no content. Switching it off in the settings and signing out end it; the permission for notifications is managed by the browser.
3. External services after a user action
TeachPie does not embed external tracking scripts on the initial website or sign-in page. For the following processes, which the user explicitly starts, they are redirected to a third-party service or a third-party service is used:
- Google, Microsoft, or Eduplaces: only after selecting the respective external sign-in option. The provider’s own cookies and storage policies may apply on its pages.
- Stripe: only after starting a checkout or billing portal process. The payment page is hosted by Stripe; Stripe may set necessary security, session, and fraud prevention cookies there. Stripe controls the specific names and durations. TeachPie itself does not store full card or bank account details. More information: Stripe Privacy Policy.
- Push service of the browser vendor: only if a teacher switches on “Notifications on this device” and the browser allows it. Depending on the browser, this is the service of Apple, Google, Mozilla or Microsoft; it delivers the notification to the device. TeachPie passes only an encrypted identifier of the notification to it, no name and no text. Details can be found in the Privacy policy, Section 5.7.
4. Technologies not used
TeachPie currently does not use cookies or similar technologies for Google Analytics, Matomo, Google Ads, Meta/Facebook Pixel, Hotjar, retargeting, personalized advertising or social media plugins. External social media links are regular outbound links, not embedded trackers.
5. Legal basis and consent
Storing information on an end device and accessing it generally require consent under § 25(1) TDDDG. For the storage described above, TeachPie relies on the exemption in § 25(2) no. 2 TDDDG, insofar as the respective storage is strictly necessary to provide a digital service explicitly requested by the user. Where personal data is processed in this context, the supplementary legal bases and purposes are set out in the Privacy policy.
As no optional analytics, marketing or advertising technologies are currently used, consent is not requested and no consent decision is stored. If a technology that is not strictly necessary is introduced in the future, it will be technically blocked until valid consent has been given, and this overview will be updated before rollout.
6. Old consent cookies
We do not use a marketing cookie or Local or Session Storage to record registration source. Only the known source of the current email registration is passed on in its request; Google and Microsoft are counted without a source. The former tp_attribution will no longer be set or evaluated; any existing remnants are removed on a limited basis at the registration and sign-in boundaries. Functional sign-in and security cookies are unaffected.
Previous versions of the website or web app included the entries cookieConsent, required and lastUpdate saved for a banner. These entries are no longer evaluated and expire no later than 180 days after they were last saved. They do not control analytics or marketing services.
7. Deletion and blocking
Cookies and Local and Session Storage entries can be deleted through the browser’s privacy or website data settings. Deleting necessary login or round session data will log you out or make you leave the round; deleting local work and display states will reset the respective local view or feature. Blocking necessary storage altogether may prevent login, security, participation in a round, or local work features.
8. Changes and contact
This overview is updated whenever there are changes to cookies, browser storage, embedded content, analytics, marketing, sign-in or payment services. Questions can be sent to datenschutz@teachpie.de must be directed. Provider details can be found in the Legal notice.