Notice

Cookie Policy

Last updated: 5 August 2026

This website uses only technical cookies necessary for the pages to function: we do not use analytics, marketing or profiling cookies. Some pages do, however, load resources served by third parties — the payment field, the anti-spam protection of the contact form — and those resources see your IP address. Below you will find both: the cookies and the third parties, with the exact moment each comes into play.

What cookies are

Cookies are small text files that websites save on your device to store information between visits. They can be set by the controller (first-party cookies) or by third parties.

Types of cookies used

Technical and necessary cookies: they ensure the website functions (session, security, language preference) and do not require consent. They are listed in the table below.
Analytics cookies: not currently used. Should they be introduced in the future, they will be enabled only subject to your consent through a dedicated banner.
Marketing/profiling cookies: not used. The website sets no third-party advertising profiling cookies. Google reCAPTCHA is active on the Contact page only: to tell humans from bots it analyses your interaction with the page and may set Google technical security cookies. It is an anti-spam safeguard, it is not used to profile you for advertising, and it relies on our legitimate interest in protecting the form (Art. 6.1.f GDPR). Stripe cookies are technical too: they recognise the device to prevent fraud during payment, they do not profile you.

List of cookies

The website uses only the technical and necessary cookies listed below. Stripe cookies are set as soon as you open the tickets page or the order confirmation page — that is where the payment field is loaded, so it happens before you even decide to pay, not just at the moment of payment; Google reCAPTCHA cookies only on the Contact page.

Name	Provider	Purpose	Duration
`the-injection-show-session`	injectionshow.com (first party)	Keeps the user session and their preferences (e.g. language). If you arrived from a speaker's QR code or from a link in one of our newsletters, it holds that reference: the speaker until you sign in (after which it is written to your account and no longer expires, see the Privacy Policy), the campaign until you complete the order (after which it is written on the order), and in the same way the site or campaign you first arrived from.	Session (max 120 min)
`XSRF-TOKEN`	injectionshow.com (first party)	Security protection against CSRF attacks in forms.	Session (max 120 min)
`tis_preview`	injectionshow.com (first party)	Grants access to the site preview in Coming Soon mode (only for those using the reserved link).	90 days
`_GRECAPTCHA`	Google (third party)	Anti-spam protection of the contact form (reCAPTCHA): tells humans from bots. Set only on the Contact page.	6 months
`__stripe_mid, __stripe_sid`	Stripe (third party)	Fraud prevention during payment. Set when the tickets page and the order confirmation page open, where the payment field is loaded.	__stripe_mid: 1 year · __stripe_sid: 30 min

Resources loaded from third parties

Some pages load code or images served by other companies. When that happens, the company sees your IP address, the browser you are using and the page you are on: it is unavoidable, because it is your browser that asks them for the file. Here is the full list, with the moment the call actually goes out.

Who	When	What they receive	Why
Stripe (js.stripe.com)	When the tickets page and the order confirmation page open, before you choose to pay.	IP address, browser, the page you are on and the technical signals its fraud prevention collects about how the page is used.	The card field is drawn by Stripe inside our page and is not an image: for it to exist when you reach the payment step, it has to be loaded earlier. Fraud prevention, for the same reason, watches the session from the start.
Google reCAPTCHA	When the Contact page — and only that page — opens.	IP address, browser and the way you interact with the page.	Telling people from bots and keeping spam out of the contact form.
Venue and contact maps	Never on their own when the page opens.	When the page opens you see a panel of ours with the address and a preview we drew ourselves: no outside company knows you are there. The real map loads only if you ask for it with a click, and the panel warns you first that at that moment your IP address will reach OpenStreetMap and CARTO.	Showing you where the event is held without firing off a call to a third party the moment you open the page.
Address and postcode lookup during purchase (OpenStreetMap/Nominatim, api.zippopotam.us)	When you type an address or a postcode in the order form.	Only the text you typed, forwarded by our server: the supplier receives neither your IP address nor your browser cookies.	Suggesting your address and filling in town and province from the postcode, so you make fewer mistakes on the invoice details.

Local storage in your browser

Besides cookies, the website saves some information in your browser's local storage (localStorage and sessionStorage). These are not cookies and they stay on your device. One of them is an exception, and it is only fair to say so: the data of the checkout in progress stays on your device while you fill it in, but the moment you complete the order it is sent to our server together with the order — including the dietary needs, which end up on the ticket (see the Privacy Policy). You can delete everything at any time by clearing the site data in your browser settings.

Name	Type	Purpose	Duration
`tis_cart`	localStorage	Keeps the contents of your cart while you choose your passes, so you do not lose them when changing page.	Until you clear the site data
`tis_checkout_v2`	localStorage	Keeps the data of the checkout in progress — including the name, email and any dietary needs of the participants you are registering — so you do not have to fill it in again if you reload the page. When you complete the order this data is sent to our server and the entry is cleared from the browser.	Until the order is completed
`tis_cookie_notice_v1`	localStorage	Remembers that you already dismissed the cookie notice, so it is not shown on every visit.	Until you clear the site data
`tis_preloaded`	sessionStorage	Avoids re-loading resources already preloaded during the same visit.	When the tab is closed

How to manage cookies

Technical cookies are necessary and cannot be disabled through a banner, but you can block or delete them at any time from your browser settings (disabling them may impair the functioning of some parts of the website). Since we do not use analytics or profiling cookies, no consent is required; should we introduce such cookies in the future, we will show you a dedicated banner to manage consent. The website fonts are served locally. The only resources loaded from third parties are the ones listed in the "Resources loaded from third parties" section: Stripe on the tickets and order confirmation pages, Google reCAPTCHA on the Contact page alone.

Duration

Session cookies are deleted when the browser is closed or when the session expires; persistent cookies have the duration indicated in the table and in any case no longer than the periods provided by law.

Contact

For information about the use of cookies write to info@injectionshow.com. For the processing of personal data, see our Privacy Policy.