Cookies and storage
Last updated 14 October 2026
We only use cookies and browser storage that are strictly necessary. On event sites, in the organiser admin and in the hub, they keep you signed in, remember a booking you’re part way through, and let payment providers check for fraud. On eventdrake.net, our own website, the only item remembers the currency you chose on the pricing page.
None of it is used for advertising or to track you across other sites, so we don’t show a consent banner.
Browser storage comes in two kinds. Local storage stays in your browser until it is removed or you clear it. Session storage is cleared when you close the tab.
1. eventdrake.net
1.1 Our website sets no cookies. Its fonts are served from our own site.
| Name | Type | Set by | Purpose | How long |
|---|---|---|---|---|
ed.currency |
Local storage | EventDrake | Remembers the currency you chose on the pricing page | Until you clear it |
1.2 We don’t run analytics on the website yet. When we do, we will use a cookieless service that doesn’t identify individual visitors.
2. Event sites and the organiser admin
2.1 These items are used on the event sites attendees book through and in the admin that organisers use.
| Name | Type | Set by | Purpose | How long |
|---|---|---|---|---|
| Login tokens | Local storage | EventDrake | Keep you signed in to your account or the admin | Until you sign out or clear them |
ed_edge_pass |
Cookie | EventDrake | Lets you into an event site that the organiser has made private, once you have signed in | 7 days, or until you sign out |
ed_edge_pass_exp |
Local storage | EventDrake | Records when ed_edge_pass expires, so the site knows when to renew it |
Until you sign out |
reg- and the event ID |
Session storage | EventDrake | Holds your booking while you go through checkout, so a page refresh doesn’t lose it | Until you close the tab |
admin-display-timezone |
Local storage | EventDrake | Remembers the timezone an admin chose for displaying dates and times in the admin | Until you clear it |
__stripe_mid |
Cookie | Stripe | Fraud prevention on payment pages: helps Stripe assess the risk of a payment | 1 year |
__stripe_sid |
Cookie | Stripe | Fraud prevention on payment pages: helps Stripe assess the risk of a payment | 30 minutes |
| Bot check | Cookies and storage | hCaptcha | Checks that a person, and not an automated script, is completing checkout or a contact form | Set by hCaptcha |
2.2 We use New Relic to monitor errors and performance on event sites and in the admin. New Relic sets no cookies.
2.3 Organisers can add their own content to their event site, such as an embedded video from YouTube. Anything an organiser adds may set its own cookies. That content is the organiser’s responsibility, including any consent it needs.
3. The EventDrake hub
3.1 The hub is where customers manage their EventDrake account.
| Name | Type | Set by | Purpose | How long |
|---|---|---|---|---|
| Sign-in session | Session storage | EventDrake | Keeps you signed in to the hub | Until you close the tab |
hub.active_customer |
Local storage | EventDrake | Remembers which customer account you are working in | Until you clear it |
| Sign-in cookies | Cookie | The hub’s sign-in page | Keep track of your sign-in while you log in to the hub | Set by the sign-in page |
4. Changes to this page
4.1 We update this page when the cookies and storage items we use change, and record each change in the version history below. Questions about this page can go to EventDrake Limited at hello@eventdrake.net.
Version history
- : First published.