Cookie Policy

1. Who are the parties involved?

In our cookie policy, the following definitions apply:

MeetDistrict NV (with company number BE0568.815.225) / MeetDistrict Gent NV (with company number BE0627.806.863), both with registered offices at Zwaanhofweg 10 in 8900 Ypres.

‘User’ or ‘you’: every natural person (B2C) or legal entity (B2B) who is or will be in a contractual relationship of any kind with MeetDistrict NV / MeetDistrict Gent NV through this online platform.

‘Law’: art. 129 Law on electronic communications, as amended by W 2012-07-10/04, art. 90, 017; (entry into force: 04-08-2012).

2. What are cookies?

A cookie is a small text and number file that we store in your browser or on the hard drive of your computer. This allows us to remember your preferences when using our website (e.g. language selection).

Unless you have adjusted your browser settings as such that cookies will be refused, our system will place cookies as soon as you visit our website.

The cookies we use on this website are safe and meant to make your visit as pleasant as possible. We anonymize as much as possible the data we collect through the cookies.

3. Types of cookies

Our cookies can be divided according to their origin, their function and their lifespan.

- First-party cookies are cookies set by a website visited by the user at that time (such as cookies set by MeetDistrict NV / MeetDistrict Gent NV).

- Third-party cookies are cookies set by a domain other than that of the website visited by the user. If a user visits a website and a third party places a cookie through that website, this is a third-party cookie (such as cookies placed by Google, Twitter, Facebook and Hotjar).

- Functional cookies are cookies that make the website work properly (such as cookies for logging in or registering, and language preferences). By definition, functional cookies are first-party cookies.

- Non-functional cookies are cookies that can be placed for statistical, social, commercial and targeted advertising purposes. They have nothing to do with the purely technical support of the website. Cookies with statistical purposes allow tracking which pages of the website you visit, where your computer is located, etc. Cookies with social purposes allow the user to share the content of the visited website directly with others via social media. Cookies for targeted advertising purposes make it possible to build a profile based on your browsing behavior so that displayed advertisements are tailored to your interests. Cookies with commercial purposes track how many and which ads were shown to a user. Non-functional cookies can be first-party or third-party cookies.

- Persistent cookies: these cookies remain on the user's device for the duration specified in the cookie. They are activated each time the user visits the website that has set this cookie (e.g., cookies set by social media such as Twitter, Facebook, Google Analytics, etc.). Most non-functional cookies are permanent cookies.

- Session cookies: these cookies allow us to simplify and link a user's actions during a browser session. A browser session starts when a user opens the browser window, and ends when the browser window is closed. Session cookies are placed temporarily. Once you close the browser, all session cookies are deleted. Most functional cookies are session cookies.

4. Managing cookies

We point out that web browsers allow you to change your cookie settings. These settings can be found in the 'Options' or 'Preferences' menu of your web browser. To better understand these settings, the following links can be useful. If not, you should consult the 'Help' function in your web browser for more details.

5. Which cookies are used on this platform?

Functional cookies

Designation

Validity

Target

Local

1 year

Language preference

Cookieconsent_status

1 year

Interactive cookie notification

Non-functional cookies

Designation

Validity

Content and purpose

1P_JAR

1 month

These cookies are used by Google to display personalized ads on Google sites based on recent searches and previous interactions.

ANID

1 year

This cookie from Google Analytics links your activities on other devices on which you have previously logged in with your Google account. This coordinates the ads you see on your devices and measures conversion events.

ADVERTISEMENT

20 years

YouTube (Google) uses this to store permission to use third-party content in frames - google.com/policies/privacy Third Party Persistent.

NID-3PAPISID

5 months

Cookie from DoubleClick, part of Google Analytics. Used to make ads more attractive.

__Secure

2 years

Builds a profile of website visitor's interests to display relevant and personalized advertisements through re-targeting with targeted advertising.

__Secure-3PSID

2 years

Builds a profile of website visitor's interests to display relevant and personalized advertisements through re-targeting with targeted advertising.

__Secure-3PSIDCC

2 years

Builds a profile of website visitor's interests to display relevant and personalized advertisements through re-targeting with targeted advertising.

_gcl_au

session

This is the first-party cookie for conversion link functionality - it uses information from clicked ads and stores it in a first-party cookie so that conversions can be attributed beyond the landing page.

__gtm_campaign_url

6 months

Stores utm data for reporting purposes.

__gtm_referrer

6 months

Retains the referring link for reporting purposes.

__utmzzses

session

These cookies are used to collect information about how visitors use our site. We use this information to compile reports and improve the site. The cookies collect information anonymously, such as the number of visitors to the site, which site visitors came from, and the pages they visited.

