Privacy

This is a personal blog. I want it to feel like reading a paper notebook — quiet, no one looking over your shoulder. Here's exactly what happens when you visit.

What this site does not do

No cookies. No tracking cookies, no session cookies, no consent banner — because there's nothing to consent to.
No advertising. No ad networks, no retargeting pixels, no affiliate trackers.
No fingerprinting. Nothing tries to identify you across sessions or devices.
No personal data collection. No email capture, no forms, no accounts.
No third-party social embeds that phone home (Twitter widgets, YouTube auto-embeds, etc.). Share buttons are plain links — they only do anything when you click them.

What it does do

Two things, both privacy-friendly by design:

Vercel Web Analytics

I use Vercel Web Analytics to count page views and see which articles people read. It's cookieless and explicitly designed to comply with GDPR, CCPA, and similar laws without a consent banner.

What it collects, per Vercel's documentation:

The page URL you visited
The referrer (where you came from), if any
A coarse, hashed identifier derived from your IP and User-Agent — used only to deduplicate visits within a single day, then thrown away. The raw IP is never stored.
Approximate country, browser, and operating system (derived from the User-Agent)

It does not set cookies, does not use localStorage, and does not follow you across sites or sessions. Vercel's full data policy for Web Analytics is at vercel.com/docs/analytics/privacy-policy.

Vercel Speed Insights

Speed Insights measures Core Web Vitals — how fast pages render and respond — so I can fix slow pages. Same model: cookieless, no PII, anonymous and aggregated.

Hosting & logs

The site is hosted on Vercel, which keeps short-term server logs (IP, request path, timestamp, User-Agent) for security and abuse prevention. I don't access these logs for analytics, and they expire on Vercel's standard schedule. See Vercel's privacy policy for details.

Embedded content & outbound links

If an article embeds an image, video, or asset from a third party, your browser will load it from that third party, and they'll see your IP. I try to keep embeds to a minimum and prefer self-hosted assets when reasonable.

Outbound links go where they say they go. I don't use link shorteners or affiliate redirects.

Fonts

The site loads EB Garamond and Fira Code from Google Fonts. Google may log this request. If you'd rather avoid it, a browser extension that blocks third-party fonts will work — the site stays readable with system fonts.

If you want zero analytics

Use a content blocker (uBlock Origin, Privacy Badger) or browser-level tracking protection. The site works exactly the same with analytics blocked — there's no fallback that tries to get around it.

Questions

If anything here is unclear or you spot something that contradicts the policy, email me at jota.jota.or@gmail.com.

Last updated: 2026-05-05