What requested functions need
Technical cookies and storage support sessions, security, device pairing, language and requested preferences. Where strictly necessary for an expressly requested service, they may be used without prior consent; applicable data protection rules still apply.
Licence validation, language selection and reading preferences do not authorise advertising tracking. Categories and lifetimes depend on the activated function, not blanket, irreversible acceptance of the website.
Website storage overview
Sessions and security: session cookies such as PHPSESSID, MPSESSID or DIVESTATIONSESSID depending on the area, validation information and technical tokens. Lifetimes depend on session and access rules; closing a browser does not necessarily revoke persistent authorisation.
Explorarium pairing: a device identifier cookie and persistent authorisation. The device marker may outlive the permission to sign in; alone it cannot open an account. Authorisation may be revoked or replaced. Accounts are limited to one phone or tablet and one computer.
Preferences: language, display level, licence acceptance, sticky-note size and position. Sticky-note preferences do not contain note text. Settings may persist until removal or expiry.
Offline use: local storage, browser databases and caches of resources expressly prepared for a logbook. They may contain personal logbook data. Clearing them may lose unsynchronised changes. Shared devices require particular care.
External content and analytics
Loading videos, thumbnails, fonts or other resources from an external provider may transmit connection data and lead to tracker use. YouTube and Google apply their own policies. A player without autoplay or a particular embedding domain does not mean no collection occurs.
Analytics, advertising or tracking technologies without an applicable exemption require prior consent. Refusing must be as easy as accepting, and withdrawal must remain possible. Continuing to browse and accepting terms do not constitute consent.
Browser settings can clear or block storage but do not replace a consent mechanism required before loading a third-party service. Video or analytics choices must remain separate from account access and licence acceptance.
Clear data and manage devices
Use available sign-out, revocation and deletion controls for your account. To remove device copies, also clear website data, caches and local storage in browser settings. These actions differ: deleting a cookie does not delete a server-held logbook.
Blocking all cookies may prevent sign-in or pairing. Before clearing logbook data, check synchronisation or export your own data. External services offer choices in their respective policies. For personal data requests, consult the privacy policy or use the contact form.