Service policies
Cookie Policy
Cookies currently used
The application sends a first-party session cookie named eventservice-session and an XSRF-TOKEN cookie. The session cookie connects requests to server-side session state, including interface language, form feedback and authorized owner or optional customer access. XSRF-TOKEN supports protection against cross-site request forgery.
Lifetime and access
The session cookie is HttpOnly, so page scripts cannot read it. XSRF-TOKEN is readable by scripts for CSRF protection. Both use SameSite=Lax in the inspected configuration. Current configured cookie lifetime: 120 minutes, renewed with activity. Cookie names and settings must be rechecked against the production environment before launch. Cookie expiry is separate from retention of order and invitation records.
Optional analytics and functional storage
When enabled by the operator, Google Analytics and Yandex Metrica load only after you allow analytics, on the homepage, catalog and service-category pages. Google and Yandex receive technical visit data; this is not anonymous processing. Advertising signals are disabled. Your choice is stored in localStorage for 180 days; Google Analytics cookies are configured for 180 days. Yandex uses its own cookies; provider cookie details and retention must be reviewed before enabling collection. Session replay, click maps, e-commerce and outbound-link tracking are disabled in the Yandex integration. You can reject or withdraw using the analytics controls in the public footer. Withdrawal stops future collection; it does not delete data already received by the providers. Browser controls can remove existing cookies. On an explicit website language change, unfinished public form fields may be saved in same-tab sessionStorage, including entered contact details and text. This handoff is used only on the same page within two minutes and removed when read; unused data may remain until the tab closes. It excludes the CSRF token. The browser also remembers the catalog return location and scroll position in sessionStorage. The order submission identifier is retained with its browser history entry to prevent accidental duplicate orders on Back or reload; it contains no contact details or invitation text.
Your browser controls
You can block or delete cookies in your browser. This may reset the interface language and prevent forms or protected access from working. Opening external links is governed by the destination service’s own cookie policy. Production cookie settings and applicable consent obligations remain subject to legal review.