Bewitt does not use cookies to sell personal data and does not use invasive advertising tracking. Optional cookies are used only where permitted by law or after consent where consent is required.
Essential cookies
Needed for login, secure sessions, registrations, participant access, payments, check-ins, organizer dashboards, and abuse prevention.
Optional cookies
Used for preferences, analytics, or performance only where permitted or after consent when consent is required.
Your choices
You can manage optional cookies through consent choices where available or browser controls. Blocking all cookies may break core event access.
1. Introduction
This Cookie Policy explains how Bewitt uses cookies and similar technologies on its website and cloud-based SaaS event-management platform.
Bewitt provides event management, registrations, agenda management, check-ins, gamification, quizzes, feedback, reporting, analytics, payments, and custom domain functionality.
This Policy should be read together with Bewitt's Privacy Policy. Where cookies or similar technologies involve personal data, the GDPR may apply in addition to the Dutch rules implementing the ePrivacy Directive.
2. What Cookies Are
Cookies are small text files placed on your device when you visit a website or use an online service. Similar technologies include local storage, session storage, API tokens, authentication tokens, security tokens, pixels, SDKs, and server-side identifiers.
These technologies may store or access information such as session identifiers, login status, security signals, browser information, device information, preferences, and usage events.
3. Why Bewitt Uses Cookies
Bewitt may use cookies and similar technologies to:
- provide the website and application;
- authenticate users;
- maintain secure sessions;
- prevent fraud, abuse, and unauthorized access;
- remember user preferences;
- support registrations, payments, event access, and check-ins;
- measure platform reliability and performance;
- improve the Service;
- generate aggregated analytics where enabled; and
- comply with legal and security obligations.
4. Types of Cookies Used
| Cookie Category | Purpose | Legal Basis | Retention Period | Required / Optional |
|---|---|---|---|---|
| Essential | Operate the website and platform, route requests, maintain sessions, enable registration flows, support payment and event functionality. | Strictly necessary under ePrivacy rules; GDPR basis may be contract performance or legitimate interests. | Session to 12 months, depending on function. | Required |
| Authentication | Keep users signed in, verify account access, protect organizer dashboards and participant areas. | Strictly necessary; GDPR basis may be contract performance and legitimate interests. | Session, or up to 30 days for remember-me style functionality. | Required where login is used |
| Security | Detect abuse, prevent fraud, protect against CSRF, rate-limit requests, maintain audit and security logs. | Strictly necessary or legitimate security interest; GDPR basis may be legitimate interests or legal obligation. | Minutes to 12 months, depending on risk and security need. | Required |
| Preferences | Remember language, interface choices, cookie choices, event display settings, or similar preferences. | Consent where required; otherwise legitimate interests for low-impact functional preferences. | Usually 6 to 12 months. | Optional unless necessary for requested functionality |
| Analytics | Understand website or platform usage, visitor counts, page performance, feature adoption, and event-level reporting. | Consent unless configured in a privacy-preserving manner that has no or little privacy impact under applicable Dutch rules; GDPR basis may be consent or legitimate interests. | Usually up to 13 months. | Optional unless exempt |
| Performance | Monitor errors, latency, uptime, diagnostics, and technical performance. | Consent where required; otherwise legitimate interests for necessary reliability and security monitoring. | Usually 30 days to 13 months. | Optional or required depending on configuration |
| Third-party | Support payments, hosting, DNS, email, analytics, error monitoring, and integrations. | Depends on cookie and provider: strictly necessary, consent, contract performance, or legitimate interests. | Set by the relevant provider. | Required or optional depending on service |
5. Essential Cookies
Essential cookies are required for the website or application to function. They may be used for login sessions, CSRF protection, secure payment flows, registrations, event access, check-ins, organizer dashboards, load balancing, and fraud prevention.
Essential cookies do not require consent because they are necessary to provide a service requested by the user or to operate the platform securely.
If you block essential cookies, parts of Bewitt may not work.
6. Functional Cookies
Functional cookies remember choices and settings, such as cookie preferences, display preferences, language preferences, or event-interface options.
Some functional cookies may be placed without consent if they are necessary or have no or little privacy impact. Other functional cookies may require consent depending on their purpose and configuration.
7. Analytics Cookies
Analytics cookies help Bewitt understand how users interact with the website and platform.
Analytics may include:
- page visits;
- feature usage;
- event registration funnel performance;
- aggregated usage patterns;
- error rates;
- device and browser types; and
- anonymized or aggregated reporting; and
- public-page experience analytics such as Contentsquare when enabled.
Analytics cookies require consent unless they are configured in a privacy-preserving way and have no or little impact on privacy under applicable law. Where Google Analytics, Contentsquare, Plausible, or another analytics provider is enabled, Bewitt will configure and present cookie choices in line with applicable consent requirements.
Contentsquare, when enabled, is loaded on public pages and standalone error pages. It is not loaded on Bewitt admin pages.
8. Performance Cookies
Performance cookies and similar technologies help Bewitt monitor reliability, speed, errors, uptime, and system health.
These technologies may be used to detect broken pages, failed requests, slow responses, API errors, or application crashes. Where performance monitoring is strictly necessary for security or service reliability, it may be used without consent. Where it goes beyond what is necessary, Bewitt will request consent where required.
9. Third-Party Cookies
Bewitt may use or integrate with third-party services, including:
- Stripe for payment processing;
- AWS for hosting and infrastructure;
- Cloudflare for security, DNS, caching, and performance;
- Google Analytics, if enabled;
- Contentsquare for public-page experience analytics, if enabled;
- Plausible, if enabled;
- email service providers;
- error monitoring services; and
- other API or platform integrations configured by Bewitt or an event organizer.
Third-party providers may set their own cookies or similar technologies. Their use is governed by their own policies and terms. Where third-party cookies are not strictly necessary, Bewitt will request consent where required.
10. Cookie Retention Periods
Cookie retention depends on the purpose and type of cookie:
- session cookies are usually deleted when you close your browser;
- authentication cookies may last for the session or a limited login period;
- security cookies may last from a few minutes to several months;
- preference cookies generally last 6 to 12 months;
- analytics and performance cookies generally last up to 13 months unless a shorter period applies; and
- third-party cookies follow the retention periods set by the relevant provider.
Bewitt aims to avoid keeping cookie data longer than necessary.
11. How Users Can Manage Cookies
You can manage cookies by:
- using the cookie banner or cookie settings tool, where available;
- accepting or rejecting optional cookies;
- changing cookie preferences later;
- withdrawing consent for optional cookies;
- using browser controls to block or delete cookies; and
- configuring privacy settings in your browser or device.
Essential cookies cannot be disabled through Bewitt's cookie settings because they are needed to provide the Service.
12. Browser Controls
Most browsers allow you to:
- view cookies;
- delete cookies;
- block all cookies;
- block third-party cookies;
- clear cookies when closing the browser; and
- set site-specific cookie preferences.
Browser settings vary. If you block all cookies, parts of Bewitt may not function, including login, registrations, dashboards, payments, check-ins, and event access.
13. Cookie Consent Management
Where consent is required, Bewitt will ask for consent before placing optional cookies.
Consent must be freely given, specific, informed, and unambiguous. Optional cookies should not be enabled by pre-ticked boxes, inactivity, or continued browsing.
You can withdraw consent or update preferences at any time through the cookie settings mechanism made available on the website or platform. Withdrawing consent does not affect the lawfulness of processing based on consent before withdrawal.
14. Impact of Disabling Cookies
If you disable optional cookies, you should still be able to use the core Service, although some preferences, analytics, or performance features may be limited.
If you disable essential cookies, Bewitt may not be able to:
- keep you logged in;
- protect your session;
- process registrations correctly;
- complete payment flows;
- verify check-ins;
- remember security state;
- load organizer dashboards; or
- provide requested event functionality.
15. Changes to This Policy
Bewitt may update this Cookie Policy from time to time to reflect changes in the Service, cookies, third-party providers, legal requirements, or consent-management practices.
The updated version applies from the date stated at the top of the Policy.
16. Contact Information
Questions about this Cookie Policy may be sent to:
BewittNetherlands
Email: [email protected]