initialTrafficSource

session

Tracks the visitor's initial traffic source with Google Tag Manager.

c_user

session

For a logged-in Facebook user.

datr

session

For a logged-in Facebook user.

dpr

session

This cookie is used by Facebook for performance purposes.

fr

session

For a logged-in Facebook user.

presence

session

For a logged-in Facebook user.

sb

session

For a logged-in Facebook user.

spin

session

For a logged-in Facebook user.

xs

session

For a logged-in Facebook user.

_fbc

session

Pixel cookie from Facebook.

_fbp

session

Pixel cookie from Facebook.

DSID

1 day

DoubleClick (Google) uses cookies to improve advertisements. They do not contain information that identifies anyone.

IDE

2 years

DoubleClick (Google) uses cookies to improve advertisements. They do not contain information that identifies anyone.

RUL

session

DoubleClick (Google) uses cookies to improve advertisements. They do not contain information that identifies anyone.

_BEAMER_DATE_zeKLgqli17986

300 days

This cookie is set by Beamer and stores the most recent date the feed was accessed.

_BEAMER_FIRST_VISIT_zeKLgqli17986

3000 days

This cookie is set by Beamer to store the date of this user's first interaction along with insights.

_BEAMER_LAST_POST_SHOWN_zeKLgqli17986

3000 days

This cookie is set by Beamer and stores the timestamp of the last time the number of unread messages for this user was updated.

_BEAMER_LAST_UPDATE_zeKLgqli17986

3000 days

This cookie is set by Beamer and stores the timestamp of the last time the number of unread messages for this user was updated.

_BEAMER_USER_ID_zeKLgqli17986

300 days

This cookie is set by Beamer to store an internal ID for a user.

_hjAbsoluteSessionInProgress

30 minutes

This cookie is used to detect a user's first page view session. In doing so, the cookie sets a True/False attribute.

_hjTLDTest

session

When the Hotjar script is run, we try to determine the most generic cookie path we should use instead of the page name on the server. The purpose of this is to be able to share cookies among subdomains (if applicable). To determine this, we attempt to store the _hjTLDTest cookie for various url substring alternatives until this fails. After this check, the cookie is deleted.

_hjid

1 year

Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. Used to store the Hotjar user ID unique to that site on the browser. This ensures that behavior on subsequent visits to the same site is attributed to the same user ID.

_hjIncludedInPageviewSample

30 minutes

Cookie that lets Hotjar know if that visitor is included in the data sample determined by your site's page view limit.

__cfruid

1 session

Helps Cloudflare detect malicious visitors to your website and limit blocking of legitimate users.

cf_clearance

1 session

Helps Cloudflare detect malicious visitors to your website and limit blocking of legitimate users.

hubspotapi

5 minutes

This cookie allows the user to access the app with appropriate permissions.

hubspotapi-csrf

1 year

This is used for CSRF prevention - preventing third-party websites from accessing your data.

hubspotapi-prefs

1 year

This is used with the hubspotapi cookie so that the system can remember if the user has checked the "remember me" box (this manages the expiration time of the main cookie authentication).

hubspotutk

13 months

This cookie keeps track of a visitor's identity. It is passed to HubSpot upon form submission, and is used for contact deduplication.

__hssc

30 minutes

This is used to determine whether HubSpot should incrementally increment the session number and timestamps in the hstc cookie.

__hssrc

1 session

If this cookie does not exist when HubSpot manages cookies, the session is considered a new session.

__hstc

13 months

Contains the domain, utk, initial timestamp (from the first visit), last timestamp (from the last visit), current timestamp (from the current visit) and session number (which increases incrementally with each subsequent session).

__stripe_mid

1 year

For the prevention of fraud

* For cookies placed by third parties (e.g. Google Analytics & Hotjar) we refer you to the statements that these parties give on their respective websites. Please note: we cannot influence the content of these statements or the content of the cookies of these third parties.

6. Applicable law and jurisdiction

This Cookie Policy is governed, interpreted and executed in accordance with Belgian law, which is exclusively applicable to any dispute.

The courts in Ypres and the court of appeal in Ghent, are exclusively competent to judge any dispute that may arise from the interpretation or the implementation of this Cookie Policy.

7. Acceptance

By visiting the website and at the latest at the time of your registration, you accept all the provisions of this Cookie Policy and accept that MeetDistrict NV / MeetDistrict Gent NV collects and processes your personal data in accordance with this Cookie Policy, our Privacy Statement and our Disclaimer, which can be found on this website.

MeetDistrict HQ

  • Mon - Thurs 08:00 - 18:00
    Fri 08:00 - 17:00
    Closed on Sat, Sun & public holidays