Cookie Policy

1. To whom and what does this Cookie Policy apply?

1.1 This Cookie Policy applies to the website ziggu.io (including its language versions) and to the Ziggu platform (web and mobile). Both are managed by Ziggu BV, with registered office at Vlasgaardstraat 52, 9000 Ghent, Belgium, company number BE 0699.472.839 ("Ziggu", "we").

1.2 For the website, Ziggu is the controller. In the platform, Ziggu primarily processes the data as a processor on behalf of the organisation that gave you access (the "Customer"). The cookies and storage in the platform are strictly necessary and are used by Ziggu in the same way for all Customers.

1.3 This Cookie Policy forms an integral part of our Privacy Policy. There you can read which personal data we collect via cookies, on what legal basis, and what rights you have.

2. What are cookies?

2.1 Cookies are small files that your browser stores on your computer or mobile device when you use a website or application. By "cookies" we also mean similar technologies, such as local storage, IndexedDB, pixels and scripts that store or read information on your device.

2.2 First-party cookies are placed by the domain you visit, third-party cookies by another domain, such as an advertising or analytics platform. Session cookies disappear when you close your browser. Persistent cookies are kept until they expire or until you delete them.

3. Which categories do we use?

3.1 Strictly necessary cookies (website and app) are essential for operation and security: logging in, remembering your cookie preferences, protection against abuse, and services you expressly request (such as scheduling an appointment or the support chat). No consent is required for these. They are used on the basis of our legitimate interest and cannot be disabled.

3.2 Analytical cookies (website only, only with consent) show us how visitors use the website, so that we can improve it. We use the results in aggregated form.

3.3 Marketing cookies (website only, only with consent) measure the performance of our advertisements, show relevant advertisements on other platforms and enable social media features. Some providers (LinkedIn, Meta) combine these data with their own data. They are (jointly) responsible for this.

4. Overview of the cookies used

"Where" column: Website = the marketing website ziggu.io; App = the Ziggu platform after logging in.

• cookieyes-consent
  Provider: CookieYes
  Where: Website
  Category: Strictly necessary
  Purpose: Remembers your cookie preferences, so that we do not ask you again on every visit and your choice is respected
  Retention period: 6–12 months
• __cf_bm
  Provider: Cloudflare (via Calendly/HubSpot)
  Where: Website
  Category: Strictly necessary
  Purpose: Distinguishes humans from bots and protects embedded services against abuse
  Retention period: 30 minutes
• _cfuvid
  Provider: Calendly (calendly.com)
  Where: Website
  Category: Strictly necessary
  Purpose: Ensures that the embedded appointment scheduler works reliably during your visit
  Retention period: Session
• firebaseLocalStorageDb (IndexedDB)
  Provider: Ziggu (Firebase Authentication, Google)
  Where: App
  Category: Strictly necessary
  Purpose: Keeps you logged in and secures your session
  Retention period: Until you log out
• intercom-session-[app-id]
  Provider: Intercom
  Where: App
  Category: Strictly necessary
  Purpose: Keeps track of your support conversation during your session, so that you can see your messages and replies
  Retention period: 1 week
• intercom-id-[app-id]
  Provider: Intercom
  Where: App
  Category: Strictly necessary
  Purpose: Recognises your device, so that previous support conversations remain available
  Retention period: 9 months
• intercom-device-id-[app-id]
  Provider: Intercom
  Where: App
  Category: Strictly necessary
  Purpose: Identifies your device for the support chat and prevents abuse
  Retention period: 9 months
• _ga
  Provider: Google Analytics
  Where: Website
  Category: Analytical
  Purpose: Distinguishes unique visitors in order to measure use of the website over a longer period
  Retention period: 2 years
• _ga_[ID]
  Provider: Google Analytics
  Where: Website
  Category: Analytical
  Purpose: Stores the session state for Google Analytics 4
  Retention period: 2 years
• __hstc
  Provider: HubSpot
  Where: Website
  Category: Analytical
  Purpose: Keeps track of visits (first and last visit, number of sessions)
  Retention period: 6 months
• hubspotutk
  Provider: HubSpot
  Where: Website
  Category: Analytical
  Purpose: Links your visit to a submitted form, so that we can follow up your request properly
  Retention period: 6 months
• __hssc / __hssrc
  Provider: HubSpot
  Where: Website
  Category: Analytical
  Purpose: Determines whether a new session starts and counts page views within a session
  Retention period: 30 minutes / session
• _bugherd_session
  Provider: BugHerd
  Where: Website
  Category: Analytical
  Purpose: Makes it possible to report feedback and errors on the website
  Retention period: Session
• bcookie
  Provider: LinkedIn
  Where: Website
  Category: Marketing
  Purpose: Recognises your browser for LinkedIn advertising and security
  Retention period: 1 year
• li_gc
  Provider: LinkedIn
  Where: Website
  Category: Marketing
  Purpose: Stores your consent for LinkedIn cookies
  Retention period: 6 months
• lidc
  Provider: LinkedIn
  Where: Website
  Category: Marketing
  Purpose: Optimises routing to LinkedIn servers
  Retention period: 1 day
• UserMatchHistory / AnalyticsSyncHistory
  Provider: LinkedIn
  Where: Website
  Category: Marketing
  Purpose: Synchronises data for measuring and targeting LinkedIn advertisements (LinkedIn Insight Tag)
  Retention period: 30 days
• lang
  Provider: LinkedIn
  Where: Website
  Category: Marketing
  Purpose: Remembers your language setting for LinkedIn content
  Retention period: Session
• _fbp
  Provider: Meta (Facebook/Instagram)
  Where: Website
  Category: Marketing
  Purpose: Measures the performance of advertisements on Facebook and Instagram and shows relevant advertisements
  Retention period: 3 months
• _fbc
  Provider: Meta
  Where: Website
  Category: Marketing
  Purpose: Stores the click ID when you arrive at the website via a Meta advertisement
  Retention period: 3 months
• _gtmeec
  Provider: Ziggu (Google Tag Manager, for Meta)
  Where: Website
  Category: Marketing
  Purpose: Stores data for measuring advertising conversions
  Retention period: Session

4.2 The platform does not use analytical or marketing cookies. Error tracking in the platform (Sentry) works without cookies. See the Privacy Policy and ziggu.io/legal/sub-processors.

5. How do you manage your cookie preferences?

5.1 On your first visit to the website, we ask for your consent for analytical and marketing cookies. They are not placed without your express consent. Refusing is as easy as accepting.

5.2 You can change or withdraw your consent at any time via the cookie icon at the bottom of every page of the website. Withdrawing your consent does not affect the lawfulness of the use before its withdrawal.

5.3 You can also block or delete cookies via your browser settings: Chrome, Firefox, Safari (Mac), Safari (iOS), Edge. If you block strictly necessary cookies or storage, the website or the platform (e.g. logging in or the support chat) may no longer work correctly.

6. Changes

6.1 We may amend this Cookie Policy, for example when we start using new tools. The date at the top shows when it was last changed. For new cookies or purposes that require consent, we will ask for your consent again.

7. Questions

7.1 Do you have questions about this Cookie Policy? E-mail privacy@ziggu.io. More information about your rights, and about how to lodge a complaint with the Data Protection Authority, can be found in section 11 of our Privacy Policy.