Public privacy posture.

This summary outlines the website's public privacy posture, including analytics, contact forms, Zendesk conversation paths, and email fallback behavior. Client-specific data handling is defined in the appropriate project and contractual context.

Talk to CRM Scene Back to home

Last reviewed: Aug 14, 2026

Analytics use privacy-preserving consent controls for page-level performance and conversion review.

Google Analytics is enabled by default for page-level performance and conversion measurement. Visitors can disable Analytics at any time through the persistent Privacy control, and a saved opt-out remains in effect on later visits. Advertising storage, advertising user data, personalization signals, and Google Signals remain disabled. CRM Scene tracks aggregate website engagement such as page visits, CTA clicks, contact intent, form starts, form submission outcomes, and email fallback use. The site does not send raw form message bodies to analytics.

Support intake may route through the Zendesk widget, email, LinkedIn, or Help Center links.

The Zendesk widget is requested only when a visitor asks to start a Zendesk conversation. If the widget is blocked or unavailable, the page provides email and LinkedIn alternatives.

Contact forms collect the information visitors choose to submit for scoping.

Form fields are intended to route Architecture Review and implementation requests. For the AI-Ready CRM Review, CRM Scene sends the submitted contact details, score, category profile, priority actions, timeframe, context, and first-touch attribution through SmartForms to the CRM Scene inbox. CRM Scene may route that email into Zendesk through its normal inbox workflow; the website does not create a second request through the Zendesk API. The public read-only CRM Scene Knowledge service receives only configured checklist and service keys, never assessment answers or contact details. Optional marketing consent is recorded but does not create a marketing subscription. Do not submit sensitive credentials, secrets, customer records, or production data through public website forms.

Browser and server safeguards reduce accidental data exposure.

The site uses security headers, no-store API responses where appropriate, honeypot form protection, and redacted IndexNow Studio logs for keys, tokens, secrets, payloads, and pasted text.

External links leave CRM Scene's website.

LinkedIn, Zendesk Marketplace, Google Analytics, Bootstrap Studio Smart Forms, and Zendesk services apply their own privacy and security practices once visitors interact with those services.

Detailed client data handling is defined per engagement.

Project work, access, retention, subprocessors, and security obligations are governed by the relevant commercial, contractual, and operational context rather than this public website summary alone.