Code ownership and lock-in
Botflow repeatedly emphasizes that users own the generated code and can push projects to GitHub. Its product comparisons also say a user can connect an independent Convex account, reducing dependence on a proprietary Botflow-only backend.125
Those are meaningful design choices for a young platform. If Botflow changes pricing, pivots or disappears, standard source code in Git and a backend account controlled by the user are more recoverable than a project that exists only inside a closed builder.
This does not mean migration is frictionless. Generated applications can still depend on Convex APIs, Botflow-specific build assumptions or third-party authentication/deployment services. “You own the code” should be understood as a strong portability signal, not a guarantee that another developer can move the whole application with zero work.
Privacy and data handling
Botflow's privacy policy is effective May 2, 2026 and identifies the operator as Botflow LLC in North Carolina. It says account authentication is handled by Clerk; project files, code, configuration and metadata are stored in a PostgreSQL database hosted on Neon; uploads are handled through UploadThing; and GitHub OAuth tokens are stored to perform requested Git operations.6
AI features can send relevant code or conversation content to OpenAI, Anthropic or Fireworks AI depending on the model used. Botflow explicitly directs users to those providers' own privacy policies for provider-side handling.6
The policy says Botflow does not sell personal information and does not use project code to train AI models without explicit consent. Account and project data are retained while the account remains active; after account deletion, Botflow says it will delete or anonymize personal data within 90 days except where legal or compliance retention applies.6
For security, Botflow says it uses TLS for data in transit and access controls for data at rest. It does not, in the material reviewed here, advertise the extensive certification portfolio typical of mature enterprise vendors. Buyers handling regulated or highly sensitive source code should therefore evaluate the underlying provider terms and their own compliance requirements rather than inferring enterprise certification from general security language.6
There is also an infrastructure distinction worth preserving. The privacy policy describes Botflow's own platform storage/hosting subprocessors, including Neon, UploadThing and Vercel, while generated applications are marketed with Convex backends and Cloudflare publishing. These are different layers of the stack, not a contradiction.621
Security: thoughtful defaults are not the same as an audit
Botflow publishes extensively about security risks in AI-generated software and argues that typed backend functions, isolated environments, Git history and scoped credentials reduce common failure modes. Its own material says GitHub is connected through scoped OAuth and that secrets are encrypted.41
The architecture has sensible properties. Keeping database logic behind server functions can reduce some classes of accidental direct-client database exposure, and maintaining real Git history is plainly useful when an AI change breaks a project.25
External validation and company maturity
This is currently Botflow's weakest evidence category.
Beyond current public evidence, the founder's public profile describes OpenVibeCode/Botflow as a recent project and documents the earlier chatbot version of Botflow as a separate pre-pivot product.7 The Botflow company LinkedIn page currently identifies one employee and a very small follower base while announcing a Product Hunt launch.8
These details are useful primarily as maturity context. They mean users should expect a startup-stage product: potentially fast iteration and direct founder involvement, but also higher continuity and support concentration risk than a large established development platform.