This is a personal site. It runs writing, a few demos, and a set of client-side file tools. There are no user accounts, no logins, no payments, no API resale. The privacy story is short.
What this site does not do
- No accounts, no passwords, no profiles, no sessions.
- No payment processing. No Stripe, no card data, ever.
- No upload of your files to any server. The file tools at /projects/pdf-tools/ run entirely in your browser — PDFs, images, CSVs, signatures, everything. Bytes never leave your device.
- No tracking pixels beyond Google Analytics on the marketing pages (see below).
- No selling, sharing, or brokering of data with third parties. Ever.
What gets logged
The hosting provider (Railway) keeps standard HTTP request logs — IP address, user-agent, path, response code, timestamp. These are operational logs for debugging and abuse prevention, retained for a short window and not connected to any identity.
The blog and the projects list load from a public Supabase database using a read-only anonymous key. Row-level security restricts reads to published posts and project metadata — no private data is reachable.
Analytics
Some marketing pages include Google Analytics 4 (measurement ID G-VFML1FVJ7D) to count pageviews
and understand which posts get read. Google receives standard analytics signals (IP, UA, referrer, device) under their own
privacy policy. No identifiers are linked to anything personal on this site.
If you prefer not to be measured: use a privacy extension (uBlock Origin, Privacy Badger), enable your browser's "Do Not Track" / "Global Privacy Control" headers, or use a private window.
Cookies
The site itself sets no cookies. Google Analytics may set _ga* cookies on pages where it loads.
Local browser storage may be used by individual tools to remember your preferences (e.g. last-used pen colour) —
purely client-side, never transmitted.
External links
Outbound links to GitHub, LinkedIn, Evolv AI, and CDN providers (jsdelivr, cdnjs, unpkg, Google Fonts) are governed by those services' own privacy policies. The tools and posts load JavaScript and fonts from those CDNs.
Your rights
Since this site does not store personal data, there is nothing to access, export, correct, or delete on the backend. For analytics data held by Google, contact Google directly per their data subject request flow.