What we measure. What we don't. Who processes the data.

We run a small B2B marketing site for fractional AI engineering. We measure traffic and identify visiting companies because that is how a one-person operation decides who to follow up with. Everything below is the full list of tools that run on this site, what each one captures, and how long the data lives.

// 01 · THE STACK

What runs on every page

First-party event log (D1)

A small inline script posts conversion events (Brief Submitted, Teardown Booked, CTA clicks) and AI-engine-referrer detection (Perplexity, ChatGPT, Claude, Gemini, Copilot, Bing, Brave) to /api/track/, which writes a row to a Cloudflare D1 database we own. No third-party processor, no cookies, no fingerprinting. The event row stores the event name, a small JSON of properties, the page path, the referrer URL, a truncated User-Agent, and the country Cloudflare's edge inferred from the IP — no IP address stored.

Cloudflare Web Analytics

Edge-side Real User Monitoring. Captures Core Web Vitals (LCP, INP, CLS) and performance metrics from 100% of visitors with no client-side script, no cookies, and no individual user tracking. Operates entirely inside Cloudflare's network. Cloudflare privacy policy.

Microsoft Clarity

Session replay and heatmaps. Captures anonymized mouse movement, click patterns, scroll depth, rage clicks, and dead clicks. Input fields (your name, email, message) are automatically masked by default — Clarity never sees the values you type. Recordings expire after 30 days. Microsoft privacy statement.

RB2B

Person-level visitor identification for US-based B2B traffic. Matches visitors against a directory of professional profiles and surfaces name, title, company, and LinkedIn URL — same data already published on public LinkedIn profiles. We use it to decide who to follow up with personally. If you'd rather not be identified, opt out at rb2b.com/opt-out.

// 02 · FORMS AND BOOKINGS

What happens when you submit a brief or book a teardown

Brief submissions go to Resend (transactional email service) and arrive in [email protected]. We read every one. We may reply by email; we do not enroll you in any drip campaign or automated sequence.

Teardown bookings are stored in a Cloudflare D1 database with the booking time, your name, your email, and the meeting label. A calendar event is created in Google Workspace and a confirmation email goes through Resend.

We do not sell, rent, or share form data with third parties. We do not use it to train AI models. If you want your data deleted, email [email protected] and we'll delete it within five business days.

// 03 · WHAT WE DON'T DO

What is explicitly not running on this site

// 01

Google Analytics, Meta Pixel, TikTok Pixel, or any ad-network tracking
// 02

Cross-site retargeting cookies or third-party advertising trackers
// 03

Cookie consent banners (we don't set tracking cookies that require consent under GDPR)
// 04

Newsletter signup with auto-enrollment or pre-checked boxes
// 05

Live chat with visitor session recording (no Drift / Intercom / Crisp)
// 06

AI model training on form submissions or visitor data

// 04 · CONTACT

Questions, opt-outs, deletion requests

Email [email protected]. We reply within two business days. We do not have a privacy ticketing system because we are one person and you can talk to the one person directly.

This page is the source of truth. Last updated when this file last shipped — check the git history at github.com/isai-guerrero/advisorylabs.