Legal page
Cookie policy
Version 1.0
Last updated on 7 September 2026.
On dotnetlab.eu, we use cookies and similar technologies. Some are needed to make the website work properly. Others are only used if you give consent.
In this cookie policy, we explain which technologies we use, what we use them for and how you can adjust your preferences.
1. Who is responsible?
This website is managed by:
dotNET lab holding BV Gravin de Merodestraat 132 2260 Westerlo Belgium Enterprise number: BE 0797.521.231 Email: contact@dotnetlab.eu
More information about the processing of personal data can be found in our privacy policy: /en/privacy-policy.
2. What are cookies and similar technologies?
A cookie is a small file that can be stored in your browser through a website. Cookies can, for example, be used to recognise a browser, remember a preference or measure the use of a website.
We also use similar techniques, such as:
- localStorage in your browser;
- tracking pixels;
- JavaScript tags;
- identifiers created by external services.
For readability, this cookie policy sometimes uses the word "cookies" as a collective term for these technologies.
3. Which choices do you have?
Non-necessary analytics and marketing technologies are disabled by default.
Through our cookie popup, you can choose between different categories.
Necessary
These technologies are needed to make the website and your privacy preferences work correctly.
We do not ask for consent for these technologies.
Analytics
If you allow analytics, we can activate Google Analytics and related tags.
This information helps us understand how visitors use the website and where we can improve it.
Marketing
If you allow marketing, we can activate, among other things, Leadinfo and LinkedIn marketing technology.
These technologies help us better understand business visitors and campaigns and measure marketing results.
You can allow analytics and marketing separately.
4. How do we remember your choice?
We store your cookie preference in your browser's localStorage under the name:
dotnetlab_cookie_consent
In it, we store which categories you have allowed.
This setting is strictly intended to remember your choice. We do not use it to track your website behaviour.
We consider your choice valid for a maximum of six months. After that, the stored choice is ignored and we ask for your preferences again.
If you clear your browser data or localStorage, the website may ask for your preference again sooner.
5. Changing or withdrawing your preference
You can adjust or withdraw your consent at any time.
At the bottom of every page, you will find the Cookie preferences link. This allows you to reopen the cookie settings and change your choice.
When you withdraw consent, the relevant technologies are not activated again.
Cookies that are already present in your browser may, depending on the service involved, remain present until they expire or until you delete them. You can also delete cookies yourself through your browser settings.
6. Necessary technologies
The website itself uses technology that is needed to correctly load pages, navigation, forms, spam protection, images, self-hosted fonts and other parts of the site.
We also use localStorage to remember your cookie preference.
| Name | Type | Purpose | Retention period |
|---|---|---|---|
| dotnetlab_cookie_consent | localStorage | Remembering your choice for analytics and marketing | Valid for a maximum of 6 months |
This technology is used regardless of whether you allow analytics or marketing.
7. Google reCAPTCHA
We use Google reCAPTCHA v3 to protect forms against spam and automated abuse.
reCAPTCHA analyses technical signals and interactions to assess whether a form submission is likely to be legitimate. This check happens before a form is sent to us.
Because reCAPTCHA is needed to limit form abuse, we treat this technology as necessary for forms.
For this purpose, Google may use scripts, iframes, localStorage and cookies, including the _GRECAPTCHA cookie.
Provider: Google
8. Google Tag Manager
We use Google Tag Manager to manage scripts and tags on our website centrally.
The code that determines whether Google Tag Manager may be loaded can already be present on the website. The external Google Tag Manager script is only loaded when you have given consent for a category that requires a tag.
Google Tag Manager therefore helps determine which other technologies are activated. It does not itself grant consent for analytics or marketing.
Tags remain blocked as long as the required consent is missing.
9. Google Analytics
If you consent to analytics, we use Google Analytics 4.
Google Analytics helps us gain insight into, among other things:
- the number of visitors;
- visited pages;
- sessions and interactions;
- browser and device used;
- general traffic source;
- how visitors navigate through our website.
Google Analytics is not loaded before you have allowed analytics.
Google Analytics may place, among others, the following first-party cookies:
| Cookie | Purpose | Default duration |
|---|---|---|
| _ga | Distinguishing visitors | Up to 2 years |
| _ga_<id> | Storing session state | Up to 2 years |
The actual retention period may be shorter due to our configuration, browser restrictions or if you delete the cookies yourself.
Provider: Google
10. Leadinfo
If you consent to marketing, we use Leadinfo.
Leadinfo helps us recognise which organisations visit our website and gives insight into the use of the website by those organisations.
In doing so, information about visited pages, date and time, referring page and IP address may be processed. Leadinfo links IP addresses to publicly available company data to recognise organisations.
Leadinfo is not loaded before you have allowed marketing.
Leadinfo may use, among others, the following cookies:
| Cookie | Purpose | Retention period |
|---|---|---|
| _li_id.xxxx | Information about a visit or session | Session |
| _li_ses.xxxx | Recognising visits across multiple sessions | Up to 2 years |
Leadinfo may also temporarily store data in localStorage to buffer events that have not yet been sent.
Provider: Leadinfo B.V.
11. LinkedIn
If you consent to marketing, we may use the LinkedIn Insight Tag.
This allows us, among other things, to:
- measure whether LinkedIn campaigns lead to website visits or conversions;
- analyse campaign results;
- obtain aggregated information about visitors;
- create audiences for business advertising and retargeting.
LinkedIn may receive data such as:
- the visited URL;
- referring URL;
- IP address;
- browser and device data;
- time of the visit;
- interactions used for campaign measurement.
The LinkedIn Insight Tag is not loaded before you have allowed marketing.
On third-party websites, LinkedIn may use cookies such as:
| Cookie | Purpose | Retention period |
|---|---|---|
| bcookie | Browser identification and security | Up to 1 year |
| lidc | Selection of LinkedIn data centre | 24 hours |
| li_gc | Storing cookie preferences at LinkedIn | 6 months |
| li_mc | Supporting LinkedIn consent management | 6 months |
| UserMatchHistory | Synchronisation of advertising IDs | 30 days |
| AnalyticsSyncHistory | Synchronisation for analytics | 30 days |
| lms_ads | Supporting advertising purposes | 30 days |
| lms_analytics | Supporting analytics | 30 days |
Not every cookie in this table is necessarily placed on every visit. This depends, among other things, on your browser, your LinkedIn status and the LinkedIn functionality used.
Provider: LinkedIn
12. Google Ads and other marketing tags
Our technical setup supports Google Consent Mode.
Without consent for marketing, the following consent signals, among others, remain denied:
- ad_storage;
- ad_user_data;
- ad_personalization.
Marketing tags that need this consent are not activated as long as you have not allowed marketing.
When we activate additional marketing tags, we update this cookie policy where necessary.
13. YouTube videos
Some pages may contain videos provided through YouTube.
Where possible, we use youtube-nocookie.com. This more privacy-friendly embed limits the use of cookies by YouTube, but loading the video may still establish a direct connection with YouTube. Technical data such as your IP address and browser information may be sent to YouTube.
At the moment, such a connection is made when a page or section containing the relevant video is opened.
We are exploring a setup where YouTube is only loaded after you make a separate choice via a button such as Load video.
14. Third-party services
The technologies on our website are partly provided by external parties.
These include:
- Google;
- LinkedIn;
- Leadinfo.
These parties may also process personal data themselves and may use their own cookies or other identifiers once their technology is activated.
More information about how we handle personal data and international transfers can be found in our privacy policy: /en/privacy-policy.
15. Deleting cookies yourself
You can also view and delete cookies and stored website data through your browser.
How this works differs per browser. Please consult your browser's privacy or cookie settings.
Deleting cookies or localStorage may cause us to ask for your cookie preference again.
16. Changes to this cookie policy
The technologies on our website may change.
When we add new cookies, tags or other tracking technologies or use existing technologies differently, we update this cookie policy where necessary.
At the top of this page, you will always find the version and date of the latest change.
17. Contact
Do you have a question about our use of cookies or other technologies? Contact us at:
dotNET lab holding BV Gravin de Merodestraat 132 2260 Westerlo Belgium contact@dotnetlab.eu