Last updated: March 30, 2026
This Cookie Policy explains how jeromedanvers.com (“we”, “our”, or “us”) uses cookies and similar technologies when you visit our website.
Cookies are small text files that are stored on your device (computer, tablet, or mobile) when you visit a website. They help websites function properly and provide information to site owners about how visitors use their site.
We use cookies for a limited number of purposes:
a) Analytics Cookies
We use Google Analytics to understand how visitors interact with our website. These cookies collect information such as:
This data helps us improve the performance and usability of our website.
Google Analytics may set the following cookies:
_ga_gid_gatAll data collected is anonymized and does not directly identify you.
b) Functional Cookies
We may use basic cookies to ensure the website functions correctly, such as:
Our website includes a contact form that allows you to get in touch with us. This form does not use cookies for tracking purposes.
Any information you submit through the form is used solely to respond to your inquiry and is not used for marketing or shared with third parties.
Some cookies are set by third-party services we use:
These third parties may process data according to their own privacy policies.
You can learn more about how Google uses data here:
https://policies.google.com/privacy
You can control and manage cookies in several ways:
Please note that disabling cookies may affect how the website functions.
If you are located in the European Economic Area (EEA), we rely on:
You will be asked to accept or reject cookies via a cookie banner when you first visit the site.
We may update this Cookie Policy from time to time. Any changes will be posted on this page with an updated revision date.
If you have any questions about this Cookie Policy, you can contact us via the contact form on the website.
Note: This policy is intended for a simple website using only Google Analytics and a contact form. If you add features such as advertising, embedded content, or user accounts, this policy should be updated accordingly.
Like what you see? If you’ve got something similar in mind, I’d love to hear about it.
