Current preview
Inquiry submissions are validated on the server and delivered to a server-configured Slack channel over HTTPS. Webhook credentials remain private on the server. Plain-text message blocks prevent visitor text from triggering Slack mentions. Short-lived process-local submission references reduce duplicate sends. User accounts, payments, and file uploads are not enabled.
Production requirements
Before public multi-instance hosting, configure shared submission limits and idempotency, anti-bot verification, trusted proxy restrictions, Slack channel membership and retention/deletion controls, and operational monitoring. The website has no durable lead storage or automatic retry queue. A network interruption can leave Slack delivery uncertain. Private attachment handling remains a separate launch task.
No certification claims
This preview makes no security certification, audit, uptime, or regulatory compliance claim. A final security page will describe controls that are actually implemented and verified.