This Cookie Policy was last updated on 12 februari 2026 and applies to citizens and legal permanent residents of the European Economic Area and Switzerland.
1. Introduction
Our website, https://keybox.nl/en (hereinafter: “the website”) uses cookies and other related technologies (for convenience all technologies are referred to as “cookies”). Cookies are also placed by third parties we have engaged. In the document below we inform you about the use of cookies on our website.
2. What are cookies?
A cookie is a small simple file that is sent along with pages of this website and stored by your browser on the hard drive of your computer or another device. The information stored therein may be returned to our servers or to the servers of the relevant third parties during a subsequent visit.
3. What are scripts?
A script is a piece of program code that is used to make our website function properly and interactively. This code is executed on our server or on your device.
4. What is a web beacon?
A web beacon (or a pixel tag) is a small, invisible piece of text or image on a website that is used to monitor traffic on a website. In order to do this, various data about you is stored using web beacons.
5. Cookies
5.1 Technical or functional cookies
Some cookies ensure that certain parts of the website work properly and that your user preferences remain known. By placing functional cookies, we make it easier for you to visit our website. This way, you do not need to repeatedly enter the same information when visiting our website and, for example, the items remain in your shopping cart until you have paid. We may place these cookies without your consent.
5.2 Statistics cookies
We use statistics cookies to optimise the website experience for our users. With these statistics cookies we get insights in the usage of our website. We ask your permission to place statistics cookies.
5.3 Marketing/Tracking cookies
Marketing/Tracking cookies are cookies or any other form of local storage, used to create user profiles to display advertising or to track the user on this website or across several websites for similar marketing purposes.
5.4 Social media
On our website, we have included content from Facebook to promote web pages (e.g. “like”, “pin”) or share (e.g. “tweet”) on social networks like Facebook. This content is embedded with code derived from Facebook and places cookies. This content might store and process certain information for personalised advertising.
Please read the privacy statement of these social networks (which can change regularly) to read what they do with your (personal) data which they process using these cookies. The data that is retrieved is anonymised as much as possible. Facebook is located in the United States.
6. Placed cookies
Sharing data
This data is not shared with third parties.
Functional
session
Store items in shopping cart
persistent
Functional
365 days
Store information about cookies that have been detected on the site
365 days
Store accepted cookie policy ID
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store cookie consent preferences
365 days
Store if the cookie banner has been dismissed
Sharing data
This data is not shared with third parties.
Functional
session
Store browser details
persistent
Store user preferences
session
Check if cookies can be placed
persistent
Store logged-in users
Sharing data
This data is not shared with third parties.
Statistics
3 days
session
Store the user's usage history
Sharing data
This data is not shared with third parties.
Statistics
6 months
Store the user's usage history
6 months
Store and count pageviews
6 months
Store and count pageviews
6 months
Store browser details
session
Store and track interaction
6 months
Store a unique session ID
30 minutes
Store and count pageviews
Statistics
1 day
Store and count pageviews
1 year
Store and count pageviews
2 years
Store and count pageviews
Functional
session
Provide technical monitoring
Sharing data
This data is not shared with third parties.
Functional
2 days
Preventing cached pages depends on what you mean by "cached pages" and what you're trying to prevent. Here are a few common scenarios and their solutions:**1. Preventing Browser Caching of Your Website's Pages (for website owners/developers):**This is when you want to ensure visitors always see the latest version of your web pages and not an older, cached version from their browser.* **Set HTTP Headers:** The most common and effective way is by setting appropriate HTTP cache-control headers.
* **`Cache-Control: no-cache`**: This tells the browser to revalidate with the server before using a cached version. It's a good balance between performance and freshness.
* **`Cache-Control: no-store`**: This tells the browser (and any intermediaries like proxies) not to store the page at all. This is the strongest cache disabling option but can impact performance.
* **`Cache-Control: max-age=0`**: Similar to `no-cache`, this specifies that the resource is immediately stale.You typically implement these in your web server's configuration (e.g., Apache, Nginx) or within your application's code.* **Use Unique URLs for New Content:** If you frequently update content and want to ensure the new version is always loaded, give it a new, unique URL. This could involve:
* **Versioning:** `/styles/style-v2.css` instead of `/styles/style.css`
* **Timestamps:** `/images/logo-20231027.png`
* **Cache Busting Query Strings:** `script.js?v=1.2.3` (though HTTP headers are generally preferred for static assets).* **Disable Caching on Specific Pages:** For pages that change very frequently or contain sensitive, time-critical information.**2. Preventing Users from Caching Specific Content (e.g., images, sensitive data):**If you want to prevent users from saving or caching specific sensitive files or data within their browser.* **Similar to Website Caching:** Use `Cache-Control: no-store` or `Cache-Control: no-cache` on the resources themselves (e.g., for image files).
* **Disabling Right-Click and Download Options:** While not a true caching prevention, you can use JavaScript to disable right-click context menus and potentially prevent direct saving of images. However, this is easily circumvented and not a robust security measure.**3. Preventing Search Engine Caching:**If you want to prevent search engines like Google from indexing and caching your pages.* **`robots.txt` File:** You can add directives in your `robots.txt` file to tell search engine crawlers not to index specific pages or sections of your site. However, this is a guideline, not an enforcement. If a page is linked from elsewhere, search engines might still index it.
* **`noindex` Meta Tag:** The most effective way is to use the `noindex` meta tag in the `` section of your HTML:
```html
```
To prevent both crawling and indexing, you can combine it with `nofollow`:
```html
```**4. Preventing Caching in Other Contexts:*** **Server-Side Caching (e.g., Redis, Memcached):** If you're referring to caching mechanisms within your application's backend, you'd typically clear or invalidate specific cache entries when data changes. The exact method depends on the caching system you're using.
* **Proxy Caching:** Similar to browser caching, you configure proxy servers (like Varnish or Cloudflare) with cache-control directives.**In summary, the most common and effective methods involve:*** **HTTP Headers (`Cache-Control`)** for web pages and assets.
* **`noindex` Meta Tags** for search engine exclusion.
* **Unique URLs** for ensuring the latest versions are loaded.To give you the *exact* best advice, I'd need to know precisely what kind of "cached pages" you're trying to prevent.
Purpose pending investigation
rc::c
rc::b
rc::a
Purpose pending investigation
Google Fonts API
Purpose pending investigation
GPS
VISITOR_INFO1_LIVE
YSC
PREF
Purpose pending investigation
_js_datr
_fbc
fbm*
xs
wd
fr
act
_fbp
datr
c_user
csm
sb
actppresence
*_fbm_
Sharing data
Sharing of data is pending investigation
Purpose pending investigation
hst_ai_blocks_added
greeting_screen_visited_v1
general-data-store
kodee_pro_banner_dismissed
widget_opened_v1
ag_script_item
chatbot_input_message
wp-settings-time-1
tk_or
tk_lr
aelia_user_logged_in
wp_lang
7. Consent
When you visit our website for the first time, we will show you a pop-up with an explanation about cookies. As soon as you click on “Save preferences”, you consent to us using the categories of cookies and plug-ins you selected in the pop-up, as described in this Cookie Policy. You can disable the use of cookies via your browser, but please note that our website may no longer work properly.
7.1 Manage your consent settings
You have loaded the Cookie Policy without javascript support. On AMP, you can use the manage consent button on the bottom of the page.
8. Enabling/disabling and deleting cookies
You can use your internet browser to automatically or manually delete cookies. You can also specify that certain cookies may not be placed. Another option is to change the settings of your internet browser so that you receive a message each time a cookie is placed. For more information about these options, please refer to the instructions in the Help section of your browser.
Please note that our website may not work properly if all cookies are disabled. If you do delete the cookies in your browser, they will be placed again after your consent when you visit our website again.
9. Your rights with respect to personal data
You have the following rights with respect to your personal data:
- You have the right to know why your personal data is needed, what will happen to it, and how long it will be retained for.
- Right of access: You have the right to access your personal data that is known to us.
- Right to rectification: you have the right to supplement, correct, have deleted or blocked your personal data whenever you wish.
- If you give us your consent to process your data, you have the right to revoke that consent and to have your personal data deleted.
- Right to transfer your data: you have the right to request all your personal data from the controller and transfer it in its entirety to another controller.
- Right to object: you may object to the processing of your data. We comply with this, unless there are justified grounds for processing.
To exercise these rights, please contact us. Please refer to the contact details at the bottom of this Cookie Policy. If you have a complaint about how we handle your data, we would like to hear from you, but you also have the right to submit a complaint to the supervisory authority (the Data Protection Authority).
10. Contact details
For questions and/or comments about our Cookie Policy and this statement, please contact us by using the following contact details:
Keybox.co.uk - Dutch Trading Company Blaricum B.V.
Laarderweg 73A, 1402BE, Bussum
Netherlands
Website: https://keybox.nl/en
Email: info@ex.comkeybox.co.uk
Phone number: +31651132330
This Cookie Policy was synchronised with cookiedatabase.org on the 14th april 2026.
