Two cookies. Both necessary. Nothing to reject.

1. Our position

We do not use analytics, advertising, profiling or social-media cookies. We do not embed third-party trackers, and no fonts, scripts or images are loaded from another company's servers. The only cookies set are the strictly necessary ones listed below, which do not require consent under Article 5(3) of the ePrivacy Directive.

We took that decision deliberately. Loading a font, a script or an image from another company’s server would disclose your IP address and the page you are reading to that company, whether or not it set a cookie. So this site is entirely first-party: every stylesheet, script, icon and font instruction comes from worlddigitalforum2025berlin.com itself, and the typefaces used are the ones already installed on your device.

2. Every cookie we set

The table below is the complete list. If a cookie is not in it, this site did not set it.

Cookies set by worlddigitalforum2025berlin.com.

Name	Purpose	Duration	Type
wdf_session	Keeps your form session and CSRF protection token so that a submitted form can be verified as genuine.	Session (deleted when you close your browser)	Strictly necessary · first-party
wdf_notice	Remembers that you have seen the cookie notice so it is not shown on every page.	6 months	Strictly necessary · first-party

Both cookies are set by worlddigitalforum2025berlin.com itself. Neither contains your name, your email address, or anything that describes your behaviour. Neither is readable by another website.

What each one actually holds

• wdf_session holds a random session identifier. The server uses it to associate your browser with a one-time security token, so that a form submitted to us can be shown to have come from a page we served rather than from another site acting in your name. It is only set when you use a page containing a form, and it disappears when you close your browser.
• wdf_notice holds the single value 1. Its only job is to stop the cookie notice reappearing on every page you visit. Without it, the notice would be shown again on every page load, which would be worse for you, not better.

3. Why there is no consent banner

Article 5(3) of the ePrivacy Directive requires consent before storing information on your device — except where the storage is strictly necessary to provide the service you asked for. Both cookies above fall within that exception: one secures your form submission, the other remembers that you have already read this information.

Because there is no non-essential cookie to refuse, presenting you with an “Accept” and a “Reject all” button would be theatre. The button would do nothing, and a consent choice that changes nothing is not a consent choice. So the notice you see on this site is exactly what it says it is: a notice, telling you what is stored and why, with a button that dismisses it.

If we ever introduce a cookie that is not strictly necessary, we will ask for your consent first, through a real choice with a genuine refusal option, and we will not set the cookie until you have given it.

4. Third-party content and trackers

We do not use any of the following on this site:

• analytics or measurement services of any kind;
• advertising, retargeting or conversion-tracking tags;
• social-media buttons, share widgets or embedded feeds;
• webfonts, icon fonts or stylesheets loaded from another company’s servers;
• content-delivery networks, tag managers or A/B-testing tools;
• embedded video, maps or comment systems;
• tracking pixels, web beacons, fingerprinting scripts or session recorders.

Our web server keeps ordinary access logs, which include your IP address. Those are server-side records rather than cookies, and they are described in our Privacy Policy, where you can also see how long we keep them.

5. Controlling and deleting cookies

You are in charge of your browser. Every major browser lets you view the cookies a site has set, delete them individually or in bulk, and block cookies from being set at all, usually from a “Privacy” or “Site settings” section of its preferences.

Because our cookies are strictly necessary rather than optional, blocking them has consequences we would rather you knew in advance:

• Blocking wdf_session means we cannot verify that a form submission came from our own page, so the subscribe, contact, preferences and unsubscribe forms will refuse the submission. You can still reach us by email, and the one-click unsubscribe link inside our emails will still work.
• Blocking wdf_notice simply means the cookie notice reappears each time you load a page. Nothing else changes.

6. Other browser storage

We do not use local storage, session storage, IndexedDB, service workers or any other client-side storage mechanism, and we do not attempt to identify your device by fingerprinting it.

7. Changes to this policy

If the cookies we set change, this page changes with them, and we will update the date below. This page is generated from the same single source of truth that configures the site, so the table above and the code that runs cannot drift apart.

Last updated: 7 September 2026. Questions about this policy go to awatef.keltai@worlddigitalforum2025berlin.com.