Privacy policy
Last updated: June 2026
Horse to Unicorn (“we”, “the site”) is a personal newsletter written by Thomas Budin. This page describes what data we collect, how we use it, and the rights you have. We aim to collect as little as possible.
What we collect
- Your email address, when you subscribe to the newsletter. This is the only personal data we actively collect.
- Basic server logs (IP address, user agent, request path), kept transiently by our hosting provider (Vercel) for operational and abuse-prevention purposes.
How we use it
- Your email is used to send the newsletter (one email per article), the confirmation email when you subscribe, and a welcome email when you confirm. We do not share it.
- We use double opt-in: when you subscribe we send a confirmation link and only add you to the list once you click it. This is your evidence — and ours — that you consented.
Where it lives
- Our email service provider is Resend. Your email address is stored in our Resend audience until you unsubscribe.
- Images for articles are served from Cloudflare R2. No personal data sits there.
- The site itself runs on Vercel. Vercel keeps short-lived request logs but receives no email content.
How long we keep it
Email addresses are kept for as long as you're subscribed. If you unsubscribe, your address is flagged as unsubscribed in Resend and is no longer used to send anything. We may retain the unsubscribed record briefly to make sure we don't accidentally re-email you.
Your rights
Under GDPR and similar regimes you have the right to:
- Unsubscribe at any time. Every newsletter has a one-click unsubscribe link in the footer. You can also reach the unsubscribe page directly at /unsubscribe (you'll need the token from an old newsletter).
- Access, correct, or delete your data. Email privacy@horsetounicorn.com and we'll handle it within 30 days.
Cookies
The site itself sets no tracking cookies. The admin panel uses one session cookie for authentication and only loads for the site owner.
Changes
If this policy changes materially, the next newsletter will mention it. The “Last updated” date above will reflect the change.