Privacy

What data this site collects directly

Nothing. There are no analytics scripts, no cookies, no tracking pixels, no contact form, and no accounts. Visiting any page sends no data to me beyond the HTTP request itself (described below).

What data the hosting infrastructure processes

The site is hosted on Vercel, which operates the content delivery network (CDN) and runtime that serves every request. As part of normal infrastructure operation, Vercel processes the data that's inherent to any HTTP request:

• your IP address
• the URL you requested
• the time of the request
• your browser's user-agent string
• the HTTP referrer (the page you came from, if any)

Vercel is the data processor for this information; I am the controller. Their handling is governed by Vercel's privacy policy and data processing addendum.

Cookies

The site sets no cookies. If a future feature requires them (for example, a comment system, a contact form, or analytics) this page will be updated before that feature ships.

Error monitoring

Client-side and server-side errors are reported to Sentry to help me find and fix bugs. Sentry receives the error itself (stack trace, browser version, the URL that triggered it) along with the IP address that initiated the request. Sentry is also a data processor for this site; their handling is governed by Sentry's privacy policy and data processing addendum. Error events are processed on Sentry's US infrastructure; the EU→US transfer relies on EU Standard Contractual Clauses (SCCs) per Sentry's DPA.

External links

The site links out to GitHub, LinkedIn, and a small handful of other services. Once you follow a link, the destination's own privacy policy applies — I have no visibility into or control over how those services handle your visit.

Requesting deletion

If you'd like Vercel's or Sentry's log entries for your visits removed, email me at matt@mksolutionsky.com and I'll forward the request to the relevant processor. Retention is short by default (typically a few weeks for routine CDN logs), so most data ages out on its own.

Your rights

If you're in the EU/UK, the GDPR (and the equivalent UK regime) gives you rights over the data Vercel and Sentry process on my behalf. Because I'm the controller but hold none of this data myself — it lives entirely in those processors' systems — the fastest route for most requests is the processor's own data-subject-request flow:

• Access — confirm whether your data is being processed and get a copy of it.
• Rectification — have inaccurate data corrected.
• Erasure — have your data deleted (the email path above also covers this).
• Restriction — have processing limited while a dispute is resolved.
• Portability — receive your data in a machine-readable format.
• Objection — object to processing based on legitimate interests.

Vercel and Sentry each run their own request mechanisms for the data they hold: Vercel's privacy policy (see its data-subject-request contact) and Sentry's privacy policy cover how to reach them. For anything that needs me to forward it on your behalf — or if you're not sure where to start — email me at matt@mksolutionsky.com and I'll route the request to the relevant processor.

Updates to this page

The site's source is on GitHub — any change to this page is in the commit history. There's no separate "last updated" date because the git log is authoritative. The underlying processor inventory (the internal record this notice is based on) lives at PRIVACY_DATA_PROCESSORS.md.