Privacy
Here’s everything my site collects, why, and what happens to it. No data brokers, no ad networks, no fine print I’m hoping you skip.
Analytics
I use Google Analytics to see which pages get read and which get ignored. It sets cookies and records the usual: the pages you visit, roughly where you are (city-level, from your IP), your device and browser, and a few things you do on a page, like reading a post to the end or clicking a link off to another site. I read it in aggregate. “The résumé page got 200 views this month,” not “here’s what you did.”
Google does the processing on their side, under their privacy policy. A tracker-blocking browser extension keeps you out of it entirely.
Personalized links
Sometimes I send someone a private link to my work: jeremyfuksa.com/p/ followed by a code. Those are tied to the person I sent them to, and they’re tracked more closely than the public site. I log which case studies you open and when, along with your browser and the IP you came from. The IP also tells me if a link’s been opened from more than one place, like when it gets forwarded.
Opening one also sets a cookie that lasts 30 days. While that cookie is there, every page you visit anywhere on this site gets logged against your link, with the same browser and IP, plus the time between the page opening and you leaving it. Leave a tab sitting open all afternoon and it records the afternoon. I use it to tell whether what I sent got read or only got opened.
I’m spelling this out because you might be reading this on one of those links right now. If you’d rather not be, clearing this site’s cookies stops it, though opening my link again starts another 30 days.
When you email me
The contact form posts to my server. Before anything gets sent, I write a copy of your message (your name, your email, and what you wrote) to a database I control, so that if the send fails on the way out, your message is sitting there instead of gone. Then it goes to me as email through Mailgun, who handle the delivery under their privacy policy. I also store your browser’s user-agent string and a hashed version of your IP address, which is how I spot someone pushing fifty messages through the form. The address itself never gets written down.
Once it lands, I have your message and your email address, the same as any email you’d write, and I use it to write you back. If you’ve opened one of my personalized links in the last 30 days, I also log that a message came in from that link, which tells me which company reached out and what they had been reading. That entry is the link and the time: your name, your email, your message, your IP and your browser are not on it. I won’t put you on a list.
If you buy something
If I sell a product here, checkout runs through Lemon Squeezy, who act as the merchant of record. They take the payment, so your card details go to them, never to me or my server. What I get back is what any shop owner gets: your name, email, and what you bought, so I can deliver it and honor the refund policy. Their side of it runs under their privacy policy.
The product's buyer area sets one cookie after you log in with your license key, so you do not have to re-enter it for a month. That cookie identifies your purchase, not your browsing.
What I don’t do
I don’t sell your data. I don’t run ads. There are no third-party trackers here besides Google Analytics, and I’m not building a profile on you to chase you around the rest of the internet. The one other outside script is Lemon Squeezy’s checkout, and it loads only on the product page.
Keeping it, and getting rid of it
Analytics stays in Google under their default retention. The personalized-link logs and the contact messages live in a small database I control, and I clear anything older than a year automatically. Want yours gone sooner, or want to know what I’ve got? hello@jeremyfuksa.com.
Last updated: September 4, 2026.