Cookie Policy

Last updated: 4 June 2026

This is an English translation of the Dutch “Cookiebeleid”. Only the Dutch version is legally binding; if the two differ, the Dutch version prevails.

1. What are cookies?

Cookies are small text files that are stored on your device when you visit a website. For the purposes of this policy, similar techniques (such as localStorage) are subject to the same rules.

2. We use only necessary cookies

Exposentry places only functional, strictly necessary cookies. These are needed to make the website work and to let you log in securely. Under the Dutch Telecommunications Act (Telecommunicatiewet) and the GDPR, no consent is required for strictly necessary cookies. You will therefore not see a cookie consent banner: there is nothing for you to accept or reject.

Cookie / storageTypePurposeRetention period
session-tokenFunctionalManaging the login sessionDuration of the session
csrf-tokenFunctionalCSRF protection during authenticationDuration of the session
callback-urlFunctionalCorrect redirect after loginDuration of the session
The technical names of these cookies may depend on the authentication component used. Their function and necessary nature remain the same.

3. No analytics or tracking cookies

We do not use analytics cookies, advertising cookies or third-party trackers. For website statistics we use Plausible Analytics, a privacy-friendly tool that is self-hosted on our own server and places no cookies. Plausible processes no personal data and is therefore not covered by cookie legislation.

4. Managing cookies

Because we place only necessary cookies, you do not need to configure anything. If you wish, you can always delete or block cookies through your browser settings. Blocking necessary cookies may mean that you cannot log in or that the Service does not work properly.

5. More information

If you have questions about this cookie policy, you can contact us via scan@exposentry.io. This policy has been drawn up in accordance with the Dutch Telecommunications Act and the GDPR. See also our privacy statement.