How contact information is handled.

AI Business Services uses contact form information to review and respond to requests for workflow, automation, reporting, custom-tool, and practical AI support. The MVP lead path is intentionally limited: it captures the request, records consent, blocks obvious spam, and supports internal follow-up.

Information Collected

Name, business name, email address, phone number, and business context submitted through a form.
Workflow, tool, team-size, industry, and request details provided so the request can be reviewed.
Consent status, consent timestamp, form source, page URL, storage status, and notification status for auditability.

How It Is Used

Respond to the request and decide the smallest useful next step.
Route the lead into the approved storage path and required internal email backup notification.
Troubleshoot failed submissions, spam rejections, and staging tests without exposing private form details in public logs.

Storage And Notifications

Lead storage follows the approved project order: Supabase only if ready, Firestore if available, controlled Sheet fallback if no database path is ready, and internal email backup notification for every valid lead. Service-role keys, Firebase admin credentials, and private customer data must not be exposed in browser code.

AI And Automation Boundary

Public lead forms do not send customer-facing AI responses. Any future AI lead summary must be internal-only by default, configurable, budget-controlled, and able to fall back to manual review if AI is unavailable.