Privacy
Last updated 18 September 2026
This is the privacy notice for danydujardin.com, operated by Dany Dujardin. It is written plainly and kept short, because the site does little with your data and never sells it.
What this site is
A static marketing site. There are no accounts. There is one advertising tag, LinkedIn's, and it only runs if you agree to it: see Analytics and cookies below. The only place you can submit information is the contact form on the home page and on the contact page. Nothing is shared or sold.
The contact form
If you fill in the form on the home page or the contact page, the details you enter (your name, work email, company, and what you tell me about the deal you want to talk about) are collected through a form provided by HubSpot and stored in my HubSpot account, hosted in the EU, under HubSpot's privacy policy. I use them for one thing: to prepare for our call and to come back to you about it, and I do not pass them on. The form carries one optional box for occasional emails. Leave it unticked and you will only ever hear from me about what you sent.
I keep what you send for as long as we are talking, and for two years after our last contact, then delete it. You can ask me to delete it sooner and I will. The form asks you to confirm you are happy for me to store and use your answers to prepare for and follow up our conversation, and that is the only thing I use them for. Analytics is separate, and that is what the cookie notice is for.
The form itself is displayed inside a frame served by HubSpot and places no cookie on danydujardin.com. HubSpot's tracking code is a separate thing, it does set a cookie here, and it is covered under Analytics and cookies below. HubSpot's own domains set one short-lived cookie of their own, named __cf_bm, which Cloudflare uses to tell real visitors from automated traffic. It is not an advertising or cross-site tracking cookie, it is set by HubSpot rather than by me, and I cannot read it.
One thing about the form that I would rather state than leave you to find. The script that draws it loads with the page, before you have chosen anything in the cookie notice. It stores nothing on your device, which is why it sits outside that notice, but loading it does tell HubSpot your IP address. I have left it that way so the form works for everyone, including people who decline everything. If you would rather not have that happen at all, write to me at the address below instead of using the form.
If you email me, I receive your message and address to reply. My mail runs on Google Workspace, so Google handles it on my behalf as my provider. I do not add you to a mailing list, and I do not share it.
Tracked links, if I sent you one
If I sent you a piece of work I made about your company, the link in that email carries a short code. When the page opens, my own server writes a line saying that code was opened, when, and roughly what kind of device it was. If you press play on the video, it records that too.
This does not use a cookie and it does not depend on the choices below, because it is my server writing its own log rather than something placed on your device, so there is nothing for you to accept or refuse in your browser. The code identifies the company I sent it to, which usually means you. I use it for one thing: to see whether the work was worth making before I make twenty more. My basis is my legitimate interest in knowing that, and the record is minimal by design. Ask me what that log says about you and I will tell you, or delete it, whichever you prefer.
Analytics and cookies
I use Cloudflare Web Analytics to see which pages are visited. It is cookieless and counts visits in aggregate, without identifying you and without setting any cookie. It needs no consent and runs for everyone.
If you accept analytics on the cookie notice, I also use PostHog (hosted in the EU) to understand how the site is used, including session replay, which records how a page is scrolled and clicked with typed input masked, under PostHog's privacy policy. Accepting analytics also loads HubSpot's tracking code, which sets a cookie on danydujardin.com named hubspotutk. It exists so that if you later fill in the contact form, the pages you read are attached to your record rather than sitting anonymously in a dashboard, which means I know what you were interested in before we speak. If, separately, you accept advertising, I load the LinkedIn Insight Tag, under LinkedIn's privacy policy. This one is an advertising tag, and I would rather say so than bury it. It sets LinkedIn cookies, and it lets LinkedIn tell me two things: whether an ad of mine led to someone filling in the contact form, and how many LinkedIn members visited the site, reported in aggregate by job title, company and industry, never as a list of names. It also lets me show later LinkedIn ads to people who have been here. I cannot see who you are from it, and I do not buy or receive any list of visitors.
These are two separate choices and the notice asks them separately. Analytics covers PostHog and HubSpot. Advertising covers LinkedIn, and nothing else does. You can accept one and refuse the other, refuse both, or accept both. If you decline, or leave without choosing, none of them loads.
PostHog, HubSpot and LinkedIn are the only three things I set cookies with, and none of them loads before you agree to the purpose it belongs to. You can change your mind at any time: reopen the cookie choices. Turning something off reloads the page so it stops running immediately. What that cannot do is delete cookies LinkedIn has already set on linkedin.com, which only LinkedIn or your browser can clear.
Hosting
The site is served by Cloudflare Pages. As with any web host, Cloudflare may process standard request data such as your IP address and browser type to deliver the site and keep it secure, under Cloudflare's privacy policy.
Why I am allowed to do this
Plain version, because the legal wording is short. What you send through the form: your consent, which the form asks for, alongside the fact that you are asking me to prepare something for you. Cookies and the tools behind them: your consent, given per purpose in the notice, and nothing loads without it. Email you send me: answering someone who wrote to me. Server logs, keeping the site up, and the tracked-link record described above: my legitimate interest in running a working, secure site and in knowing whether work I sent was opened. I never rely on consent for something you cannot refuse.
Where your data is handled
HubSpot and PostHog hold their data in the EU. Three others are American companies, so data reaches the United States: Cloudflare, which serves the site, Google, which carries my email, and LinkedIn, if you accept advertising. Each of them covers those transfers with the safeguards the GDPR provides for, which in practice means the European Commission’s standard contractual clauses and, for some of them, certification under the EU to US Data Privacy Framework. If that matters to you, declining advertising removes LinkedIn from the list; the other two are how the site and my mailbox exist at all.
Your rights
You can ask me to show you what I hold about you, correct it, delete it, limit what I do with it, object to what I do with it, or send it to you in a portable format. You can withdraw a consent at any time, and withdrawing does not undo what was lawful before you did. Email me and I will handle it, normally the same week and always within a month. Asking costs you nothing and I do not ask why.
To change or withdraw your cookie choices, reopen the cookie choices; it takes the same two clicks as giving them did.
If I get it wrong, you can complain about me. The Belgian supervisory authority is the Autorité de protection des données / Gegevensbeschermingsautoriteit, in Brussels. You can go to them directly, and you do not have to come to me first, though I would rather you did.
Contact
Questions about this notice: [email protected].
If the site later changes what it collects or which tools it uses, this notice will be updated to match.