Remarque : nos documents juridiques sont disponibles uniquement en anglais.
Cookie Policy
Dernière mise à jour : 2026-05-26
What cookies and similar technologies openevent.io uses, why we use them, and how you can change your choice at any time. This page complements our Privacy Policy — see §10 there for the high-level summary.
What cookies are
Cookies are small text files that websites store on your device. They let a site remember things between page loads — for example, the fact that you are logged in, the language you have chosen, or whether you have already dismissed a banner. Similar technologies (local storage, session storage, pixels, fingerprinting) are used in similar ways. In this policy, "cookies" means cookies and similar technologies together.
Some cookies are set by us. Some are set by third-party services we use — they are called third-party cookiesand the third party's own privacy policy also applies to them.
Our approach
We use as few cookies as we can get away with. Cookies that aren't strictly necessary to run the site are off by default— they only load if you actively accept them in our cookie banner. Strictly necessary cookies are always on, because the site won't work without them.
We never use cookies to collect special-category data (health, religion, sexual orientation, etc.). We never sell the data collected by cookies. We never share what you do on openevent.io with advertisers unless you have accepted the Marketing & advertising cookie category.
The four categories
Every cookie set on openevent.io belongs to one of four categories.
1. Strictly necessary — always on
These cookies make the site work. They handle log-in sessions, security, load balancing and they remember your cookie-banner choice itself. Without them, the site can't function.
Examples:
- Session identifier
- Cross-Site Request Forgery (CSRF) token
- Cookie-consent preference
You cannot switch this category off. It does not require consent under Swiss or EU law because it is strictly necessary to provide the service you have asked for.
2. Functional — opt-in
These cookies remember choices you have made to give you a better experience. The site works without them; it just doesn't remember your preferences between visits.
Examples:
- Language preference (e.g. EN / DE)
- "Don't show this announcement again" dismissals
- Embedded Calendly widget cookies (loaded only on pages that use the demo-booking widget — currently the pricing and demo pages)
3. Analytics — opt-in
These cookies tell us, in aggregate, how the site is being used so we can improve it. They count visits, measure how long people spend on different pages, and tell us which content is useful. They do not identify you personally.
Currently planned:
- Google Analytics 4 — a small set of cookies (
_ga,_ga_*) used to count visits and measure conversions. IP addresses are truncated. We may also add a cookieless alternative (e.g. Plausible) as we evolve our analytics setup.
This category is off until you accept it.
4. Marketing & advertising — opt-in
These cookies measure how well our paid advertising campaigns perform on third-party platforms and let us avoid wasting ad spend on people who are already customers. They share specific events (you reached a page, you booked a demo, you signed up) with the ad platform so it can show our ads to similar people.
Currently planned:
- Meta Pixel (Facebook / Instagram) —
_fbpand related cookies, plus matched events sent via the Meta Conversions API. - TikTok Pixel — TikTok identifier cookies plus matched events sent via the TikTok Events API.
- LinkedIn Insight Tag (potential) — LinkedIn identifier cookies, if we ever run B2B campaigns on LinkedIn.
This category is off until you accept it. Reject this category and none of the ad-platform pixels fire on your visit. We will not share any event signal with any ad platform from your visit.
If you have accepted this category in the past and want to change your mind, click "Cookie settings" in the footer and switch it off — we stop loading the pixels immediately, for future visits.
Full cookie table
The table below is the v1.0 best-effort list based on what we plan to ship. Before this page goes live, we will run an automated cookie audit on the staging site and confirm every cookie actually set, its real name, exact lifetime, and whether it is first- or third-party.
Strictly necessary
| Cookie | Set by | Purpose | Lifetime | Party |
|---|---|---|---|---|
__session | openevent.io | Keeps you signed in to gated areas of the site. | Session | First |
csrf_token | openevent.io | Protects forms against cross-site request forgery. | Session | First |
oe_cookie_consent | openevent.io | Stores your cookie-banner choice so we don't ask again. | 12 months | First |
Functional
| Cookie | Set by | Purpose | Lifetime | Party |
|---|---|---|---|---|
oe_locale | openevent.io | Remembers your language preference. | 12 months | First |
oe_dismissed_banners | openevent.io | Remembers which one-off announcements you have dismissed. | 12 months | First |
__cf_bm, _cfuvid | Calendly | Bot protection and session continuity inside the Calendly demo-booking widget. | 30 min / 30 days | Third |
Analytics (planned: Google Analytics 4)
| Cookie | Set by | Purpose | Lifetime | Party |
|---|---|---|---|---|
_ga | Google Analytics | Distinguishes unique visitors. | 24 months | First |
_ga_<property-id> | Google Analytics | Persists session state for GA4. | 24 months | First |
_gid | Google Analytics | Distinguishes users over a shorter window. | 24 hours | First |
Marketing & advertising (planned: Meta, TikTok, LinkedIn)
| Cookie | Set by | Purpose | Lifetime | Party |
|---|---|---|---|---|
_fbp | Meta (Facebook / Instagram) | Identifies the browser for ad attribution and audience matching. | 90 days | First |
fr | Meta | Set on facebook.com for ad delivery and measurement when you cross to Meta-owned properties. | 90 days | Third |
_ttp | TikTok | Identifies the browser for ad attribution and audience matching on TikTok. | 13 months | First |
tt_* (various) | TikTok | Session and event-tracking cookies set by the TikTok Pixel. | Session – 13 months | Third |
li_fat_id, bcookie, lidc | Identifies the browser for LinkedIn ad attribution and audience matching, if we activate LinkedIn ads. | Up to 24 months | Third |
How to change your choice
There are three ways to change your cookie preferences:
- Click "Cookie settings" in the footer of openevent.io. The banner re-opens and you can switch any opt-in category on or off.
- Clear your browser cookies for openevent.io. The next time you visit, the banner will appear again and you can start fresh.
- Use your browser's privacy controls.Every modern browser lets you block third-party cookies, send "Do Not Track" signals, or use private/incognito mode. Some of these will reduce site functionality.
To opt out of advertising on the platforms themselves, use each platform's controls:
- Meta: accountscenter.facebook.com → Ad preferences
- TikTok: in-app settings → Privacy → Ads
- LinkedIn: linkedin.com/psettings/advertising
- Google Analytics: Google Analytics Opt-out Browser Add-on
How long we keep cookie-consent records
When you accept or reject categories, we store your choice for 12 months in the oe_cookie_consent cookie. We also keep a server-side log of consent events (timestamp, choices, banner version) for 24 months to demonstrate compliance under GDPR / revFADP accountability requirements.
Changes to this policy
If we add a new sub-processor that sets cookies, or change the categories or the consent mechanism, we will update this page and the version number at the top. For material changes, we will also re-show the cookie banner so you can review your choices.
Contact
Questions about this cookie policy: info@openevent.io.
The full Privacy Policy is at /privacy. The Legal Notice (Imprint) is at /imprint.