ГоГулять Cookies and Local Storage
DRAFT 2026-11-08-draft. LEGAL REVIEW REQUIRED. Verify actual key names, settings and expiry in the release; technical names are not invented here.
Effective date: {{EFFECTIVE_DATE}}. Controller: {{OPERATOR_FULL_NAME}}, address: {{OPERATOR_ADDRESS}}, contact: {{PRIVACY_EMAIL}}.
The web service uses cookies for login and session protection. The browser may store language, theme and app cache. Native apps use protected device storage for credentials and may retain local cache. These technologies do not provide cross-service advertising tracking.
| Purpose | Ordinary duration and controls |
|---|---|
| Web authentication | Within session lifetime: adult/independent participant refresh up to 30 days, child refresh up to 90 days, renewed on refresh; cookie lifetime must not exceed the corresponding authorisation. Logout revokes the session |
| Request protection, if a separate key exists | As needed for the protected session; actual use must be verified before publication |
| Language, theme and local preferences | Until changed or cleared on the device; no separate off-service profile |
| App and offline-data cache | Until refresh, logout or clearing; prior-account data must be cleared at logout/account change |
| Push subscription | Only after separate consent for push before the system request; until purpose withdrawal, session revocation or invalidation. Purpose withdrawal deletes tokens and prevents queued notifications from being sent |
Optional device advertising or analytics tracking is outside this list. The server may record events under the policy; this does not make all analytics necessary for login.
You may block cookies, clear site storage or uninstall the app. Blocking necessary cookies may prevent login. Device clearing does not delete your server account; use deletion.
Any added optional technology requires an explanation and a separate choice before activation where law requires. Refusal and withdrawal must not impair core features. Browsing or a general “Continue” action does not replace required consent. A release using only necessary technologies does not use an “accept all cookies” banner as fictitious consent.