Necessary storage
The central web account uses per-tab sessionStorage for account tokens and the current service return journey, rather than a shared parent-domain account cookie. Necessary storage supports a function you requested. Your explicit language choice is stored as stoodia.locale.
Optional history
History across browser sessions is off by default. Choose “Remember journeys” to allow it or “Necessary only” to decline. Neither choice prevents sign-in, registration or return to your service in the current tab. You may use the site without making a choice. Storage settings in the footer let you withdraw as easily as you consent; withdrawal removes persistent journeys on this origin.
Keys and periods
stoodia.cookie-choice.v1 records your choice and version for up to 180 days. With consent, stoodia.auth-journey.v1 in localStorage stores up to five service routes eligible for return for 30 days. The same sessionStorage key supports the current tab. Routes can contain a document identifier, but never authentication codes, state or passwords. Account access lasts 15 minutes and refresh up to 30 days; these are token validity periods, not a promise of storage after closing the tab. Expired optional history is removed on the next history access. Necessary sessionStorage keys: stoodia.web.session.v2 (account tokens and email) and stoodia.web.accessToken.v1 (compatibility access token).
No advertising or payment trackers
No advertising cookies, Google Analytics, Yandex Metrica or payment SDKs are enabled on this website. The preference record is necessary to honour your storage choice. Clearing site data removes it. Blocking browser storage must still allow the current sign-in flow to return to the requested address.
Return after sign-in
After successful sign-in or registration, the account retains up to five requested service routes for up to 30 days to offer continuation in another browser or after tabs close. Records contain the service identifier, relative path and time, not sign-in codes, passwords, document text or research data. A route can include a document identifier. This functional continuation of a requested journey is separate from optional localStorage history and stays in its own contour. Reading it requires sign-in to the same account; later visits do not automatically redirect. In the account you can forget one route or clear routes. Expired records are removed on subsequent use of the feature.