Your project details should be treated like your project details

information you choose to send

• project inquiry details such as your name, email, phone number, company, budget, timeline and the problem you describe
• messages and photos you send through the AI project assistant, plus the conversation you choose to forward to Leon
• booking details you enter in the Cal.com scheduler, which Cal.com collects on its own embedded form

limited website measurement

• page path, referring-site origin, the five standard UTM campaign fields, and actions such as opening chat or submitting an inquiry
• page loading time, response time and layout shifts, grouped by page and broad device size; these performance events do not include page text or form answers
• an advertising click identifier such as gclid, gbraid, wbraid, fbclid or msclkid when one is already present in the link you open
• a random session identifier stored for the current browser tab so page views are not mistaken for separate visitors
• the opaque booking identifier reported after a successful embedded booking so campaign details can be connected to the booking without putting your contact details in the event stream
• your language preference and bounded first- and last-touch referral details stored in your browser so the site can stay in the language you chose and preserve attribution

Advertising click identifiers are pseudonymous campaign identifiers, not names or contact details. Contact details and message text are not placed in the website event stream.

how it is used

• to answer your question, scope a project, prepare for a call and follow up on an inquiry
• to understand which pages and outreach sources lead to real inquiries
• to distinguish a booking from an attended, qualified, proposed, won, lost, cancelled or no-show opportunity
• to prevent spam, diagnose failures and keep the lead and booking flows working

services involved

• Render hosts the assistant API and its operational logs
• OpenAI processes assistant messages and attached photos to generate a reply
• Resend may deliver a copy of a submitted inquiry to Leon's inbox
• Cal.com provides the booking calendar and handles the information entered there
• Google Ads receives standard tag data and conversion-measurement events only after you select “Allow measurement”
• a separately configured storage or CRM receiver may receive minimized booking-stage records; it is not used unless Leon configures and verifies it

Signed Cal.com lifecycle updates are reduced before storage to a booking identifier, stage, time and bounded campaign fields; the webhook's attendee names, email addresses, answers and notes are not copied into the acquisition-stage record. Links to email, phone, WhatsApp and WeChat leave this site and are governed by those services and your device settings.

retention and your choices

Inquiry receipts, opportunity stages and copies are kept only as long as reasonably needed to respond, work on the requested project, maintain business records, understand acquisition and resolve delivery problems. Browser attribution expires after no more than 90 days unless a new referral touch refreshes it. Hosting logs follow the hosting provider's retention settings. Local JSONL files may reset during deployments unless durable storage is explicitly configured.

Google Ads conversion measurement is optional. Until you select “Allow measurement,” the Google tag is not requested and no data is sent to Google. If you allow it, the standard Google tag sends a configuration/page-view hit that may include the page URL—including campaign or advertising-click identifiers already in it—plus IP and device/browser signals and advertising-cookie identifiers. It uses those signals to connect an ad click with an API-accepted project inquiry, successful booking completed in the embedded Cal calendar, phone-link click or WhatsApp-link click. A link click does not prove that a call connected or a message was sent.

Leon Builds site code does not intentionally put names, email addresses, phone numbers, form contents or chat messages in these Google conversion events. Each explicit conversion event sets Google's user-provided-data field to an empty value, and ad personalization stays denied. That code does not control Google Ads' separate account-level automatic customer-data collection setting, which must remain disabled. Quote receipts and opaque booking identifiers are used only to prevent the same conversion from being counted twice; no monetary value is assigned to these actions. Choosing “No thanks” does not limit the site.

Your choice is kept in this browser. Review or change the conversion-measurement choice. You can also clear this site's browser storage. If you revoke a prior grant, the already loaded tag receives a denied-consent update and no further conversion events are sent on that page; later pages keep the tag blocked. Campaign values already present in the landing link remain available to bounded first-party measurement whether or not you allow Google measurement.

You can avoid the assistant, use email or phone instead, and open the direct Cal.com link if the embedded calendar is blocked.

important limits

Do not send passwords, payment card details, government identifiers, medical records or other highly sensitive information through chat or a project form. The services are intended for business owners and adults, not children under 13.

You may ask to access, correct or delete information you submitted. Some information may need to be retained when required for security, legal or ordinary business recordkeeping.