Cookie Policy
This policy explains the cookies and similar browser storage used by the eTickets public, portal, API, and docs surfaces.
Our cookie position
eTickets does not use any advertising, remarketing, analytics, or tracking cookies on any of its sites. The public eTickets website uses only strictly necessary browser storage, such as holding an in-progress checkout. The logged-in promoter portal additionally stores a small number of first-party functional items that remember your preferences and in-progress work — for example your sidebar layout and a draft of an event you are creating — as part of the portal service you sign in to use. These are listed in the table below.
Because we use no tracking, advertising, or analytics technologies, we do not operate a cookie-consent banner. We keep this under review and will update this policy and provide a consent mechanism before introducing any non-essential cookies, such as analytics, in future.
First-party cookies and storage
| Name or technology | Where used | Purpose | Type |
|---|---|---|---|
__Host-etickets_session in production, etickets_session in development | Promoter portal | HttpOnly server-side portal session. Used to keep a logged-in portal user authenticated and scoped to the correct organisation or platform-admin role. | Strictly necessary |
etickets_csrf | Promoter portal | Readable CSRF token cookie sent back in the X-CSRF-Token header on state-changing portal requests. | Strictly necessary security |
sessionStorage: etickets.public.checkoutDraft.v1 | Public checkout | Stores in-progress ticket selections and checkout contact/guest details in the browser for the current tab/session until checkout is completed or cleared. | Strictly necessary checkout continuity |
localStorage: sidebar-collapsed | Promoter portal | Remembers which portal sidebar groups the user collapsed. | Functional preference |
localStorage: authReturnPath | Promoter portal | Temporarily remembers the route a user was trying to access before login/session expiry. | Strictly necessary navigation |
localStorage: eventWizardProgress:user:<id> | Promoter portal | Saves an in-progress event the promoter is creating (the event-wizard form data and current step) so work is not lost if the page is reloaded. Cleared when the event is created or the wizard is reset. | Functional event-draft continuity |
Legacy authToken and userInfo cleanup | Promoter portal | The portal removes old local-storage authentication keys and does not use them for active login. | Legacy cleanup |
Third-party services
| Provider | Where used | Purpose |
|---|---|---|
| PayPal | Paid checkout, PayPal card fields, Apple Pay, Google Pay through PayPal, refunds, and promoter onboarding. | PayPal may set cookies or use device/browser data for payment processing, fraud prevention, authentication, and compliance under PayPal's own policies. |
| Cloudflare Turnstile | Promoter enquiry form and ticket-link resend form. | Anti-bot checks. Cloudflare may process technical data needed to verify that a request is legitimate. |
| Google Wallet | Optional "Save to Google Wallet" ticket feature. | Creates or updates wallet pass objects when the buyer requests a wallet pass. Google may process data under its own policies. |
| Apple Pay / Google Pay | Optional wallet payment methods where enabled and eligible. | Payment authorisation through PayPal SDK integrations. eTickets does not store full card numbers. |
Analytics and advertising
We do not use advertising or remarketing cookies, and no analytics is currently enabled. If we introduce a privacy-friendly analytics tool in future, we will update this policy and review any consent requirements before enabling it.
Managing storage
You can delete cookies and site storage through your browser settings. Deleting portal cookies will log you out. Deleting checkout session storage may clear an in-progress order draft.
Any future non-essential cookie consent will be handled separately for each subdomain (www, portal, and docs).
Changes to this policy
We may update this policy if the cookies or storage we use change. The version number and "last updated" date at the top of the page show the current version.