A clear account
of what happens
here.

Scope of this notice

This notice describes the current SynthCrew public website preview. It is written for the site as it exists today, not for a future product console or an unconfigured marketing stack.

What the site does today

The pages are static HTML, CSS, JavaScript, and local assets. The navigation script opens the mobile menu; it does not create an account or send a product action.

• The access form shows success only after the configured delivery provider accepts the request; a mailto fallback remains available.
• Measurement and error monitoring are off until an explicit analytics choice is made.
• Standard web-server logs may contain technical request data such as an IP address, user agent, requested path, and timestamp; the eventual host must document its retention and access controls.

If you request access

The access form sends your name, work email, optional company, and message to the configured SynthCrew inbox through the approved delivery provider. The reply address is the email you enter. If the form is unavailable, the mailto fallback opens your configured email client. Share only the context needed to discuss a private preview; do not send credentials, API keys, or sensitive customer data.

Mailbox ownership, retention, response-time commitments, and any CRM handoff must be configured and reviewed by the owner. This page does not invent those settings.

Provider boundaries

Google Analytics, a tag manager, CRM, support, or marketing integration is not enabled by this release. The access form delivery provider is limited to the request details needed for response. Any provider must have an updated notice, a documented purpose, a retention decision, a consent/opt-out path where required, and a verified configuration. Public IDs and private credentials must never be guessed or committed into this site.

If Sentry is enabled in a configured release, it receives only bounded browser error text, a release label, and pathname after consent; it does not receive form contents or session replay. The owner must still document project retention and alert access.