If we later introduce cookies, ad tracking, user accounts, or stronger tracking, we will reassess and update this page.

Visit-level observation

This site uses Cloudflare Web Analytics to understand aggregate traffic (for example page views, referrers, and device types). That capability is injected at the edge by Cloudflare; this Vue app and index.html do not insert a second Web Analytics beacon.

Cloudflare infrastructure may process network requests under its platform rules; this site’s application code does not write visitor IP addresses, full User-Agent strings, or similar into our own database.

Conversion events (anonymous event store)

The site records two anonymous conversion event types via Cloudflare Pages Functions and a D1 database: campaign_landing (valid UTM landing) and contact_click (clicks on real contact entry points — currently mailto email links).

D1 does not store names, inquiry message bodies, email content, phone numbers, application-layer IP, full User-Agent, cookie identity, browser fingerprints, user IDs, or profiling fields.

Without valid UTM parameters, the site does not write campaign_landing records.

What we do not use

Analytics V1 does not use cookies for on-site tracking, does not establish user identity, does not do cross-session recognition, ad attribution, or profiling, and does not collect scroll/hover behavior. There is no consent banner in the current product scope (a product decision, not a legal conclusion).

This site does not use GA4, GTM, Plausible, Umami, Mixpanel, PostHog, or similar third-party analytics SaaS.

Contact and email

When you click an email link, your mail client handles the message; this site does not collect or store what you type in your email client.

Real inquiries and follow-up are handled manually and are outside the automated analytics database.