A clear account
of what happens
here.

Scope of this notice

This notice covers the public marketing website. It does not describe the signed-in product console or invent settings for a future provider.

Bounded first-party measurement

After consent, the browser may send one of six allowlisted events to the same-origin /api/v1/growth/events endpoint: a general page view, CTA click, pricing view, pricing interval choice, signup click, or docs view. Each event contains only its event name, a one-way visitor identifier, UTC time, an allowlisted page path, and bounded categorical properties such as CTA location, plan, or monthly versus annual pricing.

The event payload does not contain an email address, contact-form value, message, request or response body, credential, API token, full URL, query string, referrer, or raw IP address. Like every web request, network infrastructure receives a source IP while handling the connection; it is not supplied as a growth-event field. Separate security or web-server logs may process technical request data under their own access and retention controls.

One-way visitor identifier

When measurement is allowed, the same-origin consent endpoint issues a high-entropy token in a Secure, HttpOnly cookie that page JavaScript cannot read. The service returns and persists only the token’s SHA-256 digest as the visitor identifier; the browser stores that digest locally so event and deletion requests can name the same visitor. The public site does not resolve the digest to an email address or contact submission. If you later sign in to SynthCrew and explicitly allow activation measurement, the authenticated product may link that pseudonymous digest to your workspace solely to measure activation; the link is workspace-scoped, is not exposed to other visitors, and can be deleted with the visitor data. This is a pseudonymous identifier, not a claim that the request is anonymous.

Legacy analytics consent and identifier values are removed locally and are never reused or transmitted by this measurement flow. PostHog is not used by the current public-site flow.

Consent, revocation, and deletion

Declining or revoking stops new optional measurement events. The cookie and storage controls let you review the choice, revoke it, or request deletion using the one-way identifier. A deletion success is shown only after the same-origin endpoint accepts the request; a failed request leaves the one-way local identifier available for a retry. There is no numeric retention promise here: accepted deletion removes the visitor record, while infrastructure logs and backups follow their own documented controls. The local identifier is removed and the HttpOnly cookie is cleared only after the server accepts deletion. If the server does not accept it, the browser keeps the identifier so the request can be retried.

If you contact us

The access form separately sends the name, work email, optional company, and message you choose to provide to the configured SynthCrew inbox through the approved delivery path. Contact-form contents are never measurement properties. If the form is unavailable, the mailto fallback opens your configured email client. Do not send credentials, API keys, or sensitive customer data.

Optional error monitoring

If an approved Sentry DSN is configured and measurement is allowed, browser errors are sent without blocking navigation. The report uses a fixed error label plus a bounded error category, allowlisted page path, release, event identifier, and time. The original error message, stack, form contents, email addresses, URLs, request bodies, and tokens are not included. No Sentry request is made while optional measurement is declined.