Collect what the workflow needs. Avoid what it does not.
Effective September 8, 2026. This notice describes the current founding-validation product and may be updated as the service changes.
Information collected
- Business blueprint inputs such as company name, email, state, industry, company size, team/vehicle counts, operational needs, and selected current software.
- Blueprint recommendations, configuration QA results, provisioning records, and onboarding state created by the service.
- Payment and subscription status or identifiers returned by Stripe. Card details are entered with Stripe Checkout rather than the BusinessBuilt AI blueprint form.
- Basic website and funnel analytics used to understand traffic and conversion.
- Technical logs needed to diagnose failures, secure the service, and operate the product.
How information is used
Information is used to generate the requested software blueprint, determine configuration recommendations, provision Founding Access, process and reconcile payments, deliver onboarding communication, diagnose failures, protect the service, and improve the product based on real usage.
Service providers
The current product relies on third-party infrastructure including Vercel for hosting and analytics, Stripe for payment processing, Neon for application data infrastructure, and Resend for transactional onboarding email. Information is shared with those providers only as needed for the functions they perform.
Selling personal information
BusinessBuilt AI does not use the founding product to sell customer personal information to advertisers or data brokers.
Data retention
Blueprint, provisioning, payment-status, onboarding, and operational records may be retained for as long as reasonably needed to provide the service, maintain business records, resolve disputes, prevent abuse, and meet legal obligations. Retention practices may become more specific as the product moves beyond founding validation.
Data requests
Founding customers may use the support instructions provided during onboarding to request access, correction, or deletion where applicable. Some records may need to be retained for legitimate business, security, payment, or legal reasons.
Sensitive information
The blueprint is intended for business-operational inputs. Do not submit Social Security numbers, full payment-card data, protected health information, passwords, or other highly sensitive information unless a future workflow explicitly requests it and the handling requirements have been confirmed.