This article describes the different types of cookies used on your Bevy community site. Cookies are set by Bevy and by third-party services.
Cookies set by Bevy
The table below lists the different cookies set by Bevy and their purpose.
| Cookie | Purpose |
|---|---|
| csrftoken | Bevy core functionality – Security |
| cookie_consent_is_true | Bevy core functionality – Tracking user consent Only used when you have the Bevy cookie consent acknowledgement banner enabled (learn more in Privacy settings) |
| correlation_key | Bevy core functionality Error tracking |
| sessionid | Bevy core functionality |
All the cookies are browser session cookies, except per "cookie_consent_is_true" which has 9999 days TTL.
Cookies set by third-party services
There are different third-party services integrated with the Bevy platform. These services can set cookies for their functionality. For example, Google Analytics is an integration that tracks page views or Stripe is a service integrated for purchasing tickets.
The tables below show different cookies, where they're used, and their purpose:
| Cookie | Pages | Purpose Vendor | Vendor |
| _ga, _gid, _ga_<container-id>, _gac_gb_<container-id> | All pages on the platform | Distinguish users and persist session state | Google Analytics |
| muxData | Virtual conference pages | Conference video streaming | Mux |
| opentok-network-test | Virtual conference network test page | OpenTok stores a UUID in a cookie to record session-related data debugging and analytics | Vonage |
| __stripe_sid | Event page | Payment processing for events | Stripe |
Note: There may be cookies added by third-party scripts if a client adds them through Google Tag Manager which we are unable to track.
Google Analytics trackers
Bevy uses two trackers:
-
BevyGlobal—allows Bevy to see aggregate interactions with Bevy platform sites across clients.
-
It allows Bevy to provide website analytics for our customers. This data displays in the admin and chapter analytics dashboards.