Privacy policy
This starter privacy page describes the data flows in this static BotConsent implementation. Review it before production launch.
Information collected
BotConsent forms may collect domain names, work email addresses, role selections, domain counts, audit notes, pricing requests, and other information you choose to submit.
Generated policy data
The free generator runs in your browser. The current static implementation stores the captured email locally in the browser so exports can proceed after capture. A production implementation may send form submissions to CRM, email, payment, or database systems.
Analytics events
The site emits events such as generator_started, email_captured, policy_exported, audit_clicked, checkout_started, and plan_selected to window.dataLayer. Connect those events to your analytics provider only after updating this policy to name that provider.
Payments
Pricing and audit buttons open Stripe checkout. Stripe may process payment details, billing information, fraud-prevention signals, and payment confirmations under its own terms and privacy policy.
How information is used
Submitted information may be used to provide generated policy exports, respond to audit or pricing inquiries, create checkout sessions, deliver hosted policy pages, send monitoring alerts, and improve product workflows.
Sharing
BotConsent should not sell personal information. Production integrations may share necessary information with service providers such as CRM, email, hosting, analytics, monitoring, and payment vendors.
Retention
Retention periods should be configured in the connected CRM, database, and analytics tools before production launch. Remove data when it is no longer needed for support, billing, compliance, or product operations.
Contact
Connect this page to the correct privacy contact or support inbox before production launch.