Cookies and browser storage

Last updated

10 September 2026

Technical cookies

The Pilot form uses two first-party technical cookies. They support secure submission and confirmation of the requested service. No analytics, advertising cookies, tracking pixels, embedded social feeds, remote fonts or profiling tools are included. A profiling-consent banner is therefore not used for this configuration.

pilot_session

Set when you open the Pilot form. It contains a random session identifier that binds the security token to your browser. It is host-only, Path=/, HttpOnly and SameSite=Strict, with a maximum age of one hour from setting. A fresh form may renew the cookie lifetime; that does not renew enquiry retention.

pilot_receipt

Set after durable receipt of an enquiry. It contains a signed receipt with opaque identifiers, language and expiry, not the submitted contact fields. It allows confirmation after redirect. It is host-only, Path=/, HttpOnly and SameSite=Strict, with a maximum age of one hour from setting. A repeated submission can reissue the cookie without extending the enquiry’s retention period.

Browser storage and choices

The HTTPS collection profile adds Secure to both cookies. The site does not use localStorage, sessionStorage, IndexedDB, service workers or a browser analytics identifier. Responses request no-store caching. Browser history and network connection processing still exist. You can remove or block cookies in browser settings; blocking these technical cookies prevents secure form submission or confirmation. Any future non-essential technology requires its own prior assessment and consent controls.