Company
Company Policy
AutoBuilder is built for serious builders. Our policies protect user trust, encourage momentum, prevent abuse, and make the product better every time users get stuck.
We optimize for builder momentum
Every product decision should answer: does this help the user move forward faster? Features should help users build, fix, deploy, learn, or launch.
Failed builds are product intelligence
A failed build is not only a support ticket. It informs prompts, templates, onboarding, diagnostics, recovery flows, docs, and roadmap.
The best support ticket is the one future users never need to submit.
We are honest about AI
AutoBuilder uses AI to accelerate execution, but AI is not magic. Output may need review, editing, testing, security checks, legal review, compliance review, and business judgment.
Our promise is not perfection. Our promise is momentum.
We do not sell fake certainty
We do not guarantee startup success, funding, revenue, legal compliance, flawless code, perfect security, app store approval, customer demand, or business viability. You still own the mission.
We protect user work
Projects, prompts, files, notes, build history, and private details are handled carefully. Aggregated patterns may improve the product; private work is not exposed publicly without permission.
We respect serious builders
Beginner-friendly and serious: clear docs, real support paths, honest limits, no dark patterns, no fake scarcity, no hidden cancellation, no pretending support exists where it does not.
Good faith
We reward good-faith users
If you are genuinely trying to build and get stuck, we help. Thoughtful feedback and real bug reports make the product better. Early serious users should feel respected.
We do not reward abuse. AutoBuilder should not support spam, scams, impersonation, malware, fraud, phishing, illegal activity, harassment, mass-generated deceptive sites, refund abuse, platform overload, or bypassing limits.
Fair use
Fair Use Policy
Clear boundaries keep the platform usable for builders who show up in good faith.
Allowed
- •Good-faith startup and product building
- •Testing ideas, MVPs, and launch plans
- •Sharing your own work when you opt in
- •Reasonable personal or team usage within plan caps
- •Reporting bugs and giving product feedback
Not allowed
- •Spam, scams, impersonation, or phishing
- •Malware, fraud, or illegal activity
- •Harassment or mass-generated deceptive sites
- •Refund abuse or bypassing usage limits
- •Platform overload or automated abuse of free tiers
Product loop
We turn support into product
Every repeated issue should become docs, an automated check, a better error message, a product fix, clearer onboarding, a template improvement, or a roadmap signal.
- ✓Docs article for recurring questions
- ✓Automated check when we can detect the failure
- ✓Clearer error message at the point of failure
- ✓Product fix when the root cause is ours
- ✓Onboarding step when users get lost early
- ✓Template improvement for common venture types
- ✓Roadmap signal when many builders hit the same wall
Scale
We build for trust before scale
Growth only matters if users believe the product helps them, billing is fair, support is real, their work is handled carefully, and the system keeps improving.
Related
More trust resources
Guarantee
Builder Momentum Guarantee
Refund Policy
Fair refund review
Company Policy
Standards and fair use
Ethos
Bill of rights and beliefs
Support
Help and build recovery
Docs
Product documentation
See also Privacy Policy and Data Use Policy. This page is product policy, not a substitute for attorney-reviewed terms.
Momentum is the product.
Read how we talk to builders in our ethos and how we handle billing fairly in our guarantee and refund policies.