Privacy policy
Last updated November 9, 2026
This site doesn't track you. It runs no analytics, sets no cookies of its own and has no ads. There are two third-party services, Cal.com and Stripe, and both load on exactly one page.
Cal.com, on the Work with me page only. The booking calendar on Work with me is loaded from Cal.com, so on that page your browser talks to their servers, and Cal.com may set its own cookies to make the calendar work. If you book a time, the name, email and notes you enter go to Cal.com and to me, and I use them only to hold the meeting. Cal.com handles that data under its own privacy policy.
Stripe, when a booking is paid. Some sessions are paid at the time you book. The payment form inside the Cal.com calendar comes from Stripe, and your card details go straight to Stripe; they never pass through this site, and I never see your full card number. Stripe may set its own cookies and collect information about your device to prevent fraud. What I receive is the record of the payment: your name, email, the amount, the date, and the card's brand and last four digits. Stripe handles payment data under its own privacy policy. No other page on this site loads anything from Cal.com, Stripe, or anyone else.
What your browser keeps. If you switch between light and dark mode, your choice is saved in your browser's local storage under the key theme, so the page looks the same on your next visit. It stays on your device and is never sent to me. Clearing your site data deletes it.
What the server keeps. Like nearly every web server, this one writes a standard access log: your IP address, the page you asked for, the time, and the browser identifier your browser sends. I use these logs only to keep the site running and to deal with abuse. I don't analyze them for traffic, combine them with anything else, or share them, and they're deleted automatically after about two weeks.
Email. If you write to me, I'll have your address and whatever you send. I use it to reply and for nothing else.
Legal basis. Where GDPR applies, booking and payment details are processed to arrange and charge for the meeting you asked for (Article 6(1)(b)), payment records are kept because tax law requires it (Article 6(1)(c)), and the server logs rely on my legitimate interest in keeping the site secure and working (Article 6(1)(f)).
Your rights. You can ask what I hold about you, or ask me to delete it, at j@jeffdrew.me. The one thing I can't delete on request is the record of a payment, which I have to keep for as long as tax law says. In practice, the answer is almost always "a few lines in a log that's about to expire."