Cookie Policy
Last updated: August 6, 2026
General Information
This Cookie Policy explains how MADIS uses cookies and similar technologies on this website.
Cookies are small text files that may be stored on your device when you visit the website. They help the website function properly, remember your preferences and, with your consent, measure interactions with the website and the effectiveness of marketing campaigns.
Technologies We Use
Necessary Cookies and Similar Technologies
These technologies are used for the basic operation of the website, including:
- ensuring that pages and forms function correctly;
- maintaining security;
- storing your choice regarding marketing technologies;
- providing other technical functions necessary for the operation of the website.
Separate consent is not required for technologies that are necessary for the operation of the website or for providing a function requested by the user.
NameTypePurposeStorage Periodmadis_marketing_cookie_consentCookieStores the user’s choice regarding marketing technologies. Up to 12 months or until the choice is changedmadis_marketing_cookie_consentLocal Storage. Additionally stores the user’s choice in the browser. Until the choice is changed or website data is cleared
Language cookies or local storage entries may also be used to remember the selected website language. Their exact names and storage periods depend on the current technical configuration of the website.
Marketing Cookies and Related Technologies
We use marketing technologies only after obtaining your consent.
They help us:
- measure page visits;
- record successful form submissions;
- evaluate advertising effectiveness;
- improve marketing campaigns.
We use Meta Pixel to measure visits and may additionally use Meta Conversions API to record successful enquiries.
Meta Pixel is not loaded and marketing events are not sent to Meta until you click “Accept all” in the cookie banner.
If you choose “Necessary only”, marketing technologies are not activated.
NameProviderPurposeStorage Period_fbpMetaHelps identify the browser for advertising and conversion measurementUp to 90 days_fbcMetaHelps identify a visit from a Meta advertisement when the page URL contains the fbclid parameterUp to 90 days
Meta Pixel
Meta Pixel is a browser-based technology that, after consent has been provided, may record events related to the use of the website.
The following events are currently sent through Meta Pixel:
PageView— a page view;Lead— a successful submission of an enquiry form.
The Lead event is sent only after the form has been successfully processed. Clicking the submit button, a validation error or unsuccessful processing of an enquiry is not treated as a Lead event.
Events may contain non-personal technical information about the page or service, if such information is available for the relevant form.
Meta Conversions API
Meta Conversions API allows marketing events to be sent directly from our server to Meta.
Currently, we send only the Lead event through Meta Conversions API after a form has been submitted successfully.
Meta Conversions API is used only after you have provided consent to marketing technologies.
Depending on the information available for the relevant form, the following data may be sent to Meta:
- the
Leadevent name; - the date and time of the event;
- a unique event identifier;
- the URL of the page from which the enquiry was submitted;
- the service identifier or slug;
- the IP address;
- information from the browser’s user-agent;
_fbpand_fbcvalues, if available;- the email address in a normalized and hashed form;
- the telephone number in a normalized and hashed form.
The page URL and service identifier are sent only when they are available for the relevant form.
The email address and telephone number are normalized and hashed using the SHA-256 algorithm before being sent. They are not sent to Meta in plain text.
Hashing is a data protection measure, but it does not mean that the data is fully anonymized. Hashed values may be used by Meta to match an event with a user of its services.
Event Deduplication
The Lead event may be sent simultaneously through Meta Pixel and Meta Conversions API.
To prevent one enquiry from being counted twice, the browser and server versions of the event receive the same unique event_id.
Meta uses this identifier together with the event name to match the browser and server events.
Managing Your Choice
When you first visit the website, you can choose:
- Necessary only;
- Accept all.
If you choose “Necessary only”:
- Meta Pixel is not loaded;
PageViewandLeadevents are not sent through Meta Pixel;- the
Leadevent is not sent through Meta Conversions API; - marketing cookies are not activated.
If you choose “Accept all”, the website may use Meta Pixel, marketing cookies and Meta Conversions API to measure visits, enquiries and advertising effectiveness.
You can change your choice using the “Cookie settings” button or link on the website.
If there is no separate button for reopening the cookie banner, you can clear the cookies and website data in your browser settings. The cookie banner will then be displayed again.
Deleting or Blocking Cookies
You can delete or block cookies in your browser settings.
If you block all cookies or local storage, some website functions may not work correctly and your choice regarding marketing technologies may not be saved.
Third-Party Providers
We use Meta services for marketing measurement.
Data may be transferred to and processed by Meta Platforms Ireland Limited and other companies within the Meta group in accordance with their terms and privacy policies.
More information about how Meta processes data can be found in the Meta Privacy Policy.
Information about the website controller, the legal grounds for processing, user rights and possible international data transfers can be found in our Privacy Policy.
Contact
If you have any questions about the use of cookies, marketing technologies or the processing of personal data, please contact us through the contact form on the website or using the contact details provided in the Privacy Policy.