LEGAL · REVIEW REQUIRED
Privacy
This route documents the implemented privacy boundaries so the final legal notice can match the product. It is intentionally noindex until counsel reviews the final notice, retention language, vendor list, and data-subject process.
Public website measurement
Necessary site functions operate without optional analytics. Public analytics is disabled until a visitor grants analytics consent. Marketing event contracts prohibit prompts, responses, trace content, Lesson content, signal values, credentials, email addresses, and phone numbers from analytics payloads.
Authenticated Studio
Studio and authenticated product surfaces use a separate product telemetry boundary. Advertising remarketing pixels are not part of the Studio tracking policy.
Global Privacy Control
When the browser exposes Global Privacy Control, the public consent layer forces advertising consent off. Advertising scripts are not enabled in the current release regardless of that choice.
Demo and enterprise contact requests
Contact-form identity and free-text use-case details are sent only to the configured first-party durable lead ingest service. Marketing analytics receives only a first-party conversion identifier and allowlisted event metadata when analytics consent permits it. Campaign and click identifiers are retained or forwarded only under the matching consent category.
Product data, retention, and deletion
Runtime traces, evidence, Lessons, behavior revisions, audit records, and related product data follow product-specific governance rather than marketing analytics rules. The final legal notice must state the actual retention, deletion, export, and subprocessor practices used in the deployed environment.