Technical data and cookies
Version dated 1 November 2026
Essential technologies for the website and secure form.
Document sections
1. Secure form
The session cookie IMPORTFSESSID links a single-use token to the browser and is required to validate submission. It is not used for advertising. The cookie lasts for the session, has HttpOnly and SameSite attributes, and the Secure attribute when HTTPS is used.
The token is valid for no longer than an hour and is invalidated after successful submission. Blocking essential cookies may prevent the form from working; in that case you can contact us by email.
2. Analytics and retention
Yandex Metrica code is not loaded and analytics cookies are not set before separate consent is given. To enable it, click “Allow analytics” in the “Analytics settings” panel. Declining does not prevent you from using the website or sending an enquiry. Webvisor, click maps, link tracking and advertising mailings are disabled.
Your analytics choice is valid for 180 days and can be changed using the “Analytics settings” button in the footer. The if_analytics_choice cookie stores the server-signed choice and a random identifier; the if-analytics-choice-v1 entry in localStorage contains a copy. These essential records are not used to analyse behaviour. Refusal and withdrawal disable the counter and clear _ym_* cookies accessible to this website. Enquiry fields are not saved in localStorage; a shopping basket and saved selections are not used.
3. Technical requests and controls
The server technically receives the request address, time and connection service information. Their use is limited to operating and protecting the website under the data processing policy.
Cookies can be deleted or restricted in your browser. After Metrica is permitted, _ym_uid and _ym_d (up to one year), _ym_isad (up to 20 hours), _ym_metrika_enabled (up to 60 minutes) and other technical cookies described in the service documentation may be used. A new choice is required to continue analytics after 180 days; remaining cookies do not in themselves authorise the counter to start. Withdrawal does not retroactively delete data already lawfully sent to the service; requests about its processing should be sent to the Controller.