Cookie statement
Cookies and similar technologies, and who is responsible for each environment.
Last updated: 25 September 2026
Version: 2026.09.25
Read this document together with the signed offer, agreement or order confirmation.
These documents describe Mirobrowse’s services, including websites, custom applications, event and ticket systems, communities and equestrian scoreboards. The applicable agreement specifies the services provided. They do not replace the customer’s own privacy information, sales conditions or event rules.
This cookie statement describes the use of cookies and similar technologies within websites, applications, platforms and other digital services offered, developed, managed or hosted by MiroBrowse. The cookies actually used differ between websites, applications and customer environments. The inventory in article 5 concerns Mirobrowse’s managed CMS and account environment. It is not a cookie inventory of every customer website or custom application. The party responsible for each environment must state which technologies are actually used there.
1. What are cookies and similar technologies?
Cookies are small data files that may be stored on or read from a user’s device when using a website or application. Similar technologies include local browser storage, session storage, pixels, tags, scripts, software development kits and other technologies that store or read information on a device.
This statement refers to these technologies collectively as “cookies”. Some cookies may be directly or indirectly linked to personal data. In that case, the privacy statement also applies.
2. Who is responsible?
For cookies on its own website, own accounts and own business environments, MiroBrowse determines why and how cookies are used. In that case, Mirobrowse is responsible for their use.
Within a customer’s website, event, platform, scoreboard, ticketing environment or other environment, the customer usually determines the purposes of that environment and any additional cookies. The customer is then generally the controller, and MiroBrowse processes technical data for hosting, security, maintenance and support on that customer’s instructions.
The customer concerned may have additional cookies, external integrations or services used. The customer must then ensure that visitors and users are correctly informed and can give valid prior consent where necessary.
3. Categories of cookies
3.1 Strictly necessary cookies
Strictly necessary cookies are needed for a service requested by the user to operate securely and correctly. They may be used, for example, for:
- login and session management;
- form and CSRF protection;
- security and prevention of abuse;
- retaining a shopping basket or ticket selection during checkout;
- applying user roles and access rights;
- load balancing, availability and technical operation;
- storing cookie preferences.
These cookies are used without prior cookie consent where they are genuinely necessary for the requested service or its security. They are not used for advertising or tracking users for other purposes.
3.2 Functional and preference cookies
Functional cookies may remember choices such as language, display, filters, accessibility settings or other preferences selected by the user. Where these cookies are not strictly necessary or have more than a minor impact on privacy, they are used only after consent has been given.
3.3 Analytics cookies
Analytics cookies may be used to understand how a website or application functions and to investigate errors, performance and usage. Analytics cookies are used without consent only where they meet the legal conditions for limited privacy impact. Otherwise, they are activated only after consent.
3.4 Marketing and tracking cookies
Advertising and tracking pixels are disabled by default. They are added only at the customer’s express request and after assessing the technology used. A customer’s request does not replace the required information and visitor consent. Statistics for internal use are not automatically exempt either: the technology and privacy impact determine which rules apply.
Marketing and tracking cookies may track use across pages, services, applications or websites, create profiles or show personalised advertising. These cookies are not placed or read before the user has given valid consent.
3.5 External media and services
External elements, such as videos, maps, social media content, payment features, chat features or other embedded services, may use third-party cookies or similar technologies. Where consent is required, the external element is loaded only after that consent is given or the user deliberately chooses to activate the element concerned.
4. Applications and customer environments
MiroBrowse services, including the CMS, websites, ticketing software, event platforms, community platforms, scoreboard systems, judging environments and custom applications, may use necessary cookies for matters including:
- logging in and staying logged in;
- session management and security;
- forms and data entry;
- shopping baskets, reservations and ticket checkouts;
- user roles and access rights;
- language, screen and interface preferences;
- temporary storage of unfinished actions;
- prevention and investigation of abuse;
- technical availability and troubleshooting.
A cookie being technically useful does not automatically mean it may be used without consent. Each cookie is assessed for necessity and whether prior consent is required.
5. Current cookie and storage inventory
The inventory below concerns Mirobrowse’s CMS and account environment. It includes optional functional storage, for example when you choose to stay signed in. It does not declare which cookies a customer website uses. An existing cookie notice records only that it was dismissed; this is not consent to statistics or advertising. Older cookies may retain their previously configured lifetime until replaced or cleared through the browser.
| Name | Category | Provider or domain | Purpose and stored data | Maximum duration | Consent required |
|---|---|---|---|---|---|
mirobrowse_cms_session |
Strictly necessary | www.mirobrowse.com |
Maintains a secure user session and enables login and navigation.
Data: A random session identifier; session contents are stored on the server. |
Until the session ends or at most the configured session lifetime | No |
XSRF-TOKEN |
Strictly necessary | www.mirobrowse.com |
Protects forms and requests against forged commands from other websites.
Data: A technical security token. |
During the session or at most the configured session lifetime | No |
remember_web_* |
Strictly necessary | www.mirobrowse.com |
Keeps you signed in only when you choose Remember me.
Data: An encrypted authentication reference; no plain-text password. |
Up to 400 days, or until logout or invalidation | No |
EditLanguage |
Functional preferences | www.mirobrowse.com |
Remembers the language selected for editing website content.
Data: A language code, such as nl or en. |
Usually 7 days; at most 31 days when set by the server | No |
mirobrowse_products_active_product_type (localStorage) |
Functional preferences | www.mirobrowse.com |
Remembers the last product type selected in the product overview.
Data: The selected product type identifier; no product contents. |
Until overwritten or browser site data are cleared; no automatic expiry | No |
laravel_cookie_consent |
Functional preferences | www.mirobrowse.com |
Remembers dismissal of the legacy cookie notice when enabled; it is not consent to tracking.
Data: A yes value, without individual category choices. |
Up to 365 days for newly stored choices | No |
The actual retention period may be shorter if the user logs out, deletes cookies, withdraws consent or the storage is no longer needed. The stated duration is the maximum configured duration, not a guarantee that a cookie will be retained for that entire period.
6. Consent and cookie preferences
The inventory contains only necessary or functional storage. No consent to tracking has been requested for it. Any general cookie notice shown does not provide that consent either. Before adding elements requiring consent, a working mechanism is needed to block them beforehand, accept or reject them separately and withdraw consent.
7. Third-party cookies
A customer form may use Google reCAPTCHA or other external spam protection. This is not a standard cookie of the CMS account environment. IP addresses, browser data and interaction signals may be sent to the supplier. A security purpose does not automatically exempt an external technology from consent. The version used, purposes, storage periods, transfers and necessity must be established for each implementation and recorded in its own cookie inventory. Where consent is required, the technology may be loaded only after valid consent.
When a third party uses cookies or similar technologies within this environment, that party is identified in the current inventory. A third party may be an independent controller for its own processing. Its privacy and cookie terms may also apply to that processing.
MiroBrowse and the customer concerned assess which external elements are used and whether they must be blocked before consent. MiroBrowse cannot determine which cookies an external website places after a user leaves the current environment and visits that external website independently.
8. Managing cookies through your browser
Browser settings allow a user to view, block and delete cookies. Local storage and other website data can usually also be deleted there. The available options differ between browsers and devices.
Blocking or deleting strictly necessary cookies may stop login, form processing, ticket selection, saved preferences or other features from working correctly. Deleting cookies does not always fully withdraw previously recorded consent. To change a choice, preferably also use the cookie preferences button where shown above.
9. Changes
This cookie statement and inventory are updated when the use of cookies, similar technologies, suppliers or purposes changes. If a change affects consent previously given, consent may be requested again.
10. Contact
Questions about MiroBrowse’s use of cookies may be sent to info@mirobrowse.com. For questions about cookies or choices within a specific customer website or environment, first contact the organisation identified there as the responsible party.