Privacy Policy

This is a personal portfolio, so I collect as little information as possible. This page explains what that is, why, and what you can ask me to do with it.

Contact form. If you send me a message, I receive your first and last name, email address, subject, message, and your phone number if you choose to add it.

No analytics or ad trackers. This site doesn’t use analytics, advertising, or tracking tools, and it doesn’t ask you to create an account.

Basic technical data. Like any website, the hosting provider may automatically log standard request details, such as your IP address, browser type, and the time of your visit, to keep the site running and secure.

• To read and reply to your message.
• To keep the site working, secure, and free from spam.

I don’t sell your information, share it for advertising, or add you to any mailing list.

• Web3Forms delivers contact form messages to my email inbox.
• Vercel hosts this website and may process the basic technical data described above.
• GitHub provides the contribution and language stats on the home page. The site requests these itself, so none of your information is sent to GitHub when you view them.

Links to GitHub, LinkedIn, WhatsApp, and my résumé on Google Drive take you to those services, and their own privacy policies apply there.

This site doesn’t use cookies for tracking. It saves one setting in your browser’s local storage: your light/dark theme preference. It stays on your device, is never sent to me, and you can clear it anytime in your browser settings.

The site is served over HTTPS, so what you type into the contact form is encrypted while it’s sent. Messages are kept in my private email inbox, not in a public database. No system is 100% secure, but I take reasonable care to protect what you send me.

I keep messages only as long as they’re useful for our conversation. You can ask me at any time to see, correct, or delete the information you sent through the contact form, and I’ll do it.

Prefer not to use the form? You can email me directly instead. See also the Terms & Conditions.

If how I handle information changes, I’ll update this page and the “last updated” date at the top.