Billing trust
Refund Policy
Refunds are reviewed fairly. We protect good-faith builders who were blocked from meaningful use, while also protecting the platform from abuse and heavy-usage refund exploitation.
First paid week
First-time paid user refund window
First-time paid users may request a refund within 7 days of their first paid subscription or first paid purchase.
Refunds are reviewed based on whether AutoBuilder functioned as described, whether you accessed meaningful output, whether a technical issue blocked meaningful use, how much the account was used, whether support was contacted when relevant, and whether the request appears good-faith and fair. We do not offer automatic refunds.
Usually approved
When refunds are usually approved
- ✓AutoBuilder technical issue prevented meaningful use during the first paid week
- ✓Duplicate billing or mistaken charge verified
- ✓Charged after cancellation due to a platform billing error
- ✓Paid account could not be accessed because of an AutoBuilder platform issue
- ✓Paid functionality materially did not work as described for your use case
- ✓Request within 7 days of first paid purchase with minimal usage and good-faith explanation
May be denied
When refunds may be denied
Denial is not automatic for heavy usage, but usage matters in the review.
- •Substantial usage of paid features, reports, or builds
- •Multiple projects or heavy generation before the request
- •Exported, copied, downloaded, or deployed generated work
- •Request outside the first-time paid refund window without ongoing platform fault
- •Violation of acceptable use or fair use rules
- •Spam, scams, illegal content, phishing, malware, or harmful use
- •Changed mind after receiving meaningful value from paid features
- •Repeated subscribe-use-refund behavior
- •Issues caused primarily by third-party services
- •Refusal to provide reasonable details for investigation
Usage
Heavy usage policy
AutoBuilder can involve compute, generation, analysis, code production, and build assistance. Substantial usage does not automatically deny a refund, but it matters in the review.
Examples of substantial usage:
- •Creating many projects or ventures in a short period
- •Generating multiple full apps or deep report packs
- •Repeatedly using build, recovery, or repo-aware tools
- •Exporting or deploying generated work before requesting a refund
- •Using paid tiers heavily then requesting a full refund
Recovery first
Build recovery before refund
Technical refund requests may first be offered build recovery.
Build recovery can include identifying likely build errors, explaining missing environment variables (never share secrets in tickets), helping with deployment blockers, reviewing generated output quality, recommending a rebuild path, and guiding toward a launch-ready version when possible.
Diagnose the issue
Understand what broke, when, and what you were trying to ship.
Identify likely cause
Scope, limits, environment, intake quality, or product gap.
Recommend fix or rebuild
Concrete path: edit, retry, smaller slice, or different mode.
Retry or recover
Recover the project when possible instead of closing the loop.
Log the pattern
Anonymized patterns help future builders hit fewer blockers.
Improve future builds
Product, prompts, and docs get sharper from real failures.
Credits
Account credits
Sometimes credits are a better outcome than a refund.
Extra days of access
When an outage or issue cut into your paid period.
Plan credit
Applied to renewal or upgrade when fair.
Build credit
For another build or recovery attempt.
Recovery credit
After a failed build that can still be salvaged.
Discounted upgrade credit
When you want to keep building after a rough start.
Subscriptions
Subscription cancellation
You can cancel before the next billing cycle. Cancellation stops future renewals but does not automatically refund previous charges. You may keep access until the end of the paid billing period unless your plan terms say otherwise.
Annual
Annual plans
Annual plan refund requests are reviewed case by case. Refunds may be considered if the request is shortly after purchase, usage is limited, or AutoBuilder failed to provide material paid functionality. Outcomes may include prorated refund, credit, or denial depending on usage and circumstances.
Services
One-time services and launch assist
One-time services, setup work, launch assistance, custom reviews, implementation work, or founder support packages are generally non-refundable once work has started. If AutoBuilder or Noaerth cannot reasonably deliver the agreed service, the situation may be reviewed for partial refund, credit, replacement support, or revised scope.
Request
How to request a refund review
Better details lead to faster, fairer reviews.
- 1.Account email
- 2.Plan name
- 3.Purchase date
- 4.Project or venture name
- 5.What you expected
- 6.What happened instead
- 7.Screenshots or logs (redact secrets)
- 8.Whether the issue blocked launch or meaningful progress
Related