This Cookie Policy explains which cookies and similar technologies (browser storage, embedded third-party content) the Eve Platform uses, why we use them, and how you can control them. Last updated: 19 September 2026.
1. Summary
Eve uses only strictly necessary cookies and browser storage. We do not use advertising cookies, tracking pixels, social-media trackers or third-party analytics. Embedded content from Google Maps and YouTube on event pages is loaded only after you choose to load it; the two smaller Google requests we make without asking — the sign-in button on sign-in pages and a cookieless video still on event listings — are described in Section 4.
2. Strictly necessary cookies
- __Secure-Eve_browser_session — keeps you signed in across Eve pages. Set only after you sign in; HttpOnly and Secure; expires after 7 days, or up to 30 days if your session allows it. Set by Eve.
- __stripe_mid and __stripe_sid — set by Stripe when the payment form loads at checkout, to detect fraud and complete your payment. __stripe_mid lasts one year, __stripe_sid 30 minutes. Governed by Stripe’s privacy policy.
- g_state — set on our domain by Google’s sign-in script, on the pages that show the Google button (sign in, organizer sign-up, your account, and the identity step of checkout and registration). It remembers whether you dismissed Google’s sign-in prompt and lasts about six months. Governed by Google’s privacy policy; you can delete it in your browser at any time.
We treat these cookies as strictly necessary: the sign-in cookie is what keeps you signed in, and the Stripe cookies are set by our payment processor solely to detect fraud on the payment you asked us to take. Strictly necessary cookies do not need your consent under the EU ePrivacy rules, the GDPR or the Israeli Protection of Privacy Law. Blocking them will prevent sign-in and payment.
3. Browser storage (not cookies)
Some things are saved in your browser’s storage rather than in a cookie. Most of them never leave your device; the three that are sent to Eve — the sign-in tokens, the seat-hold identifier and the door-scanner device identifier — are noted as such, and are sent only to serve your own requests. Items marked “session storage” disappear when you close the tab.
- eve_language — the language you chose.
- Eve_theme — light or dark mode.
- Eve_organizer_token — the sign-in session for organizer, promoter and admin dashboards.
- Eve_last_email and Eve_last_brand — the email you last signed in with and the last organization you worked in, so the sign-in form can be pre-filled on this device.
- Eve_sidebar_collapsed and Eve.recentSearches — dashboard layout and your recent searches.
- Accessibility widget preferences — text size, contrast and motion settings you chose with the accessibility button.
- eve_geo_country — the country we inferred from your connection when you first arrived, kept so later visits open in the right language without another lookup.
- Eve_embed_consent — whether you agreed to load Google Maps or YouTube content (Section 4).
- Checkout verification (session storage) — the email address you verified for the current checkout and a short-lived verification token, so you are not asked for a new code on every step.
- Eve_public_checkout:<event> and Eve_checkout_attempt:<event> (session storage) — the tickets you selected and a one-time key for the order you are in the middle of, so a refresh does not lose your place or charge you twice.
- Eve_seatpick_session — a random identifier for this browser, created when you first hold a seat and sent to Eve with seat requests so the seats you are holding survive a refresh. It identifies the hold, not you.
- eve_event_country_v1 and eve_public_language_override — the country and language you chose while browsing events, so the next page opens the way you left it.
- eve_api_cache_v1 (session storage) — a short-lived copy of the last public settings and event responses, so pages open faster.
- eve.terms.accepted.<version> — a note that you already accepted the current Terms on this device, so you are not asked again.
- Eve_invite_token_<event> — an invitation link you opened, kept so the private event stays reachable on this device.
- Eve_help_chat_state_v3 — whether the Help Center chat is open and your place in the conversation.
- Eve_checkin_device_id — for door staff only: an identifier for the scanning device, sent to Eve with each scan so a lost or misused device can be cut off.
- Identity-verification draft (session storage) — for organizers only: the fields read from a document you are submitting, until you finish or leave the page.
4. Third-party content you choose to load
Event pages may include a venue map from Google Maps and videos from YouTube. Because these load content from Google’s servers — which may set Google cookies and receive your IP address — we show a placeholder first and load the content only when you click “Load”. Your choice is remembered in browser storage on this device so you are not asked on every page; you can reset it with the button below or by clearing your site data. Once loaded, Google’s use of data is governed by Google’s privacy policy.
Wherever we offer “Sign in with Google” — the sign-in page, organizer registration, the identity step of checkout and the buyer account page — displaying Google’s sign-in button loads a script from Google, which may set Google cookies on that page. It is not loaded anywhere else. Event listings may also show a still image of a YouTube-hosted cover video; that image is fetched from Google’s cookieless image server (i.ytimg.com), which receives your IP address like any image request but sets no cookies.
5. Analytics and advertising
Two further requests leave your browser without asking: Google’s sign-in script also loads a font from fonts.gstatic.com, and an organizer may host an event’s cover or gallery image on its own or a stock-image provider’s server, which then sees your IP address. We currently run no analytics, measurement or advertising trackers on the Platform. If we introduce any technology that is not strictly necessary, we will ask for your consent first where the law requires it and update this policy before it goes live.
6. Do we need your consent?
No consent banner is shown because we set no optional cookies of our own. The only cookie we do not set ourselves is g_state, written by Google’s sign-in script on the pages described in Section 2; it carries no advertising or cross-site tracking function. Consent is requested in place before Google Maps or YouTube content is embedded. The Google sign-in button and the cookieless video still described in Section 4 are loaded without asking, because the first is the sign-in method you came to use and the second sets no cookies. Because we do not track you across sites, browser signals such as Do Not Track or Global Privacy Control need no further action from us.
7. Controlling cookies in your browser
You can delete or block cookies and site data in your browser settings at any time. If you block the strictly necessary cookies you will not be able to sign in or pay.
8. More information
How we handle personal information more generally is described in our Privacy Policy. Questions: support@goeve.io.
Legal entity and privacy contact
Legal entity: Eve Technologies Ltd., Tel Aviv, Israel.
Legal domain: goeve.io. Legal email: support@goeve.io. Support email: support@goeve.io. Contact email: support@goeve.io. Security email: support@goeve.io.