Trust is built into the workflow.
Below are technical safeguards visible in the supplied marketing lead-capture code. Other production and merchant-platform security assertions require engineering review.
A few concrete safeguards.
Durable lead receipts
The Cloudflare Worker writes lead submissions to D1 before acknowledging them, then retries failed HubSpot delivery from a stored queue.
Restricted browser input
API requests are limited by origin, body size, email and website validation, IP rate limiting and an optional hidden spam field.
Booking confirmation
A browser click is not treated as a booked appointment. A matching Google Calendar event must be confirmed by the backend.
Conversions API boundaries
The backend hashes matched email for the Meta booking event and reuses a stable event ID to avoid double-counting.
Secrets outside the site
HubSpot, Google OAuth and Meta API tokens stay in protected Worker environment secrets rather than the static frontend.
Operational verification
Production monitoring, data retention, certifications and broader platform controls are not independently certified by this website.