Cookie Policy

This policy explains the cookies and browser storage WAIRLE uses. Some are strictly necessary and always on. Two analytics tools, the Meta Pixel and Contentsquare, are not necessary to provide the service: they load only if you select ACCEPT in the cookie banner. The film on our homepage may play in another provider's video player, described below.

Your choice

The first time you visit, a banner asks whether you accept analytics cookies. Until you choose, and if you select REJECT, neither the Meta Pixel nor Contentsquare loads and none of their cookies are set. REJECT is as easy as ACCEPT, and the rest of WAIRLE works the same either way.

You can change your mind at any time with the Cookie settings control in the footer, or the one at the end of this policy, which also works with JavaScript switched off. If you withdraw consent, both tools stop at once, in any other WAIRLE tab or window open in the same browser too, and their cookies are deleted from your browser, except _cs_optout, which Contentsquare sets to record that you opted out. Withdrawing does not undo anything collected while you had accepted.

Strictly necessary

To operate the service WAIRLE sets strictly necessary cookies that keep you signed in (your authenticated session) and protect form submissions, and one functional cookie that remembers the display theme you chose in System Configuration. It also sets these:

• wairle_consent: remembers your answer to the cookie banner for six months, so that you are not asked on every page. It records your choice and nothing that identifies you. When it expires, or if you clear it, the banner asks again.
• pending_verification_email: set when you sign up, or when you log in before confirming your email address. It holds that address for 30 minutes so that the confirmation page can show it without putting it in the page address. It is sent only to that page, and no script on the page can read it.
• wairle_unsub: set only when you follow the unsubscribe link in one of our emails. It holds that email's unsubscribe reference for one hour so that the reference never appears in a page address. It is sent only to the unsubscribe page, and no script on the page can read it.

Because the cookies in this section are essential to providing the service you have requested, they do not require separate consent, but you can clear them at any time through your browser — note that doing so will sign you out and bring back the cookie banner. Payment pages are hosted by Stripe on its own domain under its own cookie policy.

Browser storage

Some screens keep small items in your browser's storage on this device only. In local storage, the Library's prompt builders and the Fitness and Fuel Programmers keep an unsent draft, and the guided tours remember which ones you have seen. The homepage access-link window (shown on phones) also keeps one item there, wairle:access-popup: whether you asked for a link or closed the window, with the time you closed it, so that it stays away for seven days after you close it and for good once you have asked for a link. It stores that choice only, never your email address or anything else that identifies you. A timed test keeps your answers in progress, and the diagnostic screens a dismissed device advisory, only until you close the tab. Nothing in them is sent to us until you choose to act.

Homepage video

The film on our homepage plays in Vimeo's video player, or in YouTube's if we host the film there instead. The player is how the film is shown, not an analytics tool, so it loads whatever you choose in the cookie banner, and when it loads the provider receives your IP address and basic details of your browser. We load Vimeo's player with its do-not-track setting, which Vimeo says prevents the player from tracking your session, cookies included. We load YouTube's player from youtube-nocookie.com, its privacy-enhanced mode, which YouTube says does not use cookies that track what you watch; if you play a film there, YouTube may still store data in your browser under its own cookie policy. When we serve the film from our own server instead, no other provider is involved.

Analytics cookies (only if you accept)

Meta Pixel. An advertising measurement tool provided by Meta. If you accept, it loads on each page you view, except our staff administration pages, tells Meta that the page was viewed, and sets an identifier cookie (_fbp) so that visits can be attributed to our advertising. That cookie is set on the wairle.com domain itself, not by facebook.com. Unlike the cookies above, it is not necessary to provide the service.

Contentsquare. A behaviour analytics tool from the company behind Hotjar. If you accept, it records how pages are used — the pages you view, clicks, scrolls and mouse or touch movements — as session recordings and heatmaps, so that we can see where the site confuses people or breaks. Personal and health information shown in the Laboratory is masked in your browser, nothing you type into a form field is recorded, and it does not run on our staff administration pages, while you are taking an assessment, or on the Fitness and Fuel Programmer pages. Its cookies are also set on the wairle.com domain.

The analytics cookies are listed below. Contentsquare also writes a few test cookies to check what your browser supports, and removes them at once.

• _fbp: Meta Pixel. A random identifier that lets Meta attribute visits to our advertising. 90 days, renewed on each visit.
• _fbc: Meta Pixel. Set only when you arrive from a link in a Meta ad, to record that click. 90 days.
• _cs_id: Contentsquare. A random identifier that links your visits to this site. 13 months.
• _cs_s: Contentsquare. The current session, such as how many pages you have viewed. 30 minutes, renewed while you use the site.
• _cs_c: Contentsquare. Whether recordings of your visit must be fully masked. 13 months.
• _cs_cvars: Contentsquare. Details of the current session. Deleted when the session ends.
• _cs_optout: Contentsquare. Set only if you withdraw consent, so that Contentsquare stays off. 13 months.

You can also block the two tools in your browser: most content blockers and tracking-protection lists block connect.facebook.net and t.contentsquare.net, which is where they load from. You can change how Meta uses what it receives in your Facebook or Instagram ad settings. What each tool receives, and what is kept from it, is set out in the Privacy Policy.