Operated by NOMI VENTURES LIMITED
Cookie Policy
Approved for publication · Effective 24 July 2026
Arrival Shows Cookie Policy
Status: Approved for publication by NOMI VENTURES LIMITED Version: 1.1 Effective date: 24 July 2026 Last updated: 25 July 2026
1. About storage and access technologies
Cookies are small text files placed on a device. Websites can also use local storage, pixels, SDKs, scripts, and similar technologies to store information on or access information from a device. This policy calls all of them “technologies”.
NOMI VENTURES LIMITED operates Arrival Shows and is responsible for the choices described here. Contact curator@arrivalshows.uk with questions.
2. How we use them
Strictly necessary
These technologies are essential to provide a service you request or transmit a communication. They may secure forms and personal links, maintain checkout or submission state, balance traffic, prevent fraud, record a privacy choice, and protect the site. They cannot be switched off through our consent control where the legal exception applies, although you can block them in your browser and some parts of the service may then stop working.
Preferences
These remember optional choices, such as interface preferences. Where the law requires permission, they remain off until you choose them.
Analytics
Arrival Shows does not use analytics cookies, pixels, browser storage, or third-party analytics scripts. The server keeps aggregate hourly counts of successful public page requests without storing an analytics identifier or placing information on the visitor's device. If optional analytics technology is introduced later, it will remain off until any legally required permission is obtained, with rejection as easy as acceptance and a continuing withdrawal route.
Payment and embedded services
A secure payment provider may set technologies on its own checkout to process payment, prevent fraud, and secure the transaction. Optional embedded media or social features must not load non-essential tracking before permission.
3. Production technology register
This register reflects the technologies used or planned for the current service. We review it when the production service, providers, or purposes change.
| Technology/provider | Purpose | Category | First/third party | Duration | Set before permission? |
|---|---|---|---|---|---|
arrival_submission_session | Maintain the protected submission session after a personal link is redeemed | Strictly necessary | First | Maximum 12 hours; expires after 60 minutes of inactivity server-side | Yes, only after link redemption |
| Account-free magic-link record | Server-side token record used to issue and redeem a requested secure link; not stored on the visitor’s device by Arrival Shows | Not a device-storage technology | First | Submission link: 24 hours; recovery link: 30 minutes; preview link: correction deadline | No device storage |
| Stripe Checkout technologies | Secure hosted payment, fraud prevention, and transaction protection | Strictly necessary where the applicable exception is met | Third | Controlled by Stripe and described in its current policies | On Stripe checkout |
| Aggregate server-side page counts | Count successful public page requests by hour and path without an analytics identifier or device storage | Not a device-storage technology | First | Maximum 13 months | No device storage |
| Optional analytics technologies | Not used | Not applicable | Not applicable | Not applicable | No |
| Client-side error-monitoring technologies | Not used at launch | Not applicable | Not applicable | Not applicable | No |
No technology may be labelled strictly necessary merely because it is convenient, improves analytics, or supports a business preference.
4. Your choices
Because the site does not use optional analytics or other non-essential device technologies, it does not display a consent banner merely for strictly necessary operation or aggregate server-side request counting. If optional technologies are introduced, the consent control must offer:
- Accept optional technologies
- Reject optional technologies
- Choose settings
The site must add a persistent Cookie settings route at the same time as any optional technology requiring permission. Withdrawal will apply from that point forward and remove or disable optional technologies where technically possible.
Browser controls can also block or delete technologies, but blocking strictly necessary functions may prevent checkout, submissions, previews, or secure links from working.
5. Legal basis and personal information
Where a technology stores or accesses information on a device, we follow applicable UK electronic-communications rules. Where the resulting information is personal information, the Privacy Policy explains the lawful basis, recipients, transfers, retention, and rights.
Consent for a technology and a UK GDPR lawful basis are related but distinct assessments. The production consent record must include the notice version, choice, time, and a way to withdraw.
6. Changes
We update this policy and the register when technologies, providers, purposes, or law change. The date and version above identify the current policy.