This Cookie Policy explains how dibl.eu uses cookies and similar technologies to recognize you when you visit our website.
What Are Cookies?
Cookies are small text files stored on your device to help websites function efficiently and provide a secure user experience. They are used to ensure proper functioning of our sites (auth.dibl.eu, web.dibl.eu, admin.dibl.eu), maintain user sessions, and support authentication processes. We do not use cookies for tracking, advertising, or any non-essential purposes.
How We Use Cookies
We use cookies to:
- Ensure the proper functioning of our sites dibl.eu and dibl.it.
- Understand how visitors interact with our content
- Improve your browsing experience
Types of Cookies We Use
- Essential cookies – Required for the website to function (e.g., security, page navigation)
- Analytics cookies – Help us understand website usage so we can improve it (e.g., Google Analytics)
- Preference cookies – Remember your settings and preferences
What cookies we use
| Cookie | Host | Purpose | Type | Duration |
| .AspNetCore.Identity.Application | auth.dibl.eu | Stores user authentication data, including claims and identity information for secure login sessions. | First person | 14 days with sliding expiration (if “Remember Me” is selected), otherwise session |
| idsrv.session | auth.dibl.eu | Manages user session state for OpenID Connect authentication flows, including session ID and authentication time. | First person | Session |
| AspNetCore.Cookies | web.dibl.eu | Stores local authentication ticket after successful login via the identity server, maintaining user session on the site. | First person | 10 hours (fixed expiration, no sliding) |
| .AspNetCore.Cookies | admin.dibl.eu | Stores local authentication ticket for admin interface access after successful login via the identity server. | First party | 12 hours (fixed expiration, no sliding) |
| Microsoft.AspNetCore.Authentication.OpenIdConnect.Nonce.* | auth.dibl.eu, web.dibl.eu, admin.dibl.eu | Security cookie used during OpenID Connect authentication flow to prevent replay attacks. | First party | Session |
| Microsoft.AspNetCore.Authentication.OpenIdConnect.Correlation | auth.dibl.eu, web.dibl.eu, admin.dibl.eu | Security cookie used to correlate authentication requests and responses during OpenID Connect flow. | First party | Session |
| _cf_bm vimeo.com | vimeo.com | Necessary | Third party | 1 day |
| _cfuvid vimeo.com | vimeo.com | Necessary | Third party | Session |
| _grecaptcha | gstatic.com | Necessary | Third party | Persistent |
| _GRECAPTCHA | gstatic.com | Necessary | Third party | 180 days |
| CookieConsent | dibl.eu | Necessary | Third party | 365 days |
| rc::a | gstatic.com | Necessary | Third party | Persistent |
| rc::b | gstatic.com | Necessary | Third party | Session |
| rc::c | gstatic.com | Necessary | Third party | Session |
| rc::f | gstatic.com | Necessary | Third party | Persistent |
| li_gc | .linkedin.com | Stores the user’s cookie consent preferences for LinkedIn cookies. | Third party | 6 months |
| bcookie | .linkedin.com | Browser identifier cookie used to uniquely identify devices accessing LinkedIn services, supporting security and analytics. | Third party | 1 year |
| li_sugr | .linkedin.com | Collects anonymised browser and device data to measure ad performance and build retargeting audiences via the LinkedIn Insight Tag. | Third party | 90 days |
| ln_or | .linkedin.com | Used by the LinkedIn Insight Tag to track conversions and attribute them to LinkedIn ad campaigns. | Third party | 1 day |
| AnalyticsSyncHistory | .linkedin.com | Stores information about when syncing with LinkedIn analytics last took place. | Third party | 30 days |
| UserMatchHistory | .linkedin.com | Used by LinkedIn for ad targeting and audience matching by syncing visitor IDs across partner sites. | Third party | 30 days |
| wp-wpml_current_language | dibl.eu | Preference | Third party | Session |
Managing Cookies
You can manage or delete cookies through your browser settings. Please note that disabling some cookies may affect site functionality.
Security configuration
- SameSite=None: Required for cross-domain authentication flows between our subdomains
- Secure=Always: All cookies are only transmitted over HTTPS connections
- HttpOnly: Authentication cookies are not accessible via JavaScript (where applicable)
Contact Us
If you have any questions about our use of cookies, feel free to contact us at info@dibl.eu.