Cookies and tracking preferences
Updated 30 September 2026. Optional analytics and advertising are off until you choose to allow them. You can use Ticketflex and buy tickets without accepting either category.
Your choices
Open cookie settings to accept, reject or withdraw permission. Analytics and advertisement are separate choices. Rejecting advertising does not prevent a purchase or subscribe you to emails. Email marketing choices are separate.
When our tracking purposes change, we ask you to choose again. Withdrawal stops future optional tracking. It cannot recall information already sent. If you are offline, an advertising withdrawal is saved on this browser and retried when it reconnects; a server-confirmed purchase could be processed before that update arrives.
What we use
| Purpose | Storage and information | Duration |
|---|---|---|
| Necessary | CookieYes remembers your choices in cookieyes-consent. Ticketflex uses tflx.consent.* in local storage for the notice version, advertising permission reference and pending withdrawals. These references are used to enforce your choice, not to profile you. Basket, login and security storage support services you request. | CookieYes: up to one year. Advertising permission reference: up to 24 hours; pending withdrawal: up to 48 hours. Notice version: until replaced or browser storage is cleared. Basket/login duration depends on the service. |
| Analytics: Ticketflex | With analytics permission, tflx.analytics.* local storage holds event visit identifiers and a delivery queue. We count page views, ticket additions and checkout starts, and link consented visits to confirmed orders to report conversion statistics. We do not add customer names, email or phone to these browser events. | Visit expires after 30 minutes of inactivity; queue expires after 24 hours. Server visit and checkout links: up to 91 days. Delivery receipts and withdrawal markers: seven days. Expired browser entries are removed on subsequent use. Aggregate totals are retained. |
| Analytics: Microsoft Clarity | On pages where enabled, Clarity loads after analytics permission to help us understand page interaction and improve usability, including heatmaps and session replay. Clarity uses _clck and _clsk. We send its advertising permission signal separately. See Microsoft's privacy statement. | _clck: up to one year; _clsk: up to one day. Provider retention varies by data type and project settings. Withdrawal stops the page's recording; a new recording after reacceptance begins on a later page load. |
| Advertising: Meta | Where an organiser enables Meta, advertisement permission allows its pixel and purchase matching. Purchase details may include value, order reference and event page address, plus SHA-256 hashed email and phone to match customers on Meta. Hashing is not anonymisation. _fbp and _fbc may be used by Meta. See Meta's privacy policy. | Meta browser cookies: generally up to three months. Our server advertising permission expires after 24 hours; permission/withdrawal evidence and its basket link are retained for up to one year. Meta's retention is governed by its policy. |
| Advertising: attribution | With advertisement permission, tflx-mkt-* cookies and marketing-attribution-* local storage hold campaign parameters, referral and landing-page details for order attribution. Optional referral measurement is disabled without that permission. | Up to seven days, removed on withdrawal. Attributed order records may remain under the order retention policy. |
Orders and security
We keep operational order counts and values independently of optional analytics. Confirming your purchase is not permission to send it to an advertising platform. Security rate limits use rotating keyed IP hashes rather than storing raw IP addresses in the event analytics tables; these rate-limit records expire after 48 hours. Other security logs are covered by our privacy policy.
Contact [email protected] about these practices or your data rights. Your organiser's privacy notice also applies to its use of customer data. CookieYes's automated inventory may be supplemented by the information above, including local storage that is not a cookie.