Inquiry data should stay useful and limited.
This page describes the public site’s current inquiry and analytics flow. It is not a substitute for a project-specific data-processing agreement or other written terms.
What we collect and why
CategoryDataUse
Inquiry detailsName, work email, company, phone, project message, and optional planning details that you submit.To acknowledge, review, and respond to a consultation request.
Site activityInternal page paths, referrer origins, bounded campaign parameters, and allowlisted interaction events.To understand site use and acquisition performance. Full query strings, inquiry free text, contact details, calculator inputs, and arbitrary event payloads are not sent in public analytics events or retained in lead attribution.
Operational deliveryA submitted inquiry may create an internal notification, a domain enrichment request, and an AI-assisted internal lead-analysis task.To route and prepare for the inquiry.
Where an accepted inquiry goes
ProcessorPurpose
Stack Renew administration serviceStores accepted inquiry records and their delivery status.
Google Analytics and Meta PixelReceive bounded site-activity events when their respective analytics tags are enabled.
Slack or TelegramMay receive an internal new-inquiry notification when configured.
FirecrawlMay receive a business domain plus available name or company context for lead enrichment; it is not sent the inquiry message.
Configured AI lead-analysis providerMay receive inquiry contact details and message content for internal lead analysis when that internal task is enabled.
Retention and deletion
Accepted inquiry records remain in the Stack Renew administration system until an authorized operator removes them. To request access, correction, or deletion of an inquiry, email [email protected] from the address used in the request. We will confirm any required identity or legal-retention checks before acting.