See which cookies Bevy sets, which cookies third-party services set, and what the built-in consent banner does not cover.
What the built-in banner covers
Bevy has two built-in banners. Neither one is a full cookie-management platform.
Enable the Bevy cookie consent acknowledgement banner shows one button. Choosing it stores cookie_consent_is_true. There is no Decline choice and no category list. The banner does not stop third-party cookies on its own.
Enable enhanced cookie consent management shows Accept, Decline, and Manage Cookies. Manage Cookies lists Essential, Analytics, Social, and Advertising. Essential stays on. Decline turns Analytics, Social, and Advertising off and stores that choice in cookie-consent. Essential cookies, including sessionid and csrftoken, still run.
Important: These banners record a choice. They do not scan the site for every cookie, assign a legal category to each vendor, or block each third-party cookie. For that, use a dedicated cookie tool such as OneTrust, Osano, Fides, or TrustArc. A dedicated tool, and any script added in Google Tag Manager, can set cookies this page does not list.
Banner wording, the button label, and the privacy link are in Privacy settings.
Cookies set by Bevy
| Cookie | How long it lasts | Purpose |
|---|---|---|
csrftoken |
One year | Protects form submissions. The page can read it so a form can send the token. |
sessionid |
30 days | Keeps someone signed in. Closing the browser does not clear it. |
cookie_consent_is_true |
99,999 days | Records that the visitor chose the acknowledgement button. Present only when Enable the Bevy cookie consent acknowledgement banner is on. |
correlation_key |
Until the browser session ends | Set on event pages and sponsor invoice pages. Connects that visit to error reports and to ticket checkout. |
cookie-consent |
365 days | Stores Analytics, Social, and Advertising choices. Present only when Enable enhanced cookie consent management is on. |
Cookies set by third-party services
A service loads only when that part of the community uses it. Google Analytics loads when a measurement ID is set. Stripe loads on paid checkout. Daily loads in a Bevy Virtual room. Mux Data loads on video playback when it is turned on for that video or conference.
| Cookie | Where | Purpose | Vendor |
|---|---|---|---|
_ga_gid_ga_<id>_gac_gb_<id> |
Pages that load Google Analytics | Tell repeat visits apart and keep session state. | Google Analytics |
muxData |
Video playback, and virtual conference pages when Mux Data is on | Video quality and playback analytics. | Mux |
__stripe_sid |
Event checkout and invoice pages | Payment and fraud checks for that checkout session. | Stripe |
__Host-audio-input__Host-audio-output__Host-video-input
|
Bevy Virtual event pages | Remember the microphone, speaker, and camera the person picked. | Daily |
Note: Google Tag Manager can add scripts Bevy does not list. Those scripts can set their own cookies.
Google Analytics
Two Google Analytics 4 properties can load on the same pages.
- Bevy's measurement ID lets Bevy see aggregate activity across communities. Admin and chapter Website analytics use that Bevy data. See About website analytics.
- Google Analytics 4 Measurement ID, when you add one, sends page data to your Google Analytics property. It does not replace the Website tab. See Google Analytics, Google Tag Manager, and UTM.