Data the intake workflow collects
The consultation form collects contact details, an inquiry summary, practice and office preferences, landing page, referrer, UTM parameters, and common advertising click IDs. The live demonstration is not intended for real legal requests or confidential information.
CRM delivery
Server-side validation, nonce verification, a honeypot, and rate limiting run before delivery. The webhook endpoint and token are configured only through environment variables. Failed requests are retried, and logs contain request identifiers and status codes—not form contents or personally identifiable information.
Analytics
A GTM-style dataLayer event is emitted only after confirmed delivery. It records the form identifier and delivery mode; it never includes a name, email address, telephone number, message, or other PII.
Retention and security
The mock adapter does not persist form contents. A production CRM would define access, encryption, retention, deletion, and incident-response requirements with the firm and its vendors.
Your choices
Because this is a fictional local demonstration, do not submit personal information. In a production deployment, privacy requests would use a verified workflow appropriate to the applicable jurisdiction.
Last updated August 24, 2026.