Legal
Cookie policy
The short version: the pages you can browse set no cookies. The exceptions are a sign-in cookie on the team's own editorial admin, which never touches a visitor, one that remembers you filled in a request form (the media kit, the 2026 RAISE Gala film), and the payment step of the checkout, where Stripe sets the cookies it needs to take a payment safely. Visit counting runs only if you say yes, and even then it sets no cookie. Here is exactly what is stored, and what the site loads from elsewhere.
Laatst bijgewerkt op 18 November 2026
What we set today
On every public page, until you fill in a request form: nothing. There are no analytics cookies, no advertising cookies, and nothing that follows you across other sites. You can check with your browser's developer tools, and we would rather you did. The payment step of the checkout is the one place a third party sets cookies, described below.
The single exception lives behind a password at /admin, the private page where the team writes the news section. Signing in there sets one strictly functional session cookie so the editor stays signed in. It is scoped to the admin area, holds a signed token rather than any personal data, and is never set by anything a visitor can reach.
- Name
- raise-admin-session
- Type
- HttpOnly cookie, first party, /admin only
- Set when
- A team member signs into the news admin
- Expires
- After 12 hours, or on sign-out
Two pages open something only to people who ask for it: the media kit, at /media-kit, and the film of the 2026 RAISE Gala. Sending one of their forms sets one strictly functional cookie, so the page can show you what you asked for without asking again. It holds no personal data, only the fact that the form was sent; your details go with the request itself, as the privacy policy describes. Neither page loads anything from a third party: the media kit's scripts and fonts are served from this site.
- Names
- raise_media_kit, raise_gala_film
- Type
- HttpOnly cookie, first party
- Set when
- You send the media kit form or the VIP Dinner film form
- Expires
- After 30 days, or by clearing site data
The one thing stored on your device is the answer you give the consent banner, and only after you answer it. It is a single entry in your browser's local storage, not a cookie, it never leaves your device, and it exists so that we stop asking.
- Name
- raise-cookie-consent
- Type
- Local storage, first party
- Holds
- Your choice, and the date you made it
- Cleared
- By choosing again from the footer, or by clearing site data
Counting visits, only with your yes
If you accept in the consent banner, the site loads Vercel Web Analytics, from Vercel, the company that hosts it. It tells us which pages are read and where visitors come from, which is how we learn what actually helps people decide to come. If you decline, or never answer, it is never loaded.
- Name
- Vercel Web Analytics
- Stores on your device
- Nothing: no cookie, no local storage
- Records
- Page, referring site, country, region and city, browser, operating system, device type
- Tells visitors apart by
- A hash of the request, discarded by Vercel after 24 hours
- Never records
- The /admin area, or what you type into the news search
You can change your answer from the footer at any time. Withdraw during a visit and nothing more is sent from that moment.
Why ask at all, then
Because the answer decides whether visits are counted. The counting reads the stored answer and stays off unless it says yes, which is the order it should be built in: the switch first, then the thing it controls.
Declining costs you nothing on this site. Every page works identically either way.
What your browser loads from elsewhere
One host, for images only:
- img.youtube.com, which serves the still frames on the video cards. The videos themselves are not embedded, so YouTube's player and its cookies only enter the picture if you click through to YouTube, where their policy applies rather than ours.
Both see your IP address and user agent, which is unavoidable for any server that sends your browser a file. Typefaces are served from this site rather than from Google, so no request reaches a font host.
On the checkout's payment step, and only there, the page loads Stripe, which takes the payment:
- js.stripe.com and its payment form, shown in a secure frame inside the page. Your card details go from that frame straight to Stripe and never reach us. Stripe sets its own cookies there to detect fraud, which a card payment cannot be taken without, so they are strictly necessary and not covered by the consent banner. Stripe's privacy policy applies to them.
Booking a call takes you to a different site, which sets its own cookies under its own policy, and the banner here has no authority over them.
Changing your mind
Use the cookie settings link in the footer of any page to answer again. You can also clear site data in your browser, which removes the stored answer and brings the banner back.








